Work · Events and membership

Nine years of events became a site the team edits themselves.

Almost a decade of events, photographs and write-ups scattered across tools, on a website platform nobody in the team could change without help, on domains held somewhere nobody had the login for.

Client
An events organisation with a nine-year archive

What we built

A site generated from the organisation's own working document. Content is pulled overnight, committed as data, and the pages are rebuilt from that data, so the site keeps serving even when the document is slow and every content change leaves a reviewable record. Every event since 2017 has its own page. Visitors can favourite a photograph, and the vote is stored against a hashed identity rather than an address, because the membership reaches Europe.

The archive as the organisation's own team edits it.
A drawing of the interface, not a capture. The archive as the organisation's own team edits it.

What happened once it was running

Two domains moved to new hosting without an outage, checked automatically rather than by eye, and the overnight content run has been unattended since.

238Event pages, one for every night since 2017
1,115Photographs published
21Automated checks passed on the domain move
8,800Guests recorded across the archive
From the live site

Page and photograph counts are measured from the built site. The domain checks are an automated verification run recorded on 19 August 2026, and the script that ran them can be run again.

Why this page is short

Every figure on this page traces to something we measured.

This page once carried claims that described the work inaccurately. They came down in an audit of our own copy, and each one went back up only when its numbers could be traced to something measured. A case study you cannot check is worth nothing to you, and one that turns out to be wrong costs us more than it ever earned.