Experience Fragments and Translations with Variations | Community
Skip to main content
Level 6
April 27, 2023
Solved

Experience Fragments and Translations with Variations

  • April 27, 2023
  • 1 reply
  • 551 views

What is best practice? should I be creating translation experiences under variations for experience fragments. Currently I have something like

  • /content/experience-fragments/my-site/structure/header/en-gb.html
  • /content/experience-fragments/my-site/structure/header/en-ca.html
  • /content/experience-fragments/my-site/structure/header/fr-ca.html
  • /content/experience-fragments/my-site/structure/header/es-ca.html

What is the preferred way to prepare and structure my experience fragments for translations?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sady_Rifat

In my opinion that should be the same structure as the content structure.

If your content structure is like this:

    /content/my-site/{country}/{language}/page

then the experience fragment should be like this way

    /content/experience-fragments/my-site/{country}/{language}/structure/header

 

Benefits:

  1. Authors will never be confused at the time of authoring.
  2. You can create content packages easily. For example, you need to create a content package for Germany. So your filter path will be, /content/my-site/de, /content/experience-fragments/my-site/de, /content/dam/my-site/de.
    Otherwise, there will be unnecessary content.

1 reply

Sady_Rifat
Community Advisor
Sady_RifatCommunity AdvisorAccepted solution
Community Advisor
April 27, 2023

In my opinion that should be the same structure as the content structure.

If your content structure is like this:

    /content/my-site/{country}/{language}/page

then the experience fragment should be like this way

    /content/experience-fragments/my-site/{country}/{language}/structure/header

 

Benefits:

  1. Authors will never be confused at the time of authoring.
  2. You can create content packages easily. For example, you need to create a content package for Germany. So your filter path will be, /content/my-site/de, /content/experience-fragments/my-site/de, /content/dam/my-site/de.
    Otherwise, there will be unnecessary content.