hello ruben. use case sounds a bit similar to
https://github.com/apache/sling-org-apache-sling-superimposing (a bit outdated) and https://github.com/apache/sling-org-apache-sling-resourcemerger can you differentiate what DDR does differently? stefan >-----Original Message----- >From: Ruben Reusser <[email protected]> >Sent: Tuesday, April 20, 2021 1:54 PM >To: [email protected] >Subject: Re: Sling Declarative Dynamic Resources > >totally forgot to add the link to the code base - sorry > >https://github.com/apache/sling-whiteboard/tree/master/org.apache.sling.ddr > >On 4/19/2021 10:29 AM, Ruben Reusser wrote: >> dear sling community >> >> Andreas has been working to create a way to dynamically create >> component proxies in Sling based on a configuration. In peregrine-cms >> we are planning to use this approach when a new tenant (a new website) >> is created by a user. It allows us to proxy the base components into a >> new /apps folder for the website. A super user for the site can then >> potentially change the title/group of a component and the default >> structure that is used when adding a component to a page. >> >> We hope this component may be useful to other sling based content >> management systems as well. We'd like to ask to move this module out >> of the whiteboard - but of course we welcome any >> comments/concerns/things we should consider to make sure everybody can >> benefit from this module. >> >> looking forward to your comments! >> >> Ruben
