Skip to main content
Okhare Paul — Portfolio©2026
000
Back

Case study · 10 / 12

Mary & Paul

A cinematic wedding website

Fig. 10 — Mary & PaulA curtain lifts. After that, the scroll tells the story.
About the project

My own wedding website: a full-stack Next.js app with a scroll-told story, a WebGL photo wall, RSVP and a guestbook on Supabase, and a private admin ledger for the day itself.

This is the one project where I was the client, and the hardest to please. It had to feel like the opening of a film and still do a real job: tell guests where to be, take their replies, and keep their messages. So it is two things at once. The front is cinema. A burgundy curtain lifts on a hero that is already composed underneath, the story unfolds as you scroll, and the gallery is a wall of photographs you drag through, drawn in WebGL. The back is a proper application: validated forms, a database that the public key can barely touch, and an admin page where replies are counted and guestbook notes are approved before anyone sees them.

Main features

What it does

  1. 01Lifts a curtain on the hero, which is already in place beneath it
  2. 02Counts down live to the ceremony
  3. 03Tells the couple's story on a timeline driven by the scroll
  4. 04Opens a drag-to-explore wall of photographs, drawn in WebGL
  5. 05Takes RSVPs and guestbook notes through validated forms
  6. 06Shows only the guestbook notes that have been approved
  7. 07Gives the couple a private ledger to review replies and export them
  8. 08Switches to a night palette, with its own photograph, before the first paint
Approach

How it was solved

  1. 01Composed the hero under the loader from the first paint, so the reveal uncovers a finished page and nothing jumps
  2. 02Wrote the gallery in hand-written WebGL beneath real, focusable buttons, with plain images as the fallback
  3. 03Kept every database write on the server: forms are validated with Zod inside server actions, and new notes are always saved as unapproved
  4. 04Locked the database with row-level security, so the public key can read approved notes and nothing more
  5. 05Signed the admin session with HMAC-SHA256 in an httpOnly cookie, and compared passwords in constant time
  6. 06Guarded the CSV export against spreadsheet formula injection
  7. 07Stripped location data from every photograph before upload, then served them from a CDN at the right size
  8. 08Kept all timing in one motion file, so every animation on the site speaks the same language
  9. 09Regenerated the home page every 30 seconds, and at once when a note is approved
  10. 10Raised the reference palette's grey until it passed contrast rules, and wrote a script that re-measures it
Results

Live for guests on Vercel. Layout shift recorded at 0.0013, text contrast at 9.73 to 1, and every layout checked from 360 to 1920 pixels.

Technologies

Stack

Languages
TypeScriptSQLGLSLCSSHTML
Front-end
Next.js 15 (App Router)React 19Server ActionsIncremental static regeneration
Motion and graphics
GSAPScrollTriggerSplitTextLenisHand-written WebGL
Forms and validation
React Hook FormZod
Back-end
SupabasePostgreSQLRow-level securityHMAC-signed sessions
Styling
Tailwind CSS v4CSS ModulesDesign tokensnext/font
Media
ImageKit CDNsharpResponsive srcset
Testing and delivery
PlaywrightESLintVercelGitGitHub

The case study is the how. The site is the proof.

Next project · 11 / 12Delivery Drone