A wedding website has one job: answer guest questions before they become texts to the couple. Judge every section against that job and the site writes itself.
The sections guests actually use
- The essentials, above the fold. Names, date, city, venue. A guest forwarding the link to a partner should need nothing else on screen.
- Schedule. Ceremony time (and the arrive-by time, fifteen to twenty minutes earlier), reception timing, and end time — the last one matters to anyone booking a sitter or a taxi.
- Travel and accommodation. Nearest airport, drive times, two or three hotel options at different prices, and any room block codes. For destination weddings this section carries half the site's traffic.
- Dress code, translated. "Cocktail attire" means different things across families and cultures. One plain-language sentence — and a note about grass, sand, or cobblestones underfoot — prevents a hundred anxious messages.
- RSVP. The reason the site exists. Collect attendance, meal choice, and dietary notes in one form, with a stated deadline. No login, no account creation — every step of friction costs you responses you'll chase by hand later.
- Registry or gift note. Linked plainly. If you'd prefer contributions to a honeymoon fund, say so simply; guests prefer clarity to coyness.
The FAQ that saves your inbox
Write answers to the questions couples report being asked most: Can I bring a plus-one? Are children invited? Is there parking? Is the ceremony outdoors? Will there be food before the reception? Each answer should be one honest sentence. The FAQ is also the polite place to state the things that are awkward to say in person — adults-only receptions, unplugged ceremonies, no boxed gifts.
What to leave off
- The full love story. A paragraph, if you like — not a timeline with chapters. Guests skim.
- Anything you'd edit weekly. Vendor names, evolving menus, decor details. The site should be finished, not maintained.
- Surprises. The band, the sparkler exit, the midnight snack — if it's a surprise, it isn't content.
Match the site to the wedding
The website is most guests' first glimpse of the wedding's tone. It should look like the day: typography, palette, photography style. That's why Lovina generates the wedding website and the RSVP page from the same workspace as the planning tools, themed in six editorial styles — the data (schedule, venue, RSVP list) stays in one place, and the site simply renders it.