Set Up Translation

Document Authoring comes with a Translate app out-of-the-box, which you can use to localize pages. The defaults handle the most common use cases. However the translation service is flexible and allows a great deal of configuration if necessary.

Before you start translating content, make sure you have considered your localization strategy.

Create a Translation Configuration

Configuration files are kept in a hidden (dot) directory. You will need to create a new file for your site's translation configuration.

Navigate to your site in Document Authoring. In this example, we are examining the site da-harvey-dent, which we have previously translated to German and French.
Navigate to the hidden .da directory for your site by appending it to the URL in your browser. For example we are currently at https://da.live/#/bohnertchris/da-harvey-dent and would then navigate to https://da.live/#/bohnertchris/da-harvey-dent/.da.
In the .da directory, create a new sheet by clicking New → Sheet and then entering translate as the name and click Create sheet.
Click the edit icon of the default sheet to change its name from data to config. Click the checkmark to save the change.
On the newly-renamed config sheet, you can enter the configuration parameters and their values as key-value pairs. Start by entering key in the first column in the first row and value in the second column of the first row.
Now you can add the configuration parameters you wish to define. In this case, we will change the default translate behavior to merge.
Click the publish button and select Publish to publish your configuration sheet and thus activate the configuration changes you made.
Grab the URL of some pages you would like to translate and return to the Translate app.
Create a new project and proceed to the Confirm options tab. Note that the default has been changed.

Translation Options

The following is a list of options available for your translation configuration.

On the config sheet.

Key	Description	Value	Description
`translate.behavior`	How to handle old content when new docs come back from translation	`overwrite`	Overwrite the old content. Useful for no-touch translation.
`translate.behavior`		`merge`	Merge the old content with the new content. Useful if there is content you want to retain. This option requires human intervention after translation.
`translate.staging`	Stage content in a separate area from your source content before sending to translation service.	`on`	This will copy your source content into a separate folder. This is typically done to make changes to your source docs before sending to translation but *not* affecting your live content.
`translate.staging`		`off`	Send source documents directly to the translation service.
`rollout.behavior`	How to handle old content when new docs get rolled out to the locale. This is only used for hybrid and locale-based localization strategies.	`overwrite`	Overwrite the old content. Useful for no-touch translation.
`rollout.behavior`		`merge`	Merge the old content with the new content. Useful if there is content you want to retain. This option requires human intervention after translation.