For the invitation page itself
One page has to carry the welcome, the timings, the travel, the dress code and the reply button without reading like a terms document. Here is a model invitation page, top to bottom, with original passages to borrow.
Guests do not tour a wedding site. They open the link, look at the first screen, and decide there and then whether the day will be easy to attend. So the invitation page carries the essentials in a fixed order: who and when, then what happens, then what they need to do.
What makes an invitation page feel strong is sequence, not decoration. Every section should answer the question the one before it raised. Below, the page walked from top to bottom, with sample passages you can take as they are.
Names, the date, and one welcome sentence. Nothing above the fold competes with it; nothing below is guaranteed to be seen on a first open.
Date, time and full address for each venue, in short lines. This is the block people screenshot; keep it standalone, and repeat the facts on the venue sections where the map sits.
Rows, not paragraphs: ceremony, drinks, dinner, dancing. A reader should be able to trace the shape of the day in one downward scroll.
Distances from the airport or station, hotel notes, whether the day spans two venues. This section answers the questions relatives ring you about.
The name of the code plus a two-sentence translation into real terms: grass underfoot, evening chill, hats optional.
The repeated questions, answered outright, and then the reply itself: a clear deadline, what to tell you, and the button. The ask always comes last, after the information it depends on.
Original wording, invented people. Adapt freely.
Marta and Tom are marrying on 12 September, at the chapel in Grünholz and the barn directly behind it. This page holds everything we hope you will want to know, and a place to let us know you are coming.
If you are driving in the evening before the wedding, the courtyard gate sits on the north side, not the main road. Park where the marshals point; there is more room behind the hedge than it looks.
Please reply by 1 August. The caterer fixes the final number that week, and we would far rather add a plate than take one away.
How it works
Open the wedding template library and choose for legibility at arm's length on your own phone, not for the fanciest header illustration.
Write the opening block and the details rows first; they carry most of the errand. Let the AI drafter propose the travel and FAQ sections, then edit them down.
A draft is invisible to guests until you publish it, so hold the share until the invitation page is live and true.
Put the short link or QR on the paper card. If plans shift, you edit the page once and card-holders see the current version when they scan.
Questions
On the facts, yes: names, dates, venues and dress code should read the same on both. Tone can differ, and the page can hold far more. Crucially, only the page can be updated when something changes, so point guests there for anything time-sensitive.
Within the first screen or two, and again at the end of the details. On a phone, an invitation whose reply button lives somewhere further down becomes a task for later, and later quietly never happens. Put the deadline beside the button.
Yes. The whole site can be password-protected, and you share the password in the invitation message. Useful when the link will travel through group chats wider than your actual guest list.
Publish what is firm and be honest about the rest: drinks around five is enough until the band is booked, then you edit once. Guests trust a page that corrects itself; a page that contradicts the card is what erodes trust.
Once you have answered the same question twice, yes. Parking, children, arrival times, the rain plan. Written answers stop the group chat from becoming the wedding's second website, and they let you sleep on the day the details changed.
Get Started
Build the invitation page once, keep it honest, and let it do the explaining for every guest at once. Share the link and watch replies gather on their own.
