RTL is a layout problem, not a translation problem
Arabic text inside a left-to-right template produces menus anchored on the wrong side, progress indicators running backwards and form labels detached from their fields. Enabling Arabic here mirrors the whole interface — navigation, RSVP flow, schedule direction — because translated strings in an unmirrored layout are still unusable.
The civil and the traditional celebration are separate events
A mairie ceremony and the traditional celebration are frequently on different days, in different places, with different guest lists and dress expectations. Each gets its own schedule entry, location and description in both languages, rather than a single date that leaves half the guests guessing.
The henna night needs its own entry
Guests unfamiliar with it will not know whether they are invited, what to wear, or how long it runs. Treating it as a first-class event with its own time, venue and description answers all three without a group message thread.
Catering questions are easier to ask on a form
Halal requirements and other dietary needs are simpler for guests to state in a free-text RSVP field, in their own language and script, than to raise in conversation. Responses arrive in one list whichever language they were written in.
Common questions
Is the Arabic version really right-to-left?
Yes. The layout mirrors — navigation, forms, timelines and gallery order — rather than only the text direction. This is the specific thing most wedding site builders do not do.
Can guests RSVP in Arabic script?
Yes, including free-text fields for dietary needs and messages. Responses arrive in one list regardless of script.
Can we run two ceremonies with different guest lists?
Yes. Events are separate entries with their own times, locations and descriptions.
Can we add a third language?
Yes — English is a common third for these weddings, and adding it does not disturb the existing content.