Kind of, if I understand you correctly. But we have *one* resource, (meaning one jcr node if it's a jcr backed resource), at /content/home with sling:resourceType H
if a request is for http://www.example.com/home.html, H points to /specific/www.example.com/H/html.jsp if a request is for http://m.example.com/home.html, H points to /specific/m.example.com/H/html.jsp Does it make sense? Alessandro On Fri, Nov 1, 2013 at 11:25 AM, Bertrand Delacretaz <[email protected] > wrote: > Hi Alessandro, > > Trying to find a "simplest thing that works" scenario... > > Assume you have two content resources at /content/www.example.com/home > and /content/m.example.com/home, both with resourceType=H > > When rendering www.example.com/home.html, Sling looks for scripts in > the following folders, in order: > > /specific/www.example.com/H > /apps/H > /libs/H > > And if rendering com.example.m/home Sling looks under > /specific/m.example.com/H, /apps/H and /libs/H > > You'd then have specific rendering scripts under /specific, and if > needed common scripts under /apps and /libs > > There's a number of details to refine of course, but would that > basically work for you? > > -Bertrand >
