Segregate Content Fragments in AEM AMS 6.5.23 by usage

[Mahesh_Gunaje]

Hello Everyone,

For my project I need to create many content fragment models(Around 40-50).
I want to segregate these models by the usage. Note: I have a hierarchy of models by usage/reference.
Example: Will create CF-Model-abc-1, CF-Model-abc-2, CF-Model-abc-3 etc.
Will create CF-Model-xyz-1, CF-Model-xyz-2: Here, 1 field is Fragment Reference, where I need to refer to (CF-Model-abc-1 or multiple CF model-abc)
Will create CF-Model-qwerty-1, CF-Model-qwerty-2: Here, 2 field is Fragment Reference, where I need to refer to(CF-Model-xyz-1, CF-Model-abc-1)

Whats the best way to segregate models into multiple folder?

cc @arunpatidar  @giuseppebag @SantoshSai @HrishikeshKagne 

Thanks in advance

[giuseppebag]

hi @Mahesh_Gunaje,

you can create folders under /conf/<project>/settings/dam/cfm/models to group models logically:

/conf/myproject/settings/dam/cfm/models/
│
├── abc/
│   ├── CF-Model-abc-1
│   │    ├── subitems
│   │        ├── CF-Model-abc-subitem-1
│   │        ├── CF-Model-abc-subitem-N
│   ├── CF-Model-abc-2
│   ├── CF-Model-abc-3
│   └── CF-Model-shared/
│            ├── CF-Model-shared-subitem-1
│            └── CF-Model-shared-subitem-2
│
├── xyz/
│   ├── CF-Model-xyz-1
│   └── CF-Model-xyz-2
│
└── qwerty/
    ├── CF-Model-qwerty-1
    └── CF-Model-qwerty-2

This logical grouping offers several benefits:

• It facilitates organization by purpose or dependency
• It simplifies access control, including permissions and replication
• It enhances the authoring process, allowing authors to easily locate related models
• You can still reference models across different folders without any issues.

Btw you can add metadata or tags on CFMs to categorize them (e.g., “domain: product”, “domain: content-block”, “level: base/composite”). This can help authors find the right model using the UI filter in AEM Assets.

[SantoshSai]

Hi @Mahesh_Gunaje,

In addition to @giuseppebag  I’d like to add a few best practices that can make managing a large number of Content Fragment Models even more scalable and easier to maintain.

When dealing with 40–50 CFMs, it’s helpful to think not just about folder structure but also about reusability, model relationships, and long-term maintainability.

/conf/myproject/settings/dam/cfm/models/
│
├── abc/
│   ├── base/
│   │   ├── CF-Model-abc-1
│   │   ├── CF-Model-abc-2
│   └── composites/
│       ├── CF-Model-abc-composite-1
│       └── CF-Model-abc-composite-2
│
├── xyz/
│   ├── CF-Model-xyz-1
│   └── CF-Model-xyz-2
│
├── qwerty/
│   ├── CF-Model-qwerty-1
│   └── CF-Model-qwerty-2
│
└── shared/
    ├── CF-Model-common-author
    ├── CF-Model-common-image
    └── CF-Model-common-metadata

[Mahesh_Gunaje]

Thanks @SantoshSai   @giuseppebag   for your help.

Is it possible to create folders under: /conf/myproject/settings/dam/cfm/models/ ? From UI its not possible to create. I tried to create folder from crx/de (nt:folder or other options). In that case too, that folder is not visible in UI.

Note: If each CFM is independent of each other, then I can thik of having separate configuration browser folders under /conf/myproject.

example: /conf/myproject/abc, /conf/myproject/def, /conf/myproject/xyz

Or else /conf/myproject/abc,  /conf/myproject/abc/xyz

But, in my case, from one CFM, I need to reference other CFM.

Thanks

[giuseppebag]

The user interface only recognizes models that are placed directly under the main directory. If you create folders using CRXDE (regardless of the node type), those folders will not appear in the Content Fragment Models console. The system is designed to display models at a single level and does not support traversing nested folder structures.

Since you need to reference CFMs from other CFMs, you can still use separate configuration folders under the main directory to enable cross-configuration fragment references. However, please note that the UI capabilities will only be available for CFMs located at the first level.