How to Share Wedding Details Online
Wedding details do not get lost because couples forget to send them. They get lost because they are sent in pieces — a date in one message, a hotel tip in another, a schedule change buried above forty replies. One link that always shows the current version fixes almost all of it, and it costs nothing to set up before the invitations go out.
Why a group chat loses the details
A group chat is a stream, and a wedding is a reference. Guests do not want to scroll for the ceremony time; they want to check it on the tram on the way there.
Three failures repeat in every planning season. Someone was never added to the chat and never received anything. A change was posted, but the old message is still above it and reads as current. And the guests who are not fluent in the chat's language quietly stop reading it and ask one relative instead — which turns that relative into your support desk.
What belongs on the site, and what does not
Keep the site to the things a guest needs in order to show up and decide something.
- When and where: date, ceremony time, venue, and how to get in.
- The shape of the weekend: welcome drinks, ceremony, dinner, day-after brunch.
- Travel and stay: the nearest airport or station, hotel suggestions, parking, shuttles.
- Dress code, in one sentence a guest can act on.
- The RSVP, with anything you genuinely need from them.
What to leave off: the budget, the seating plan, family logistics, and anything you would not want a colleague or a distant cousin to read. A wedding site is a semi-public document even when it is link-protected.
Put the link where guests will look for it
The invitation is the natural place. One line — "All the details, and your RSVP: your personal link is on the card" — plus a QR code covers both the guests who type and the guests who scan.
After that, send the link the way each part of your list actually communicates: a message to the friends, an email to colleagues, a printed card for the relatives who do not use either. What matters is not the channel; it is that every route ends at the same page.
Guests who do not share your language
This is where a shared link either works or quietly fails. Sending an English page to a guest who does not read English is not sharing the details with them — it is delegating the translation to whoever in the family speaks both.
On LumiWed each guest gets their own invitation link, and that link decides the language. The same wedding, the same schedule, opened in the language that guest actually reads, with the RSVP in the same language. Guests do not create an account and do not install anything; they tap the link and the site is already theirs.
Change it once, not in four places
The real payoff arrives when something moves. A shuttle leaves twenty minutes earlier, the welcome drinks change venue, the dress code needs a sentence about the church.
Edit the site once, and every guest who opens their link sees the current version — the ones who were added last week included. There is no message to re-post, no chat to correct, and no guest still reading a version you stopped meaning three weeks ago.
FAQ
How do I share wedding details online?
Send each guest a personal link. It opens the schedule, venue, travel, and RSVP in their language, with no account and no app to install.
Should the wedding website go on the invitation?
Yes — a short line and a QR code are enough. The invitation carries the feeling and the date; the website carries the details that will change between now and the wedding.
How do international guests get the details in their own language?
On a multilingual wedding site the guest's link decides the language, so they open the schedule and travel page already translated. That is the part a group chat cannot do for you.
Resources
