How this site is put together.

Every post is a markdown file in a folder in a git repository. Astro renders those files to static HTML at build time, the output goes to a CDN, and nothing on the page waits for a server to think. A build takes eleven seconds, which is short enough that I never talk myself out of fixing a typo.

Type

A serif for the argument, a mono for the evidence

Headlines and captions are set in Instrument Serif, which has the narrow, slightly editorial feel I wanted without costing much to load. Body copy is Archivo. Everything factual — dates, tags, file names, benchmark output — is Chivo Mono, so the eye can tell an assertion from a measurement before reading either.

Code and figures

Highlighted at build, never in the browser

Shiki highlights every snippet during the build, so the page ships plain coloured HTML with no highlighter to download and no flash of unstyled code. Diagrams are SVG exported from the notebook that produced the numbers, and screenshots sit on a dark plaque so a light interface shot does not blow a hole in the page.

What runs in your browser

Two small scripts, and that is the whole list

An intersection observer marks your place in the table of contents, and a click handler copies code blocks to the clipboard. There is no analytics, no tag manager, no consent banner, and no font loaded from a third party. Server logs are kept for a week to tell me which posts get read, and they record no addresses.

NOTE The whole thing is open source, including the posts. If a page renders badly for you, the fix is a pull request away and I will take it.