Website Meta
How this website is made
A website is a set of decisions wearing a nice coat. These are ours — the stack, the palette, the type, and the reasons we chose them. Nothing private here: no keys, no server names, just the thinking. Steal what is useful.
The stack
Six decisions, top to bottom. None of them are unusual on their own; together they mean there is almost nothing to maintain.
- Framework
- Astro 7. It writes HTML and hands each page to a Cloudflare Worker.
- Host
- One Worker, one custom domain. There is no server for us to patch.
- Rendering
- Every page is baked once at build time and served as a finished file from Cloudflare. Publishing a change means deploying it — there is no database reading itself at request time.
- Storage
- None. No SQL database, no object store, no cache namespace, no scheduled job. The site keeps no data of its own.
- Browser
- No client framework, no hydration. A few lines of plain JavaScript open the menus; everything else is HTML and CSS.
- Words
- Atlas, the internal app where we run the studio. This site is a read-only projection of it.
The source
Atlas holds the services, the audiences, the writing, the partners — and the small strings most sites bury in a template: the footer tagline, the column heads, the contact address. The site reads them from a read-only API, and only rows we have marked for publication.
Every page is then generated once, at build time, and served as a finished file. An edit in Atlas appears on the site when we deploy — a minute or two after we decide it should. That delay is deliberate: nothing goes live by accident, and a draft stays a draft. An unpublished row never arrives at all, because the gate sits at the source, not in the template.
Two guards keep that honest. One stops the build if any route reaches for an internal collection — our worldview notes, position papers, content ideas. The other scans the build output for the same material. If a private note ever leaked into a page, the deploy would fail before anyone could see it.
The colour
The palette comes from a Mindful Palettes set we catalogued as MP132. Six colours, each with a job rather than a mood.
- Royal Gold
- Deep Ocean
- Floral White
- Vibrant Coral
- Rebecca Purple
- Coffee Bean
Two rules turn a list of colours into a system. Colour is assigned by role, never by eye: a link is brand teal on a light page, and on the dark footer the same teal measures 3.8:1 — so links there turn gold instead. If a link looks wrong, the fix is a role, not a hue.
The grounds are never flat. Every page wash is a soft mesh, diluted with transparency over warm off-white, then covered by a film grain that hides the banding an 8-bit gradient leaves behind. Measured, not assumed: gold on coffee-bean holds about 10.5:1, floral-white on deep-ocean about 7.2:1. Both clear AAA for body text.
The type
Lora headings
A serif with a real 700 weight. That detail replaced an earlier face that shipped one weight only, which meant every browser invented its own bold — so Firefox and Chrome drew what looked like two different typefaces.
Commissioner body copy
A humanist sans with flared stems: enough voice to sit beside the serif without arguing with it. It also carries the Greek subset, so the site can speak Greek later without a face swap.
One scale drives every heading and two ratios keep the order clear: √2 between the display levels, 1.10 between the interface levels. The h1 is pinned at 68.7px and the rest derive from it. Body text is a single dial — 16px on a phone, 18px on a large screen — and supporting text is sized in em, so it steps with the body instead of shrinking beside it.
The layout
Header, main and footer share one sheet — 1344px wide. Nothing shifts sideways when you move between pages. Prose inside it is held to about 70 characters a line and centred, because a narrow column hugging one edge of a wide screen reads as a bug, not as taste.
There are no cards here. No rounded panels, no soft shadows, no boxes. One hairline, a numeral and the type do all the grouping. A tinted card with a shadow is the quickest way to make an editorial page look like a template with your logo in it.
The washes have names. Every gradient in the system is catalogued against a real star — Electra, Fomalhaut, Mizar — one hundred and seven of them. Our services ground is Unukalhai. The naming is a memory aid: the catalogue tells you which two colours a ground is made of without opening a stylesheet.
The footer has its own weather. The page darkens before the footer arrives — up to 32rem of smoke — and the grain is masked by the same curve as the darkness, so it can never begin before the dark does. A handful of stars arrive with it. Light pages get none: stars only make sense in the dark.
The build
A design system decays when nobody checks it. So the check runs at build time, before anything ships.
One scale, no exceptions
Every spacing value, font size, radius and duration in every component is compared against the scale read from the stylesheet itself. A 13px gap fails the build. So does a raw hex or a hand-picked 0.2s.
Three breakpoints
The site allows 40, 56 and 68rem and nothing else. A fourth tier is a local invention, so the build rejects it and asks for a tier that already exists.
A ratchet, not a target
The gate keeps a baseline of known violations. It may shrink. It may never grow, so yesterday’s exception cannot quietly become tomorrow’s standard.
The gate also reports tokens that nothing reads. A variable declared and never used is documentation pretending to be code, and saying so out loud is the only way to keep the two honest.
Deploying is the boring part, which is the point: push to the branch, a GitHub Action builds on Node 22, Wrangler ships the Worker. Two minutes, usually less. This page has a public build stamp if you want to know when it last ran —build-info.json.
The policy
The robots file states a position rather than a preference. Search engines may index us. AI systems may read our pages and use them to answer a question. Nobody may train a model on the work. One line says all of it:
Content-Signal: ai-train=no, ai-input=yes, search=yes
The plain-language version of the same policy lives at /llms.txt.
There is no analytics script, no advertising pixel, no chat widget and no pop-up. If we cannot learn something without watching a person, we do without it.