Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

AEM Content Fragments: Content Structure | AEM Community Blog Seeding

Avatar

Administrator

BlogImage.jpg

AEM Content Fragments: Content Structure by exadel

Abstract

Content Structure
There are no restrictrictions where you can store content fragments in AEM. Originally, you would store them in /content/dam/site-com’ (the We Retail site has this type of structure, for example). This might be not handy if your site folder has a lot of subfolders, and having several folders for every language would create a mess.

To create the language root, you create a folder and use an ISO language code as a name. The language code must be in one of the following formats:

 The supported language code is a two-letter code as defined by ISO-639-1 (like en).
_ or - The supported country code is a lower-case or upper-case two-letter code as defined by ISO 3166, such as en_US, en_us, en_GB, en-gb.
AEM will determine where the language root is automatically. You can have a separate folder for CFs just for your comfort. This approach might be particularly handy if you want to configure quick access to the CFs folder from Navigation (this will be explained below).

Our content fragments are stored under ‘/content/dam/site-com/content-fragments’.

Read Full Blog

AEM Content Fragments: Content Structure

Q&A

Please use this thread to ask the related questions.

0 Replies