Who tunaos.org is for, what we want each of those people to do, and the site
rules that follow from that. This is the reference for changes to
src/pages/, src/components/ and the nav; the visual language itself
(Vesper dark base, one blue accent, JetBrains Mono, borderless panels on a 6px
radius, no gradients, no emoji) lives in src/css/custom.css and
src/css/page.module.css.
Five people arrive here. Each has exactly one thing the site wants them to do next, and each of those actions is reachable from the front page in one click.
| # | Who | What they want | Primary CTA | Where it goes |
|---|---|---|---|---|
| 1 | On Windows, curious about Linux. Has one machine and cannot repartition it. | To try Linux without risking the machine | Try from Windows | /wootc |
| 2 | Wants a desktop Linux to install. Comparing distributions, or wants a long-support desktop. | A bootable ISO for their hardware | Download | /download |
| 3 | Already runs bootc (Universal Blue, Bluefin, Fedora Atomic). | A one-line move to a TunaOS image | Rebase (bootc-migrate --target-image …) |
/download, docs |
| 4 | On some other distribution, wants the apps. Does not care about the OS. | The office suite, terminal, file manager | Flatpaks | /flatpak |
| 5 | Builder or contributor. | The tooling and where the code is | Build an ISO / Docs / GitHub | /iso-builder, /docs, GitHub |
Persona 1 is the one the site used to serve worst: wootc is the most distinctive thing the org ships and had no page at all. It is now the first CTA in the hero and has its own landing page.
-
One click from the front page to every primary CTA. The hero carries personas 1-3; the nav bar carries 2, 4 and 5. If a CTA needs a second hop, the front page is wrong.
-
Lead with the path, not the product. People choose how to install (from Windows, from a USB stick, by rebasing, in a VM) before they choose which image. The "Ways to install" band comes before the image lineup.
-
Four images, not fourteen. Albacore, Yellowfin, Skipjack and Bonito are the images we ask people to choose between. The other bases (Ubuntu, Arch, Debian, openSUSE, Gentoo, RHEL, and the rolling siblings) are real, but they are for people who came looking for them: they live on
/variantsand in the build matrix, not in the nav bar, the footer, or the docs sidebar. Their pages still exist and their URLs still work. -
Name things plainly. No pitch copy, no "blazing fast", no exclamation points. Say what a thing is and what it runs on.
-
No emoji in the interface. Each variant carries its mark from tuna-os/branding — vendored into
static/img/marks/, mapped insrc/data/marks.ts, and verified against the branding manifest byscripts/check-branding-marks.test.mjs. Each project carries a glyph fromsrc/components/Icon.tsx, named in itssrc/data/projects.tsentry. Those marks are where a variant or project gets to look like itself; the interface around them stays one hue. Emoji survive only where they are content (a project's own docs, synced from its repository). -
Every list on the site derives from
src/data/. The nav, the footer, the matrix, the picker and the landing pages read the same arrays. A hand-maintained second copy is how images went missing from menus before. -
Build state is read, never written. What has shipped — which ISOs exist, how big they are, when they were built — comes from the release bucket's own index (
static/iso-index.json, refreshed byupdate-iso-index.yml) throughuseIsoIndex./matrixrenders the shape of things fromsrc/data/immediately and the live state on arrival, and says "built; live ISO state loads with the index" in between rather than asserting something it cannot yet know. Never hand-write a build status into the site: it would be wrong within a day and nobody would notice. -
bootc-migrate is the smarter
bootc switch. Anywhere the site tells someone to move to another image (another base, desktop or project), it showsbootc-migrate --target-image …and links/docs/bootc-migrate. It takes the same target asbootc switch, checks it first, and carries/home,/varand/etcacross. Plainbootc switchstays only where it is the whole job: pinning a digest, or updating your own derived image.
The site is audited with axe-core (WCAG 2.2 A and AA rules) against the built
output; npm run a11y runs it over the pages people actually land on. Keep it
at zero violations — the checks that matter most here are contrast on the dark
panels, a visible focus ring on every control, and real button/label semantics
in the image picker and the carousels.
The visual direction is by @HuntedRaven7 (website remake, #380). It is credited in the site footer.