Hi, I'm trying to understand if I can use the resource overlay concepts and apply them to static resources. This for a more client side oriented style of application made with react
I know that I can define something in /libs and a customization as recommended in /apps. This implies the definition of nodes in /content and the specification of a resourceType pointing to a path that could be on /apps (checked first) or /libs (checked last). For this I need to specify each and every node on /content and rely on the native resource resolution. I wonder if I can use this concepts but with static resources. Let's imagine that I have a super simple application with the following base layout specified in libs: /libs/acme/img /libs/acme/img/logo.png /libs/acme/css /libs/acme/css/acme.css /libs/acme/index.html and on content /content/acme Then I would like that a customer uses my definition as base but only with a customization on the css and on the logo /apps/acme/img/logo.png /apps/acme/css/acme.css and on content /content/clientacme I know that this is not cleary the intent of the mechanism more geared to server side components, however for client side applications this could be very interesting. Is it possible to achieve something like this over the sling infrastructure ? Bear with me, maybe I'm missing something super simple or this is simply a big deviation from the initial purpose of sling but I think the resource overlaying concept is very powerful much more if coupled with a content server like sling. I have investigated a little and ( maybe I didn't understand it fully ) it seems that I can achieve something like this with https://github.com/apache/sling-org-apache-sling-superimposing namely with the experimental sling:superimposeOverlayable. It's a way for this or there's another alternative ? Regards, Ivo Leitão -- Sent from: http://apache-sling.73963.n3.nabble.com/Sling-Users-f73968.html
