Reference config sheets
Below you will find a few sample configurations to help fast track your localization setup. For a complete guide on localization configurations, please see the localization setup guide.
To use:
- Right click the reference config that best describes your desired setup.
- Download the file to your computer.
- 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
Adobe recommends a hybrid-based approach to localization. This generally means only creating locales where you maintain truly differentiated content. What a hybrid approach looks like in practice depends entirely on your own market. For this reason, Adobe provides sample language-based and locale-based configs, which you can adapt as required to your own hybrid setup.
For more information about localization strategies, please see the document Strategies for translation, localization, and rollout.
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.
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.