Separate content from layout
Store headings, labels, policies, metadata and reusable content as structured fields. Avoid designs that depend on one English sentence length or embed essential copy inside images. The same content model should support different reading directions without duplicating business truth.
Design for right-to-left behaviour
Navigation order, arrows, progress indicators, forms, tables and mixed-script values need explicit RTL review. Test components with representative Arabic-length content early; a global CSS direction switch is not a complete interaction design.
Define language ownership
Decide who approves terminology, updates both languages and handles content that is temporarily available in only one language. Record verification dates for legal, commercial and operational statements so stale translation is visible.
Protect URLs and discovery
Choose a durable language URL strategy, canonical and alternate metadata, sitemap rules and internal linking before publishing. Translated pages should have their own useful intent—not become duplicate shells that search engines or customers cannot distinguish.
Test the operating journey
Validate enquiry, booking, payment context, validation errors, email or WhatsApp handoff and admin records in both languages. A bilingual public layer is incomplete if the team receives context it cannot identify or action.
Apply this to a real system.
Bring the context and we will identify the useful first decision.
Request a Direct Revenue Review