The Problem
Events need different admission paths: some tickets are paid, some are free RSVPs, some have tiers, and staff still need one reliable way to validate entry at the door. The private platform needed that flow without publishing real attendee details, venue information, ticket IDs, QR tokens, or payment records.
What I Built
I built a full-stack event-admission workflow: event publishing, ticket tiers, paid checkout, free RSVP, QR-backed ticket delivery, attendee dashboard access, and staff check-in tools. The public case study describes those verified boundaries with fictional labels and recreated diagrams.
Project Overview
This is a private client platform. The public page is a sanitized case study based on inspected source structure.
My Contribution
- Built paid ticket checkout and free RSVP paths that create individual ticket records for each requested quantity.
- Modeled event capacity, reserved-ticket counts, ticket tiers, sale windows, RSVP status, QR tokens, and checked-in state.
- Implemented staff workflows for ticket listing, event stats, CSV export, QR verification, scanner-assisted check-in, manual check-in, voiding, and undo check-in.
Ticketing Flow
Paid and free admission paths
Paid checkout and free RSVP both converge on ticket records that can be delivered, displayed, verified, and checked in.
The diagram uses generic labels and excludes real events, attendee names, venue addresses, QR tokens, and payment identifiers.
Technical Decisions
Use one QR-backed ticket model for paid checkout, free RSVP, and staff check-in.
- Staff need one verification workflow even though guests can enter through paid ticket tiers or free RSVP.
- The ticket logic has to preserve source, tier, capacity, and reservation state without creating separate door workflows.
- Paid and free admission paths converge on a single ticket record that can be delivered, displayed, verified, and checked in.
How I Work
Engineering Challenge
- A ticketing project contains sensitive event, attendee, and payment data by default.
- I traced the safe source boundaries: event models, ticket tiers, checkout and RSVP routes, QR generation, dashboard display, admin scanner, event stats, and ticket export.
- The case study publishes the workflow shape while withholding real records, QR tokens, venue details, private URLs, and private screenshots.
- The page communicates ticketing depth without leaking operational data.
Quality & Testing
Quality Evidence
Product engineering evidence
- Private source includes event/ticket models, migrations, checkout and RSVP routes, QR email generation, dashboard ticket display, admin ticket tools, and check-in UI. No public test totals are claimed.
- Private CI/deployment files were inspected for service shape only; run logs, environment values, and resource identifiers are not published.
- Source evidence verifies Next.js, FastAPI, PostgreSQL, Stripe checkout, QR code generation, Resend email, ticket tiers, capacity reservations, and admin check-in workflows.
Public page quality
- The public visual is a recreated SVG with accessible title and description.
- The SVG diagram scales inside the shared case-study layout.
- No attendee data, event records, QR tokens, payment identifiers, private screenshots, or production URLs are bundled.
| Area | Evidence | Published detail |
|---|---|---|
| Event setup | Event routes, ticket tier routes, admin event pages | Generic event/tier model |
| Admission | Checkout route, RSVP route, ticket model, email service | Paid and free ticket paths |
| Door workflow | Admin tickets, scanner UI, verify/check-in routes | QR-backed check-in flow |
Results & Impact
This slice shows a complete event-admission system: event publishing, ticket tiers, capacity reservations, paid checkout, free RSVP, QR-backed ticket delivery, attendee dashboard display, event-specific scanner check-in, manual fallback, CSV export, voiding, and undo check-in.
What I Learned
Ticketing software needs to be generous to both sides of the door. Buyers need a clear confirmation path; staff need a fast, constrained tool that can tell valid, duplicate, and wrong-event scans apart.