Wedding website builder for multi-event South Asian weddings

A Direction is more than a theme. It is a bundle of cultural references — a palette, a type pair, a hero recipe, and a set of section-variant defaults — that together evoke a specific feeling. Mehfil-nights leans into late-evening sangeet light: deep velvets, gold leaf, a serif headline you can almost hear pronounced. Haveli- courtyard pulls from Rajasthani sandstone and cooler dawn light — terracotta and ochre warmth grounded against a quiet stone palette. Monsoon-letterpress is a printer's love letter to Bengali wedding stationery, with high-contrast type and a paper-stock feel that scans on a phone the way a real wedding invitation feels in your hands.

We ship 11 Directions out of the box, each with a name a desi couple recognizes the moment they see it. Banarasi-gold leans into ceremony reds and gold metallics; coastal-mehndi pulls cooler greens for a Kerala or Konkan beachside ceremony; thali-brass moves between warm copper and ivory for a south-Indian ceremony aesthetic; chai- stains keeps the visual language soft and editorial. The Directions are not skins — they are deliberate visual systems, designed by someone who has actually been to enough mehndis to know the difference between a yellow that reads "wedding" and a yellow that reads "wallpaper."

Each Direction comes with a recommended palette and type pair, but nothing is locked. Pick mehfil-nights and swap the palette to monsoon-tide if you want the velvet feel with the cooler colorway. Mix and match until your site looks like your wedding rather than a generic builder template that 10,000 other couples also picked this season.

Every ceremony in your wedding gets first-class treatment on the site. Mehndi page with its own hero photo, its own schedule, its own dress code ("wear something you do not mind getting henna on"), its own venue, and its own map link. Sangeet page with a separate hero and a separate run-of-show that lists the family dance items. Haldi page with its own everything. Ceremony page. Reception page. Welcome dinner if you are hosting one. Farewell brunch if the out-of-town guests are staying long enough. Each event is a real page, not a row in a single "events" table that a generic builder shoves into one accordion.

The schedule on each event page reads from the same canonical data that powers your dashboard, your seating chart, and your RSVP. Edit a start time once and it updates everywhere — the site, the schedule card on the homepage, the per-event RSVP page, and the guest's personalized journey view. No more copy-pasting the mehndi start time across three places only for the website to lag a week behind because someone forgot.

You can show or hide events per guest. The kids' mehndi page is visible only to family. The reception is visible to everyone. The intimate haldi for immediate family is gated to that guest segment, so the work-friend who clicks the link does not see a ceremony they were not invited to. Guests open one link and see only the events on their invitation — same site, different slices, built on the same per-event invitation graph that powers the RSVP.

The visual builder ships with 15 section types organized into 6 groups: hero, story (how we met, family, traditions), events (per-ceremony cards and schedules), logistics (travel, accommodations, parking, maps), guest (RSVP, FAQ, registry, gift notes), and closing (gallery, hashtag, save-the-date, thank-you). Each section type ships with multiple variants — the hero alone has six layouts ranging from full-bleed editorial to centered formal to split-image-and-text — so the same page on two different weddings can feel meaningfully different without leaving the builder.

Every change pushes onto a 50-item undo stack. Redo brings it back. The auto-save runs every few seconds against a draft state stored separately from the published site, so you can be in the middle of redesigning the mehndi page at 11pm and your guests still see the previous version on the live site. When you are ready, hit Publish and the draft replaces the live state atomically — no intermediate broken state where half the page has loaded the new design.

The builder feels editorial rather than enterprise. The section settings panel slides in from the right with the same atelier burgundy and gold language as the rest of the workspace. Drag a section to reorder it. Click into a section to edit its content, variant, and per-section style overrides. Click outside to commit. Preview mode renders the full live site in a panel beside the editor, so you see the change land in context — not on a generic desktop preview that has no relationship to what a guest will actually see on their phone.

South Asian wedding websites are often opened from a phone in WhatsApp first. Maybe in a browser later. Often never on a desktop. Anvaya is built mobile-first: templates, section variants, and Directions are designed to stay legible at narrow phone widths. The desktop rendering still matters, but the first target is a guest tapping a link from a message thread and finding the right event details quickly.

Accessibility is not an afterthought. Every template ships with WCAG AA contrast ratios across the palette swatches; if you swap to a palette that would drop a token below AA, the editor warns you. Section headings are real H1/H2/H3 elements in semantic order. The RSVP form has proper labels, aria-described-by hints, and works fully with a keyboard and a screen reader. The schedule cards use real time elements with datetime attributes so accessibility tools can read them out correctly.

The reading flow works in multiple languages on the roadmap — critical for the cousins in Bangalore who would rather read the mehndi page in Hindi than English, and the older relatives in London who would rather read in Gujarati. The current site renders in English by default; the i18n scaffolding is in place so we can ship the rest as we go. Every page has a real lang attribute and proper text direction so screen readers and translation tools handle the content correctly.