BUILT FOR THE LOVE OF RACING.Your next track day starts here

TRACKSUITE / PRESENTER GUIDE

THE CLUB IS THE STORY.
TRACKSUITE POWERS IT.

A practical walkthrough of a real integration pattern: the organisation owns its website, and TrackSuite brings the results into it.

Before your presentation

The existing embed URLs have been preserved. At the last check, the staging results returned an unavailable message. Replace them with your new demo links before presenting live results. The club identity and editorial content are fictional; data inside each embedded panel comes from TrackSuite.

A FIVE-MINUTE WALKTHROUGH

START WITH THE ORGANISATION.

  1. 01

    Start at the club homepage ↗

    This feels like the organisation’s own site. Its brand, events and community lead the experience; embedded podiums and standings fit into the page.

  2. 02

    Follow an event entry ↗

    Open the Test & Tune page, then follow Tickets & entries to the existing masked-domain portal. The portal currently retains its Toronto Roll Racing Club staging identity.

  3. 03

    Relive the event ↗

    Move through the results tabs: podium, leaderboard, elimination ladder, spread, driver and rounds. The club keeps its navigation around each embedded view.

  4. 04

    Tell a driver’s story ↗

    A club article combines editorial copy with driver-scoped results. Share the article without rebuilding a results table.

  5. 05

    Zoom out to the season ↗

    Finish with series standings, the organisation’s record book and the circuit event’s lap-progression view.

DEMO DETAILS

WHAT’S LIVE. WHAT’S EDITORIAL.

Connected to TrackSuite

All nine iframe types, driver scoping (cars #11 and #336), metric units, light and dark themes, organisation and discipline-filtered records, ticket links and public results links.

Use the theme button in the header to show the club site and its embeds switching together.

Fictional club content

The Redline name, history, membership proposition, event display names and editorial copy are demonstration content. Photographs are illustrative and do not depict the seeded events or drivers. Membership opens an explanatory dialog; it does not collect details or create a real registration.

Updating the demo links

Open /assets/embeds.json for the full inventory of current iframe URLs and the pages they appear on. After replacing URLs in the HTML files, run npm run inventory to refresh that list.

All embeds remain literal iframe tags in the HTML. A club can use the same pattern in an existing CMS without adopting a new framework.

Before a prospect session

  • Replace staging URLs and confirm the nine embeds contain results.
  • Check the driver numbers and series ID against the refreshed data.
  • Confirm the masked ticket portal’s branding and event links.
  • Recheck event dates against the replacement dataset.