I have authored these content fragments in AEM , but these all are taking a locale property when viewed as list (List View of CF).
From where this these locale properties are coming and can we change this property?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @VanitaNa
The root content fragments folders inside the project folder that is created will define the language root of your fragments.
It is necessary to define the language node for the root asset folder for translation projects in ISO language code format
/content
/- dam
/my-project
|- en
|- fr
|- de
|- es
|- it
|- ja
|- zh
All content fragments that are created under en will take English as language. And the same will be applicable to other languages
Example below -
References :
Hope this helps
Thanks
Hi @VanitaNa
The root content fragments folders inside the project folder that is created will define the language root of your fragments.
It is necessary to define the language node for the root asset folder for translation projects in ISO language code format
/content
/- dam
/my-project
|- en
|- fr
|- de
|- es
|- it
|- ja
|- zh
All content fragments that are created under en will take English as language. And the same will be applicable to other languages
Example below -
References :
Hope this helps
Thanks
The locale properties in AEM for content fragments are typically derived from the language variants (e.g., /content/mycontent/en, /content/mycontent/de) or the content fragment model.
You can change these properties by:
This allows you to control and change the locale properties.
Views
Likes
Replies