Thanks for the response, I can see that this might "work", but it certainly is not workable.So I'll log a daycare ticket for it, instead of losing more of my time (again).

I already tried that, and in several configurations (global and site specific), but it does nothing. After digging a bit deeper this is not very surprising, because the required node for "Tools > Assets > Content Fragment Models" is missing in "/libs/dam/gui/content/nav/tools/assets".While figuring ...

Did anyone get Content Fragment Models to work on an AEM 6.3 instance with Service Pack 3 and Cumulative Fix Pack 1 installed?I created the required configuration through the configuration browser, and even set the cq:conf node manually on the Assets folders, as described in the documentation and se...

Hi Scott, thanks for that.Fyi, it is not a blocking issue. But as I find the Editable Templates a big improvement over the static ones, I would certainly like to contribute by trying to point out some possible areas of improvement.Having looked at the (decompiled) code, I think it might be possible ...

Hi Scott,Thanks for taking the time to read my question.Let me try and illustrate what is going on in a different way:_ 0. Editble Template     |_ 1. Layout Container: I can configure a policy mapping to a policy that sets allowed components below           |_ 2. Text Cmp: I can configure a policy m...

Hi,when reuse of an existing component is not possible, the next best thing is to create a new composite component through assembly of existing components. However, when trying to do so, I seem to get into trouble when it comes to the content policy for this composite component (in the context of Ed...