TT Classic

One website being asked to do five unrelated jobs.

An athlete wants to know the categories, the dates and how to enter. A trade vendor wants stand availability. A potential sponsor wants audience numbers and brand fit. An international competitor wants to know whether they're even eligible. And a member of the public wants tickets, photos and a reason to care.

All five were landing on the same page, and all five were applying by whatever route they could find — direct messages, comments, forwarded emails. Applications were being lost not through carelessness but through volume and fragmentation.

Underneath sat something more important than logistics: a charitable cause about prevention, wellbeing and rehabilitation, with a tagline the client was rightly protective of. It had to be present without being drowned by event marketing — a tonal problem as much as a structural one.

A site organised around who's arriving.

• An interactive battle map. Eleven cities as a hand-tuned SVG, labelled on the side that keeps the map legible. Geography is the series' main story, so it leads rather than sitting in a list.
• Athlete presentation. Competitors given real profile treatment rather than a spreadsheet row — the material that makes an event feel worth entering.
• A dedicated category page. Divisions and criteria explained in full, so the most common pre-entry question is answered without a message.
• Gallery with live social. Curated photography with a lightbox, alongside an automatically updating Instagram feed — proof the series is active, without a manual upload ritual.
• A future events page. Six planned events with individual register-interest forms, turning demand into a measurable list before a venue is ever booked.
• Sponsor and partner placement. Real estate that makes commercial partnerships worth paying for, integrated rather than bolted on.

Every enquiry lands in the same place, tagged.

The five application routes all post to one endpoint, each carrying a type — athlete, vendor, international, future event, general — which files it into the correct destination automatically. One pipeline, five labelled streams, no inbox archaeology.

• Typed submissions. The form's type field drives the routing, so adding a sixth audience later is a configuration change rather than a rebuild.
• Static delivery. Hand-written HTML deployed straight to the edge. Event sites face spiky traffic — an announcement, a share, a results day — and a static page absorbs that without capacity planning.
• A protected brand. A fixed palette, a display typeface used consistently and a tagline treated as untouchable. Consistency is what makes a young event series look established.
• Separated charitable identity. The cause was given its own quiet, single-page home, linked from the events site but tonally distinct — so a serious message isn't competing with competition promotion.

• Semantic HTML5
• CSS3
• Vanilla JS
• Inline SVG mapping
• Webhook form pipeline
• Instagram feed
• Vercel

An organiser's evening, given back.

The measure of an events platform isn't how it looks on launch day. It's whether the organiser can find every vendor application eight weeks later without opening a single message thread.

• Nothing gets lost. Five audiences, one structured record, sorted on arrival.
• Demand measured before money is spent. Register-interest forms turn "should we run one in Glasgow?" into a number rather than an argument.
• A sellable sponsorship product. Defined placements and a professional presentation make commercial conversations straightforward.
• Credibility ahead of scale. A cohesive brand across events, athletes, gallery and cause makes a growing series look like an institution.
• Room to grow. New cities, new events and new audiences are additions to a structure that already anticipates them.