Ever
Invitation and RSVP suite, proven on a real wedding.
Private · 2026 · Personal project
What it is
Event software: personal invitation links where the link is the guest's login, RSVP with plus-ones and capacity, and an operator dashboard. The host runs the guest list from the Google Sheet they already use, synced two ways with the database, with preview, confirm, and snapshot before any structural change. First run was a friend's wedding in September 2026: 98 of 99 invitations opened, 92% of 131 guests responded, 91 parties RSVP'd on their own, and the couple needed the manual override twice in eleven weeks. On the day, over half the guest list used the site and the database never registered the load. Lighthouse 97 mobile, 100 accessibility, about $3.40 of infrastructure for the wedding month. Afterwards the code was split into shared packages, with one small app and one database per event.
Why I built it this way
The hosts are not technical, so the spreadsheet had to stay the source of truth and nothing could depend on them learning an admin panel. Real guest data set the rules: point-in-time restore and dumps before the first RSVP, guest data never in git, nothing on a timer touching the database, and each event archived to a static keepsake when it is over.
Implementation and public artifacts
Next.js, Neon, Drizzle, Apps Script, Vercel
The source repository is private. This page is a personal project record.
Thinking behind this
Architectural parallels with my research. These links do not claim that an essay historically caused a project decision.
- Business Shape Morphology
Design around the workflow that owns the constraint, including the work outside the interface.
Published artifacts and reported outcomes have different evidential limits. How to read this portfolio's evidence.