Test a CMS through a multilingual editorial workflow
A completed trial plan for source content, translation, approval and handover when choosing a CMS.
Start with a real work case
When choosing a CMS, ask the future editorial team to complete an entire content workflow in a separate test installation. Record the product version, edition, extensions and roles used. A demonstrated feature may depend on an extra licence or configuration. Compare candidates under the conditions you intend to buy and operate.
The fictional company below plans ten language versions of its website. In the first pass, the team creates the German article ART-32 and prepares its Turkish version. The table sets out expected results for this trial; fill in actual findings and outstanding work for each candidate.
Completed trial plan
Step | Editorial task | Expected evidence |
|---|---|---|
Create the source | Save the German title, text, URL identifier and cover image. | Editors can find the saved article with its preview and edit it again. |
Link the translation | Create a Turkish version with its own text, URL and image alternative text. | Both language versions visibly belong to the same content; metadata and translation status can be found. |
Change the source | Change the German content from | The system or an agreed editorial step makes the need to check the Turkish version again visible. |
Try the roles | Have an author and an approver work with separate test accounts. | The author cannot perform an approval outside their permissions; the approver and reviewed version remain traceable. |
Switch languages | Switch between available versions and request a missing language. | Available links lead to the same article; a missing version follows the agreed behaviour without mislabelling the language. |
Hand over content | Export text, language mapping, references, media and alternative text, then reuse them in an agreed target model. | The article, relationships and required media files can be opened and correctly mapped in the target; gaps are identified. |
Observe the difficult transitions
Ask who notices a source change and sends the translation back for review. Drupal, for example, documents translatable fields and a flag for outdated translations. The trial must establish whether that facility fits the proposed setup and approval workflow. Visible Turkish text alone says little about ongoing maintenance. Also check which fields are shared across languages: changing an image can affect several versions.
A downloaded export starts as a file. WordPress, for example, describes a WXR export with particular content types and filters. That does not establish a complete transfer to any target system. Have the required media and relationships actually remapped during the handover trial.
Explain the selection
Repeat the relevant checks for all ten planned languages, including characters, date display and language switching. For each obstacle, record the configuration needed, remaining manual work and responsible role. Use this evidence to choose a CMS with which your editors can reliably complete the intended workflow. Extra licences and maintenance effort belong in the same comparison as the product price.
Sources
Written by
- Anna NeumannEditor for Content and Digital MarketingAnna Neumann plans and writes content on digital marketing at ASES. Her topics include search engine optimisation, content strategy and web analytics, with a focus on evaluating marketing activities and their results in a transparent way.
Read more
All articles
Software Development with ASES
Custom software, web and mobile apps