This site is a small, slightly over-engineered publishing setup that exists because I wanted to write about software without pretending it always behaves like the diagram.
Type is set in a system font stack: whatever your device already uses for UI text. No custom webfonts, no performance lecture required.
Most of the code lives on GitHub. It's maintained by one person, which explains both the consistency and the occasional classic-editor paragraph block that collapses into a single immovable lump.
Built and written by Christian King. Questions, corrections, or stories about software that 'mostly works' are welcome.
Energy
I try to keep this site light: system fonts instead of webfont downloads, a single stylesheet, no third-party trackers, and no decorative animations chewing through your battery for no reason.
According to the Website Carbon Calculator, this site currently scores A+, at less than 0.01g of CO2 per page view (last checked 2 June 2026). The internet still uses a lot of electricity globally - that tool is a useful reminder that small pages add up differently than heavy ones.
Accessibility
This site aims to meet WCAG 2.2 Level AA where practical: semantic HTML, a skip link, sensible heading structure, and keyboard-friendly navigation. It's maintained by one person with a checklist and occasional embarrassment when something obvious slips through.
The W3C HTML checker reports no errors on the home page; it did flag that the document has headings but none at level 1, which I'm aware of and may tidy up. If any part of the site is hard to use - screen reader, keyboard, contrast, motion, or anything else - please email me and I'll fix what I can.
Privacy
I don't run analytics on this site. No Google Analytics, no Fathom, no cookie banner, because there's nothing to consent to. Pages are server-rendered HTML; I don't sell data or build profiles of visitors.
Site files
There are a few plain-text files at the site root for crawlers and tools: /robots.txt (crawler rules and a link to the sitemap), /llms.txt (a short guide to this site for AI systems), and /security.txt (security contact and policy - this page).
RSS
The feed at /feed.xml is valid RSS according to the W3C Feed Validation Service. Some readers prefer a <description> before <content:encoded> - a fair recommendation I may implement later; the feed works as-is.
Notice an issue?
Typos, broken links, layout glitches, accessibility problems â email christian@madebyck.com.