>Points to consider (mostly AEM specific):
>- CACs can be problematic with MSM
>- CACs can be problematic with replication
>- CACs can be problematic with translations (if CAC contents need to
>be translated)
>- CACs are unintuitive for content-editors
if these problem are still unsolved it may
>-Original Message-
>From: Nicolas Peltier
>Sent: Friday, October 12, 2018 10:34 AM
>To: users@sling.apache.org
>Subject: [caconfig] using caconfig spi for cq content policy fallbacks
>
>Hi,
>
>because i'm talking about context aware config, i'll give some context he
Hi,
because i'm talking about context aware config, i'll give some context here
:-) i'd like test using caconfig logic to replace specific inheritance like
core breadcrumb's [0] that will allow less code and additional inheritance
levels (assuming i'm storing different content policies at
