This site is where I keep project writeups, music, blog notes, and things I am learning. This case study covers the contact flow, optional admin inbox, typed content, and service setup without turning it into a bigger app than it needed to be.
Architecture artifact
Sketch of the contact path and optional admin persistence - useful for keeping assumptions explicit when iterating alone.
What runs in production
Server-side Zod validation for contact and waitlist before side effects
Honeypot field plus Upstash sliding-window rate limiting on contact submissions
GitHub OAuth via Auth.js for admin routes and inbox views when configured
Optional Prisma persistence for contact and waitlist records after email sends
Playwright smoke tests on public routes, titles, and OG metadata
Tradeoffs
Managed services to keep the site small
Used Resend, Upstash, and Neon-backed Prisma integration so the site can handle contact, rate limits, and optional persistence without becoming a separate backend project.
Delivery first, then persistence
Contact action treats email delivery as the primary success path, with inbox persistence as best-effort to avoid silent form success when mail is misconfigured.
Small, reviewable changes
Incremental PRs and merge gates so each fix stays review-sized and the history stays legible when something regresses.
