terminal/site

site

The download page for Terminal. It is one static page built with SvelteKit for Vercel, plus a /download route that redirects to the latest release DMG and saves the email visitors give before downloading.

This folder is its own npm project, separate from the Cargo workspace. Run the commands below from site/, and set the Vercel project's Root Directory to site. It needs Node 22.17 or later, the minimum SvelteKit supports; .npmrc turns on engine-strict, so npm install stops on older versions.

cd site
npm install
npm run dev       # http://localhost:5173
npm run build     # Vercel output in .vercel/output
npm run preview   # serve the production build on http://localhost:4173
npm run check

How it fits together

• src/routes/+page.svelte is the page. It is prerendered and then hydrated, because the demo and the feature cards animate in the browser. Without JavaScript the page still reads: the demo shows the app window and every section is visible.
• src/lib/demo/ is the hero demo. script.ts holds the 20-second timeline: when each command is typed, the camera moves, the captions and the sound cues. Scene.svelte draws one frame for a given time over the app screenshot, player.svelte.ts advances the time, and sound.ts synthesizes the sounds with the Web Audio API, so there are no audio files. The demo plays muted on a loop while it is on screen; "Play with sound" restarts it once with sound.
• src/lib/cards/ holds the feature card animations. Each one loops only while it is on screen.
• With reduced motion, the demo and cards hold one still frame and nothing fades in on scroll.
• The theme button in the nav switches the page, the demo and the cards between dark and light, and remembers the choice. Dark is the default. The page colors are in src/app.css, including the app's own Terminal Dark and Terminal Light colors under .app.
• src/lib/site.ts holds the version, architecture, minimum macOS, site URL and download URL, plus the name, title and description used by the page's metadata. Update it with each release. static/robots.txt and static/sitemap.xml repeat the site URL.
• src/routes/download/+server.ts answers GET /download with a 302 to https://github.com/michaelshimeles/terminal/releases/latest/download/Terminal.dmg. That URL works only once a GitHub release includes an asset named exactly Terminal.dmg.
• The download buttons open src/lib/DownloadDialog.svelte, which asks for an email, sends it to POST /download, then starts the download with GET /download. The browser remembers that it gave an email, so later downloads skip the dialog. If saving fails or takes more than 3 seconds, the download starts anyway. Without JavaScript the buttons link straight to /download.

Wallet sign-in (/wallet/)

src/routes/wallet/ is where Terminal users create or open their built-in Hyperliquid testnet wallet (design: docs/architecture/trading-hyperliquid.md §4.5). The desktop app opens it in the system browser and the web app in a popup. The page signs the user in with an email code or a passkey through Turnkey's Auth Proxy (@turnkey/core). It then asks Turnkey for a 15-minute session bound to the app's own key, hands that back, and logs out. In export mode (#mode=export) it shows the recovery phrase in Turnkey's export iframe instead.

It reads two public build-time variables, which are identifiers and not secrets:

• VITE_TURNKEY_ORGANIZATION_ID: the parent Turnkey organization.
• VITE_TURNKEY_AUTH_PROXY_CONFIG_ID: the Auth Proxy configuration.

Set them in the Vercel project's environment variables; the deploy workflow's vercel pull brings them into the build. Without them the page only says that wallet sign-in isn't set up. No server route holds a Turnkey key: the Auth Proxy creates each user's sub-organization with a key Turnkey keeps. VITE_TURNKEY_API_BASE_URL and VITE_TURNKEY_AUTH_PROXY_URL point the SDK elsewhere (a local stand-in); leave them unset in production.

Deploys

GitHub Actions deploys the site, not Vercel's Git integration, because the browser app at /app is built from Rust and Vercel's build doesn't run Rust. .github/workflows/deploy-site.yml runs scripts/build-web.sh, then vercel build and vercel deploy --prebuilt from the repository root. Pushes to master deploy to production. Pull requests from branches in this repository get a preview, linked from the pull request; pull requests from forks only build the app. vercel.json turns off Vercel's own Git deployments, so each commit deploys once.

The workflow reads three repository secrets:

• VERCEL_TOKEN: a Vercel access token (Account Settings › Tokens) scoped to the goshen-labs team.
• VERCEL_ORG_ID and VERCEL_PROJECT_ID: orgId and projectId from .vercel/project.json, which vercel link --scope goshen-labs --project terminal writes.

To redeploy without a new commit, run the workflow from the Actions tab. Run on master, it deploys to production.

vercel.json also routes the browser app. /app redirects once to /app/, which serves static/app/index.html without a redirect, so the page's relative URLs resolve under /app/. scripts/build-web.sh puts each build's JS and wasm in static/app/immutable/<hash>/, named after a hash of those files, and the browser caches everything under /app/immutable/ for a year. A new build gets new URLs, so a page never loads one build's JS with another build's wasm. index.html and the fonts keep Vercel's default max-age=0, must-revalidate, so the browser checks them on every visit. A request under /app/immutable/ for a file that doesn't exist gets a 404 with no-store, so that year-long header never sticks to a 404. vercel.json uses routes rather than headers and rewrites because only routes can add that rule after the filesystem check, the same way the SvelteKit adapter guards /_app/immutable/. npm run dev doesn't apply vercel.json; open /app/index.html there.

Emails

POST /download adds each email to the emails sorted set in Upstash Redis, scored by when the address was first given in milliseconds since the epoch. It reads KV_REST_API_URL and KV_REST_API_TOKEN, declared in src/env.ts. Without them the site still builds and serves downloads, but every save fails and logs an error.

To set them up, add Upstash for Redis to the Vercel project, which connects the database and sets both variables:

vercel link --scope goshen-labs --project terminal
vercel integration add upstash/upstash-kv --name terminal-emails
vercel env pull .env.local    # for npm run dev

To list the emails, oldest first, with the read-only token the integration also sets:

set -a; . ./.env.local; set +a
curl -H "Authorization: Bearer $KV_REST_API_READ_ONLY_TOKEN" "$KV_REST_API_URL/zrange/emails/0/-1"

Images

assets-src/ holds the sources: two 3200x1920 window captures of the app (hero-dark.png and hero-light.png), the icon (icon.svg) and the Open Graph card template (og.html). scripts/build-images.sh regenerates everything in static/ from them: the two captures as full-size WebP for the demo (it zooms into the chart, so they stay at 3200 px), the icon, favicons, the touch icon and og.jpg. It needs ImageMagick, cwebp, and Google Chrome or Chromium. The script finds google-chrome, google-chrome-stable, chromium or chromium-browser on your PATH, then Chrome in /Applications. To use another browser, set CHROME to its path or command name, such as CHROME=brave-browser.

./scripts/build-images.sh

The icon is the candlestick mark from src/lib/Logo.svelte. The app bundle doesn't ship an icon yet; if it gets one, update both.