East Lake Classic
A 22-year-old marching band competition got its own home: fast on a phone in the stands, free to host, and editable by volunteers without the risk of breaking it.


The problem
The East Lake Classic is a regional marching band competition (FMBC) hosted every October by the East Lake High School Silver Sound in Tarpon Springs, Florida, and the program's most valuable sponsorship asset. For years it lived on one page of the band's Wix site: a wall of PDF links and Google Form buttons, with a 2025 registration deadline next to a 2024 schedule, and nowhere for sponsors to be seen.
The booster board turns over every year and Wix was awkward to edit, so the page went stale every season. The event needed its own site, one that:
- looks like a premier competition and works on a phone in the stands,
- gives band directors, families and sponsors each a clear path,
- costs nothing to run, and
- can be kept current by whoever is on the board next year, without being able to break it.
My role
I wrote the product requirements, built the site and its admin dashboard, and ran it through show night. I'm the only committer: 87 commits and 49 pull requests in five weeks, from the first build on September 14 to a leaderboard update the night before the show.
I worked from a design handoff and paired with Claude Code for much of the implementation. I set the requirements, made the architecture calls, and reviewed and verified every change before it reached main. Every change went through a pull request with its own preview URL.
Stack
Site
Static output with no client framework. Content is YAML files in the repo.
Content safety
One schema module, shared by the build, the admin Worker and the browser form.
Hosting
$0 a month; the domain is the only cost.
Integrations
Tickets, fees and voting run on Cheddar Up. The site links out rather than taking payments.
Architecture
There's no database and no server runtime for visitors. The only code that runs on a request is one small Worker, and only for the admin dashboard. Every page a parent or director sees is a static file.
Key features





- Battle of the Band DirectorsA fundraising vote ($1 = 2 votes) with a live leaderboard, a host handicap, a switch to hide counts before the ceremony, and native sharing.
- Admin dashboardSchema-driven forms for every content type, a raw YAML tab, per-file history with diff and restore, and live build status.
- Show-night toolsResults entry, leaderboard updates, bulk gallery upload (resized and EXIF-stripped in the browser), and a link checker.
- Short links for print
/tickets,/programand/resultsfor flyers and QR codes, each pointing at the right thing for the current season. - Self-expiring promosBlocks with a deadline hide themselves both at build time and in the visitor's browser, so nothing goes stale between builds.
- Season rollover"Start next season" rolls the event to the new year in one checked commit, then lists what's left to fill in, so next year's board starts from a working site, not a blank page.
Hard problems
Volunteers can edit it, but can't break it
What happened: on October 2, an edit made through GitHub's web editor renamed a school on the vote leaderboard, and every deploy after it failed.
The fix: the admin Worker now runs the exact checks the build runs. It parses the YAML the way the build does, validates it with the same Zod schemas, then checks the cross-file rules: leaderboard and schedule names must be real bands, and images and PDFs must exist. If the build would reject a change, the dashboard rejects it first and says why. Renaming a band also updates the schedule and leaderboard in the same commit.
data = readRecordAsBuild(w.text, collectionForPath(w.path)!.rootKey);
...
const fileIssues = validateRecord(w.path, data);
issues.push(...fileIssues);
...
issues.push(...crossCheck({ event, bands, schedules, images, documents }));
...
if (issues.length > 0) return json({
error: 'The site would not build with this change.', issues,
}, 422);Saving YAML without wrecking it
What made it hard: event.yaml carries more than 100 lines of comments explaining each field to the next maintainer. A naive parse-and-stringify round trip reflows the file and throws those comments away.
The fix: splice only the nodes that changed, re-parse the result to prove it means what the form said, and fall back to a full re-serialise only if that check fails. A test script mutates every value in every content file to make sure that holds.
const want = clean(value);
try {
const text = splice(source, want, rootKey);
if (deepEqual(readRecord(text, rootKey), want))
return { text, fallback: false };
} catch {
// fall through to the safe path
}
return { text: reserialise(source, want, rootKey), fallback: true };Free tier, safe concurrent saves
Cloudflare's free plan gives a Worker about 10 ms of CPU per request. So the heavy work (YAML editing, image resizing) happens in the editor's browser. Uploads go one file per request as data the Worker never parses, and a typical save costs about 3 ms.
If two board members save at once, GitHub's createCommitOnBranch with expectedHeadOid refuses the commit when main has moved. The Worker refreshes and retries once instead of silently overwriting someone's change.
input: {
branch: { repositoryNameWithOwner: this.repo,
branchName: this.branch },
expectedHeadOid: opts.expectedHead,
message: { headline: opts.headline, body: opts.body },
fileChanges: {
additions: opts.additions,
deletions: opts.deletions.map((path) => ({ path })),
},
},An off-by-one date on a static site
Formatting the show date in America/New_York at build time once rendered it as October 16. Now calendar dates render in UTC, instants such as deadlines must carry an explicit offset (the schema enforces it), and "today" for the countdown is worked out in the visitor's browser on the venue's clock.
/* The venue's local calendar day, as YYYY-MM-DD. */
const today = new Intl.DateTimeFormat('en-CA', {
timeZone: 'America/New_York',
year: 'numeric', month: '2-digit', day: '2-digit',
}).format(new Date());
const days = Math.round(
(Date.parse(iso + 'T00:00:00Z') - Date.parse(today + 'T00:00:00Z'))
/ 86400000,
);Accessibility that Lighthouse missed
Lighthouse gave the accessibility score 100 while the hero headline sat at 1.59:1 contrast over a photo, because it can't check text against images or video. I added a contrast checker (Playwright plus ffmpeg) that measures each run of text against the brightest pixels behind it, at several screen widths, and steps through every second of the hero video. Every tap target is at least 44 px, and the background video has a pause control.
Results
The site launched in time for the 22nd annual show on October 17, 2026. It carried the full 2026 lineup of 16 bands across five classes, 8 judges with bios, and the sponsor wall, and the director vote leaderboard was updated right up to the night before. The old Wix page's mix of years is gone; each season has its own page, and last year's show becomes part of the archive instead of being overwritten.
Need a site your team can actually keep up to date?
I build fast, low-cost sites and tools for organizations run by volunteers and small teams.
Let's talk →Visit the site ↗