The April issue of Adobe Edge contains the article, Review of open source content management systems. The article provides an overview of what the author describes as "five of the top open source software (OSS) solutions". The five open source CMS included in the author's list are CMS Made Simple, Drupal, Joomla!, WordPress, and XOOPS. After reading the article, I found myself wondering how we "reviewers" can actually improve our reviews of open source CMS. More importantly, I've come to the realization that I can no longer claim to be non-biased in which CMS I believe is the best out there.

The author does a fine job in the article describing the similarities and differences between the CMS being reviewed. However, one of the issues I have in this article and many others I've read that review CMS is the big jumps in the conclusion:

Drupal, Joomla!, and XOOPS are best for building an e-commerce site because all three offer:

• Inventory management
• Support for third-party payment processing mechanisms (such as PayPal)
• Modules for shipping and sales tax calculators
• Shopping cart functionality

While it is true that Drupal, Joomla! and XOOPS can do e-commerce, none of these CMS can do that straight out of the box. I can just imagine a shop owner or design company trying Drupal, Joomla!, or XOOPS for the very first time and wondering, "how the heck do I get a shopping-cart into the CMS?". While the author does hint in the article that third-party modules are needed to make the e-commerce work, I think the author would have been better off better explaining that "some work is required" to get those features into the CMS.

Dries Buytaert, Drupal's project leader, has just unveiled his latest Drupal project...Mollom. Mollom's goal is to be an automated content monitoring system with one of its initial services geared toward providing a spam filter and CAPTCHA server for websites.

Dries Buytaert: Mollom, my content monitoring startup -

After several months of private beta testing, Benjamin Schrauwen and I are happy to unveil Mollom, your partner in automated content monitoring. Mollom's purpose is to dramatically reduce the effort of keeping your websites clean and the quality of their user-generated content high. Currently, Mollom is a spam-killing, one-two punch combination of a state-of-the-art spam filter and CAPTCHA server. We are experimenting with automated content quality assessments, but these are still in an early testing phase.

CMSReport.com is one in a number of Drupal sites that have been "secretly" testing Mollom over the past several months. Since installing Mollom, I've been able to sleep at night knowing that Mollom is watching over my site. The amount of time I spend on moderating anonymous comments for potential spam has been significantly reduced thanks to Mollom. This is good stuff from Dries Buytaert and Benjamin Schrauwen!

LifeType (formerly known as pLog) dropped off my radar scope some time ago. I'm not sure why, but I think at the time I had the desire to concentrate more on full featured content management systems and less on just blogging applications. So, like catching up with old classmate, it's nice to see this Linux.com article focusing on LifeType:

This is a tough time for blog reading junkies like me. I like to spend some of my time in the evenings winding down by reading CMS related blogs. Well, it seems some of my favorite blogs have decided to take a vacation. For example, many of the working group blogs found at Joomla.org are down.

Last Tuesday evening, I upgraded my Windows Vista desktop to Service Pack 1. If you regularly visit my blog, you know that I'm a long-time user of both Windows and Linux. You also know, that I've been deeply disappointed in Windows Vista.

Linux.com is featuring a story by Susan Linton titled "Drupal 6 keeps getting better". The author claims she has been using Drupal since version 3.1 and seems to know Drupal well enough to write a decent article. In short, she does a fairly nice job of summarizing the features introduced in Drupal 6. However, she ends the article with a rather strange conclusion.

My primary complaint with Drupal is still not addressed in this release. I believe having advertising capabilities is almost a necessity in any content management solution. Instead, Drupal leaves users to their own skills or to use a contributed module. The lack of native advertising support remains a major drawback.

I rarely have seen such request for an "advertisement feature" in the core of any CMS I've reviewed. Yes, some CMS do have an advertisement feature but in most cases the capabilities of such built-in features are usually limited. Either way, I just can't imagine with the latest drive to strip the less needed modules in Drupal 7 and beyond, that the Drupal developers would go for an ad module in the core.

Serendipty 1.3 has been released. This new version of the blogging applications introduces 41 changes. Not only are enhancements and additional features introduced, but also changes to address a nasty cross site scripting issue (security exploit).

Some of the more significant features and enhancements for Serenditpity 1.3 include:

• The karma rating plugin has been upgraded to support nice, CSS-based rating graphics and an overall rehaul on the its coding.
• Make the Spartacus plugin be able to use FTP upload, a workaround for SafeMode PHP restrictions. Also add a remote backend for plugin update checks.
• Import scripts for phpNuke and lifetype.

Alldrupalthemes.com did a performance comparision between Joomla 1.5 & Drupal 6.1. As the author of the post infers, the numbers collected may not mean much to the user in the "real world" and limitations in the test results should be noted. Nevertheless, numbers that compare Drupal and Joomla performance are always interesting.

The conclusions drawn from the results are:

Drupal Module Finder...very cool and very fast. Looks like John Forsythe is owner of this non-Drupal.org project.

The search engine was built from the ground up to produce incredibly fast results. Query times average under 20 ms, and the results are cached for even faster performance.

The user interface is powered by jQuery v1.2.3 and a number of custom plugins. The jQuery Update module was used to improve compatibility with Drupal 5.

I joined the new Content Wrangler Community with hopes of improving my social networking with other content management professionals. Scott Abel discusses his goals for the community on his blog.