I began running this website on Drupal 6 shortly after the official release.  Before then, I periodically installed development versions of Drupal 6 on the production server during the weekends so others could judge the progress that was being made.  During this period, I made the claim that I didn't really need any contributed modules to run my site 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.

It could have been a bold statement that I made at the beginning of the year.  Although Drupal 6 interest has finally overtaken Drupal 5, there still are a number of popular modules still under the designation of release candidate, beta, and even alpha.  My site has shown that you don't have to always wait for contributed modules to upgrade a site to the latest version of Drupal.  However, my statement was a lie. By the time Earl Miles released Views 2.0 Beta 1, I found I didn't want to live without my essential modules for very long.

The following are a list of contributed Drupal modules that I wouldn't want to do without here at CMSReport.com.  I am neither the first word nor the last word of which modules you should be running for your Drupal site.  In fact, by coincidence, Kathleen Murtagh has just written a similar list of contributed modules that should be considered.  Some of the modules on my list are still going through their development phase and you'll have to assess the risk of using the modules on your own sites.  Personally, I like to take the risk for my hobby sites such as these, but I am more cautious when using development code for sites managed at my day job.  Whichever modules you choose, be sure to thank the developers that have made your site possible. 

Contributed modules used at CMSReport.com

Sends e-mail to notify both registered and anonymous users about new comments on pages where they have commented. The goal is to drive one-time users that comment back to you site to convert them to real registered users. This conversion step is an essential one in building a blog comment community.

This Drupal site of mine has taken quite a bit of beating the past couple weeks.  While Mollom has been protecting this site well enough from the comment spammers, it isn't designed to prevent the bots from trying to ping me so much.  It has been an incredible experience to see the bots try to open every possible URL and directory here at CMSReport.com.  But probably the real stress on the site has been my testing of numerous contributed modules that are still under development.  Probably using a production server to test new modules isn't the smartest thing for anyone to do, but it does provide a nice adrenaline rush from time to time.

To make a long story short, I'm testing a number of ways I can use a Web content management system more efficiently to run this site.  I also want to do some restructuring of the site so that I have more flexibility in the look and feel of the site as well as how the content is delivered.  For the most part, I'll be using Pathauto, Views, Panels, and one of the aggregation modules.  I'm currently testing the FeedAPI module for aggregation, but none of the aggregation related modules really do what I want them to do.  I'll put up a site recipe in the next month or two on the modules I finally settle on to support this site.

Now it is time for me to go.  Evidently, one of the modules I've installed is causing some cron issues.  Am I having fun, yet?  Yes, I am.

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!