Flatten the MSM Content Structure | Community
Skip to main content
V
vsharm
Level 4
August 12, 2020
Solved

Flatten the MSM Content Structure

  • August 12, 2020
  • 4 replies
  • 2550 views

We have MSM with about 10 different languages. Our authors are having issues when any time they need to manage contents they have to navigate to each locale location (en, es, fr, ru etc) and update the content on the content fragment.

 

Looking for suggestion if anyone has tried a different approach like having a single page where all the translated contents are available fro a particular content through different tabs or sections? Basically looking if flattening the structure is possible instead of following the Adobe's suggested structure?

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 SundeepKatepally

MSM in 10 locales.

 

I am expecting that in the blue print you will have all locales (example in language masters ../content/wknd/language-masters/<locales>)

I am expecting that similarly for content fragments ,in the blue print you will have all locales (example in language masters ../content/dam/global/language-masters/<locales>) 

 

Once the content is available in source language , then its the translation tool which will handles all translations and then MSM will handle to push data to the live copies.

For content fragment ---> MSM feature is available from 6.5.5 only.

 

for I18n/tags -->  at a time we can see all locales data.

 

4 replies

SundeepKatepally
Community Advisor
SundeepKatepallyCommunity AdvisorAccepted solution
Community Advisor
August 13, 2020

MSM in 10 locales.

 

I am expecting that in the blue print you will have all locales (example in language masters ../content/wknd/language-masters/<locales>)

I am expecting that similarly for content fragments ,in the blue print you will have all locales (example in language masters ../content/dam/global/language-masters/<locales>) 

 

Once the content is available in source language , then its the translation tool which will handles all translations and then MSM will handle to push data to the live copies.

For content fragment ---> MSM feature is available from 6.5.5 only.

 

for I18n/tags -->  at a time we can see all locales data.

 

    V
    vsharmAuthor
    Level 4
    August 13, 2020
    Hello @sundeepkatepally - correct. The challenge comes when authors have to navigation to several levels down to a particular locale and then again navigate to the particular page to see the translation every time they submit the master copy for translation.
    Shashi_Mulugu
    Community Advisor
    Shashi_MuluguCommunity Advisor
    Community Advisor
    August 13, 2020

    @vsharm Can you please share your blueprint structure once. Also i see from your question that authors having issues to go to each locale location and modify content, does that means, one team/person managing all content? not regional specific authors? MSM is a beautiful concept if we have specific authors for specific country/region and share similar content between them. If everything is maintained by one team or if no content sharing between regions or all regions having same content, then i feel it may not be best Usecase of MSM.

    V
    vsharmAuthor
    Level 4
    August 13, 2020
    @shashi_mulugu - we have few people in the content team who are responsible for managing the contents for different locale. We have english content which has the live copy as "Translation master" aka TM. From TM, we submit to TDC which brings back the content for each locale. Before publishing authors review the content for the translation and then they publish if it looks good.
    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    August 13, 2020

    If you are using the MSM I would strongly suggest to stick with the suggested structure (country/language), because that is how the MSM is supposed to be used, how it is working and how everyone is expecting the setup to be.

    But of course you can build a custom maintenance UI on top, which allows you to open the various livecopies of a page in a more covenient way. But that's only UI then, the underlying structure remains the same.

      V
      vsharmAuthor
      Level 4
      August 24, 2020
      ok. thank you for all for your input. We will stick to the suggested structure but may be do some our won customization onto the UI to ease up the process for authors.
      Nikhil-Kumar
      Community Advisor
      Nikhil-KumarCommunity Advisor
      Community Advisor
      August 24, 2020

      @vsharm As mentioned by @joerghoh, Best way to implement MSM is country language hierarchy. 
      That's how almost all the MSM AEM sites are designed. Never came across any other method to handle country language.

      Below is the basic structure of MSM.


      Thanks,
      Nikhil

       

        Terms & ConditionsAccessibility statement

        Loading footer...