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.