Choose a content management system around who writes, who reviews and what must be published. Arabic and English are linked editorial assets, not an extra text field added at the end. Test the publishing workflow before choosing an architecture or signing a licence agreement.
Start with editorial responsibilities
List the content types: services, case studies, articles, people and downloadable resources. Define required fields, evidence and reviewers for each. Decide who may change a commercial claim, who can publish, and whether Arabic and English require separate editorial review. An editor usually does not need permission to change site-wide security or integration settings.
Specify what happens when a source page changes after its translation was published. The other version may need a review flag, not an automatic date update that makes stale copy look fresh. Drafts should remain out of public indexing, and language links must not suggest an unavailable translation is complete.
Compare capabilities with tasks, not badges
| Capability | Task to demonstrate |
|---|---|
| Content structure | Enforce required fields without manually copying pages |
| Approval workflow | Separate draft, review and publication permissions |
| Language relationships | Link equivalent content with appropriate slugs |
| Revision history | Identify who changed a claim and restore the intended version |
| Portability | Export content, media and their relationships |
| Operations | Explain updates, backups and tested recovery ownership |
A conventional CMS can suit a straightforward editorial website. A headless system may suit several delivery channels, but adds responsibility for previews, rendering and integrations. Do not purchase complexity the team will not use. A recognizable platform name is not proof of accessible authoring, secure configuration or fast delivery.
Run an editor-led purchasing trial
Ask a non-technical editor to create an Arabic service page, add its English version and send it for review. Reject a revision, correct it and publish only after approval. In an isolated trial, change a published slug and inspect the redirect, restore a previous revision and export the content.
Inspect the resulting server-rendered HTML, page titles, language links and social metadata. Meaningful images need useful alternatives; decorative images should not repeat the page text. An SEO score in the admin interface is not a reason to add hidden paragraphs or keyword-stuffed fields.
Record where the editor needed help. Developer speed is not a substitute for the team being able to repeat the workflow safely. Include an unsuccessful publication attempt, such as a page missing its required description, to verify that the guard actually works.
Estimate the cost of owning the system
Include hosting, updates, training, migration, support and editorial time, not just licence fees. Clarify domain and account ownership, export formats and the process for leaving the provider. Agree how long revisions and media need to be retained and how recovery will be tested.
A CMS enables correct publishing; it cannot guarantee a search position. Define acceptance around observable outcomes and the team’s ability to maintain them.
Discuss the scope through corporate website development, then review RTL-first design systems and data ownership before selecting a platform.
Sources and editorial status
- Google: localized versions.
- W3C: Authoring Tool Accessibility Guidelines.
- Original contribution: an editor-led CMS purchasing trial, not a sponsored platform ranking.
