Skip to main content

XTM Connect – Adobe Experience Manager

Example of Launch creation and translation

Imagine that a company that used English as its primary operating language wanted to prepare a campaign for the upcoming winter season. Firstly, it would create a Launch from existing English-language content on its site. Content in Launches is based on top-level source pages. In Adobe Experience Manager, these are known as Production pages. The company would then arrange translation of the files in the Launch into all the languages its site supports (de, es, fr and it) so that the content can be published across multiple countries at the right point in time.

In our example, the campaign would be based on two top-level (English-language) content pages:

  • /content/wknd/language-masters/en/magazine/guide-la-skateparks

  • /content/wknd/language-masters/en/magazine/ski-touring

Note

Note the path on which the two pages are stored: it is important to store content in the correct location, to ensure that it will be updated, sent for translation, synchronized and so on correctly. If you are not familiar with how content is structured in Adobe Experience Manager, see Recommended content tree structure.

To create and process the Launch (example):

  1. Create copies of the two English-language Production source pages.

    • If you want these copies to automatically inherit content from the Production source pages, if those pages are modified, create Live Copies. In that case, promoting (synchronizing) the Launch content duplicates it in the source pages in Production (in the source language). The Launch content can be promoted manually or automatically (dependent on fields set when the launch was created and editing).

    • If you want these copies to be completely independent, stand-alone pages with no live relationship between them and the Production source pages, create normal copies.

  2. Store your copies in a Launch. This is simply a container in which copied content is stored for editing separately from its original source files.

  3. If required, make changes in these copies so they are ready for the target markets (while leaving your current source pages unchanged and, if required, live).

  4. Using XTM Cloud connector, send the copied files for translation in XTM Cloud. When they have been translated, they will be ready for reuse later, when required. Launches enable you to review translations before overwriting the copied source file with the translation.

  5. To publish the translations so that site visitors can see and use them, promote the language copy pages in the Launch back to the original source files:

    • When the translated page is imported into Adobe Experience Manager, it overwrites the language copy page in the Launch.

    • The translated page only overwrites the language copy page when the Launch is promoted.

    For details, see Adobe Inc.'s online help about promoting Launch pages.

In this section: