Brand system · unlisted
What this site is made of.
Every specimen here renders the shipped component, not a picture of one, and the token page reads globals.css at build time. A design system that keeps its own copy of itself goes wrong quietly, in the documentation, which is the worst place for it.
Reachable from the footer and by URL. Not in the header.
Marks
PixelRack, the one canvas component behind the favicon, the nav mark, the plugin badges and the hero. Every device, every size, every behaviour.
Devices · Accents · Sizes · Dissolve modes · still and once · fluid · Props
Primitives
The small site-level helpers: the fading rule, the theme toggle, and the class idioms that carry every card, label and link on the site.
Hairline · ThemeToggle · .label · Card surfaces · Link idioms · Entrance
Skeleton
The shared JUCE layer the instruments are built from: one palette, one LookAndFeel, and the blocks a plugin gets assembled out of. The plugin-side half of the same design system.
Blocks · Chassis · Accents · Using it
Tokens
The palette as swatches, read out of globals.css at build time so this page cannot drift from the stylesheet. Surfaces, lines, text, and the five accents.
Surfaces · Lines · Text · Accents · Radius
01
akaSTYLE
The same design language as akaOSS: mono for structure and sans for prose, uppercase mono kickers labelling every section, depth from a 1px border and a translucent fill rather than a shadow, and motion that translates and displaces rather than flashing.
Everything is greyscale on a warm near-black ground. Each instrument owns exactly one accent and spends it inside its own mark. Light and dark are both real themes; press D to flip.
02
Server-first
Next.js App Router with Tailwind v4 and the shadcn token conventions. Every page and every section is a Server Component. The client boundary is drawn as deep in the tree as it goes: the theme provider, the theme toggle and the canvas mark, and nothing else.
The site reads no environment variables and calls no APIs. Every route is static.
03
Facts come from the plugins
Versions, formats, plugin codes and platform support are read out of each instrument’s own CMakeLists and committed as JSON, so the site cannot drift from the builds. Where a README and a build disagree, the build wins: i4’s README claims a universal binary, its CMakeLists does not configure one, and these pages say Apple Silicon.
Prose stays hand-written. Only things with a single correct answer are generated.
04
One canvas engine
Every mark is PixelRack, built on the same grammar as akaOSS’s PixelHead: a deterministic hash PRNG, one sampled cell set, an assemble-and-hold timeline, colour resolved from the theme and repainted when the theme flips.
What is its own is that each instrument gets a device whose idle motion is what that instrument actually does, and that all geometry is laid out in whole cells, so the same component reads correctly at 26px in the nav and 360px in a hero.
The plugin repositories are proprietary and each carries its own licence. The plugins themselves are not yet code-signed or notarised, which is why nothing here offers a download.