Introduction

A publication workflow enables you to work at your own pace, ensuring only completed content is made available to an Intuiface experience. 

It can also be a way for a primary editor to prepare all the content, stage it for publishing, and have a different user proofread or validate it and actually publish that content live. 

Publication workflow for individual Content changes

All modifications you make in the Content panel are automatically saved in a Draft state. 

For a Group Component, or for each item in a Collection Component, there is a rocket icon that - when clicked - indicates the available publishing options:

• Stage for publishing: This will label content as ready for publishing without actually publishing it. Think of it as staging in advance of publication.
• Publish now: This will push the new content into production, making it available to Intuiface experiences.
• Discard changes: Undo all Draft updates for the selected item.

Content in either the Draft or Staged for Publish states will never appear in a running experience. Only published content will appear in running experiences.

Publication workflow for multiple content changes

Click the "Publish content changes" button in the bottom left corner to access all publishing options. Click the visible option in the pop-up,  "Publish all x changes now" to make all changes available to deployed experiences.

To access the other publishing options, click the rocket icon in the pop-up. (See below.) Use "Stage for publishing" to protect your work from the "Discard changes" option; use "Discard charges" to undo all changes in the Draft state. You can also use the "Publish now" option, which is identical to "Publish all x changes now" in the original pop-up.

Refreshing the local base copy after publishing content changes

Experiences using a base are unaware that new and/or updated content has been published. Rather, the local copy of the H-CMS base must be intentionally refreshed by either you or the experience.

Multiple methods exist for refreshing the local base copy. Some methods result in automatic synchronization with the cloud-hosted base master; others rely on you or the experience to intentionally force a refresh.