Context
A professional congress organiser running scientific and accredited training events, with several editions a year and different rules for each one. From one congress to the next, the audience, the fees and even the questions asked at registration all change.
Problem
Every congress has its own rules: different fees per participant category, registration forms that change from event to event, abstracts to submit and review, accompanying persons, extra services and hotel bookings. The previous site was hand-written procedural PHP and could not be reused for the next event: the team started again each time, under the pressure of an opening date already announced.
What I built
A configurable platform where each event defines its own registration forms, fee types, statuses and payments from the admin panel, without new code. It covers abstract submission with a review flow, participant and companion management, additional services, room booking by property and room type, payments, and a multilingual back office. In the second version I rewrote the foundation and added itemised payments, documents gated behind payment, and participant impersonation for support, which cuts the time it takes to answer someone who cannot complete their registration. I wrote both versions on my own.
Outcome
A new congress is configured from the admin panel, with no code written: the same platform has served several editions, replacing a hand-written PHP site.