MSM image rollout from en to all the locales | Community
Skip to main content
V
vsharm
Level 4
October 29, 2020
Solved

MSM image rollout from en to all the locales

  • October 29, 2020
  • 1 reply
  • 1232 views

We are following we.retail example and we have the language copy containing the master (blueprint) for live copies (language branch).

language-masters/en is the blueprint for live copy - en,

language-masters/fr is the blueprint for live copy - fr,

 

Our requirement is that if we have any image (static content which do not require translation) in language-masters/en, we can rollout to not only it's live copy (en) but also to all the locales (eg. fr, ja, es..) (assuming all the locales needs to have the same sets of images).

 

We know we can do the rollout from master (language-masters/en) to it's live copy (en) but how do we make sure we also push the images to other locales which do not even have the live copy relationship with the language-masters/en?

 

For other text content, those locale blueprint copies  (eg.language-masters/fr) will use the translation and rollout the translated contents to their respective live copies (en).

 

Is it even possible? Any idea or suggestion how it can be achieved?

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 Vijayalakshmi_S

Hi @vsharm,

Below requirement (which is outside translation to have image available across multiple locales when authored in master) can be achieved using "Reference" component or Content Fragments or Experience Fragments where initially/very first time respective components needs to be authored in all locales. But going forward/future updates to image can be managed from one single location. 

Without direct live relationship, we can't rollout the changes, Hence the above alternative. 

1 reply

Vijayalakshmi_S
Vijayalakshmi_SAccepted solution
Level 10
November 2, 2020

Hi @vsharm,

Below requirement (which is outside translation to have image available across multiple locales when authored in master) can be achieved using "Reference" component or Content Fragments or Experience Fragments where initially/very first time respective components needs to be authored in all locales. But going forward/future updates to image can be managed from one single location. 

Without direct live relationship, we can't rollout the changes, Hence the above alternative. 

    V
    vsharmAuthor
    Level 4
    November 9, 2020
    Thank you for the response. I will take reference component or content fragment into the consideration.
    Terms & ConditionsAccessibility statement

    Loading footer...