Uses

This is a /uses page: a list of the tools I build with. The format comes from the developer community that collects them at uses.tech, which indexes several hundred of these.

Everything below is checkable against this website’s own source. That’s the point of the page. It’s the one part of my work that’s fully public.

The site itself

Hugo, extended edition, v0.151.0. A static site generator. There’s no server rendering anything at request time, no database behind a page view, and no CMS. Every page you can read here exists as a markdown file in a git repository before it exists as HTML. The version is pinned to v0.151.0 so a local build and a production build produce the same output.

Cloudflare Pages. Git-connected hosting. A push to the default branch triggers a build; the build runs the validation scripts; a failing script means nothing deploys. Headers and redirects are files in the repository (static/_headers, static/_redirects), not settings in a dashboard someone can quietly change.

GitHub Actions. Runs the checks: link validation, SEO structure rules, and the source checker that re-requests every cited URL on this site and fails the build if one stops returning 200. That last one is the mechanism described in the colophon.

Markdown and git. The whole site is text files. If Cloudflare and GitHub both disappeared tomorrow, the content would still be readable in a text editor, which is more than the previous version of this site could say.

Cloudflare beyond the site

Workers. Small serverless functions for scheduled jobs and API glue. I should be plain about this: a Worker on an hourly cron is exactly what generated the 739 English articles (2,922 files after machine translation) that I deleted. The tool was fine. The absence of a human between the tool and the publish button was not. Read the postmortem before you take any workflow advice from me.

D1. Cloudflare’s SQLite database, for the side projects that need to remember something between requests. Nothing on this site touches it. This site has no database.

The three GPTs I built

Custom GPTs in ChatGPT, public, free to open. They’re prompt engineering and structured checklists, not models I trained. Each one will happily be wrong about your specific business, and none of them replaces looking at your own data.

• Landing Page Reality Check walks a page’s message clarity, proof placement, and CTA friction.
• Dropshipping Growth Operator answers product, sourcing, offer and prioritisation questions for e-commerce operators.
• Nano Banana Prompt Maker turns rough image ideas into structured generation and edit prompts.

More detail on each, including what they can’t do, is under Tools.

What I deliberately don’t use here

• No analytics product of my own, and no tracking cookie. No Google Analytics, no tag manager, no Plausible, nothing loaded from a template. Traffic is counted by Cloudflare Web Analytics, which Cloudflare injects at the edge and which sets no client-side state; what I get back is page paths and country counts. The detail, and Cloudflare’s own wording for it, is on Privacy.
• No CSS framework. One hand-written stylesheet, no Tailwind, no Bootstrap.
• No font CDN. Both typefaces are served from this domain, so reading a page here doesn’t make a request to Google.
• No comment system, no newsletter pop-up, no chat widget, no A/B testing script.
• No automated publishing. Nothing reaches this domain that a person didn’t write and read first.