You can create a release of a map or a topic to archive the content in its current state.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. Click Create Release.

   

3. In the Create Release dialog, do the following:
   1. Fill in the Release name field.
      Tip:

      We recommend making the release names consistent for each set of documentation and representative of how the document progressed from one release to another. For example, the first release for a a specific product can be called "Product A Release 1.0", then the second one "Product A Release 1.1", and so on.

   2. Optional: Fill in the Notes field.
      Note: Here you can add additional details and information about a specific release.
   3. Click Create.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. To deprecate a release, hover over the release that you want to deprecate and click Deprecate.
   Deprecated releases are listed below the active releases.

   

3. To reactivate a deprecated release, hover over a deprecated release and click Undeprecate.

1. Hover over a release and click Localize.

   

2. From the Job type drop-down menu, select a localization package type.
3. For XLIFF packages, do the following:
   1. Fill in the Project Notes field for the localization team.
   2. Optional: If needed, modify the Manager field.
   3. In the Pick Target Locales field, add target languages.
   4. Optional: If you want to include existing translations, select the Include existing translations check box.
4. For Media packages, do the following:
   1. Fill in the Project Notes field for the localization team.
   2. Optional: If needed, modify the Manager field.
   3. If you are localizing the released content for the first time, from the Include field, select All Media.
   4. If you have already localized the released content, from the Include field, select Only Changed Media.
   5. In the Pick Target Locales field, add target languages.
5. For Source packages, do the following:
   1. Fill in the Project Notes field for the localization team.
   2. Optional: If needed, modify the Manager field.
   3. If you are localizing the released content for the first time, from the Include field, select All Resources.
   4. If you have already localized the released content, from the Include field, select Only Changed Resources.
   5. In the Pick Target Locales field, add target languages.
6. For XTM packages, do the following:
   1. Fill in the Project Name field.
   2. In the Pick Target Locales field, add target languages.
   3. If you are localizing the released content for the first time, from the Include field, select All Resources.
   4. If you have already localized the released content, from the Include field, select Only Changed Resources.
   5. From the Customer drop-down menu, select a relevant option.
   6. From the Template drop-down menu, select a relevant option.
7. Click Save.
8. For XLIFF, Media, and Source packages only:
   1. Click Download Localization Package to save the ZIP to your computer.
   2. Send the downloaded file to your localization provider.
   3. Once the localization is complete, upload the ZIP file with localized content back to Heretto CCMS.
      See one of the following:

      • Upload a Localized XLIFF Package
      • Upload a Localized Media Package
      • Upload a Localized Source Package

You can branch released content to edit it.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. Hover over a release and click Branch.

   

3. Click Create Branch.

   

4. Fill in the New branch name field.
5. Optional: If you do not want to switch to the new branch when it is created, clear the Navigate to new branch check box.
6. Click Create.

You can merge released content into a new or an existing branch.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. Hover over a release and click Branch.

   

3. Depending on what kind of branching operation you want to perform, select Create Branch or Push Changes.

   • If you want to push the release to a new branch, choose Create Branch.

   • If you want to push the release to an existing branch, choose Push Changes.

4. If you chose to create a new branch, select a name for the branch by filling in the appropriate field and click Create.
   Note:

   You can navigate to the newly create branch by choosing the Navigate to new branch option in the Create Branch menu.

   

   You created a new branch that will contain an editable copy of the files from the release.

5. If you chose to push the release to an existing branch, select Merge... and continue with 3 in Merge Branches.

You can overwrite a branch with released content.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. Hover over a release and click Branch.

   

3. Click Push Changes, select Replace and continue with 3 in Overwrite Branches.

You can download the source files of the released content.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. Hover over a release and click Download.

   

You can publish released content.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. Hover over a release and click Output.

   

3. In the top-right corner, click the Publish button.
4. From the list on the left, select a publishing scenario.
5. Optional: In the Enter description field, add a meaningful description of the publishing job.
   Once you publish the document, you can see that description in the list of completed publishing jobs.
6. Set the publishing parameters.
7. Click Publish.
   The resource publishes. It may take a moment to complete.

You can preview the archived versions of your content by viewing a release.

1. In the Content Library, click a topic or a map and in the right pane, click the Releases tab.
2. Hover over a release and click View.

   

3. In the top right corner, click the Open file in editor button.

   Releases are non-editable snapshots of your content. To edit a release, branch it first. See, Branch a Release.