Our Doha WordPress development follows a methodology designed for Arabic-first, bilingual websites: (1) Requirements and planning (week 1): understanding the Qatari context. Business requirements: what the website needs to achieve — lead generation, information delivery, eCommerce, or brand building. Qatari requirements: Arabic as the primary or co-primary language, specific Arabic design expectations, and any government or regulatory requirements. Content planning: bilingual content strategy — what content exists in both languages, what's Arabic-only, what's English-only, and how translations will be managed. Arabic content: whether new Arabic content needs to be written or existing content needs to be translated. Translation workflow: defining who translates, who reviews, and how content updates trigger translation updates. Site architecture: defining the site structure — pages, sections, navigation, and content types. Arabic IA: potentially different from English — Arabic sites sometimes prioritising different navigation items or content sections. URL strategy: /ar/ and /en/ prefixed URLs, or subdomain-based (ar.example.qa, en.example.qa). (2) Arabic design (weeks 2-3): designing for RTL from the start. RTL-first design: designing the Arabic version first, then adapting to English LTR — not the other way around. The approach: ensuring Arabic design is the primary consideration, producing better Arabic UX than the typical "English design mirrored" approach. Arabic typography: selecting Arabic web fonts — tested across browsers and devices for readability. Font pairing: Arabic and English fonts that complement each other (e.g., Cairo for Arabic paired with Inter for English — similar geometric sans-serif characteristics). Arabic responsive design: mobile-first Arabic — navigation, forms, and content layouts working correctly in Arabic on mobile devices. Arabic mobile: specific challenges including Arabic text input on mobile keyboards, RTL carousel/slider behaviour, and Arabic-specific form validation (Arabic characters in name fields). Design system: creating a bilingual design system — components that work correctly in both Arabic RTL and English LTR. Colour: considering Arabic cultural associations (green with positive connotations in Islamic culture). Design review: Arabic native speakers reviewing every design screen — catching RTL issues that non-Arabic designers miss. (3) WordPress development (weeks 3-5): building the bilingual site. Theme development: custom WordPress theme — not a purchased theme with RTL stylesheet. Custom theme: built with Arabic RTL as a core requirement, not an adaptation. CSS methodology: logical properties (margin-inline-start instead of margin-left) where possible, enabling CSS to adapt to text direction automatically. WPML integration: bilingual content management — Arabic and English content managed side-by-side. WPML configuration: language switcher placement, slug handling (Arabic vs. transliterated slugs), and string translation (theme strings translated for Arabic interface). Content types: WordPress custom post types for structured content — team profiles, services, projects, testimonials, and FAQs. Each content type: supporting bilingual content through WPML, with Arabic and English versions linked. Forms: Contact Form 7 or Gravity Forms configured for Arabic — RTL form layout, Arabic field labels, Arabic validation messages, and Arabic email notifications. Qatari-specific: phone field with +974 prefix, Qatar municipality dropdown, and Arabic name field supporting Arabic characters. Performance: WordPress performance optimisation — caching (WP Rocket or W3 Total Cache), image optimisation (WebP conversion, lazy loading), and database optimisation. Arabic performance: Arabic web fonts loaded efficiently — subsetting if possible, preloading for above-the-fold text. Security: WordPress security hardening — strong passwords, two-factor authentication, file permissions, database prefix change, XML-RPC disabled, and security plugin (Wordfence or Sucuri). Qatari hosting: WordPress hosted on servers with good connectivity to Qatar — Middle East cloud regions (AWS Bahrain, Azure UAE) or Qatari hosting providers. (4) Content population (weeks 4-5): entering bilingual content. Arabic content: professionally written Arabic content — not machine-translated. Arabic web writing: specific conventions for formal (فصحى) vs. colloquial Arabic, appropriate formality level for the business type, and engaging Arabic web copy that reads naturally. English content: clear, professional English content — matching the Arabic content in quality and coverage but not necessarily word-for-word translation. Image and media: professional photography and graphics — with Arabic text in images where needed (infographics, banners, and promotional graphics). Arabic media: images with Arabic text properly typeset — not just Arabic overlaid on English designs. Content entry: systematic bilingual content entry — each page completed in both languages before moving to the next, ensuring consistency. Content review: Arabic content reviewed by native speaker, English content reviewed for accuracy and tone. (5) Testing and launch (weeks 5-6): ensuring bilingual quality. Arabic testing: comprehensive Arabic testing — text rendering, RTL layout, Arabic form submission, Arabic search, and Arabic navigation. Testing devices: mobile (iOS and Android — Arabic interface), tablet, and desktop. Arabic browsers: Chrome, Safari, and Firefox all rendering Arabic differently — testing across all major browsers. Bilingual testing: language switching (seamless switching between Arabic and English on every page), content alignment (Arabic and English versions showing equivalent information), and mixed content (pages with both Arabic and English elements rendering correctly). Performance testing: page load speed tested from Qatar — targeting under 2 seconds. SEO testing: Arabic and English meta data verified, hreflang implementation confirmed, and sitemaps for both languages submitted. Launch: DNS configuration, SSL verification, and post-launch monitoring. Arabic monitoring: specifically checking Arabic rendering and functionality after launch.