Writing · Journal

Building a wedding website for an Indian wedding

An Indian wedding runs across several functions over several days, and the guest list changes for each one. A wedding website built for it treats every function as its own event with its own venue, timing and invited list, rather than flattening the week into a single date on a page.

Most wedding website builders were designed around one ceremony and one reception on a single afternoon. An Indian wedding rarely fits that shape. A Mehendi on Thursday, a Sangeet on Friday, the ceremony itself at an hour chosen by the family priest, a reception two days later in a different city. Each function has its own venue, its own dress code, its own start time, and its own guest list.

Force that into a template built for one date and you end up publishing a page that is wrong for most of the people reading it.

Start from the functions, not the date

List every function before you think about design. For each one, write down the venue with a map link, the date, the time guests should actually arrive, and who is invited. That last column is the one that changes everything downstream.

Your colleague invited only to the reception should not open your site and read three paragraphs about a Haldi they were never invited to. Your cousin flying in for the whole week should see all of it. The same URL has to answer both people correctly.

Decide who can see the site at all

A wedding website is not a marketing page, and it carries information you would not post publicly: home addresses, a family phone number, the hotel where relatives are staying, the exact hour a house will be empty.

Decide early whether the site is open to anyone with the link or restricted to invited guests. An invite-only site means each guest opens a link tied to them, sees the functions they belong to, and answers for themselves. It also means you can change a venue at eight in the evening and know that everyone who needs the update will see it.

Write for the guest who has never been to a wedding like yours

A guest unfamiliar with the traditions will not know what to wear to a Haldi, whether food will be served at the Sangeet, or how long a ceremony runs. Two sentences per function fixes that, and it saves your family a hundred repeated phone calls.

Include the things people actually ask: parking, whether children are welcome, what time the event realistically starts as opposed to the time on the card, and who to call on the day.

Collect the answers in one place

Every function needs its own yes or no. A guest invited to four functions may be able to attend two. If your site collects a single yes for the whole wedding, you are back to counting plates in a spreadsheet and chasing people on WhatsApp.

The same applies to photos afterwards. A shared drive link decays within a month, and the good pictures end up scattered across a dozen chat threads. One private gallery attached to the site keeps them together and lets guests find themselves in it.

What to have ready before you build

Function names, dates and venues. A rough guest list split by function. Two or three photographs you like. Names and numbers for the two people who will handle questions on the day.

That is enough to publish something useful. Everything after that, the story of how you met, the travel notes, the registry, can land in the weeks that follow. Guests need the logistics first.