Overview
Once a draft source space has been configured to publish to a target space and enabled for publishing you can
publish an individual page or publish all the content in a space to the target space (standalone publishing)
publish a page to the target space using Comala Publishing together with one of the Comala Document Management family of apps
Both the source space and the target space must be in the same cloud site.
Comala Publishing Cloud does not support publishing the home page of a space and cannot be used to publish blog posts.
Publishing Actions
You can choose one of the following ways to publish your content.
As a standalone publishing app to
publish pages individually (single-page publishing)
publish all pages in a space at the same time (space publishing)
Single-page publishing is enabled in a space by default when space publishing is enabled. A space administrator can choose to disable single-page publishing whilst space publishing is enabled.
Together with an applied workflow from the Comala Document Management family of apps to
Although the Comala Document Management family of apps can be applied to both pages and blog posts, Comala Publishing can only publish page content. Any blog post with a Comala workflow applied will simply be ignored by the Comala Publishing app.
The first publishing action for a page will generate a copy of the source page content and properties in the target space.
Confluence version metadata is not copied from the draft page. The first publishing action will set the page version in the published/target space is set as v.1. Each subsequent publishing action for the page will increment the target space page version.
The published content in the target space will maintain where possible the page hierarchy in the source space. However, the order of the published pages in the target space may be different from that in the source space.
Comala Publishing is designed to publish to a target space that is “empty”. Although you can set any space as a target space you may encounter some publish and sync issues if the target space was not empty (except for the space homepage) before the first space publish and sync occurs.