Teamsite, CMS etc.

What I'm learning so far from the observation of our experiences with Teamsite CMS is that we are not using it right. Working area per group of users is a terrible idea IMHO because it breaks a very fundamental principle of isolation of concurrent changes. Attempt to fix it with creating additional workflows is making this problem only worse. There is also an issue of Teamsite stability from what it seems or luck of knowledge on how to administer it or both. Having working area per group of users in part motivated by costs. It created a somewhat schizophrenic situation. On one hand we have a CMS to have content management problem solved, on the other because of the headaches associated in dealing with it - we are trying to avoid using it whenever possible. I think we should be open at least considering alternatives for minimizing the costs and simplifying content management.

Here is an interesting CMS review http://www.cmswire.com/cms/cms-reviews/index.php

Matt had recommended considering Magnolia http://www.cmswire.com/cms/open-source-cms/magnolia-revs-java-open-source-cms-000650.php

The article above seems to recommend OpenCMS:

http://www.infoworld.com/article/05/08/08/32FEosscms_1.html?s=feature
http://www.infoworld.com/reports/32SRoss.html


Mumbo Looks very good and has online demo which is very impressive

http://www.mamboserver.com/

More: Free Content Management Buyer's Guide

http://www.hannonhill.com/google-bg.html?s=content+management

Here are tons more:

http://www.cmsreview.com/OpenSource/directory.html

Sorted by Language

http://www.la-grange.net/cms