this gets very AEM product specific, i'm not sure if this is the right list for
it.
still, why do you want to configure your fallback below /content/conf and not
in /conf? they could be stored in /conf as cq:Page nodes as well with some
tweaking of configuration. looking up configuration data
Hi,
bear in mind i really want to “customize” as less as possible. Hence in my
point of view it’s wrong too to customize the conf path.
However, context aware configuration allows me to use widgets for AEM pages in
/content/conf, i can then reuse in component dialogs in my site, and then
in my point of view it is wrong to store the config data in /content/conf if
the only motivation to do this is the limitation of some tooling.
i would recommend to keep the config root of the default strategies at /conf.
what is the purpose of the "AEM content management tools" - edit the
