Drupal

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!

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.

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'll have to browser drupalmodules.com and find all the fun stuff there is to see at this site.

You and I have a dirty little secret. Many of the Web applications that we call content management systems (Web CMS) are not really content management systems. Huh? A lot of this confusion stems from the difficulty most of us have in answering what should be a simple question, what is a content management system? Scott Abel, The Content Wranger, has noted in previous comments that one of the problems in discussions about content management is that we really lack a common definition of CMS.

Last December, I mentioned my excitement about Drupal's project lead, Dries Buytaert, along with Jay Batson starting a company called Acquia. While it was known that the $7 million startup would focus on Drupal for the enterprise, what was not known was the products and services that would be offered by the company. In a press release today, Acquia finally unveiled its roadmap to commercially support Drupal.

The company announced the two initial products and services it will be offering, Carbon and Spokes. Carbon is Acquia's commercial supported version of Drupal which will focus on social publishing applications. Spokes is an update will be an enhanced update notification sercice that provides "site owners personalized alerts with actionable recommendations". At this time I'm, not clear as to whether Spokes will be available for just Carbon or for all Drupal distributions. Both services will be available through a subscription offering.

Last night, I took the opportunity to spend some time with the Drupal community at a Twin-Cities Drupal Meetup. My trip to Minneapolis for the meetup was on the tail-end of a 1300 mile drive. Those miles covered a drive that looped me south to the state of Missouri and then eventually back north. My activities during the past week ranged from sleeping in the Missouri woods at an old scout cabin with outhouse included...to having conversations in Minnesota with some of Drupal's brightest and most active members.

Open Source Community was the first place I saw mentioning an error in a post at Mashable.com regarding Drupal 6. OSC's article is Mashable Blunders, Cleans it up, and Moves on!

A few days ago, I mentioned that "Drupal 6 feels ready to me" for public release. Evidently, that was more than feeling as Drupal 6 was released early Wednesday morning.

Yesterday evening, I spent about two hours updating my site from Drupal 5 to Drupal 6 RC 4 for another weekend test at my site. About 30 minutes was spent backing up the site and installing Drupal 6. The rest of my time was spent with tweaking things via Drupal's admin menus as well as looking at the contributed modules and themes available for D6. I'm currently using the Salamander theme and only two contributed modules, Image and CAPTCHA. I also spent some time placing snippets of PHP code in my blocks to replace many of the functions I was doing with Views. The end result is that with only two hours of work, I am just fine running CMSReport.com on Drupal 6

As I said last week, it's amazing how many people overlook the power of Drupal...even without its contributed modules. Yes, I'll be glad when the Views, Panels, and even the TinyMCE contributed modules are ready to use with Drupal 6. But I've always looked at contributed modules as modules of convenience and not necessity. I'm convinced that most people do not have to wait for Views to move onto Drupal 6. Views only automated a number of SQL tasks that can easily be done with PHP. Some Drupal users are going to object when I say it is "easy" because they are not PHP developers, but you know what, I'm not a PHP developer either. In fact, I'm kind of slow, but I seem to manage along just fine with D6.

As usual during this period of the development process, people are wondering if the new version of Drupal is ready to be released or if there will be another release candidate. Whether this is the last release candidate or not for Drupal 6 I'm not sure anyone can really say. All I will say is Drupal 6 feels ready to me.