Hi Matteo, Thanks for the reply.
"first: 100.000 micro sites with CE, that is MONO-site.. uhm, think about it.." Is the concern more on technicality or features? My initial thought was to create: - pages, one for each site - asset folders, let's say one folder for each site as a start - roles with ACLs, so each role is restricted to each asset folder - users assigned to groups/roles which restrict users to certain sites Is this oversimplification of micro sites not feasible in Magnolia? Or is the problem on something technical like scalability? e.g. maybe one site uses up a certain amount of RAM, and it's not feasible for 100.000 sites to live on the same Magnolia instance? "second: you can NOT add folders on the website workspace. But you can use the "redirect-to-first-child" template as a workaround." The problem with this approach is that users won't be able to duplicate a home page unless the user is assigned ACL for Website at the top node /. I want user roles to be restricted to a folder (a sub-node), e.g. /foobar , so they can then create /foobar/microsite1, which they can then duplicate and create /foobar/microsite2 . If the microsites are at the top, e.g. /microsite1, then all users will have ACL Website at / node, and everyone can access everything. I have tried setting ACL to /microsite1, but then users won't be able to duplicate that page due to ACL restriction. Is it fair to say that this scenario does not suit Magnolia? 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]> ----------------------------------------------------------------
