Colophon
How this site is built
You found the page for people who view source. Welcome — this one's for you, and it's allowed to use the technical words the rest of the site politely avoids.
The premise
If someone is selling software competence, their website is the first work sample. So this site is built the way I'd build for a client: boring, fast, durable, and owned outright.
The particulars
- Static HTML, generated by Astro. Zero framework runtime ships to your phone. The JavaScript on most pages is one console message.
- System fonts. The typography budget went to typographic care — tabular numerals on every figure — instead of font downloads.
- A byte budget enforced by CI. The homepage's first load must fit in 100KB compressed (HTML ≤15, CSS ≤15, JS ≤15, photo ≤30), with LCP under one second on a throttled mid-range phone and zero layout shift. The build fails if a change breaks any of that — the budget is merge-blocking, not aspirational.
- A banned-words check, also merge-blocking. Template-speak and jargon are kept out of the copy by the same CI that guards the bytes.
- No servers, no databases, no API keys. The demos are self-contained client-side bundles, capped at 250KB each, loaded only when you tap them, running on seeded sample data with relative dates. The site has nothing to babysit and nothing that expires — it should work identically if nobody touches it for a year.
- No tracking. No analytics scripts, no cookies, no third-party requests. Not one.
- Hosting: a global CDN's free tier, in my own account — the same own-your-accounts arrangement the exit plan promises clients.
Why it looks like this
Warm paper, near-black ink, one accent red, hairline rules: a machinist's drawing crossed
with a ledger. Real photography only, no stock images, no decorative icon grids. Animations
are rare, short, and honor prefers-reduced-motion. Prices never animate —
numbers that dance are numbers you shouldn't trust.