Content workflow

Magnolia ships with a basic "four-eye" editorial content workflow used for page activations. An editor submits content to a workflow queue for approval. A publisher opens the work item to see what the changes were, who made them and when. The publisher decides whether to publish the modified content to a public instance.

Content staging

Content staging is the practice of publishing content to an intermediate instance (staging site) for review and test. Once the content is approved, it is published forward to production instances. Staging is useful when you need to publish large amounts of content such as a campaign that consists of many pages and assets. You can also use staging as workflow step when content needs to be user acceptance tested or reviewed for compliance.

Create a new staging instance between the author and public instance. Publish content first to this staging instance, then to production.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels