← All projects

Web / moderated media platform

Wedding Site

A bilingual wedding site with a guest photo pipeline: moderated uploads, a paged gallery with batch downloads, and an admin dashboard for RSVPs, review and event settings.

Verification notesLive at sagehenny.com/wedding · personal details replaced in the demo

View live site ↗Production site · the demo below uses fictional data

System sketch
  1. 01Guest upload (signed, rate limited)
  2. 02Pending queue and admin review
  3. 03Signed-URL gallery and downloads
Simplified data flow. Storage, database and API routes are replaced by an in-memory store in the demo.
wedding-site.demoDemo data · no backend

Runs entirely in your browser. Opens with fictional sample data; Regenerate builds fresh rows from the project's schema. Clears on refresh.Open full screen ↗

Authorization in this portfolio

The real admin dashboard is a server page behind an HMAC-signed, expiring session cookie and reads storage with the service role. In the demo the password is a published placeholder and the session is a flag in memory; it shows the review flow, not access control.

01

Operational problem

Guests take the best photos of a wedding, but those photos end up scattered across phones and group chats. The couple needed one place where guests could upload without an account, while nothing reached the public gallery until an admin approved it, and guests could still save the photos they wanted at full quality.

02

Technical constraints

Uploads come from anonymous guests on phone connections, often as large HEIC files. Storage had to stay private, the upload endpoints had to resist abuse without user accounts, and the admin area needed a real session rather than a client-side flag. The gallery had to stay responsive as photos accumulated, on mid-range phones.

03

Architecture

Next.js App Router with server route handlers in front of Supabase. A guest asks the sign route for a one-time signed upload URL, uploads straight to a private bucket under a pending path, then calls complete, which validates the object and records it as pending. Public gallery and download routes only resolve approved rows and redirect to short-lived signed URLs with image transforms for thumbnail and medium sizes. The admin dashboard is a server component behind an HMAC-signed session cookie and reads with the service role. Event details and schedule live in a settings row validated with Zod.

04

Implementation

Sign and complete are rate limited per hashed IP (sign also against a database count), and they check type, size and uploader name before any storage write. Admin login is rate limited and issues a versioned, expiring HMAC-SHA256 session compared in constant time; the old unsigned cookie is never trusted. Review approves, rejects or removes uploads and tracks views and downloads per photo. The gallery pages a 4×4 grid with swipe, a view-all overlay that windows its images with a shared IntersectionObserver, a lightbox that only fetches the original after a short dwell, and a 20-photo selection for batch saving. Saved copies have their EXIF and XMP dates rewritten byte-for-byte so they appear first in the guest's photo library. The portfolio demo runs these components against an in-memory store: same validation, limits and review states, with no network.

05

Testing

The source has unit tests for signed admin sessions, the photo selection store and the EXIF date rewrite. In this portfolio the demo is covered by a browser smoke test that generates data, uploads a photo, approves it in the admin and checks it reaches the gallery. Supabase policies, storage transforms and the production rate limits were not exercised here.

06

Current status

The site was built for a real wedding. The demo replaces the couple's names, contact details, payment QR code, registry link and photos with fictional placeholders, and the RSVP form is paused in the source as it is here. The production site is live again at sagehenny.com/wedding; unlike the demo, it shows the real event.

Project links

Public demo and source links have not been approved for this portfolio.

Continue exploring

All case studies →