Indian wedding website builder

Plan each function and invitation separately

Start with the celebrations your family actually plans to host. A mehndi at home, sangeet in a hotel, and reception at another venue need different directions, arrival times, and invitations. Traditions and event sequences vary; your website should describe your plans rather than prescribe a standard wedding format.

Several wedding builders support multiple events. The useful test is whether your setup makes each guest’s invitation clear and produces the separate headcounts your vendors need. In Duva, maintain one roster and choose the events each guest is invited to.

• Every function is its own event. Haldi, mehndi, sangeet, baraat, ceremony, and reception each get their own time, venue, and details — not one lumped-together date.
• Different guests per event. Invite everyone to the reception but keep the mehndi to close family. Each event has its own guest list.
• A dress code for each. White for haldi, colorful for mehndi, formal for the reception — every ceremony shows its own attire note.

A schedule that builds itself, one ceremony at a time

You enter the details of each function once — the name of the ceremony, the date and start time, the venue and address, the dress code, and a short description. Duva turns that into a clean schedule page that lists every event in order, so guests can see the full flow of your celebration at a glance.

Each ceremony entry can carry its own add-to-calendar button and its own map link, so a relative flying in from out of town can drop the baraat and the reception straight into their phone and get directions to two different venues. Because the schedule is generated from your data rather than hand-built, updating a start time or a venue updates it everywhere the ceremony appears — the schedule page, the RSVP flow, and any reminder you send.

• Per-ceremony times. Haldi at 10am, sangeet at 7pm the next evening — each function shows its own start time and date.
• Per-ceremony venues. Different halls, gurdwara, banquet, hotel ballroom — each event links to its own map and address.
• Add to calendar. Every ceremony has a one-tap add-to-calendar so out-of-town family never miss a function.

Example: give guests a usable sangeet page

Illustrative wording for fictional couple Priya and Arjun: “Sangeet — Friday, October 16, 6:30 pm. Example Hotel Ballroom, 100 Example Road. Dinner at 7:00 pm; dancing follows. Wear festive attire you can move in. Please arrive through the north entrance.” Replace every placeholder with your confirmed plans.

Add the venue address, arrival time, meal timing, and any transport or accessibility notes. Put hotel and airport details on the Travel page. Assign sangeet invitations only to the guests invited to that function, then preview a sangeet-and-reception guest and a reception-only guest before sharing the site.

Check your written descriptions as well as the interface language. If your family needs Hindi or Gujarati explanations, provide those details and have a trusted speaker read the final guest page. The standalone party RSVP link currently uses English.

Before you share: check two different guest invitations

Use a fictional example while planning: Priya and Arjun invite the Shah household to the sangeet and reception, and their colleague Maya to the reception only. Both invitations need a clear arrival time and venue; only the Shah household should have a sangeet response to complete.

First, check the event assignments in your guest list. Then preview the relevant guest experience and confirm that the RSVP form offers the intended events, each with its own response. Read the general Schedule and Travel pages separately: an event invitation assignment is not a promise that all descriptive website content is hidden from other visitors. Review what you publish and use the optional site password when appropriate.

• Confirm the arrival details. Check the full address, entrance, parking or shuttle instructions, and local start time for each venue.
• Check the response choices. A guest invited to two functions needs two separate response choices; a reception-only guest needs the reception choice.
• Review each household. Check names and event assignments for every invited person before sending a household RSVP link.

Built for the traditions you actually follow

Duva uses the real names of your ceremonies rather than forcing everything into "rehearsal dinner" and "reception." Whether your family celebrates a Hindu wedding with the pheras under the mandap, a Sikh Anand Karaj in the gurdwara, a Nikah, a Jain ceremony, or an interfaith fusion of two traditions, you name each function what your family actually calls it and the site respects that.

That accuracy matters for guests, too. When a relative sees "Anand Karaj — 9:00am, head covering required" or "Mehndi — women and close family," they know exactly what they are attending and how to show up prepared. You are not translating your own wedding into someone else’s template.

• Hindu. Haldi, mehndi, sangeet, baraat, and the wedding ceremony with the pheras, each named and scheduled as its own event.
• Sikh. An Anand Karaj at the gurdwara, with the day-before functions guests need to plan around.
• Muslim, Jain & fusion. Nikah, walima, Jain rites, or an interfaith blend — use the ceremony names your family uses.

Travel and logistics for family flying in from everywhere

At an Indian wedding, a big share of the guest list is traveling — cousins from another city, aunts and uncles from India or the UK, college friends coming in for the weekend. A dedicated Travel page lets you publish hotel room blocks, the nearest airport, shuttle details, and directions to each venue in one place, so you stop answering the same logistics questions in twenty separate group chats.

The website is multi-page by design — Home, Schedule, Travel, Gallery, Registry, FAQ, and Our Story — so there is a natural home for everything guests need. Add an FAQ entry about parking at the reception or whether kids are welcome at the ceremony, and it is answered once, for everyone.

• Travel page. Hotels, airports, shuttles, and venue directions collected in one place for out-of-town guests.
• Custom address. Share one clean link — your own withduva.com address — across every invitation and save-the-date.
• Gallery, registry & story. Multi-page site with room for your photos, a registry, an FAQ, and how you two met.

In English, Hindi, or Gujarati

Choose English, Hindi, or Gujarati for the wedding-site interface. Review the exact page you will share and write your event descriptions and travel notes in the languages your guests need. The standalone party RSVP link currently uses English.

• Site interface languages. Choose English, Hindi, or Gujarati and preview the guest-facing page.
• Write useful guest notes. Provide your own attire, venue, and travel information in the languages your guests need.

Guests RSVP to each event, and you keep a real headcount

The website is only half the job — you still need to know who is coming to what. Duva collects RSVPs per ceremony, so a guest can accept the sangeet and the reception while declining the early-morning haldi, and your dashboard tracks a separate attending count for every function. That is the number your caterer, your venue, and your sangeet coordinator actually need.

Guests can respond right on the website by looking up their name, or from a browser link delivered by SMS or WhatsApp — no app to download and no account to create. Households RSVP for their whole party in one go, so a family of five is one clean response, not five loose ones. And optional password protection keeps the whole site private if you would rather it not be public.

• Per-event headcounts. Separate attending / pending / declined counts for haldi, mehndi, sangeet, ceremony, and reception.
• Name-lookup RSVP. Guests find themselves by name on the site and respond — for their whole household at once.
• Optional password. Keep the site private with a passcode you share only with invited guests.