Some couples say wedding website, some say wedding page, plenty say wedding homepage — all three mean the same thing. This page answers the question underneath: what such a homepage actually consists of, which sections it has, what belongs on each one, and who is allowed to see it. Not a plan of action, a blueprint.
Protected by invitation code
Built for the phone
Ordinary homepages spread their content across menu items, each of them hiding a page of its own. For a wedding that is the wrong cut. Your guests arrive with a handful of concrete questions — when, where, what to wear, how to reply — and every click that buries an answer behind another page costs you replies. With us all sections therefore sit below one another on a single homepage, and the menu at the top jumps to them instead of loading something new.
What elsewhere would be a menu item with an address of its own is a section of the same homepage here. The navigation stays visible and marks along the way which section your guests are currently reading.
Because everything sits on one homepage, there is exactly one address. It fits on an invitation card, it can be spelled out over the phone, and it leads nobody onto a sub-page they cannot find their way back from.
Empty sections do not appear. A couple who would rather not write a story has no empty block on the homepage, simply one section fewer.
Most of your guests read the homepage on a phone, standing up, between two appointments. The order of the sections follows that and not what looks good at a desk.
What a couple begins with and how such a homepage comes about is not covered here but next door: Create a wedding website
Seven sections, in the order your guests meet them on the way down. Two of them belong to a package, the other five you can set up and look at without payment details.
Your names, the date, one large picture and the running countdown. This section answers in two seconds whose homepage this is and when the celebration happens — nothing more is asked of it.
Belongs here: names, date, one picture. Not here: times, addresses, explanations.
A picture and a short paragraph for each of you. For guests who only know one half of the couple — half the family, in other words — this is the section that introduces the other half.
Belongs here: who you are, in a few sentences. Not here: the whole relationship, that is what the next section is for.
A run of moments with a date, a text and a picture: the first meeting, the move, the proposal. The section guests linger over longest, and the only one where you really get to tell a story.
Belongs here: moments that add up to a story. Not here: inside jokes only four people understand.
The course of the day as a timeline — ceremony, reception, dinner, dancing. For every point a time, a place and a picture. This section is the most-read part of any wedding homepage, because it answers the question everyone really has.
Belongs here: time, place, what happens. Not here: buffers and preparations that concern only the two of you.
Question and answer, as often as you like. Dress code, parking, children, accommodation, gifts. Every question you answer here is one message fewer on your phone.
Belongs here: anything you have been asked three times. Not here: answers that apply to one single guest.
A picture section your guests can upload to as well, with a notification when new pictures arrive. Engagement photos beforehand, the evening from a hundred angles afterwards.
Part of the package. The section only appears on the homepage once you have switched it on.
The form guests accept or decline with, and in which you can ask questions of your own: meal preference, arrival, accommodation, favourite song. The answers gather in one place with you, not in your inbox.
Part of the package. Shown only to guests who arrived with their invitation code.
What can be set up without payment details and what belongs to a package is written out in full on the cost page. All prices at a glance
A wedding homepage is not a blog. It carries addresses, times and the names of your guests, and none of that needs showing to the whole world. That is why the homepage is closed by default and opens with a code.
Every guest receives a code of their own with the invitation. Anyone who calls up the address of your homepage without a code sees no content but a field for the code, with a bot guard in front of it so that nobody can try codes out. Because each code belongs to one guest, the reply form knows who is answering.
You can make the homepage public with a switch. It is then readable without a code — sensible if you print the address on the invitation card and would rather not hand every guest a code of their own. The reply form stays reserved for guests with a code in that case, because an acceptance without a sender helps nobody.
A code that was passed on into the wrong circle is blocked and stops working. The remaining codes are untouched by that — there is no need to protect the whole homepage again.
As the couple you are signed in and need no code. You can look at your homepage in the preview whenever you like — exactly as it reaches your guests.
Some of your guests are over eighty and type addresses with an index finger. The build of the homepage takes that into account without you having to set anything.
The bar at the top edge stays put and highlights which section one is in. A tap on it jumps onward without the homepage reloading.
There are no dead ends: whoever simply scrolls down passes every section and lands at the reply form. Nobody has to have understood a menu in order to say yes.
The homepage is designed for narrow screens and grows wider on large ones, not the other way round. Pictures, timeline and form all work with a thumb.
If a time or a meeting point changes, you change it in one place. Printed cards cannot be corrected, your homepage can — and the address for it stays the same.
Part of the structure is what stays outside it. Three things get pushed onto the wedding homepage regularly although they do harm there.
Who sits next to whom is your working surface and not public information. The seating plan therefore lives in your own area and leaves it only as a print template for the room.
Who has accepted, who has not yet and who needs a room is something you see in your overview. On the homepage it would become a list guests compare with one another, and nobody wants that.
The dress code belongs in the frequently asked questions or in the schedule, not in both. Duplicate details contradict each other sooner or later, and then nobody believes you any more.
Two of the sections raised so many questions that we gave them articles of their own.
All sections stand ready from the first minute. You fill them in any order you like, see the result straight away and decide at the end whether you want to send it out.
Create a homepage for freeNo payment details, no time limit.
