Translation config samples
Experience Workspace’s translation framework supports many different translation connectors and offers robust configuration options.
A number of sample configurations are provided to help fast track your translation setup.
How to use the config samples
- Right click the sample config below that best describes your desired setup.
- Download the file to your computer.
- Rename the downloaded file to
translate.json. - Upload the
translate.jsonfile tohttps://da.live/edit#/{YOUR_ORG}/{YOUR_SITE}/.da - Observe the existing patterns and adjust to match your needs.
Choosing the right config
Projects typically fall into one of two categories with regards to translation:
- Language-based - Useful for informational sites that need simple content translations
- Region-based - Useful for commerce or sites with regionally specific content
For more information about localization strategies, please see the document Strategies for translation, localization, and rollout.
Experience Workspace allows you to also take a hybrid approach to content. You can choose to have a largely language-based site, but create regional content as necessary. You are only limited in how your delivery-side code respects your language and region choices.
Language-based Google Translate config
This config will expect your source content in the root of your site. It makes no assumptions about what language this source content is and provides common languages to translate to.
Locale-based (language > region) Google Translate config
This config will expect your source content to live in /en. If your content lives outside (i.e. /drafts/bruce-wayne/my-page), it will ask you to sync into the /en folder before sending to translate. It expands language actions to include rollout for scenarios where you wish to rollout from the language source of truth to its associated locales.
Region-based (region > language) Google Translate config
This config will expect your source content to live in /us/en. If your content lives outside, it will ask you to sync into the /us/en folder. It expects each region EMEA, APAC to contain en content as their source of truth. This allows you to create regionally specific content and localize within a given region. As mentioned above, this pattern is useful for commerce sites that have significant regional content.
Language-based Smartling config
You will need a Smartling account to use this setup. This is for human, machine, and LLM-based translation. This config will expect your source content in the root of your site. It makes no assumptions about what language this source content is and provides common languages to translate to.
Locale-based (language > region) Smartling config
You will need a Smartling account to use this setup. This is for human, machine, and LLM-based translation. This config will expect your source content to live in /en. If your content lives outside (i.e. /drafts/bruce-wayne/my-page), it will ask you to sync into the /en folder before sending to translate. It expands language actions to include rollout for scenarios where you wish to rollout from the language source of truth to its associated locales.
Language-based Trados config
You will need a Trados account to use this setup. This is for human, machine, and LLM-based translation. This config will expect your source content in the root of your site. It makes no assumptions about what language this source content is and provides common languages to translate to.