Drupal: The Next King of CMS?

    December 26, 2007

Earlier this month I mentioned on the Platinax forums that I was keeping an eye out on Drupal as a potential CMS for the future.

This week Aaron Wall put his weight behind predicting that in 2-3 years time Drupal will be the CMS of choice.

What Drupal has going for it over other platforms is the sheer flexibility to integrate most bells and whistles of publishing, yet also focus on community integration and engagement.

A chance visit to another site showed me the power of Drupal – check this out: Lime.com

It is not only set up as a feature-packed online magazine, but also features community involvement.

The site features:

1. Today’s Most popular
2. Featured Members
3. Latest forum posts
4. Tag list
5. Blogs
6. News
7. Polls

It has everything a CMS should have, and more.

More importantly, it delivers a format that I absolutely think every serious website should be following for the future.

Familiarity with Performancing and Threadwatch have already sold me on it s flexibility and usability, not least with community integration and development.

I think webmasters need to stop thinking of websites as a collection of pages.

I think websites now need to see as a publishing channel – an online magazine featuring news, information & help, community, video, and more.

I think it’s especially important to leave plenty of room to manoeuvre with video, because if you can make & integrate that into a website, you have become a TV channel – and that means potential syndication in the still embryonic but rapidly expanding IPTV market.

That means tapping into the future.

My problem as a webmaster is that while WordPress suits blogs and small sites fine, it simply isn’t geared to community participation – featured author and commentator profile pages are not a default part of the set-up, plus WordPress has never really integrated community forums.

The result is that for my larger sites I often end up with one or more WordPress installs at the front-end, with a vbulletin community in the centre.

The result is a disconnection between the WordPress content and the community members, with myself having to link to the community to continue discussion, or else face having my vbulletin members sign-up for the WordPress install to comment.

The disconnection is a serious flaw in my publishing strategy, but looking at Drupal, I can see this bridge is gapped by default.

Maybe WordPress will look to address that in future, but my feeling is Matt Mullenweg has decided that WordPress’s strength is as a blogging tool, and remain focus on that, rather than introduce potential weaknesses and accusations of code bloat.

And while vbulletin offers a specialist forum platform, and has recently introduced vbulletin blogs, vbulletin is still a forum platform, not a CMS.

I’m now left looking at my websites, looking to the future, and can see that I need to try out Drupal, and explore the functionality. Will it really offer me the CMS of choice for now and the future?

If there is a possibility that it will, I need to get on the boat now.

(Note on Joomla: I’ve never liked the structure or coding – seems a very bloated, over-crowded attempt to create a CMS that somehow seems to struggle with basic functionality. Having been asked to look at SEO issues with Joomla a few times, I’ve developed an complete dislike of the platform – so much so that when a charity recently approached me looking for free SEO work on their CMS, I advised they would do better if I rebuilt it in WordPress for them.)