← Studio

Four wedding websites

Each is one self-contained HTML file — no build, no server, no persistence. Open, click through, take the parts that work.

The question: what shape should a wedding website be? These four disagree on purpose — different primary surface, different information architecture, different assumption about what the guest is actually trying to do. Not four skins.

All four are set at real Philippine destinations and follow Filipino conventions: church then a separate reception, principal sponsors, Filipiniana dress codes, GCash instead of a gift table.

RSVP

/wedding/rsvp 4 prototypes
  1. 01 ScrollfilmPrototype Casa Alta, Tagaytay ridge, Cavite · one day, one venue

    The invitation as a story you scroll — six chapters down the ridge, parallax photography, the RSVP as the closing beat rather than a form bolted on. Guest-name lookup, gallery with lightbox, FAQ.

    Surface
    Scroll narrative
    Input
    Guest-list lookup, then a row per seat
    Output
    Confirmation
  2. 02 ThreadPrototype San Isidro Parish then Balai Luna, Nasugbu, Batangas

    A fixed editorial poster beside a message thread that is the website. It refuses to have a details page: the couple send you the running order, the map and the photos, take your reply one question at a time, and answer free-text questions back.

    Surface
    Conversation
    Input
    Branching script, rewindable
    Output
    Summary card
  3. 03 The SuitePrototype Saint Paul Cathedral then Casa Consuelo, Vigan, Ilocos Sur

    Keeps the paper ritual: break a wax seal, the envelope opens, flick through a pocket of cards, then fill in a reply card as a sentence rather than a form. Principal sponsors on the invitation, a postmark and a guest pass at the end.

    Surface
    Stack of objects
    Input
    Fill-in-the-blank sentence
    Output
    Postmark and a guest pass
  4. 04 AtlasPrototype Sitio Ipil, El Nido, Palawan · three-day destination

    For a wedding people have to fly to. A hand-drawn map stays pinned beside the content and follows you down the page; details are filed by place rather than by topic, and the RSVP is a travel form — arrival, departure, which airport — not a yes/no box.

    Surface
    Map
    Input
    Travel form — dates, airport, party
    Output
    Itinerary receipt