The recommended translation workflow is designed for organizations that can wait for translations to be completed before further updates are made. If you need to make frequent updates to the source language content, you will need to take a different approach to translation, with branches for your updates.

Here, we explain how to use branching to manage your updates and keep your translations aligned with the correct versions of your content.

This diagram shows the typical process for using branches for updates while waiting for translations. You start by sending your original content for translation, then you create one or more branches for your updates. You can publish the updates in the source language but do not merge them into the original version. When the translation of the original comes back, import it into Paligo. At this stage, the translation is aligned with the version of the content that was translated (the original version). You can now send the updates for translation, either individually or by merging with the original version and then re-sending the original version for translation.

The following sections describe each stage of the process.