Skip to main content

XTM Connect – Adobe Experience Manager

Enabling support for Experience Fragment translation

In the current version of the XTM Cloud connector, Experience Fragments can be handled just like any other translatable content (included when the page they are in is sent for translation). However, they are not a standard content type, so they will not be included in translation unless they have been added to the Adobe Experience Manager Translation Configuration, as a resource type.

If it is necessary to do so, follow the steps below.

To add Experience Fragments to the Adobe Experience Manager Translation Configuration, as a resource type:

  1. Log in to your instance of Adobe Experience Manager as an Administrator.

  2. Select Adobe Experience Manager > Tools > General > Translation Configuration. You see the AEM Translation Configuration screen.

  3. Select the checkbox next to /content.

  4. Select the Add context button.

  5. In the Select Context pane, select the relevant content path.

  6. Select the check mark check-blue.svg in the top right-hand corner, to close the pane. You see the AEM Translation Configuration screen.

  7. Select the Edit icon in the top left-hand corner of the screen. You see the Translation Rules Editor screen.

  8. Select the References tab. At the top of the References tab screen, you see Add asset node with [resource type] with asset reference as [reference type]

  9. In the [resource type] field, enter the resource type of the implementation of the Experience Fragment component used by your project.

  10. In the [reference type] field, enter the name of the property that contains a path to a referenced resource. In the case of Experience Fragments, it is usually "fragmentVariationPath".

  11. Select Add Reference to save your changes.

Result: you have added Experience Fragments to the Adobe Experience Manager Translation Configuration, as a resource type. They can now be added to translation projects and sent to XTM Cloud for translation.

Note

Content Fragments

Unlike Experience Fragments, Content Fragments do not need to added as a resource type: they are a recognized content type that Adobe Experience Manager can extract and send for translation.

For reference, make these settings in the Translation Rules Editor, for Content Fragments, if required:

  • In the [resource type] field, enter the resource type of the implementation of the Content Fragment component used by your project.

  • In the [reference type] field: enter "fragmentPath" (this is the usual setting).

.

In this section: