racestrat.uk

This site's sibling - a team endurance racing site with live driver stats, a media gallery, and the Fuel Strategy App write-up, all on Cloudflare Workers, D1 and R2.

What it is

A team hub for iRacing endurance events - the same site the fuel calculator's own team uses. Live driver stats pull straight from the iRacing Data API, the gallery and training photos live in R2 with metadata in D1, and the Fuel Strategy App gets its own detailed write-up there, the same way this app does here. No server to patch or restart - it runs entirely on Cloudflare's edge, deployed straight from a GitHub push.

Structured data goes to D1, media goes to R2, and Pages Functions is the only thing that touches either - every page renders from the edge, nothing origin-hosted.

racestrat.uk homepage, showing the Run on real numbers hero, top navigation, and the site's live status readout

The homepage, live in local development - same premium dark design system this site uses, tuned for a team rather than a solo portfolio.

What's involved

Live driver stats

A cookie-authenticated client talks to the iRacing Data API directly - no third-party stats service in between - so each driver's profile page reflects their actual iRacing record.

Media gallery, the same pattern as this site's

Photos and captions live in D1, the files themselves in R2 - training sessions, race weekends, and family heritage shots, uploaded once and reused across the site's driver pages and gallery.

The Fuel Strategy App's own write-up

Its detailed portfolio page - screenshots, architecture, the reasoning behind the fuel math - lives on racestrat.uk rather than being duplicated here, since that's the team the app was actually built for.

Cloudflare-native, start to finish

Pages Functions, D1 and R2 - the same platform this site runs on, deployed the same way: push to main, GitHub Actions builds and ships it, no server to patch or restart.

Why it's a separate site

racestrat.uk is built for a team, not for me - driver profiles, shared media, event history. Keeping it as its own deployment means the team's content and this personal site's content never get tangled together, even though they're built with the same stack, the same design system, and the same solo-engineer discipline as everything else on this page.