Translations & Localizations

This should be used when translating small amounts of content. Best when you have made changes to one or only a few components. You can select each component individually and add it to the list of items in the workflow. For more complex translations that have many levels of dependent content changes, you should consider using the Completion-Translation workflow.

In most cases you would choose to use the copy over functionality rather than synchronization. This is legacy functionality that existed before the copy over functionality. One use case is when you wish to synchronize new content across all locales (regardless if they are children, grandchildren, etc.). The synchronization allows you to synchronize content to all locales of the same language with a single workflow. This is an all-or-none workflow as the system determines which locales to include in the synchronization. You do not get to select individual locales as you do in the Translation or Copy-Over workflows. This workflow is best for smaller amounts of content as there may be deeper dependent content that is not pulled into the workflow. For significant changes consider using the Completion-Synchronization workflow.

This is a "pre-process" required to utilize the Completion-Synchronization or Completion-Translation workflows. This pre-process attempts to gather all dependent content changes regardless of how deep they are in the content. The Completion creates a file that contains all of the dependent content for running the Synchronization or Translation workflow process using two workflows created for Completions.

For larger synchronization needs or where changes have been made multiple levels deep in the content, you can use the Completions-Synchronization workflow. You will first run a Completion workflow to gather the content and then run a Completion-Synchronization workflow on the Completion you created. This process attempts to gather all dependent content that needs to be synchronized regardless of how deep changes have been made in the content. Using the copy over is an alternative to this workflow, but you will need to determine which works best for your specific needs.

For larger translation needs or where changes have been made multiple levels deep in the content, you can use the Completions-Translation workflow. You will first run a Completion workflow to gather the content and then run a Completion-Translation workflow on the Completion you created. This process attempts to gather all dependent content that needs to be translated regardless of how deep changes have been made in the content.

When you simply want to copy content from a parent locale to a child locale with the same language. This workflow does just what the name implies. It copies over all of the content you add to the workflow. It will grab dependent content (eg. changed components within a page if you add a page to the workflow) but may not pull all changed content if it is embedded in a rich text field or is on a dependent page. This workflow functions much like a translation workflow where you choose the child locales that you are doing the copy-over to. This means that you can copy content of a different language if the parent and child are different languages, although this would not be a standard use case. In most cases you would be copying English to English, German to German, etc.