Best practice implementation scenarios for TMF

[AriWeissman]

• Implementation Scenarios
• Scenario A
• Scenario B
• Scenario C
• Scenario D

Implementation Scenarios

Below are examples of TMF best practice implementations. The scenarios lay out configuration requirements to support frequent localization needs.

Scenario A

Conditions

• Single country
• Multiple languages (English, Spanish)
• Master content in English folder

Site Structure

This is the preferred site structure. If you are focusing on only one country, the country folder is optional.

Your TMF folder structure should look like this:

Locales Config

Configure US-EN

1. Select the appropriate country and language, in the example it’s “United States” for country and “English” for language.
2. Select the Site Root. In this case, it could be “/US/en/”.

Configure US-ES

1. Select the appropriate country and language, in the example it’s “United States” for country and “Spanish” for language.
2. Select the Site Root. In this case, it could be “/US/es/”.

Use TMF to derive the content

1. Create master content in “/US/en/”.
2. Select one of the content pages and click Edit > Form.
3. Expand TMF panel.
4. If you don’t see the TMF input fields like the screenshot below, please double check if locale configs are properly set up or template files are correctly implemented.
5. Choose where you want to send for translation. In this case, US-ES is the only option available in the list.
   
6. Tick “US-ES” checkbox and click Save.
7. TMF will create a same asset in the selected locale folder.
8. Refresh the input screen.
   
9. Click Existing Translation link to check the asset.

Scenario B

Conditions

• Multiple countries (United States, Canada)
• Multiple languages (English, Spanish, French)
• Master content in United States > English folder

Site Structure

This is the preferred site structure. If you are focusing on only one country, the country folder is optional.

TMF Configuration

Your TMF folder structure should look like this.

Locales Config

Configuring CA-EN

1. Select the appropriate country and language, in the example it’s "Canada” for country and “English” for language.
2. Select the Site Root. In this case, it could be “/Canada/en/”.

Configuring CA-FR

1. Select the appropriate country and language, in the example it’s "Canada” for country and "French" for language.
2. Select the Site Root. In this case, it could be “/Canada/fr/”.

Configuring US-EN

1. Select the appropriate country and language, in the example it’s "United States” for country and "English" for language.
2. Select the Site Root. In this case, it could be “/US/en/”.

Configuring US-ES

1. Select the appropriate country and language, in the example it’s "United States” for country and "Spanish" for language.
2. Select the Site Root. In this case, it could be “/US/es/”.

Use TMF to derive the content

1. Select one of the content pages and click Edit > Form.
2. Expand TMF panel.
3. If you don’t see the TMF input fields like the screenshot below, please double check if locale configs are properly set up or template files are correctly implemented.
4. If you don’t see the TMF input fields like the screenshot below, then please double check if locale configs are properly set up and template files are correctly implemented.
5. Choose where you want to send for translation.
   
6. Select locale(s), tick the checkbox(es) and click Save.
7. TMF will create an asset in the selected locale folder(s).
8. Refresh the input screen.
   
9. Click Existing Translation link to check the asset.

Scenario C

Conditions

These are the same conditions as Scenario B but the Translation Rule is configured to limit the accessible locales.

• Multiple countries (United States, Canada)
• Multiple languages (English, Spanish, French)
• Master content in United States > English folder

Site Structure

This is the preferred site structure. If you are focusing on only one country, the country folder is optional.

TMF Configuration

Your TMF folder structure should look like this:

Locales Config

Configuring CA-EN

1. Select the appropriate country and language, in this case it’s “Canada” for country and “English” for language.
2. Select the Site Root. In this case, it “/Canada/en/” .
   
3. Hide all the locales (US-EN, US-ES).
   

Configuring CA-FR

1. Select the appropriate country and language, in this case it’s “Canada” for country and “French” for language.
2. Select the Site Root. In this case, it could be “/Canada/fr/”.
3. The screenshot below is a recommended setup for the destination locale. This will only allow the selected locale content to be derived.
   

Configure US-EN

1. Select the appropriate country and language, in this case it’s “United States” for country and “English” for language.
2. Select the Site Root. In this case, it could be “/US/en/”.
3. Hide all the locales (CA-EN, CA-FR) except US-ES.
   

Configure US-ES

1. Select the appropriate country and language, in this case it’s “United States” for country and “Spanish” for language.
2. Select the Site Root. In this case, it could be “/US/es/” or “/US-es/” based on the folder structure.
3. The screenshot below is a recommended setup for the destination locale. This will only allow the selected locale content to be derived.
   

Use TMF to derive the content

1. Select one of the content pages and click Edit > Form.
2. Expand TMF panel.
3. If you don’t see the TMF input fields like the screenshot below, please double check if locale configs are properly set up or template files are correctly implemented.
4. If you don’t see the TMF input fields like the screenshot below, then please double check if locale configs are properly set up and template files are correctly implemented.
5. Confirm that it only shows the selected locales in the Translation Rule. Choose where you want to send for translation.
   
6. Select locale(s), tick the checkbox(es) and click Save button.
7. TMF will create a same asset in the selected locale folder(s).
8. Refresh the input screen.
   
9. Click Existing Translation link to check.

Scenario D

Conditions

These are the same conditions as Scenario B but the Translation Rule is configured to limit the accessible locales

• Multiple master contents in the project
• Multiple countries (United States, Canada)
• TMF configuration folder per country folder
• Multiple languages (English, Spanish, French)

Site Structure

This is the preferred site structure.

TMF Configuration

TMF folder for Canada

TMF folder for US

Locales Config

Configuring CA-EN

1. Select the appropriate country and language, in this case it’s “Canada” for country and “English” for language.
2. Select “/Canada/en/” folder for the Site Root.
   

Configuring CA-FR

1. Select the appropriate country and language, in this case it’s “Canada” for country and "French" for language.
2. Select “/Canada/fr/” folder for the Site Root.

Configuring US-EN

1. Select the appropriate country and language, in this case it’s "United States" for country and "English" for language.
2. Select “/US/en/” folder for the Site Root.

Configuring US-ES

1. Select the appropriate country and language, in this case it’s "United States" for country and "Spanish" for language.
2. Select “/US/es/” folder for the Site Root.

Use TMF to derive the content

1. Create master content in “/US/en/” folder
2. Create master content in “/Canada/en/” folder
3. Select one of the content pages and click Edit > Form.
4. Expand TMF (Translation Model Framework) panel.
5. If you don’t see the TMF input fields like the screenshot below, please double check if locale configs are properly set up or template files are correctly implemented.
6. Tick “US-ES” checkbox and click Save button.
   
7. TMF will create a same asset in the selected locale folder.
8. Refresh the input screen.
   
9. Click Existing Translation link to check the asset.