Formula 1 calendars are incredibly detailed, but that level of depth can also be overwhelming. This project was built around a simple idea: sometimes fans don't need every session breakdown or nested detail, they just want a clear snapshot of the race schedule so they can stay informed without friction.

Many existing F1 calendar tools require fans to click through multiple layers of pages to understand a single race weekend. While powerful, this approach can make it harder to quickly answer basic questions like when a race is happening or how a weekend is structured - especially for fans who want clarity, not complexity.
Built an interactive calendar experience that models race weekends as structured data rather than static content. Designed the UI to emphasize chronological flow, scanability, and clear visual hierarchy, with sprint weekends and special formats clearly distinguished. Prioritized data correctness and maintainability, shipping the experience as a live, production-ready application.
Shipped a fully deployed, live product with CI/CD from GitHub to Vercel
Created a fan-friendly calendar that improves clarity without sacrificing detail
Demonstrated end-to-end product thinking: problem framing → data modeling → UX → delivery
Established a scalable foundation for future features and iteration