Content Fragment creation wizard to have option to allow only few models and not all.
Use-case:
When author tries to create a new CF, he/she should be able to control the models that should be populated on creation wizard.
Current/Experienced Behavior:
Currently, when creating a CF, we see a huge list of CF models available, which is cumbersome for author to scroll through all of them. Currently, there is option to search using browser or add customizations using additional clientlibs but would be better experience if taken care in product functionality.
Improved/Expected Behavior:
Pagination or Tagging or OOTB Search or having allowed models can help.
Environment Details (AEM version/service pack, any other specifics if applicable):
@milind_bachani I believe, this concept already exist. Where in, we can define selected CF Models as a Configuration inside Configuration Browser. We can then apply this configuration to Selected Folder through Folder Properties. This way you can add abstraction to different set of CFMs.
If the same CFMs are created under Global Config, it will be available to all the Asset Folders by default.
@krati_garg This is useful, however it does not fit best when you have lots of CF models created under one configuration browser. Also, you need to update configurations at asset folder level for each and every folder.
This is doable for small count of folders, configurations & models but this becomes cumbersome on a bigger picture.
@milind_bachani In that case, we should consider remodeling the Content Fragment Model to reduce the CFM count, so that it becomes more manageable and scalable.
In my approach, I would make use of Nested Fragments, and make a Parent CFM applied to a Parent Folder and then add specific CFMs to the child folders. Also, its a one time activity while the AEM DAM is being set up for Authors to play. This way the CF authors, would not be overwhelmed with CFMs.
This has been reported to the engineering under the internal reference SITES-9161. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
@milind_bachani, This should work with allowed models as folder property, for folders below which content fragments will be created. This is existing functionality.
@kautuk_sahni Agreed, but reiterating my old comment, overriding at folder level is doable when count of folders is small. I am talking about having overriding at more ease when folders rise abruptly. Also, I do understand this to be a rare edged scenario.
@milind_bachani If the folder rises abruptly or has huge CFs, then we should think to overhaul our strategy. There should be a remodeling that we should do. Wiser re-structuring help in scaling and managing it.
I agree with what Krati suggested, that can be one of the ways to manage things.
