Experience Pages Translations

Info: Experience Pages translation support is available in brXM 14.5.0 and later.

Overview

This page describes how to configure translation support for Experience Pages in Bloomreach Content.

When to Use

Enable translation for Experience Pages when working with channels that support multiple languages. This allows you to manage translated Experience Pages as you would with other documents, provided you configure layouts and folders as described below.

Prerequisites

A Bloomreach Content project with translated channels configured.
For setup instructions, see Add a Translated Channel.
Experience Page Layouts and Folders must be configured for translation.

Configuration

Experience Page Layouts

To enable translation of Experience Pages between channels, both the source and target channels must use identical Experience Page Layouts. Each layout must have the same hippo:identifier value in both channels.

The recommended approach is to define Experience Page Layouts in a shared configuration that both channels inherit from. This ensures consistency and avoids duplication.

Example configuration:

/hst:myproject/hst:configurations/common/hst:xpages:
  jcr:primaryType: hst:xpages
  jcr:uuid: 10edaa6b-7ac2-41f2-8c6a-5975469196ca
  /experience-page:
    jcr:primaryType: hst:xpage
    jcr:uuid: e4b7b977-b811-41c0-9e1c-1afdef0e3d6c
    hst:label: Experience Page
    hst:referencecomponent: hst:abstractpages/base
    /main:
      jcr:primaryType: hst:containercomponent
      jcr:uuid: 3816c438-24eb-4aa4-8b6f-c7e2472405a6
      hippo:identifier: b7ee33fd-a625-449a-8b9c-156d9030e7cf
      hst:xtype: HST.vBox
      /content:
        jcr:primaryType: hst:containeritemcomponent
        jcr:uuid: 400c260a-9259-48d9-9554-3046b186ba24
        hst:componentclassname: org.onehippo.cms7.essentials.components.EssentialsContentComponent
        hst:label: Content
        hst:template: contentpage-main

Experience Page Folders

To support translation, the root Experience Page Folder in each channel must:

Use the same node name in both channels.
Share the same hippotranslation:id property value.
Be linked as translations.

Example: English Experience Page Folder (/content/documents/myproject):

/content/documents/myproject/experience-pages:
  jcr:primaryType: hippostd:folder
  jcr:mixinTypes: ['hippo:named', 'hippostd:cmxpagefolder', 'hippostd:xpagefolder',
    'hippotranslation:translated', 'mix:versionable']
  jcr:uuid: de290994-7564-4557-bf2d-806fe6780ba2
  hippo:name: experience pages
  hippostd:channelid: myproject
  hippostd:foldertype: [new-translated-folder, new-document]
  hippotranslation:id: e10ae0b7-e85d-4f9b-8578-c11f03d4da81
  hippotranslation:locale: en

Example: French Experience Page Folder (/content/documents/mon-projet):

/content/documents/mon-projet/experience-pages:
  jcr:primaryType: hippostd:folder
  jcr:mixinTypes: ['hippo:named', 'hippostd:cmxpagefolder', 'hippotranslation:translated',
    'mix:versionable']
  jcr:uuid: bd3178d8-eae9-4dd4-807d-4c71511f2df3
  hippo:name: experience pages
  hippostd:channelid: mon-projet
  hippostd:foldertype: [new-translated-folder, new-document]
  hippotranslation:id: e10ae0b7-e85d-4f9b-8578-c11f03d4da81
  hippotranslation:locale: fr

Both folders must have the same node name and identical hippotranslation:id values to be recognized as translations of each other.

Limitations

When you create a translation of an Experience Page Document that contains component configuration with references to documents using relative content paths, those references will not be preserved in the translated copy. You must update and reconfigure these document references manually after creating the translation.