OurVows: Event pages and RSVP

People throwing a celebration still need a sane page online: something guests trust, a quick RSVP, and a way for hosts to see replies without living in spreadsheets. OurVows tries to be that: nice pages up front, boring data and permissions behind them.

One pretty page is easy. The work is doing it again for every event, keeping guests on a stable path without forcing logins everywhere, respecting plan limits in analytics, and keeping motion-heavy templates fast. I wanted one small system: one API shape, one web app, templates that do not rot as features land.

Nuxt handles marketing, the creator side, and public event views. Nest handles auth, events, RSVP writes, and analytics. The database sits behind TypeORM with real migrations in prod. Validation, throttling, and consistent errors stay on the server. The browser holds guest session continuity; owners get a typed creator session in the app.

It ships: public guest flows on one side, authenticated creator tools on the other. Heavy templates still respect reduced motion; API payloads stay predictable for the client. I am not putting traffic or revenue here; this note is about how it is built, not scoreboard stats.

• If the product looks simple, the API and permission model still need to be nailed early. Bolting entitlements on later hurts.
• RSVP is half UX and half data. The UI can feel light; the server still validates everything.
• A template registry only helps if adding a template is dull. If every new look risks RSVP core, the abstraction failed.
• Owning frontend and backend speeds you up until it does not. Shared error shape, sane pagination defaults, and logs you can read matter from the start.