Independent · Personal
A wedding website with its own RSVP system
The website for my wedding in July 2026: our story, the schedule, travel, and an RSVP flow built around invitation codes, plus a separate admin app to track who was coming. It's an archive now, with demo data in place of real guests.
- Role
- Sole developer
- Period
- 2025 to 2026
- Status
- Archived, with a working demo
Overview
MaKinna and I got married on July 11, 2026. I built our wedding website myself, mostly because I wanted RSVPs to match how our guest list actually worked: households, plus-ones, and more than one guest list.
What guests could do
- Find their invitation with a six-character code and answer for everyone in their party at once.
- Add dietary notes and song requests with the RSVP.
- Read our story, the schedule, travel details, and an FAQ, with a countdown and an hourly forecast for the afternoon of the wedding.
How it's built
- Guest site. Next.js App Router with Tailwind CSS and MDX content. RSVPs went through API routes into Azure Cosmos DB.
- Admin app. A separate Next.js app that grouped parties by guest list, split who had answered from who hadn't, and summarized dietary restrictions.
- Song requests. They fed a songs page, and after RSVPs closed a small Python script matched each request to a Spotify track.
Archiving it
After the wedding I didn't want guests' names and answers sitting online. A one-off script exported the RSVP data to a private local backup and then emptied the database. Both apps now run on fictional demo data with no database at all, so the RSVP flow still works for anyone who tries it and no real guest appears anywhere.
Technologies
- Next.js
- React
- TypeScript
- Tailwind CSS
- MDX
- Azure Cosmos DB
- Open-Meteo API
- Python
- Vercel