1st World Congress on Cancer & Sexual Health.
An SSR platform for an international medical congress bridging oncology, sexology, and patient care. Registration, abstract submission, Stripe payments and a custom ticketing system - 650+ scientists, clinicians and doctoral researchers in Szczecin.
A medical congress that has to run like a SaaS product.
The organizing team needed a platform that would handle the full conference lifecycle - abstract submission, registration, ticket sales and payments, attendee communication - without stitching together five separate SaaS tools.
Hard constraints: payments from attendees and sponsors across a dozen countries in three currencies, pricing that depends on attendee category and registration date, and SEO requirements for indexing academic sessions.
Four decisions that simplified everything else.
SSR from day one
Academic sessions must be indexable by Google Scholar and conference aggregators. Server-side rendering eliminates an entire class of SPA/meta-tag fights later on.
A custom ticketing system
The price depends on the attendee category (physician, resident/PhD, industry) and the registration date - the early-bird, regular or late tier is resolved automatically. Workshops and the gala dinner are add-ons, with capacity limits and complimentary registrations for speakers issued from the admin panel. Tickets, abstracts and payments live in one database, so the organizer sees every attendee in one place.
Stripe instead of a traditional gateway
Attendees and sponsors from 12 countries, three currencies (PLN, EUR, USD) and a single source of truth for transactions - Stripe let the focus stay on conference logic rather than gateway compliance. Institutions paying by bank transfer get a reference number, and the organizer confirms the payment in the admin panel.
Accessibility isn't optional
A medical congress draws people with a wide range of abilities - attendees, patients, accompanying guests. I targeted WCAG 2.1 AA from the start: contrast ratios, focus states, keyboard navigation, correct ARIA roles, screen-reader support. Nobody gets left at the door.
What was built.
Three functional domains - each of which could be a standalone product - fused into one coherent platform.
Conference management
The full conference lifecycle - from abstract submission to a congress ticket.
- Abstract submission with peer review
- Attendee registration
- Program schedule
- Sponsor workflow
Tickets & payments
Ticket sales with pricing by attendee category and date, payments in three currencies.
- Stripe and bank transfer (PLN / EUR / USD)
- Pricing: category × early-bird / regular / late
- Workshops and gala dinner as add-ons
- Capacity limits and complimentary registrations
Platform
The foundation holding it all up - SSR, SEO, dual-language delivery, and an admin panel.
- Admin panel
- SEO optimization
- PL / EN localization
- Monitoring & alerts
Stack.
Cuts.
Six production views - all in two languages and WCAG 2.1 AA compliant.
And this is only a slice - the abstract portal, admin panel, sponsor space, post-registration receipts, and two full language versions round out the platform.
The real work happens BEFORE the conference.
The conference itself is three days. Registration, sponsor payments, hotel bookings, attendee support - those are the processes that have to run smoothly for weeks beforehand, without draining nerves from the organizer or the attendees.
Registration, ticket choice and Stripe payment in a single flow - no jumping between external systems.
From the homepage to sponsor enrollment, prospectus download, or finding a partner hotel - everything one click away, no broken links.
Full keyboard navigation, correct ARIA roles, contrast above 4.5:1, screen-reader support. A medical congress accessible to every guest.
§ 07 / My role
- Lead developer and solution architect
- Backend: Java + Spring + PostgreSQL
- Frontend: Angular + TypeScript (SSR)
- Integrations: Stripe
- Infrastructure: Railway, Vercel, CDN
- Domain and dedicated mailbox setup
- WCAG 2.1 AA accessibility
§ 08 / Timeline
Your project
here.
If you're tackling a platform that needs SSR, payments integration, and compliance - let's talk before you start stacking tools.