Decision 01
Information hierarchy built for guests, not designers
The site structure followed how guests actually use a wedding site, focused on the questions they were asking, not on internal taxonomy.
Decision 02
Mobile-first responsive design for on-the-go access
Most guests opened the site from their phones at check-in, on the way to the ceremony, while RSVPing between meetings. Mobile was the primary surface.
Decision 03
Typography and spacing matched the couple’s personality
Clean, modern typefaces paired with generous spacing created a sense of elegance and warmth without leaning into clichés.
Decision 04
Bilingual architecture, not bilingual afterthought
Rather than duplicating pages or adding a toggle that broke layout, I built the content model to support both languages natively, with the same structure, the same visual weight, and zero compromises on either version.
next project
