Colophon

+ 01

Construction

Every page is prepared in advance, as HTML, by Astro, from strictly checked TypeScript code. JavaScript is limited to the Verity demo, a few interactions on the home page and, on every page, a few lines that check whether the browser can draw the glass effect. The site is hosted on Cloudflare Pages and published on every merge into the main branch.

The fonts, Inter, Source Serif and JetBrains Mono, are hosted with the site and cut down to the characters it displays. No tracker, no form. Every figure shown for a project comes from a file published in its repository, at a precise commit, and CI compares it with its source on every change.

Site code

+ 02

Budgets

CI fails as soon as a page exceeds one of these thresholds, measured by Lighthouse on a simulated phone:

Weight transferred by a page

at most 200 kB

Fonts of a page

at most 90 kB

Largest Contentful Paint (LCP)

under 1.5 s

Cumulative Layout Shift (CLS)

under 0.02

Lighthouse scores, in all four categories

at least 98 out of 100

Weight is counted gzip-compressed, a little heavier than what Cloudflare actually sends: the budget is therefore stricter than what the reader receives. Thresholds: lighthouserc.cjs.

+ 03

Real measures

What CI measured on 6 November 2026, on commit b328dbf: median of 5 Lighthouse runs per page (CI run).

+ 04

Accessibility

• Text colours are checked against their background by a test: AA contrast, in light and dark mode.
• The site can be browsed with the keyboard, with a visible focus and a link to skip to the content.
• The site follows the system settings: dark mode, reduced motion, reduced transparency.
• On every change, axe checks every page in light and dark mode, and a test checks that the fonts can draw every character displayed.

+ 05

Agents and review

The code, the tests and the first drafts of the texts are written by coding agents (Claude Code), under rules written in the repository: a failing test before every fix, no figure without a source, no success announced without the command that proves it (agent rules).

Every change goes through an independent review (a second agent, without the first one’s context), then I read the report and the preview, with the help of an AI assistant, before merging it myself. I am the only one who merges into the main branch, which GitHub rules protect. What the machine checks better than I do, it checks every time: budgets, accessibility, links, and every figure compared with its source.