Tomorrow is another WebHeads meeting, and I’ve been asked to talk some about Content Management Systems and our experiences with them. At last month’s meeting, Edgar talked about using Subversion for versioning web-applications, which I recapped with the blog post Using Subversion for Web Projects. For this post, I plan to outline some generalized notes about the different CMS’s we’ve used to help have a more focused talk for tomorrow.

This post is not intended to be read as a conventional post. I am updating this post live:

Content Management System

Google define: content management system

System for the creation, modification, archiving and removal of information resources from an organised repository. Includes tools for publishing, format management, revision control, indexing, search and retrieval.
members.optusnet.com.au/~webindexing/Webbook2Ed/glossary.htm

In the context of a Web site a CMS is a collection of tools designed to allow the creation, modification organisation and removal of information from a Web site. It is common for a CMS to require users to have no knowledge of HTML in order to create new Web pages.
www.bized.ac.uk/educators/16-19/business/marketing/lesson/sup_glossary.htm

Resources

Reviews

PostNuke

OI PostNuke

Mambo

OI Mambo

Xoops

Interoperability Xoops

Drupal

WordPress is an open source weblogging platform. It’s the platform I use to manage this blog and the platform - with some modifications - that Global Voices runs on. It has a reputation for being very user friendly, but for having some underlying architectural problems that make it hard to scale. Drupal is an open source multi-purpose content management system designed for the support of complex websites with multiple authors. It has a reputation for being ludicriously flexible, ungodly powerful and far too complex for mere mortals to use.
http://drupal.org/node/29364

OI Drupal

MediaWiki

OI MediaWiki

WordPress

OI WordPress — this site!