HOFMI's ministry leadership needed one page that explained the whole operation we'd built for them — the AI assistants doing the work, the machinery running underneath, and what all of it was actually producing. One place a non-technical person could read from top to bottom and come away understanding what they were looking at.
The instinct in our trade, faced with a request like that, is to build something clever. Lots of moving parts, lots of polish. We did the opposite. We made the equivalent of a single, well-laid-out printed document: one page, written by hand, with nothing underneath it that could quietly fall over.
Who fixes it when it breaks
The decision came down to a question we don't ask often enough: when this thing misbehaves one day, who is standing in front of it, and can they do anything about it?
Think of the difference between a wall clock and a smartwatch. The clock has one job and almost nothing to go wrong. The smartwatch does far more — until the morning it won't turn on, and the person wearing it has no idea whether it's the battery, the software, or something else. They just know it's dead, and they can't tell you anything more useful than that.
A clever, modern web page is the smartwatch. When it breaks, it tends to break invisibly, in ways only an engineer can name. The people we were building for are the person wearing the watch. If the page they were shown on Friday was broken on Sunday morning, all they could have told us was "it's not working" — and they'd have been right to be frustrated.
A page that stays up on a Sunday morning, when nobody technical is watching, is worth more than a clever one that doesn't.
So we took the watch off and handed them a clock. We stripped away every layer that could go wrong on its own. What's left has nothing to rot, nothing to quietly expire, nothing that needs rebuilding before it shows. It looks the same next year as it does today. And the page someone edits is the very same page everyone sees — there's no hidden step in between where a mistake can creep in.
What you give up, and what you don't
This way is not free. You write more by hand, and the fancier touches take real effort instead of arriving for nothing. We still built moving, animated diagrams into two of the eight sections — but that was deliberate craft, not something we got off the shelf.
What you keep is the thing that mattered: a page that stays up, and a turnaround so quick that changing it feels like editing a document rather than shipping software. Fix a line, and it's live moments later. That tightness is exactly what kept the page current instead of letting it go stale the first time something underneath it cracked.
The rule worth keeping
Match the tool to whoever has to maintain it — not to whoever builds it.
When the people on the receiving end can diagnose their own broken page, by all means build them something elaborate; you've got someone to fix it. When they can't, every extra layer you add between the words and the screen is one more thing that can fail in a way nobody there can name, let alone repair.
The clever version earns its place when it genuinely needs to be clever. For a page that mostly had to load and stay loaded for people who just needed to read it, it didn't. Boring, in this case, was the feature.
For the technical reader
The brief, in May 2026, sounded like a job for a dashboard: eight tiers walking HOFMI's leadership from why the operational fleet exists down to its net effect. The default would have been React, a component library, a single-page app.
Instead we wrote one static HTML file. No framework, no build step, no external dependencies. The whole thing lives in static markup a person can open in a text editor and change a sentence in. It deploys to Cloudflare Pages in roughly thirty seconds, behind an Access policy that only admits addresses on the organisation's own email domain.
The "things that break invisibly" in the story are concrete failure modes of the dashboard path:
- a dependency drifts a major version out of date;
- a build step fails silently in CI;
- a service worker keeps serving a cached bundle from three weeks ago, and no amount of refreshing clears it.
Each is a five-minute fix for an engineer and a dead end for everyone else. A static file has no build to fail and no dependency tree to rot, so none of those modes exist. The surface the author edits is the surface that ships — no compilation step where a mistake can hide.
The cost is real: more hand-written markup, no component convenience, richer interactions take effort. The animated diagrams in two of the eight tiers were deliberate work, not a package install. The trade we'd take again: a framework earns its place when the interactivity justifies the fragility; for a leadership reveal that mostly needed to load and stay loaded, it didn't.