Credits

Almost everything here was made by other people and given away. This page names it, because a consultancy that will not say what it runs is asking for a trust it has not offered.

It is also the shortest honest answer to “what do you actually work with”. The list below is not a capability brochure — it is this site’s own bill of materials, and you can check every line of it from your own browser.

What reaches your browser

Four things, and nothing else: HTML, one stylesheet, one webfont, and images.

• HTML, written out in full before you asked for it. Every page is a file on disk, not a template assembled per request.
• One CSS bundle, concatenated and fingerprinted at build time and served with a Subresource Integrity hash, so your browser can verify it arrived unmodified.
• The Ubuntu typeface, by Dalton Maag for Canonical, under the Ubuntu Font Licence. Served from our own machine — a webfont from someone else’s CDN is a third party watching you read.
• WebP and PNG images, sized at build time.

No JavaScript runs on this site. No cookies are set. Nothing is requested from another company’s server — no analytics, no fonts, no embedded video, no consent banner, because there is nothing to consent to. Open your browser’s network panel and count the hosts: there is one.

How the pages are made

• Hugo — the static site generator, written in Go. Templates, taxonomies, both languages and the feeds are its work.
• Markdown and Go templates for the hand-written pages and the layouts.
• SQLite — the portfolio is not authored here. It lives in a bilingual CV database and is exported into this site by a Python script, so a fact is written once and appears wherever it belongs.
• Python for that exporter, and for generating the icon set and the social card with ImageMagick from a single drawing of the mark.

How it is proved

There is no hosted build service; the quality gate runs on the machine the site is written on, and every diagnostic is an error rather than a warning.

• vnu validates the HTML, Stylelint the CSS.
• axe-core audits every built page against WCAG 2.2 A and AA, in both colour schemes, and it is in the gate — not beside it.
• Puppeteer drives headless Chromium for the checks a validator cannot make: measured contrast, focus order, target size, reading measure, viewport overflow, print pagination, and a pixel-for-pixel visual regression via pixelmatch.
• Lighthouse holds the performance budgets; lychee checks that every link still resolves.
• Prettier, markdownlint, Ruff, yamllint, ShellCheck and codespell keep the source honest; gitleaks makes sure no secret is ever committed.
• Task runs all of it under one name per job.

Where it runs

One small machine does all of it: a single-core DigitalOcean server with 512 MB of memory and a 10 GB disk, standing in Toronto, Canada, answering at 165.227.39.206. That address is what DNS already hands to anyone who asks, so printing it here saves you the lookup rather than telling you anything new. What the machine records while it answers is on the privacy page.

• Debian is the operating system.
• Caddy answers every request and renews the HTTPS certificate itself, from Let’s Encrypt.
• Ansible describes that server as code, so it can be rebuilt rather than remembered.
• Soft Serve is the git server at git.engineer.company. This site’s own source lives there.
• restic takes the backups off the box.
• Cloudflare answers DNS — and only DNS. The site is deliberately not proxied: openness is worth more to us than the protection, and a proxy would put one more company between you and us.
• Mail is Apple iCloud, which is why the address on the contact page reaches a mailbox and not a marketing platform.

Standards it follows

• WCAG 2.2 level AA, guarded rather than claimed.
• schema.org structured data, marking only what is true and visible on the page.
• Web App Manifest, so the site can be installed as an app.
• RSS and JSON Feed, both carrying the full text.
• RFC 9309 robots.txt, which allows everything, to search crawlers and AI systems alike — the writing here exists to be read, and it names the sitemap both of them follow.
• RFC 9116 security.txt, plus humans.txt, llms.txt and agents.txt for the machines that come asking.

Thank you

Every project above is maintained by people who did not have to share any of it. If you build on this stack too, that is where your money and your bug reports are worth most.