Content Management

Joomla 1.5 & Drupal 6.1 Performance Comparison

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

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.

Social Publishing Systems to topple the CMS

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.

Discussing Joomla!

One of the neat things about managing a site like CMSReport.com is that discussion on a topic can happen when you least expected. This is exactly what happened in the comment section of a rather benign post regarding a Latin American University's use of the content management system, Joomla! I was thanked by Open Source Community's Amy Stephen, also a Joomla! user, for posting an excerpt from one of the Joomla! working group blogs. Instead of a "you're welcome" I decided to ask some questions that have been puzzling me about the Joomla! community for some time.

The new dotCMS 1.5

A new version of dotCMS, an open-source J2EE enterprise class web content management system, was released this week. dotCMS 1.5 incorporates web content management with CRM, eCommunication tools and ecommerce.

New features introduced in dotCMS 1.5 include:

  • Content "Triggers" using JBoss Rules to allow rule based user segmentation by usage.
  • Business Intelligence Reports - Integrated with Jasper Reports and iReports allow detailed and customized reporting on site usage, transactions and content activity.
  • Improvements to User Search Segmentation, Permissions and Management.
  • Revamped Campaign/Communication Manager.

Acquia unveils enterprise support for Drupal

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.

Joomla.org converts community forum from SMF to phpBB

The Joomla! community just completed migrating their forum from SMF over to phpBB3. Brad Baker posted some of the details on Joomla.org's use of phpBB3 for their forum. In part, some of the move to phpBB stemmed from Joomla.org's discomfort from bridging GPL applications with non-GPL applications. Baker answers the question in his own way.