Hi Richard, Thanks for the reply.
"magnolia would probably return an error, because it can't render the folder" The folder is there only to 'group' the pages so I can create a role which ACL is restricted to the group instead of the root node / . Here's what I did: I duplicated the demo-project to demo-project0, I then used JCR view to create a folder foobar, and I moved demo-project0 to be under foobar folder. The public site could be viewed from: http://localhost:8080/magnoliaPublic/default/foobar/demo-project0.html The authoring site could be viewed and edited from: http://localhost:8080/magnoliaAuthor/.magnolia/admincentral#app:pages:detail;/foobar/demo-project0:view http://localhost:8080/magnoliaAuthor/.magnolia/admincentral#app:pages:detail;/foobar/demo-project0:edit But the problem with this is that foobar/demo-project0 no longer shows up on the Pages view, which prevents user from editing the page. So I didn't expect the folder to be rendered by Magnolia. For completeness, here's the XML: A. Before creating subfolder foobar. <sv:node sv:name="jcr:root"> <sv:property sv:name="jcr:primaryType" sv:type="Name">...</sv:property> <sv:node sv:name="demo-project0">...</sv:node> </sv:node> I could have a role with website ACL /demo-project0, but that won't allow users to duplicate /demo-project0 unless I set website ACL / which unfortunately allows the user to edit other pages under /. B. After creating subfolder foobar. <sv:node sv:name="jcr:root"> <sv:property sv:name="jcr:primaryType" sv:type="Name">...</sv:property> <sv:node sv:name="foobar"> ... <sv:node sv:name="demo-project0">...</sv:node> </sv:node> </sv:node> I could have a role with website ACL /foobar, with the intention to allow users to duplicate pages under /foobar . But the problem is /foobar/demo-project0 doesn't show up on Pages view. "having 'empty' pages is bad for SEO - the closer your content is to the root, the more 'important' it is - therefore having folders in the website repo is bad for SEO" I was thinking to have a proxy up front, which URL rewrite to Magnolia pages. e.g. - microsite1.com points to host/magnoliaPublic/default/groupX/microsite1.html - microsite1.com/about.html points to host/magnoliaPublic/default/groupX/microsite1/about.html - microsite2.com points to host/magnoliaPublic/default/groupY/microsite2.html Would that solve the SEO problem? Cheers, Cliff. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=7c4115b8-d125-4191-bb23-7e56005dc264 You are invited to Magnolia Conference. Less than a month to go! Register now: http://www.magnolia-cms.com/conference/register.html ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
