Maintaining the page hierarchy

Overview

The published content will maintain, where possible, the page hierarchy in the source space. The hierarchy will be maintained as long as the parent page exists in the destination target space.

If the hierarchy cannot be maintained

the page is copied into the root of the destination target space
a warning message is displayed

Depending on the chronological sequence in which the pages were published, the order of the published pages in the target space hierarchy can be different from that in the source space.

The hierarchy is only maintained if the immediate parent page exists in the target space.

Space home page

Space Home page - Comala Publishing cannot publish and sync the space home page.

If publishing and sync are required for all space content, it is recommended that the content in each of the homepages in the source space and the target space simply list the content for the space, for example, using the Confluence children or page tree macro.

Changing the hierarchy in the source space

If the hierarchy is changed in the source space for a previously published page, the page publishing state is set as Out of Sync in both spaces.

Re-publishing the page will move the published page to the new parent in the target space, and the pages are set as Synced

Changing the hierarchy in the target space

If the hierarchy is manually changed in the target space, the page in both spaces still displays the Synced publishing lozenge, but the hierarchy will not change in the source space.

If a published page is not viewable in the hierarchy of the target space, the page has been published to the root of the target space. You can move the page from the root to the required place in the space hierarchy. Further publishing actions retain this new hierarchy.

Deleting a published page

Deleting a page in the source space that has been previously published adds a Removed publishing state byline to the remaining page in the target space to denote that the previously linked page has been deleted.

If required, this remaining page can be deleted manually.

But be aware that if you later create a new parent page in the source space with the same name as the previously deleted file and then publish the new page, it will

replace the target space page of the same name
and reflect any hierarchy changes for the page made in the source space

Deleting a page in the target space will simply set the publishing status on the page in the source page to New.

Publishing a child page without the parent in the destination space

In our example source space, the Staff Handbook page is a top-tier page and a parent to several pages.

When publishing a child page from the source space, if there is no published parent in the target space, Comala Publishing publishes the page to the root of the target space.

For example, if the first page published from the source space is the child page Staff handbook - Australasia, it is published to the root of the target space.

An on-screen warning message in the source space confirms the page has been copied to the root of the target space.

Subsequently, publishing the parent page successfully publishes the page in the target space at the same level in the hierarchy as the source space.

In most cases, the publication of the source space parent page moves the child page previously published to the root of the target space to maintain the source space hierarchy in the target space.

Comala Publishing Cloud