ZTABS builds headless CMS solutions for Doha enterprises — Arabic-English content platforms with Sanity and Contentful. Multi-channel delivery for government portals, corporate websites, and mobile apps with native RTL support.
Doha's digital transformation — driven by Qatar National Vision 2030 and accelerated by the infrastructure and visibility of the 2022 FIFA World Cup — has exposed a fundamental content management problem. Qatari organisations operate in a bilingual (Arabic-English) and increasingly trilingual (Arabic-English-French for North African audiences) environment. Every piece of content — every government announcement, every corporate website page, every marketing campaign, every mobile app screen — must exist in at least two languages, with Arabic as the primary language. Traditional CMS platforms handle bilingual content poorly. WordPress with WPML: functional but fragile — Arabic RTL (right-to-left) rendering breaks with theme updates, translation workflows are clunky, and the plugin adds significant performance overhead. Drupal multilingual: technically capable but operationally complex — configuring Drupal's multilingual stack (Language, Content Translation, Configuration Translation, Interface Translation modules) requires senior Drupal expertise that is scarce in Doha. Sitecore and Adobe Experience Manager: enterprise-grade multilingual support but at enterprise-grade cost (QAR 500K-2M+ for implementation) — overkill for most Doha organisations. Headless CMS platforms solve the bilingual challenge architecturally. Content is modelled as structured data with language variants — Arabic and English versions of each content field, managed side by side in the editor. RTL is handled at the frontend level (Next.js rendering Arabic content with RTL layout, English with LTR — the same component adapting based on language direction). Translation workflows are native: content created in one language, translation initiated from the same editor, review and publication managed through structured workflows. And the API-first architecture means the same Arabic-English content serves the website, mobile app, digital signage, and any future channel — without duplicating content across platforms.
Doha's headless CMS demand centres on three sectors. Government and semi-government: Qatar's government entities (ministries, authorities, state-owned enterprises) operate hundreds of websites and digital services. Hukoomi (the national e-government portal) aggregates services from across government — but individual ministry and authority websites remain separate, each managed on different CMS platforms (some on WordPress, some on Drupal, some on proprietary systems built by system integrators during the 2010s). The problems: inconsistent user experience across government websites, bilingual content managed inconsistently (some sites prioritising Arabic, others English — no unified approach), and accessibility compliance gaps (Qatar accessibility requirements aligned with WCAG 2.1 but inconsistently implemented). Headless CMS for government: centralised content management serving ministry-specific frontends — consistent design system, unified bilingual content management, and accessibility built into the frontend framework. Corporate: Doha's corporate sector — QatarEnergy (the state energy company), Qatar Airways, Qatar Foundation, Ooredoo (telecommunications), and the banking sector (QNB, Commercial Bank, Qatar Islamic Bank) — operates corporate websites, intranets, customer portals, and marketing microsites. These organisations: typically running multiple CMS instances (corporate website on Sitecore, marketing microsites on WordPress, intranet on SharePoint, mobile app content managed separately). Content fragmentation: the same corporate information (leadership team, financial results, sustainability reports, press releases) duplicated across platforms, managed by different teams, inevitably diverging. Headless CMS: single source of truth for corporate content — served to all channels via API. Education and culture: Qatar Foundation (Education City — home to branch campuses of Georgetown, Northwestern, Carnegie Mellon, Weill Cornell, Texas A&M, and others) manages content across multiple educational institutions, research centres, and cultural venues (Museum of Islamic Art, National Museum of Qatar, Mathaf: Arab Museum of Modern Art — all under Qatar Museums). Each institution: separate website, separate CMS, separate content team. Shared content (Qatar Foundation brand, Doha campus information, event calendars, sustainability initiatives): duplicated and inconsistent. Headless CMS: enabling content sharing across institutions while maintaining institutional identity — a shared content layer with institution-specific frontends.
Our Doha headless CMS projects prioritise Arabic-first content architecture, bilingual workflow design, and RTL-ready frontend engineering. Arabic content modelling (weeks 1-2): content modelling for Arabic-English bilingual organisations requires specific design decisions. Field-level localisation: each content field (title, body, description, CTA text) stored as an object with language variants: { ar: "Arabic content", en: "English content" }. This is more granular than page-level localisation (where entire pages are separate per language) — enabling editors to see both language versions side by side and ensuring every field is translated. Arabic-specific fields: some content exists only in Arabic (Qatari cultural content, Arabic-language press releases for Arabic media) or only in English (technical documentation, international investor content). The content model accommodates language-specific content alongside bilingual content. Rich text in Arabic: Arabic rich text requires specific handling — bidirectional text (embedded English brand names, technical terms, or numbers within Arabic text), mixed-script formatting (bold, italic in Arabic typography works differently from Latin typography), and Arabic typography settings (line height, letter spacing, word spacing optimised for Arabic readability). We configure Sanity's portable text or Contentful's rich text with Arabic-aware rendering. CMS selection for Doha: Sanity is our primary recommendation for Doha projects. Reasons: Sanity Studio's customisability enables us to build editing interfaces that natively support bilingual content — side-by-side Arabic/English editing, language completion indicators (showing which fields are translated), and preview in both languages. Sanity's GROQ query language handles localised content queries efficiently (fetch content with Arabic fields for Arabic pages, English fields for English pages — without over-fetching). Sanity's real-time collaboration is valuable for distributed content teams common in Doha (content team in Doha, translation team potentially remote). Contentful: recommended for Doha organisations with complex approval workflows and multiple content teams — Contentful's enterprise features (roles, permissions, content approval workflows, scheduled publishing) align with the governance requirements of government and large corporate organisations. RTL frontend engineering (weeks 2-5): the Next.js frontend must render Arabic content with proper RTL layout. This is more than adding dir="rtl" to the HTML — it requires: mirrored layouts (navigation flows right-to-left, text alignment right, images and icons positioned for RTL reading flow), CSS logical properties (using margin-inline-start/end instead of margin-left/right — enabling the same CSS to work for both RTL and LTR), Tailwind CSS RTL plugin (generating RTL-aware utility classes — ltr:ml-4 rtl:mr-4), Arabic typography (font selection — we use IBM Plex Arabic, Noto Sans Arabic, or Tajawal for body text; careful line-height adjustment as Arabic text requires more vertical space than Latin), and number formatting (Arabic may use Eastern Arabic numerals ٠١٢٣٤٥٦٧٨٩ or Western Arabic numerals 0123456789 — depending on context and audience). Language switching: URL-based language routing (/ar/page and /en/page) with hreflang tags for SEO. Language detection: defaulting to Arabic for Qatari visitors (based on browser language and geographic location), with clear language switcher for manual override. Multi-channel delivery (weeks 4-6): the same content served to: corporate website (Next.js — primary channel, bilingual), mobile app (React Native or Flutter — consuming CMS API, rendering with platform-native RTL support), intranet (internal web application — consuming the same corporate content, filtered for internal audience), and digital signage (screens in offices, lobbies, and public spaces — displaying rotating content managed from the CMS, bilingual with automatic language rotation). Content workflow design (weeks 2-4): for Doha organisations with structured content operations, we design editorial workflows: content creation (author creates in primary language — typically Arabic for government, English for international corporate), translation (content flagged for translation — translator receives notification, translates within the CMS using side-by-side editor), review (language reviewer verifies translation quality and cultural appropriateness — particularly important for Arabic where formal/informal register and Gulf dialect vs. Modern Standard Arabic choices affect perception), approval (department head or communications team approves for publication), and publication (scheduled or immediate — both language versions published simultaneously to maintain bilingual consistency).
Government / Public Sector
A Qatari semi-government organisation (responsible for managing national-scale infrastructure projects, QAR 15B+ in active projects, 1,200 employees across 5 divisions) operated a Drupal 7 website that had not been significantly updated since 2017. The problems: (1) End of life: Drupal 7 reached end-of-life in January 2025 — no security patches, increasing vulnerability. The organisation's IT security team flagged the website as a critical risk — the public-facing website running on unsupported software. (2) Bilingual chaos: the Drupal site nominally supported Arabic and English, but the implementation was inconsistent. 40% of Arabic content was machine-translated (Google Translate quality — obvious to Arabic readers and embarrassing for a national organisation). 25% of English content was outdated (not updated when the Arabic version was revised). The Arabic and English versions of the site had different navigation structures (pages existed in one language but not the other). RTL layout: broken on several page templates — Arabic text displaying left-to-right, mixed-directional headings, and images positioned incorrectly for RTL reading flow. (3) Content bottleneck: the Drupal admin interface was complex (Drupal 7's content editing requiring technical knowledge of content types, taxonomy, and URL aliases). Only 3 of the organisation's 8 communications team members could use it effectively. Content publication: averaging 5-7 business days from content creation to live publication — requiring IT team involvement for formatting, image resizing, and bilingual page creation. (4) Multi-channel gap: the organisation had launched a mobile app (investor information, project updates, procurement notices) but the app content was managed separately — a developer manually extracting content from the website and entering it into a separate database. App content: perpetually 2-3 weeks behind the website. Procurement notices: sometimes appearing on the website but not the app, or vice versa — creating compliance risks (procurement regulations requiring simultaneous publication across all channels). (5) Accessibility: the existing website did not meet WCAG 2.1 AA — no alt text on images, poor colour contrast, keyboard navigation broken, screen reader incompatible. Qatar's accessibility requirements (aligned with international standards) were not being met.
We built a bilingual headless CMS platform over 10 weeks: (1) Sanity as content hub: content model designed for Arabic-first bilingual management. Content types: project (infrastructure project — name, description, status, timeline, budget, location on map, progress photos — all bilingual), news/press release (bilingual with Arabic as primary — most news consumed in Arabic by Qatari audience), procurement notice (bilingual — regulatory requirement for simultaneous Arabic/English publication — with structured fields: tender number, submission deadline, contact, documents), team/leadership (bilingual profiles of senior management), and corporate content (about, strategy, governance, annual reports — bilingual). Field-level localisation: every text field stored as {ar, en} with Sanity Studio showing both language versions side by side. Translation completeness indicator: a visual indicator showing which English fields are pending translation (or vice versa) — ensuring no content is published with missing translations. (2) Custom Sanity Studio: editing interface designed for the communications team — not for developers. Arabic-first editor: Arabic fields displayed prominently (left panel), English translation alongside (right panel). WYSIWYG preview: live preview showing how content appears on the website in both Arabic and English — editors toggling between language previews without leaving the editor. Image management: centralised media library with automatic image optimisation (WebP conversion, responsive sizing) — editors uploading once, the system handling all technical requirements. Simplified publishing: three buttons — Save Draft, Submit for Review, Publish — no technical fields, no URL alias configuration, no taxonomy management. The CMS handling all technical aspects automatically. (3) Next.js bilingual frontend: two complete frontends generated from the same content — Arabic (RTL) and English (LTR). Arabic typography: IBM Plex Arabic for body text, carefully tuned line-height (1.8 for Arabic vs. 1.5 for English — Arabic requiring more vertical space for readability). Layout: CSS logical properties ensuring all layouts mirror correctly for RTL. Navigation: Arabic navigation flowing right-to-left with culturally appropriate iconography. Maps: Google Maps configured for Arabic labels when in Arabic mode. Date formatting: Gregorian dates in Arabic format for the Arabic site; Hijri dates displayed alongside Gregorian where culturally appropriate. Performance: static generation via Next.js — all pages pre-rendered at build time. ISR: content updates reflected within 60 seconds. Lighthouse scores: 94-97 across both language versions. Accessibility: WCAG 2.1 AA compliance built into the frontend — semantic HTML, ARIA labels (bilingual), keyboard navigation, screen reader testing (in both Arabic screen readers — JAWS Arabic, NVDA Arabic — and English), colour contrast verification, and alt text enforcement (the CMS requiring alt text before image publication). (4) Mobile app integration: the same Sanity content served to the mobile app via API. Project updates, procurement notices, and news: appearing on the app simultaneously with the website — eliminating the 2-3 week content delay and the compliance risk of asynchronous publication. App content: rendered with platform-native RTL support (React Native's built-in RTL handling). (5) Procurement compliance: procurement notices modelled with structured fields ensuring all required information is captured. Publication automation: when a procurement notice is published, it appears simultaneously on the Arabic website, English website, and mobile app — meeting the regulatory requirement for simultaneous multi-channel publication. Deadline tracking: automated reminders when submission deadlines approach — both to the procurement team (to prepare for tender evaluation) and to the communications team (to update the notice if the deadline is extended).
Security: Drupal 7 end-of-life risk eliminated. The new platform: modern, maintained stack (Sanity cloud-managed, Next.js on Vercel) with automatic security updates. Zero security incidents in the first 12 months (vs. 3 minor vulnerabilities detected on the Drupal site in its final year). Bilingual quality: machine-translated Arabic content eliminated. 100% of published content: human-translated with quality review. Translation completeness: enforced by the CMS — content cannot be published until both Arabic and English versions are complete. RTL: pixel-perfect across all pages, verified on Arabic screen readers. Arabic-speaking stakeholders (including government oversight bodies): noting the dramatic improvement in Arabic content quality and presentation. Content publication speed: from 5-7 business days to same-day. The communications team (all 8 members — not just the previous 3): able to create and publish content independently. Average time from content creation to publication: 2.5 hours (content creation → review → approval → publish). Training: 3-hour training session — all 8 team members competent within the first week. The Sanity Studio interface: described by the team lead as "finally, a system that works the way we think about content, not the way a developer thinks about databases." Multi-channel synchronisation: website and mobile app content: simultaneously updated. Procurement notices: published across all channels in a single action — eliminating the compliance risk. The CTO: signing off on the platform as meeting procurement publication requirements. Accessibility: WCAG 2.1 AA: achieved across both Arabic and English versions. Accessibility audit (conducted by an independent auditor as required by the organisation's governance): passed with only 2 minor findings (both remediated within 1 week). The organisation: one of the first Qatari semi-government entities to achieve full WCAG 2.1 AA compliance on a bilingual website. Performance: Lighthouse scores from 28 (Drupal 7) to 94-97 (Next.js). Mobile load time: from 6.2 seconds to 0.8 seconds. The improvement: particularly noticeable on Qatar's 4G/5G networks, where the old Drupal site's server-side rendering added unnecessary latency. Infrastructure cost: from QAR 85,000/year (Drupal hosting + maintenance contract + security monitoring) to QAR 24,000/year (Sanity team plan + Vercel hosting). Annual savings: QAR 61,000. Development cost: QAR 290,000 (10-week build). Annual value: QAR 61,000 (infrastructure savings) + content operations efficiency (estimated QAR 180,000/year in staff time freed from content management overhead) + compliance risk elimination (procurement publication synchronisation) + security risk elimination. ROI: development cost recovered within 18 months from cost savings alone; qualitative value (bilingual quality, accessibility compliance, security) providing additional justification.
Self-hosted, open-source CMS with custom content types, role-based access, and full API control. We customize and extend Strapi for your specific workflow.
Real-time collaborative editing, portable text, image pipelines, and GROQ queries. We build custom Sanity Studios with your brand and workflows.
Enterprise-grade content infrastructure with rich content modeling, localization, and powerful APIs. We build Contentful apps and custom field editors.
Design content structures that are flexible, reusable, and future-proof — supporting multiple channels, languages, and content types.
Live preview of draft content in your frontend, editorial workflows with approval steps, and scheduled publishing.
One content source feeding your website, mobile app, email newsletters, and digital signage — structured content that adapts to every channel.
Doha's CMS market is dominated by system integrators (Ooredoo Digital, Meeza, various regional SIs) that typically implement Drupal, WordPress, or Sitecore — traditional CMS approaches with limited headless capability. International agencies (Accenture, Deloitte Digital — both with Doha offices serving government clients) offer enterprise CMS implementation at QAR 500-800/hr. Freelance developers: available but variable quality, particularly for Arabic RTL implementation (many claim bilingual capability but deliver broken RTL layouts). The gap: headless CMS expertise is rare in Doha — most agencies implement traditional CMS and lack experience with Sanity, Contentful, or Next.js. Arabic-first content modelling requires understanding of both the CMS technology and Arabic content patterns. ZTABS provides headless CMS expertise with genuine Arabic-first content architecture at rates competitive with regional agencies.
Headless CMS projects in Doha range from QAR 120,000 for a bilingual corporate website to QAR 500,000+ for multi-channel content platforms with government integration, procurement compliance, and custom editorial workflows. Regional SI rates: QAR 300-600/hr. ZTABS delivers at competitive rates — our headless CMS specialisation and Arabic content modelling experience providing faster delivery and better bilingual quality than generalist agencies.
Verified reviews from real client engagements — sourced from our public testimonial archive and Clutch profile.
My experience is throughout positive. Communication, service, the short response times and the flawless execution of a challenging topic was absolutely great. ZTABS is definitely my first choice again.
Christian Neff
Bank Software Advisory · Bank Software Advisory
Fintech
Fantastic Agency! I couldn't fault them even if I tried. They always go above and beyond to meet your expectations and always produces quality work. Thank you ZTABS.
Stephanie Kal
CEO · Beauty Finder Australia
Marketplace
It has been great working with ZTABS. They bounce off the ideas along the way. Amazing Experience.
Joel Rowe
CEO · Drill Quoter
Marketplace
We don't just contract — we ship and operate our own software. 17 products in production.
Common questions about headless CMS development for Doha businesses
Yes — and it handles it better than traditional CMS platforms. In a headless architecture, Arabic RTL rendering is handled at the frontend level (Next.js with CSS logical properties and Tailwind RTL plugin) — giving precise control over layout mirroring, Arabic typography, and bidirectional text. Traditional CMS platforms handle RTL through theme modifications that often break with updates. Our frontends are built RTL-first for Arabic, with LTR as a variant — not the other way around.
ZTABS is a remote-first headless CMS development agency serving Houston businesses — including strapi development, sanity studio, contentful integration. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Headless CMS Development in New York, NYZTABS is a remote-first headless CMS development agency serving New York businesses — including strapi development, sanity studio, contentful integration. We work with Finance & Fintech, Media & Advertising, Fashion & Retail companies in New York, NY via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Headless CMS Development in Los Angeles, CAZTABS is a remote-first headless CMS development agency serving Los Angeles businesses — including strapi development, sanity studio, contentful integration. We work with Entertainment & Media, E-commerce & DTC Brands, Gaming & AR/VR companies in Los Angeles, CA via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Development in Doha, QatarZTABS is a remote-first web development agency serving Doha businesses — including full-stack development, progressive web apps, api development. We work with Smart City & GovTech, FinTech, Energy Tech companies in Doha, Qatar via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Design in Doha, QatarZTABS is a remote-first web design agency serving Doha businesses — including ui/ux design, responsive design, custom interfaces. We work with Smart City & GovTech, FinTech, Energy Tech companies in Doha, Qatar via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
AI Development in Doha, QatarZTABS is a remote-first AI development agency serving Doha businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Smart City & GovTech, FinTech, Energy Tech companies in Doha, Qatar via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Headless CMS DevelopmentLearn more about our headless CMS development services nationwide.
Partner with ZTABS for expert headless CMS development in Doha. Get a free consultation today.
