INCRC 2026 · One Nation, One Championship
ctrsports.in is the source of truth for a national racing championship: the newsroom, the calendar and its countdown, results and standings for seven classes, drivers, teams, tickets and a fan zone. The CMS that keeps it right lives on its own hostname in the same deployment, with roles, a standings engine and an audit trail.
Server ctr.arkhins.comFull-stack
Career stats
58
Tables in the Drizzle schema
9
Admin roles
7
Race classes, one weekend
106
Pages across site and CMS
01Overview
Mission briefing
A championship portal is not a brochure. It updates every session of every race weekend, its standings must be right, its calendar must be unambiguous, and its ticket path has to work for someone standing at a circuit gate on a phone. The design borrows from broadcast timing graphics so it reads like a championship, not a startup.
The primary navigation is the championship itself: Latest, Schedule, Results, Standings, Drivers, Teams, Tickets. A ticker across every page shows the current round, the session and a countdown, so the site always knows where the season is. Seven classes race on shared weekends, so results and standings are per category, and the model was generalised into championships, seasons, rounds and sessions so a future series is just another row.
The CMS is the other half of the same build. Nine roles cover the newsroom, the race editors, team and driver managers, media, pages and the fan zone; every server action re-checks its permission and writes an audit row. Publishing a session's classification recomputes the standings snapshot from the stored points, deterministically, and the site's cached reads are invalidated by tag in the same process.
A magazine Latest page: a breaking lead, secondary features, venue guides and class explainers rather than a hero and a scroll.
The ticker reads the next round and session from the same data the schedule page renders, with a countdown.
Points systems live per championship season; publishing results recomputes overall, team and sub-classification tables.
Nine roles, 29 permissions, every mutation checked on the server and logged with who, what and when.
Drop a .docx into the article editor: mammoth converts it, sharp resizes every embedded image into the media library, sanitised HTML lands in TipTap.
Accounts, predictions, polls, favourites, RSVPs and a double-opt-in newsletter, with web push and email reminders on a cron.
02Two hostnames
One Next.js app, one process, one database. The middleware reads the Host header: the admin hostname is rewritten onto the CMS routes and the public hostname refuses them, so the CMS is unreachable through the site's domain and its cookies never cross over.
ctrsports.in
Dark-first, in the manner of a timing screen: warm off-white plates on carbon, a single signal yellow, Exo 2 for type and a monospaced face for every number.
admin.ctrsports.in
Everything on the site has a screen: articles, race weekends, results entry, standings, teams and cars, drivers, media, pages, polls, newsletter, members, admins, settings and the audit log.
03Roles
| Pos | Role | Scope | Manages |
|---|---|---|---|
| 1 | Super Admin | everything | Admin users, site settings and every module |
| 2 | Manager | everything but accounts | All modules except admins and settings |
| 3 | News Editor | newsroom | Articles, categories, tags and the media picker |
| 4 | Race Editor | racing | Race weekends, circuits, results entry, standings recalc |
| 5 | Team Manager | entries | Teams, season entries and cars |
| 6 | Driver Manager | entries | Drivers and their season entries |
| 7 | Media Manager | assets | Media library, videos and galleries |
| 8 | Page Editor | content | CMS pages, blocks and sponsors |
| 9 | Fan Zone Editor | audience | Polls and predictions, fan list, newsletter |
04Under the hood
Results, standings and what the fan sees next. Each is a short chain, and each ends in the same place: the public page is right the moment the editor presses publish.
A round has sessions per class: practice, qualifying, Race 1, Race 2. Each carries its own grid and its own points scheme.
Positions, times, laps, status and fastest lap per entry, with the signed official declaration PDF attached to the session.
The action re-checks the race-editor permission, writes the results, and writes an audit row.
computeStandings reads the season's points system and rebuilds overall, team and sub-classification tables from session_results.points, deterministically.
The standings, results and round pages drop their cached reads in the same process; the ticker moves on to the next session.
Pieces
championshipSeasons.pointsSystemenabledraceSessions.sequenceenabledsession_resultsenabledcomputeStandings()enabledstandingsType: overall · team · rookieenabledrevalidateTagenableddeclarationMediaIdenabledmammoth converts the Word file to HTML, keeping headings, quotes, lists and tables.
Every embedded image goes through sharp into hero, card and thumb WebP variants under media/yyyy/mm in the bucket, and into the media library.
The HTML is sanitised and loaded into TipTap, where the editor keeps writing with the same toolbar as a fresh article.
Category, tags and a slug from github-slugger; the Latest page, the home lead and the newsletter digest pick it up on their own.
Pieces
mammothenabledsharpenabledsanitize-htmlenabled@tiptap/reactenabledgithub-sluggerenabledmedia/{yyyy}/{mm}enabledunstable_cache tagsenabledFan accounts have their own session secret and cookie, separate from admins and members, and never collide across hostnames.
Predictions on a round, polls, favourite drivers and teams, saved articles and RSVPs to rounds.
The newsletter is double opt-in; confirm and unsubscribe links are tokenised pages on the site.
A daily cron sends round reminders by web push and email; a weekly one sends the digest, with body images fitted to the reader's screen.
Pieces
FAN_SESSION_SECRETenabledweb-push · VAPIDenabledBrevo via packages/emailenabled/api/cron/round-remindersenabled/api/cron/newsletter-digestenabledconsent only for embedded videoenabled
05Key screens
A ticker with the current round, session and countdown, then a magazine: one lead, a grid of features, venue guides and explainers, the next round, the standings at a glance and the partners' marks in white.
Drivers' and teams' tables per class, with points, wins and podiums, recomputed the moment a session is published. Position numbers and points sit in the monospaced timing face.
Every session of every class across the weekend, with the circuit, its turns and direction, the countdown to the next session, and the results once they are in.
The CMS screen a race editor lives in on a Sunday: one session, every entry, positions, times and status, the declaration PDF, and a publish that recomputes the standings.
TipTap with tables, links and images from the media library; import a .docx and keep editing. Category, tags, hero image and scheduling on the side.
Every write, by whom, on what, when. Roles are enforced in the action itself, not only in the navigation, so the log is complete by construction.
06At the gate
Tickets, the schedule and the standings on a phone, and the CMS too: a race editor can enter a classification from the pit wall.
07Stack and rules
08More screens
