I have a very unique requirement where I need to be able to create new projects within web content management. To me a project is a clone of existing set of websites ie pages, resources , dam etc. where individuals can work on without effecting the current content. Ones they have completed their task the work is then merged back to the current stream . The best analogy would be how github works. The other spin to this is users are assign to projects and only those user can see the content that have been created or modified for that specific project . Im very new to Magnolia so at this stage Im trying understand the level of customization that would be required to achieve this . If anyone has done anything similar I would love hear about it.
Here are some ideas I was thinking . 1) Cloning workspaces and using JCR security to restrict access and finally merging the changes of the workspace back to original workspaces . My impression here is that it would require great deal of changes to the of core magnolia . 2) Use of JCR versioning create hierarchal versions where the parent version node represents project and apply permission at that level. 3) All content apps would have common node structure where multiple root nodes represent project names . Using the security mechanism already in place we can apply permission to those root nodes. I think this is similar to how multisite works today but expanding this to other workspaces and having a way to easily clone and merge the differences is missing. Thank you in advance -ems -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=a3680fae-94c6-4c0a-85e6-6d41e622779e ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
