Developer event discovery
Event Dev Hub
My role
Full-stack developer
2026
A focused hub for discovering developer events, opening event details, and recording bookings through one compact Next.js experience.
event API routes
persistent data models
deployed discovery flow
01 · The problem
What needed to change
Developer events are scattered across communities and platforms. The product needed a simple catalogue that could surface event details and turn discovery into a booking action without unnecessary navigation.
02 · The constraint
The hard part
The event catalogue, dynamic detail pages, and bookings needed to share a small data model while remaining easy to deploy as a personal product experiment.
03 · Decisions
How I approached it
- 01
Used dynamic event routes so each listing has a shareable, indexable destination.
- 02
Separated event and booking persistence into dedicated MongoDB models.
- 03
Added API routes for the event collection and individual event lookup instead of embedding catalogue data in UI components.
- 04
Kept the primary flow deliberately short: explore, inspect, book.
Technology