dotCMS Content Contributor Workflow
We need to make use of a standard workflow to enable Content Management Team to create the site themselves and launch quickly, while still ensure the everything is checked to a certain level of quality.
With the new dotCMS structure, Authoring environment is own by CM team and contains only live contents. That means developers don't work on this instance unless there are special requests. Below are the suggested steps in the workflow.
Description | Actor | Note | |
---|---|---|---|
1 | Templates, content types, sample sites/pages are created and tested in Sandbox environment, and then pushed to Authoring | Development and QC Team | |
2 | CM Team member create new site or page using above templates and content types | CM Team | |
3 | Once the site or page is completed, it is sent to Reviewer for proofreading and approval | CM Team Manager | |
4 | If site or page above is approved, it can be published to Live Environment | CM Team | |
5 | Once the page or site is live, contents can be exported into CSV file and sent for Translation | CM Team | Investigating on possibility to export content by site/page. We might need support from dotCMS on this feature. |
6 | The CSV file above is translated to requested languages | Translator Coordinator | |
7 | Once the translated CSV is done and sent back, it can be imported into dotCMS to create language versions | Translator Coordinator or CM Team | |
8 | Translated site or page above is sent to Translator Coordinator for Proofreading and Approval | Translator Coordinator | |
9 | Translated site or page is sent to Reviewer for approval | CM Team Manager | |
10 | Once approved, translated site or page can be pushed to Live Environment | CM Team |