


Taking a look at the adobe documentation, https://experienceleague.adobe.com/docs/experience-manager-65/assets/managing/preparing-assets-for-t...
it recommends DAM assets should be structured in a particular way to enable translations for the translations framework.
/content/dam/en
/content/dam/fr
/content/dam/de
I have a multitant AEM environment where I have /content/dam/my-site and /content/dam/my-site-2
if I structure my hierarchy like
/content/dam/my-site/en
/content/dam/my-site/fr
/content/dam/my-site/de
/content/dam/my-site-2/en
/content/dam/my-site-2/fr
/content/dam/my-site-2/de
will the translations framework still work as expected?
Views
Replies
Sign in to like this content
Total Likes
Hi @ AEMWizard,
Multi tenant structure you have described should not be a problem. Language code nodes do not have to be created directly under /content/dam. What is critical is to have a properly defined language root using ISO language code. You can explore Create a language root section from below documentation:
Hi @ AEMWizard,
Multi tenant structure you have described should not be a problem. Language code nodes do not have to be created directly under /content/dam. What is critical is to have a properly defined language root using ISO language code. You can explore Create a language root section from below documentation: