Skip to main content

Create a Publication Branch

With branching, you can create a copy of a publication that you can use independently or merge back into the original at a later date. This can be useful if you want to work on updating a publication while still having the original publication available.

When you create a publication branch, the original version has a gray branch symbol and any branches have a blue branch symbol with a number. The number represents the version. For consecutive branching (set in the System Settings), the numbering will also show the origin branch number in parentheses.

Left image, the publication labeled Version 2.1 has a blue branch symbol numbered 1. This means that it is the first branch of the original Getting Started publication.

Example of a label. The label is shown as a gray box next to the publication title, with the label text inside the box.
branch-icons.jpg

Right image, the branch labeled UPDATE is numbered 2 (1). This shows it is the second branch from the original publication, but is generated from the first branch. The first branch now has a gray branch symbol due to this.

To create a branch of a publication:

  1. Locate the publication in the Content Manager. Document_folder_small.png

    Content_Manager.png

  2. Select its the dotted menu ( ... ) and choose Branching and New Branch.

    Create_Branch_small.jpg

  3. To enter a Label name is optional. Leave it blank If you do not want to use it.

    Create branch dialog. It has a label field and auto-branching settings for publications and topics.

    Paligo displays the Create Branch dialog

    If you add a branch label it is shown next to the name of the publication. Labels make it easier to differentiate between the branches.

  4. Choose whether to create subpublication branches.

    auto-branching-topics-off.jpg

    • Clear the Publications box to not branch the subpublications. Changes will affect the originals.

      1. Some of the subpublications need to be updated, but you want to branch those separately instead of branching all of the them, see

      2. Reused publications (sub-publications) need no update.

      3. Does not contain reused publications (sub-publications).

    • Check the Publications box to create subpublication branches.

      To use new branches as a "work in progress" versions. Any changes made in the branches will not affect the originals unless they are merged back.

  5. Choose whether to create topic branches.

    auto-branching-topics-off.jpg

    • Clear the Topics box to not branch the topics. Changes will affect the originals.

      If there are topics you do need to change, you can branch those topics separately, see Create a Topic Branch.

    • Check the Topics box to create topic branches.

      To use new branches as a "work in progress" versions. Any changes made in the branches will not affect the originals unless they are merged back.

    Important

    Auto-branching of topics is designed for particular scenarios, and in most cases, we recommend that you leave it disabled (clear checkbox). This is because auto-branching can result in unnecessary branches of topics where reused topics would be more appropriate.

  6. Select Create.

    Paligo creates a branched version of your publication. It is shown next to the original version of the publication in the Content Manager. You can now work on the content in your branched version.

Note

If your branched publication has:

  • The same topics as the original, then the changes you make will affect those topics wherever they are used.

  • Branched topics will be independent of the originals. You can make changes to the branched topics without affecting the original version or other branches. But note that if a topic reuses a text fragment, that fragment is always reused, even in branched versions of the topic.

To find out more, see What Happens When You Create a Branch?.