How to Set Up Mehndi, Sangeet, and Baraat on Your Wedding Website

Most wedding website platforms have three event options: Ceremony, Reception, and Other.

Your wedding has seven events. None of them are "Other."

Setting up a proper Indian wedding website — one that actually separates Haldi from Mehndi from Sangeet, with different guest access and different RSVPs for each — requires a platform that was built for this. Here's how to do it, what to put on each event page, and what breaks when you try to force it into a Western platform.

First: map your events

Before you open any platform, write out every event you're hosting:

Pre-wedding:

• Haldi — immediate family only. Venue, timing, dress code (wear old clothes)
• Mehndi — extended family and close friends. Usually day-before or 2 days before
• Sangeet — mixed gathering, evening. Often the largest pre-wedding event
• Roka / Engagement — if not done earlier

Wedding day:

• Baraat — groom's procession. Meeting point, timing, specific roles
• Milni — families meeting at the venue. Often overlooked in website logistics
• Pheras / Nikah / Anand Karaj — the ceremony itself
• Reception — largest event, sometimes with a different (larger) guest list

For each event, you need: date, time, venue address, dress code, what to expect, and who's invited.

What you actually need from the platform

Per-event RSVP, not one universal form. If your Haldi has 60 people and your Reception has 400, those are two completely different RSVPs. Guests should respond to their specific events — not one blanket "are you coming" that creates a spreadsheet nightmare.

Guest access control per event. Your boss doesn't need to see Haldi details. Your college friends don't need the Baraat logistics. Good platforms let you assign guests to specific events and show them only what's relevant.

Different content per event. Mehndi has different logistics than the reception — different venue possibly, different dress code, different what-to-expect notes. Each event page needs its own space.

Platform reality check:

Setting up in The Curated Knot

Step 1: Add your events

From your dashboard, go to Events. Add each ceremony as a separate event. The platform has Indian ceremony types built in — you're not typing "Mehndi" into a text field that defaults to "Cocktail Hour."

Step 2: Set event-specific details

For each event, fill in:

• Date and time (separate if multi-day)
• Venue name + full address (guests will paste this into Google Maps)
• Dress code — be specific. "Traditional Indian attire" for Mehndi. "Wear something you don't mind getting turmeric on" for Haldi. "Cocktail or festive Indian fusion" for Sangeet.
• What to expect — 2–3 sentences. First-time guests at a Sangeet benefit from knowing it's an evening of music and dancing, not a formal ceremony.

Step 3: Create per-event RSVP forms

Each event gets its own RSVP. You can customise the questions per event — "How many family members are attending?" is useful for Haldi. "Dietary preference?" matters for reception dinner. "Will you be joining the Baraat procession?" is Baraat-specific.

Step 4: Assign guests to events

Tag each guest with which events they're invited to. When guests open your website, they see only their events. When they RSVP, they're responding to those specific events.

Setting up in Joy

Joy's multi-event support works, but it takes more manual work to adapt to Indian ceremonies.

Create events in the Events tab. Joy doesn't have Indian ceremony types — enter "Mehndi," "Sangeet," etc. manually as event names. This works fine.

Mark events as invite-only to enable guest-level access control. For invite-only events, import your guest list and tag guests per event. More work than it should be, but doable.

Per-event RSVP is enabled when events are marked invite-only. Guests will RSVP per event.

What Joy can't do: Hindi/Tamil support, WhatsApp-optimised sharing, Indian template aesthetic.

The content that actually reduces phone calls

Every unanswered question on your wedding website is a WhatsApp message to your parents. Here's what to put on each event page to cut those messages down:

Haldi:

• "Wear clothes you don't mind getting turmeric stains on — everything will be yellow by the end"
• What time to arrive (Haldi tends to start on time, unlike receptions)
• Whether food is served and what kind

Mehndi:

• That guests don't need to get mehndi applied — it's optional, but the artist will be there
• How long the event runs
• Dress code (most guests wear traditional Indian attire)

Sangeet:

• It's an evening of performances, music, and dancing — not a formal dinner
• Whether there's a dress code (usually festive/cocktail)
• Rough schedule if there are planned performances

Baraat:

• Where the procession starts and the meeting point
• What time it leaves (the Baraat waits for no one)
• Roughly how long it takes to reach the venue
• Who's meant to walk in it vs. who meets at the venue

Pheras / Ceremony:

• Expected duration (typically 45–90 minutes for Hindu ceremonies)
• That shoes are removed before entering the ceremony area
• Whether photography is welcome or ceremony is private

One thing most couples forget: the ceremony guide

If you have non-Indian guests or abroad-based family who grew up outside India, a brief ceremony guide on your website earns a disproportionate return.

Explain what pheras are. What the mangalsutra represents. What guests should do (sit, stand, come forward to bless the couple). That shoes come off at the mandap. That the ceremony is conducted in Sanskrit or the regional language.

Four paragraphs. Saves forty confused guests from whispering anxiously through the most important part of your wedding.

Related read

Indian Wedding Website That Works for Guests in India and Abroad

How to serve your UK/US guests and your Hindi-speaking India family from the same wedding website.

Related read

Why Joy and Zola Don't Work for Indian Weddings

Exactly where Western platforms break for multi-event Indian weddings — and what to use instead.