I would need some advice on how to setup our editorial/translation workflow.
Our website is in 4 languages; English as the source language, plus other 3 (fr,de,it)
We have 3 roles:
- English editors, creating the source content
- Translators, working on all other languages, using TRADOS
- Moderator, providing QA, adjusting HTML and formatting, and publishing
The ideal workflow (when no exception occurs) would be:
- Editor create the first draft, marks it as “ready for review”
- Moderator fixes formatting, and marks it as “ready for translation”
- Translator Exports to XLS, translates and upload back
- Moderator performs last QA checks and publishes
The content structure of our 4 languages is 100% the same. For this reason, if compatible with the workflow, we would like to use ENTITY Fields translations rather than node translation.
the main requirements are therefore:
- Entity translations to avoid duplicating metadata, share fields and images when translating
- Some Workflow, to communicate change of status between actors
- Translation interface, to allow translator export/import their translation, and have an overview of the status of translations
- Revisions, to allow creating a workflow on a new Draft after a first version has been published already
If the combination of these 4 requirements is not achievable for incompatibility, the one we could possibly compromise on would be Revisions (but obviously it would be a big sacrifice we'd prefer to avoid).
We tried the module Workbench, but it doesn't seem compatible with Entity Translations.
We are investigating the combination of Entity+Workflow+Revisioning+TMGMT but it's very complex to setup and we couldn't find the right mix yet.
Before I spend more sleepless nights on this, how are other Sites managing this? is there any best practice / experience that can be shared?
thanks
Comments