The context
The Ronde Sud Bourgogne is a stage cycling race for U19 riders held in Saône-et-Loire, Burgundy: four stages across three days, including a time trial, for its thirteenth edition. It is run by a volunteer association.
An event like this has a very particular digital profile: the site is barely used for eleven months of the year, then becomes the central tool for three days — for riders, teams, families, volunteers and local press, all connected at once from the roadside.
What I built
Edition-based structure
each year is a full edition with its own stages, partners and news, without overwriting previous ones.
Stage pages
detailed routes town by town, from Le Creusot to Viré, time trial included.
Roadbook
the reference document for teams and organisers.
Live coverage
a dedicated page activated during the race.
Online registration
separate forms for volunteer marshals and for team presentation, where everything previously went through email and phone calls.
Member area
restricted access for the organising team.
Roll of honour
an archive of winners across editions.
News, calendar and gallery
the association's life outside race season.
Partner section
sponsor visibility, the economic condition of the event's survival.
Architecture & technical decisions
The data model puts the edition at the centre: stages, news, partners and results attach to it. That is what allows the next edition to open without destroying history — a recurring-event site that overwrites its data every year loses all its memory within a few seasons.
The application is a server-driven single-page app (Laravel + Inertia + Vue 3), balancing fluid navigation with proper SEO: the race depends heavily on local search around event time.
Registration is designed for volunteers, not seasoned users: short forms, explicit confirmations, and central collection of what was previously handled by hand.
The whole site stays administrable by the association without technical help. That is a fundamental constraint: a volunteer association's budget does not stretch to calling a contractor to publish a news item the night before the start.
Technical challenges
Extreme traffic peaks. Eleven quiet months, then one very busy weekend: pages consulted during the race are aggressively cached so they stay served whatever happens.
Live from the roadside. Visits happen on patchy mobile coverage in open countryside: race pages are deliberately lightweight.
The event's memory. Thirteen editions to preserve and keep browsable, without cluttering navigation of the current one.
Volunteer coordination. Marshal registration is a regulatory matter for a race on open roads — form reliability matters as much as its ergonomics.
Partner visibility. Sponsors fund the event: their exposure had to be designed in rather than appended at the bottom of the page.