Musings

Sunday, May 14, 2006

Update: Static vs. CMS

Over the weekend, started to spec out the port to Mambo, but now the CMS game is back up for grabs.

When the news broke last year about the split in the Mambo project, I figured things would settle down and a reunification like what is happening with Debian would take place.

It looks like that isn't the case though, which makes the whole move from static pages to a CMS a bit murkier in the coming days (I'm beyond pressed for time, so I'll block out one weekend to do the whole port and won't want to have to come back to it).

Since I'm clearly going with an open-source platform for cost savings, what it comes down to now is:

Mambo
Drupal
Joomla

My bias is developing around these points:

Joomla +: Joomla is the variant of the Mambo split; essentially the entire development team left and started Joomla. (In programming, I'm typically always a fan of the core dev team over the bu.)
Mambo +: Mambo has been around for 5 years and so has stable builds of the modules I would implement.
Joomla +: Mambo has sold out to Ansearch, furthering my support of the dev group.
Drupal +: A year of stable development behind them and has developed a fairly robust community.

Two months ago and prior I would have made the move to Mambo, but with the selling out to Ansearch and the departure of the second head developer, Mambo is pretty much out of the running.

The top choice now is Drupal, but Joomla is making a major release with 1.50. It was slated for release last month, but is still pending.

So I figure, I'll hold off until the 1.50 release then get a guage of which direction to go.

General indicators that Joomla seems to be overtaking Mambo:



The Google Trends indicator will suffer distortion from the high cross correlation of the term "Mambo".



Blue: Joomla || Red: Mambo || Yellow: Drupal