It is possible to split up the policy-file, just by creating the subfolders with the content XML files. Achieving part two, pulling the subfolders from AEM, is not possible. I don't have a solution for this problem, but I thought it might be interesting to understand the root cause: Pulling from AEM...

I managed to find a solution and actually the example from Adobe works with adjustments  You have to use the Sling Resource Merger with /mnt/override and an absolute path to inherit from the parent super component.<basic jcr:primaryType="nt:unstructured" path="/mnt/override/apps/.../components/basep...

I managed to find a solution and actually the example from Adobe works with adjustments  You have to use the Sling Resource Merger with /mnt/override and an absolute path to inherit from the parent super component.<basic jcr:primaryType="nt:unstructured" path="/mnt/override/apps/.../components/basep...

@Nikhil-Kumar Do you have a more detailed example explicitly for targeting properties from an include? I'm having the problem, that I cannot target the property inside the inherited tab, even if I would write a render condition, I'd still need to target that property somehow.

I also tried this one, but it does not seem to work. I've used these properties before on custom dialogs and they worked fine.However, I'm trying to do changes to the basic tab from the Foundation page and I have no clue why it's not working here. Can you maybe point me in the right direction becaus...

I'd like to hide a property within a certain tab that is inherited from /libs/wcm/foundation/components/basicpage/v1/basicpage (e.g. hideInNav property in basic tab). This change should only affect one page-rendering component, so I tried using sling:hideChildren, but did not manage to accomplish it...