Torrenta website

The marketing + documentation site for Torrenta, a keyboard-first, cross-platform BitTorrent client. Live at torrenta-project.dev (www. redirects to it).

The site is served at the domain's root, so its Astro base (src/lib/site.ts) is "/". It was a GitHub Pages project site under /torrenta-website/ before, and the plumbing stays: templates build every internal link and asset with href() from that file, Markdown is written with plain root-relative links (/docs/search) and a rehype plugin in astro.config.mjs puts them under the base. Moving again: site and base in src/lib/site.ts, the host in public/CNAME, public/robots.txt and the social cards (scripts/gen-images.mjs, then --force), and the custom domain under the repository's Settings → Pages. The DNS is Cloudflare's, DNS only (no proxy): the apex has GitHub Pages' four A and four AAAA records, www a CNAME to adriandeleon.github.io.

Built with Astro and deployed to GitHub Pages via .github/workflows/pages.yml on every push to master. The stack, the layout and the look are Editora's site's, ported: the same components (the Pagefind search modal, the page index rail, the palette demo), the same page shapes, the same lockfile, with Torrenta's themes in place of Editora's.

Torrenta is built with the help of AI coding tools.

Develop

npm install
npm run dev       # http://localhost:4321/
npm run build     # production build to dist/
npm run preview   # serve the build (site search only works here, after a build)

Content

Most content is Markdown under src/content/:

• docs/ — documentation pages (sidebar grouped by category + order; introduction is /docs)
• blog/ — blog posts
• news/ — release-style announcements
• features/ — one page per feature (also drives the home-page grid; summary is HTML)

Add a Markdown file with the right frontmatter and it appears automatically; lists, the sitemap and RSS regenerate on the next build.

Feature screenshots go in public/screenshots/features/<slug>.png (the slug matches the page URL, e.g. /features/search → search.png); without one the card and the page show a placeholder. The app's capture hook makes them (scripts/dev-run.sh -Dtorrenta.capture=… in the Torrenta repository; its CLAUDE.md lists the actions, such as view:search or detail:overview).

Themes

The site's palettes are the app's six themes, so the picker in the header recolours the site the way Settings → General → Appearance recolours the app: Editora Dark (the default, "Caret & Ink") and Light from the app's own editora-*.css, Nord and Cupertino from AtlantaFX 3.0, which the app uses as they are. They are CSS variables at the top of src/layouts/Layout.astro; the names are Editora's site's (--bg, --accent, …) plus the app's state colours (--done, --warn, --error, --up).

Generated data

npm run build first runs scripts/gen-images.mjs: the favicon and touch icons from public/torrenta-icon.svg (a copy of the app's branding/torrenta-icon.svg), a social card per key page in public/og/, and a WebP beside every PNG screenshot. Outputs are kept unless their source is newer; --force rebuilds them.

src/lib/commands.ts (the Keybindings page, the home page's keys, the palette demo) and src/lib/version.ts are generated by scripts/GenCommands.java from Torrenta's source: the Command records in MainWindow.buildCommands(), their labels in messages.properties, their chords in ui.Chords, and the pom's version (the newest released CHANGELOG section while the pom is on a -SNAPSHOT). It is a JDK 25 compact source file (JEP 512), run with java, no build step, from the repo root:

java scripts/GenCommands.java                 # ../torrenta
java scripts/GenCommands.java /path/to/torrenta

or TORRENTA_REPO. Which group a command is listed under is a table in the script, because the menus are built from helpers the context menu shares; a command missing from it is listed under "Other" and reported, and two commands on one chord are reported too. The output is committed, so the site build needs no access to the Torrenta repository (it isn't checked out in CI). Re-run it after a release, or after a command or a chord changes.

src/lib/whatsnew.ts (the home "What's new" block) is hand-written: a handful of highlights from the current release's news post. Update it with each release.

Not ported (yet)

Editora's site has versioned docs (/docs/v-<version>/…, archived copies per release), a generated roadmap, per-command pages and a comparison page. Torrenta's docs are unversioned because nothing in the app links into them yet; when it does, port Editora's routes and archive layout rather than inventing another scheme. Cloudflare Web Analytics is left out until the domain has its own token.