Translation config samples
Experience Workspace supports multiple translation connectors and configurable translation and localization workflows. These samples provide a starting point for common setups.
How to use a sample
- Download the main config that best matches your setup.
- Rename it to
translate.json. - Upload it to
https://da.live/edit#/{YOUR_ORG}/{YOUR_SITE}/.da. - Replace placeholders and adjust languages, locations, and actions.
A sample labeled separate credentials has two downloads. Rename the main config to translate.json, rename its companion to translate-keys.json, and upload both to the site's .da folder. Update translation.service.key.path with your organization and site. Restrict access to the credential sheet as appropriate.
Choosing the right structure
- Language-based structures suit informational sites with straightforward translation.
- Locale-based structures add rollout from language content into regional locales.
- Region-based structures support substantial region-specific content.
Please see the document Strategies for translation, localization, and rollout for more information.
Google Translate
Language-based
Source content can live at the site root, with common target languages available.
Locale-based (language > region)
Source content lives in /en, with translation into language folders and rollout into their locales.
Region-based (region > language)
Source content lives in /us/en. Each region maintains English source content before localization into regional languages.
Lionbridge
A Lionbridge account, client credentials, and provider ID are required.
Language-based, inline credentials
Language-based, separate credentials
Download translate.json and download translate-keys.json.
Smartling
A Smartling account is required. Replace the account, project, user identifier, and secret placeholders.
Language-based, inline credentials
Locale-based (language > region), inline credentials
Language-based, separate credentials
Download translate.json and download translate-keys.json.
Trados
A Trados account, tenant, project template, and client credentials are required.