ems eril wrote: > 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 . Trying to implement a version control system on top of a content management system sounds a little crazy to me. Implementing a version control system is hard and we already have GitHub, Subversion, etc. Of course I don't know all requirements, but I'd do it the other way around. You could create a Magnolia module that can be installed on any machine, put its source in a version control system and have web developers work on it on their local machines and commit and merge back any changes. In this case you'd also implement access control on the VCS level. Nils. ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
