Choosing a Content Management System (CMS)
First, as a caveat (and despite all the hype of CMS’s), unless you are a major corporation with thousands of employees requiring the ability to create/maintain web content on-the-fly, the benefits of implementing a static or semi-dynamic web site may outweigh the advantages of a bona-fide Content Management System.
You should ask yourself whether or not you require a site-wide CMS. Publishers for instance may only need a news/article publishing system vs. having the ability to maintain their entire web content collection via the web. Such systems mimic the capability of popular blog systems such as WordPress (www.wordpress.org) and Movable Type (www.movabletype.org) — both very powerful programs.
A big negative of CMS’s is the fact that (out of the box) they tend not to rank well within search engines such as Google, Yahoo, MSN, etc. However, there are ways around this using mod_rewrite on UNIX/Linux systems and if you research the web enough, you may find your CMS offers add-ons/enhancements known as modules or plug-ins which can utilize mod_rewrite’s ability to automatically parse your web site and create ‘search engine friendly’ links. This may require a significant amount of time, but depending on your situation practicality of a CMS to you/your organization it may be worth the research.
All of this aside, popular open source CMS systems on the UNIX/Linux end are Drupal (www.drupal.org), Joomla (www.joomla.org) and Mambo (www.mamboserver.com). Drupal is a very advanced system used by Linux Journal, MTV (I believe in England) and many others… the downside of this system is it has a fairly high learning curve. My understanding with Joomla is many of the original core developers from Mambo’s team moved on to create Joomla so it mimics many of the basic capabilities of Mambo and is now slightly more advanced. Mambo is not a bad CMS however, was developed before Joomla and has a large community base you can use for support and is still being improved upon to date by qualified software engineers.
On the Windows end, you may want to consider looking at either DotNetNuke (www.dotnetnuke.com) or one of Ektron’s CMS’s (www.ektron.com). DotNetNuke is open source software and has a very large support base although support is limited to a forum where inquiries and responses must first be approved by a moderator which can delay response time. Ektron offers their CMS’s at-cost but they offer solid CMS products used by companies such as Yahoo, BAE Systems, etc. and you can talk to a real person when you need to by picking up the phone. Ektron offers CMS400.Net (based on ASP.Net) and CMS300 (having slightly less features and based on classic ASP)… you can review the various features via http://www.ektron.com/cms400-web-cms.aspx?id=1757.
Taking into consideration everyone’s content management needs differ, you may want to take a look at even more options available for review at www.opensourcecms.com that may more specifically match the solution you are looking for. This site lists all the major CMS’s and allows you to test-drive the front-end and administrative back-end on-demand (through their web site) vs. needing to first install on your web server and then evaluate. Google, as you may know is a great search engine for finding even more CMS options if you want to consider a commercial product instead.
And if you decide a CMS is not right for you, search engine results suggest a static/semi-static web site ranks higher than CMS-driven web sites so you have a positive here. Your organization can also manage your web site using a product called Adobe Contribute CS3 (formerly Macromedia Contribute) which allows you to assign users a key allowing them to manage certain areas of your web site while limiting their administrative permissions in the process (i.e. whether or not they can delete files, etc.)
