What a CMS Should Be

Eight Black's Simon Chen wrote a really good article today on what a Content Management System (CMS) should be. He argues that, for a company considering a CMS solution for its website, "buying into a stand alone CMS is just not logical." Instead, open source CMS' like WordPress are the way to go.

I agree. In fact, in my last job in Pakistan, I spent a couple of years trying to convince firms working in that country's development sector (both government and NGOs) of exactly that. I didn't use WordPress, but I did use, among others, applications like Mambo, Joomla, Drupal, Typo3, phpBB, Alfresco, Moodle, MediaWiki, as well as countless plug-ins, add-ons, components, and modules. Each CMS has its own strengths and weaknesses, of course, and some are designed for specific things (you can't do much else with the message board system, phpBB, for example) but all of them do their job quite well. [Good article on how to choose an open source CMS]

And, though over the last year I've worked mostly with commercial systems like Intranet DASHBOARD (iD) and Microsoft Office SharePoint Server (MOSS), I really do think that open source systems are a great way to go for most small companies and, increasingly, for medium-sized companies as well. It's only large firms that need much more than just a CMS solution that truly benefit from all the other features that systems like iD and MOSS bring with them. In fact, I'd almost feel silly using something like MOSS in a small company environment. That's like having a 40-seater bus as the company car for a firm that employs 15 people.

Anyway, my point is that Chen makes a good point, though it is worth it to look at much more than just WordPress.