Case study / Web build
A basement club, rebuilt as a production platform.
An RC racing club went from a Facebook group to a full production site. Live CMS, store, waivers, edge security.
Case study / Web build
An RC racing club went from a Facebook group to a full production site. Live CMS, store, waivers, edge security.
A club run by one non-technical person now updates races, news, photos, members, and products themselves. Every edit is live in seconds, with no rebuild and no developer.
Admin-authored articles, server-rendered for search, each with a live sitemap entry and a link into the matching photo gallery.
A legally structured season waiver, signed in two minutes on a phone at the door. A signed PDF lands in two inboxes on submit.
A config-driven CMS the club runs without touching code: events with recurrence, news, galleries, members, store, and a site-wide notice ticker.
Built as one system, so it holds together and stays cheap to run.
Events with recurrence, news, galleries, members, and page content, all editable in a clean admin.
A parts and race-entry store with server-priced Square checkout and stock control.
Season-based digital release forms, legally structured, signed on a phone in two minutes.
A five-rule WAF, rate limiting, Turnstile, and a strict content-security policy.
Schema, a self-updating sitemap, robots and llms files, verified in Search Console.
A live countdown, motion tuned by hand, and generative hero art of the club's own cars.
Static shell served worldwide, with live data and logic in Pages Functions. The only running cost is the per-sale fee when someone buys a kit.
This is the kind of work I do: full sites, tools, and software, made to run lean and last.