The framework underneath has its own page; these are the decisions specific to Burwell.
Most of this portfolio runs on one shared framework, and most sites carry a family resemblance because of it. Burwell doesn't. Its public face — layout, navigation, type, the lot — was rebuilt from scratch, and the test it set itself was to do that without modifying the framework at all. It passes: every custom thing about the front-end is an override file in the village's own folder, and the stylesheet is scoped so it physically cannot leak into the admin area. It's the clearest demonstration in the portfolio that the "domain wins, core is the fallback" rule earns its keep — you can make a site look like nothing else and still inherit every fix landed on the core.
The honest bottleneck in a village what's-on isn't software — it's whether anyone keeps typing things in. Volunteers start enthusiastically and stop. So the design refuses to depend on data entry. The move is to point the system at the artefacts that already exist — a poster on a wall, a club's website, a magazine PDF, a calendar feed — and have it do the transcribing. The unit of input is a photograph or a URL, not a form someone has to remember to fill in.
AI does the reading — a vision model lifting an event off a poster, a language model pulling items out of magazine prose — but it is never the thing that publishes. Everything it produces lands as a draft for review. That split is deliberate: the AI is treated as a fast, fallible assistant that saves the typing, not as an oracle to be trusted unseen. It's good enough to turn a photo into a 90%-complete event; it is not good enough to put that event in front of the village without a person glancing at it first.
The community magazine is the best source of what's genuinely happening locally and the most awkward to use: a PDF, published on a lag, laid out for human eyes. The reflex would be to ask the magazine to change — publish a feed, fill in a form. The choice here is the opposite: leave it exactly as it is and do the work on this side, ingesting and segmenting its PDF into reviewable drafts. The richest local sources are rarely the tidiest, and the people already embedded in a community don't want to rework their routine for a website. Meeting them where they are is the only version that actually gets the data.