Personal Wedding Website
I built my wedding website as both a personal project and a serious test of agentic coding. Designed for around 200 guests, it included custom RSVP flows, an admin dashboard, guest management tools, and a strong focus on mobile performance and reliability.
Related
Read the full write-up →Overview
This project is a full wedding website and guest management application built for a real event with roughly 200 attendees. I owned the full product: the public-facing information site, custom RSVP flows, the authenticated admin dashboard, guest management tooling, and the communication workflows needed to keep the event organized.
How It Works
- Guests use the public site primarily on mobile to view event details and submit RSVPs through a custom flow designed to be simple and low-friction.
- Behind the scenes, authenticated admin tools support guest tracking, imports, response management, and outbound email communication for planning and follow-up.
- The application uses Next.js and Supabase for the app layer, auth, and data handling, with production-minded attention to responsiveness, reliability, and operational visibility.
Technical Highlights
- Custom RSVP and guest workflows: The site goes beyond a static event page by supporting structured guest responses and the operational flows needed to manage a live attendee list.
- Admin tooling for real event operations: A private dashboard, guest import tools, and broadcast email capabilities turned the project into a lightweight event management product rather than just a microsite.
- Mobile-first reliability: Because most guests were expected to use the site from their phones, the implementation prioritized mobile UX, responsive performance, testing, and issue monitoring.
What I Built
- The public wedding site experience, including event information architecture, navigation, and RSVP submission flows.
- The authenticated admin dashboard for managing guests, tracking responses, and supporting wedding-planning operations.
- The supporting integration layer for auth, data storage, email communication, and production monitoring.
Optional Context
This project was also a serious experiment in agentic coding. I used AI heavily for implementation and design exploration, but the final quality depended on strong direction, iterative review, testing, and treating the build like a production system with real users and a real deadline.