Digital Wedding Invitation

Digital Wedding Invitation is a single page that has to do the work of a printed card, a map, an RSVP slip and a gift note — while being forwarded through group chats and opened mostly on phones. It is written as an invitation rather than a landing page: no sales language, no urgency badges, and the practical answers guests actually message to ask are given their own section.
Sections, in order

Sticky navbar with a monogram, anchors and an RSVP button.
Full-bleed hero — a darkened photograph behind the couple's names in script, the date and venue, and a live countdown to the ceremony.
Verse panel on a blush band — replaceable with a poem, a quotation or nothing at all.
The couple — two round portraits with parents' names either side of an oversized ampersand.
Two events — ceremony and reception as separate cards with times, room names and a practical note under each (when doors close, when the couple leave).
Our story — a five-entry timeline written with specifics rather than sentiment.
Gallery — a six-image mosaic with tall and wide cells.
Practical things — parking and drop-off, what to wear, and a photography request that explains why rather than forbidding.
Gifts — two bank cards with copy-to-clipboard account numbers, opening with the line that presence is the gift and these details exist because people asked.
RSVP form — name, attending choice covering ceremony-only and reception-only, party size, contact, dietary and access needs, and a message field.
Guest book — three messages already received, including one from someone who cannot attend.

Design and style. Warm and unhurried: Great Vibes script over Cormorant Garamond, taupe and sage on blush and ivory, thin ornament rules, square-cornered cards and full-width photography. Countdown, copy-to-clipboard, scroll reveal and mobile menu are vanilla JavaScript. The copied account number has its spaces stripped, because a guest pasting a spaced number into a transfer form is the most common way a digital envelope fails.
Before you publish. Set the ceremony date in the countdown script and keep it identical to the hero line, both event cards and the footer — four places, one date. Replace both account numbers in the visible text and in the copy attribute; those are two separate strings and a mismatch sends money to the wrong place. The RSVP deadline appears twice, and the caterer's cut-off is the reason it exists, so keep them consistent. The form uses named inputs with no action attribute, so PageHub attaches the submit handler on publish and every reply arrives in Form Submissions with the attendance choice, party size and dietary notes attached — which is exactly the list a caterer asks for.
Best suited to weddings and receptions, engagement and aqiqah announcements, milestone birthdays and anniversaries, and any private event where guests need to reply and find the place.