Example: Building a continuous delivery model around Delivery Branches

Organizing principle

In a continuous delivery model, all the content is published from the Delivery Branch. This ensures the content in a Delivery Branch is always ready to publish, and you can generate an output from a Delivery Branch at any time. You can even automate the generation of output so that content is published regularly.

Content in Delivery Branches cannot be edited directly, but you can push updates to content from other Branches to a Delivery Branch. Users work on content in one or more other Development Branches. Once the content is ready, users can push the content to the Delivery Branch.

Example workflow

The following is an example of how content is created and published using this information model:

1. Create a Product or Library for all of the content and add a Release.
2. Create Development Branches/Versions as needed, where users can work on content.

   One Development Branch is enough to start.

3. Review and finalize content within the Development Branches.
4. Once content is ready to publish, move the maps, topics, or other objects to the final status in their workflow.
5. Add one Branch/Version to the Release to act as the Delivery Branch.

   All of your content will be published from this Branch.

   Alternatively, you can clone the Development Branch to create a copy of the Branch instead of creating a new, empty Branch. You can then move the entire Branch to Delivery status without needing to push any content.

6. Push the content to the Delivery Branch.
7. Generate an output from the content in the Delivery Branch, and publish it as needed.