TrackSuite Demo Guide

Internal cheat-sheet for the Redline Motorsport Club demo site. Not linked prominently from the club site — only via the small footer link.

The pitch in one line

This is a plain static HTML site — no framework, no build step, no backend. Every leaderboard, ladder and standings table on it is a copy-pasted TrackSuite iframe, and every ticket link goes to a TrackSuite checkout on the club's own domain. If it works here, it works on any club website: WordPress, Squarespace, Wix, hand-written HTML.

Tell the prospect to hit View Source on any page: the iframes are right there, unmodified. That is the whole integration.

Feature map — every page → what it demonstrates

All seven embed types appear at least once. All embeds use t=dark and u=m, fixed heights of 560–760px (no auto-resize exists), loading="lazy", and a #111 container background so there is no white flash.

Embed URL reference

<iframe
  src="https://staging.tracksuite.app/em/o/{orgSlug}/e/{eventSlug}/leaderboard?t=dark&u=m"
  width="100%"
  height="640"
  style="border:0"
  loading="lazy"
  title="Leaderboard — Redline Motorsport Club"
></iframe>

• Embeds are served only from the platform domain https://staging.tracksuite.app — never from the masked ticketing domain.
• Params: t=dark|light theme, u=m metric units, n= race number(s), sr= series id, f=1 show field.
• Types: leaderboard, ladder (drag), spread, progression (circuit events only), driver?n=, rounds?n= (not for circuit events), and org-level standings?sr=.
• Bad slugs render a friendly "not available" card — nothing on this site can hard-break.

Seed data required in TrackSuite

Create this exact data in the demo TrackSuite org before showing the site, or the embeds render "not available" cards.

Organisation

• Org slug: redline-motorsport-club (load-bearing — used in every embed URL)
• Name: Redline Motorsport Club

Events (slugs are load-bearing)

Series

1. Create a series named Redline Drag Series 2026 containing the four drag events above (rounds 5–6 optional placeholders), with drop-round scoring enabled.
2. Copy its series id, then find-and-replace the literal token SERIES_ID_PLACEHOLDER across the repo (it appears in index.html and championship.html) with the real id.

Masked ticketing domain

1. Add events.storypals.au as a domain on the staging TrackSuite Vercel project (Vercel runs the storypals.au nameservers, so the DNS record is created automatically; cross-account, use CNAME events → cname.vercel-dns.com).
2. Add the corresponding Edge Config entry mapping events.storypals.au → org redline-motorsport-club.
3. Verify https://events.storypals.au/ serves the org portal, /{eventSlug} serves each event's checkout, and /{eventSlug}/results serves full results.

Talking points per page

Home

• "This is the club's own site and branding — TrackSuite is invisible except where they want it." Point at the standings and results sections updating live with zero club effort.
• View Source on the standings iframe: one tag, copy-pasted.

Events

• Buy Tickets buttons go to events.storypals.au — the club's domain, TrackSuite's checkout. No "redirecting you to a third-party site" trust drop.
• Past events keep selling the club: results become permanent marketing pages.

Drag Rd 3 (showcase)

• Best single page in the demo: leaderboard, ladder, then the driver-story and round-by-round embeds for car #21 — "your racers share their own page, that's free reach for your next event."

Circuit Sprint

• Show the progression chart — circuit-only, demonstrates TrackSuite handles disciplines beyond drag.

Roll Wars

• Same embed system, third discipline. One platform for a club that runs everything.

Championship

• Standings compute themselves — including drop-round rules. "Your competition secretary never touches a spreadsheet again."

Upcoming event pages

• Ticket teaser tables live in club HTML; the actual inventory, pricing and checkout live in TrackSuite. Change prices in one place.
• Show & Shine proves ticketing works standalone — no timing product required to start.

Deployment notes

• Pure static: deploy the repo to Vercel as-is. vercel.json sets cleanUrls: true, so all internal links are extensionless and root-relative.
• To preview locally: python3 -m http.server in the repo root (extensionless links resolve on Vercel; locally, add .html or use any static server with clean-URL support).
• No external assets except the Google Fonts stylesheet; heroes and textures are pure CSS.