02 / Events & ticketing
Ticket Fairy
A clearer front door to live events.
Website revamp · Fullstack development
Case study draft
Executive summary
I worked on Ticket Fairy’s website revamp, alongside broader fullstack development for the platform at Flux Technologies. The website brings together event discovery for ticket buyers and a substantial set of tools for organizers—two audiences that need different routes through the same product.
At a glance
- Work on the public website
- Revamp
- Ticket buyers and event organizers
- 2 audiences
- React interfaces and PHP applications
- Fullstack
- Broader platform integration work
- REST APIs
Behind the build
Technology stack
The development toolkit and connected services used at Ticket Fairy.
React and PHP powered the interfaces and services, with Stripe and seats.io integrated into the event platform.
Development & infrastructure
Building, testing, and delivering the product.
React
PHP
MySQL
Tailwind CSS
Storybook- RESTful APIs
Services & integrations
External services connected to the platform.
- Stripe
- seats.io
Introduction
Ticket Fairy helps people discover and buy tickets for events, while offering organizers tools to sell, market, manage, and report on them. Its public platform covers much more than a ticket checkout, including referrals, check-in, audience insights, and payouts.
My contribution includes the website revamp and broader application work at Flux Technologies. This case focuses on the public website, with the wider engineering work providing context—not a claim that I built every capability the platform offers.
Feature summary
Event discovery
Public product context: a route for visitors to find events and continue toward ticket purchase.
Organizer platform
Public product context: information about selling tickets, marketing events, operations, and reporting.
Fullstack contribution
My broader work includes React interfaces, PHP applications, REST integrations, and attention to database performance and test coverage.
The work
A website with two entry points
A ticket buyer arrives looking for an event. An organizer arrives looking for a way to run one. Ticket Fairy’s public website has to make both paths understandable while keeping the product’s breadth accessible.
My website revamp work sits within that context. The landing-page experience connects event discovery with routes into the organizer platform.
Give a broad product a readable structure
Ticket Fairy’s public platform groups capabilities around selling tickets, selling more, getting paid, reporting, and running teams. That organization is useful context for explaining why the website needs more than a single product pitch.
The website revamp is my confirmed contribution. It connects the public product story with the event discovery experience.
Support the interface with fullstack work
Alongside the website, my work at Flux includes React interface development, PHP applications, and RESTful integrations. It also includes database performance, test coverage, and security-focused development.
These responsibilities connect the visible interface to the underlying application. They establish the scope of my contribution without attributing the entire ticketing platform or its public feature list to me.
Impact
The delivered contribution is a website revamp supported by ongoing fullstack work. It gives this portfolio a concrete example of working across a public-facing experience and the applications behind it.
Conversion, revenue, and page-speed improvements are not included because no measured before-and-after results have been supplied.
Conclusion
The creative challenge is making a substantial product easy to enter. The engineering challenge is supporting that experience with reliable application work. Ticket Fairy brings both sides together in one project.