projects2025 · Full-stack · Live
Chennai Turbo Riders
Team Site and Console
The team's public site rebuilt as an onboard broadcast: video under scanlines, readouts in the corners, a grid walk of driver posters and a calendar that counts down to the next round. Behind it, on its own hostname, the console that edits every word of it without a deploy.

- Role
- Design, frontend, console port
- Stack
- Next.js 15 · Neon Postgres · S3
- Console
- Ported from CTR Unified
- Status
- Live at chennaiturboriders.in
- Onboard feed
- Grid walk
- Round countdown
- One build · two hosts
- Content in Postgres
- Media on object storage
- Revalidate only what changed
- Racing yellow on carbon
- 2
- Front doors, one process
- 25
- Versioned migrations
- 7
- Console modules
- 0
- Deploys to change a headline
01 · Overview
A brochure became a broadcast.
The first version was a set of hand-built pages reading a checked-in JSON file. Changing a headline meant a commit and a deploy, and only somebody with the repository could do it. This rebuild keeps the F4 design language, racing yellow on carbon, and moves every word into Postgres behind a console.
The home page opens on the team's onboard video under scanlines and grain, framed by the readouts a broadcast puts in the corners. The three words of the name wipe in one at a time, the season's numbers count up along the baseline, and the drivers arrive as a grid walk: on a wide screen the section pins itself and the posters travel sideways as the page scrolls.
The console is not a rewrite. Every screen, the media library, the rich-text editor, the role model and the S3 pipeline are ported from the CTR Unified platform, so they arrive already working. What is new is the branding, the single-site shape, and the wiring from those tables into this site's own pages.
- Onboard feed hero
- Video at full strength under scanlines and grain, corner readouts, the name wiped in word by word, numbers counting up.
- Grid walk
- Driver posters pinned and travelling sideways with the scroll; a snapping row on a phone and under reduced motion.
- Round countdown
- The calendar and the home page read the same published season, so they can never disagree about the next round.
- Two front doors
- The Host header decides: the admin hostname gets the console at its own root, every other host gets the site and nothing else.
- Media library
- Folders on Neon object storage, browser-side WebP conversion, presigned PUTs for video, and a usage scan before any delete.
- Surgical revalidation
- Saving an article clears the index, the home band, the sitemap and both the new and the old address after a rename.
02 · Two front doors
Same build, two hostnames.
One deployment, one process, one database connection. The middleware reads the Host header and mounts the console at the admin hostname's root; the mount folder itself 404s on every host, so the public domain carries no admin surface at all.
chennaiturboriders.in
The site
Server components reading one memoised query per request, the F4 design kept, every page cached for a minute and cleared the moment its content changes.
- Home, team, drivers, calendar, news, partners
- Rajdhani display face, JetBrains Mono readouts
- Session cookie is host-only and never reaches this domain
- robots and sitemap built from SITE_URL
admin.chennaiturboriders.in
The console
A monochrome tool palette in IBM Plex Sans, so the tool never reads as part of the thing it edits. One bright colour: the yellow of the action that writes.
- Team & site, drivers, sponsors, circuits, season, articles
- Owner and member roles with per-module grants
- Live previews drawn by the site's own render layer
- Accounts, media and co-admins
Shared by both
- one Next.js build
- one process
- ctr.* schema on Neon
- MEDIA_PREFIX on one bucket
- ctr.slugs: one address per thing
- revalidatePath after every write
- ADMIN_HOSTS read at build time
- no domain in the source
03 · Under the hood
What a save sets in motion.
Three chains the console runs many times a week: publishing an article, uploading a photograph, and keeping an address alive after a rename.
PublishFrom the editor to the home pageshowhide
- 01Write in the rich-text editor. TipTap with headings, lists, links, images from the media picker, normalised to a bounded document before it is stored.
- 02Set the byline. Category, author and tags: the two columns this deployment added to the shared article schema so the pages could keep their design.
- 03Preview with the site's own renderer. The console draws the article with the same shell the public page uses, so what is previewed is what ships.
- 04Save through one repo. Every table has one server-only repository; a client import of it is a build error, not a leaked connection string.
- 05Revalidate exactly the pages that changed. The news index, the home page's latest band, the sitemap, and the article's own address, old and new.
Pieces
- @tiptap/react
- normaliseRichText
- articlesRepo
- revalidatePath
- React cache()
- server-only
- 60 s page cache
MediaFrom a file to a URL on a pageshowhide
- 01Convert in the browser. Photographs and logos become WebP and are capped before they leave the machine, so a few hundred kilobytes arrive, not a camera original.
- 02Sign a PUT for anything big. Video goes straight to the bucket with a presigned request; the serverless upload route refuses bodies over a few megabytes by design.
- 03File under one prefix. Every object this site writes sits under MEDIA_PREFIX, which is what keeps the library from listing another site's uploads.
- 04Serve immutable, cached for a year. Public objects carry max-age=31536000, immutable, straight from Neon object storage or a CDN in front of AWS.
- 05Scan before deleting. Six queries, however many keys: everything that points at a file is listed in the dialog, because a delete would otherwise surface months later as a missing picture.
Pieces
- @aws-sdk/client-s3
- s3-request-presigner
- browser WebP
- MEDIA_PREFIX
- mediaUsage scan
- folders and breadcrumbs
- storage:copy between buckets
AddressesOne table for every URL the site publishesshowhide
- 01Claim an address. PRIMARY KEY (site, entity type, slug): an address belongs to exactly one thing, so two drivers can never hold the same URL.
- 02Keep exactly one live address. A partial unique index over (entity type, entity id) WHERE is_current means a thing has one current slug and any number of former ones.
- 03Answer to the old one. A rename keeps the previous slug as a redirect, resolved by one indexed lookup instead of a JSONB scan.
- 04Clear both caches. After a rename the stale page sits under the address that is now a redirect, so the old path is revalidated along with the new.
Why
- ctr.slugs
- partial unique index
- former slugs as redirects
- ⚠ replaced a JSONB array with no unique index
- docs/defaults-sync.md
04 · Key screens
Lights out to chequered flag.
The onboard feed
The full home page: the video hero, the tagline marquee, the team band, the grid walk, the car's specifications, the calendar with its countdown, the latest news and the partner marquee. Everything on it is a row in the console.
- Corner readouts: season, live marker, coordinates, founding year
- Counters roll up along the baseline
- Everything drifts up and fades as the page scrolls
The grid walk
On a wide screen the drivers section pins itself and the posters travel sideways as the page is scrolled down, the pit lane seen from the pit wall. The distance is measured, not guessed: the track's real width less the window's, so the last poster stops flush with the edge.
- Framer Motion scroll transforms
- A snapping row on phones
- Honours prefers-reduced-motion
The calendar
The season's rounds with their circuits, and a next-race panel whose countdown rolls each digit like a departures board. The home page reads the same published season, so the two can never disagree about which round is next.
- Seasons and rounds edited in the console
- Circuit maps from the tracks module
- Departures-board digits
A driver
Each driver has a poster, a profile and highlights, edited on one console screen and drawn on the drivers page, the home reel and their own address, which survives a rename.
- Posters converted to WebP in the browser
- Highlights as a repeater field
- Former slugs keep old links alive
The console's drivers screen
The tool palette is deliberately not the site's: warm greys one step apart, hairline separation, IBM Plex Sans, and a single yellow button for the action that writes to the database.
- Image fields open the media picker
- Slug field with former addresses
- Sort order by drag
The media library
Folders, tiles, an upload zone and a breadcrumb over one prefix of the bucket. Deleting asks the usage scan first and lists every page that would lose a picture.
- Neon object storage or plain AWS
- Presigned PUT for video, with a poster frame
- Copy a whole prefix between buckets with one script
05 · Trackside
In the grandstand.
06 · Stack and rules
What holds it on the track.
Two palettes that never mix
- Site: racing yellow on carbon, Rajdhani and JetBrains Mono
- Console: warm greys, one step apart, IBM Plex Sans
- Yellow appears in the console only on the button that writes
- Anything using both would look like neither
Boundaries
- lib/ is browser-safe; lib/server/ imports server-only
- The console mount folder is never a URL
- The session cookie is host-only, no domain attribute
- ADMIN_HOSTS unset means no host is the admin host
- No domain is written down anywhere in the source
Stack
- Next.js 15
- React 18
- TypeScript
- Tailwind CSS
- Framer Motion
- TipTap
- Neon Postgres
- @neondatabase/serverless
- S3 · presigned PUT
- Neon object storage
- sharp · WebP
- Capacitor · Android
- React cache()
- revalidatePath
- lucide-react
Operations
- 25 numbered, checksummed migrations
- Seed fires only on its own empty table
- create-admin makes the first owner; a trigger keeps one
- A second dist dir for verify builds
- check:source and check:articles guard the content shape
07 · More screens
The rest of the paddock.
Open any screen to see it full size.

