Hi, On Thu, Oct 20, 2016 at 2:28 PM, Carsten Steckel <[email protected]> wrote: > ...Inheritance comes to mind where a Master website is defined and every child > inherits its masters config, content, assets, ... but overwrites if > necessary...
The Sling Resource Merger [1] goes in that direction but I haven't heard so far from people using it in the way that you mention, what I've seen is simpler use cases where configuration-like resources are being merged. But if you stick to the Sling Resource API (as opposed to JCR) and manage access rights carefully it might work for your use case. -Bertrand [1] https://sling.apache.org/documentation/bundles/resource-merger.html
