WordPress vs Drupal
There has been a wide variety of talk on the internet about different blogging platforms and content management systems, including ways to trick out one system to act like the other. WordPress, reportedly the most widely used blogging platform, and Drupal, the most commonly used content management system in the US, are no exception to our discussions. This question is usually at the maelstrom of our storm: Which platform is better for my next project? To answer this, I want to point out the differences between WordPress and Drupal.
WordPress
WordPress is a system that comes hopped up on easy pills, and because of this, bloggers and developers love it equally. With WordPress 2.8, you can have a whole system online within a few minutes, including a pre-packaged theme. But this blogging platform also comes with some disadvantages.
The Positives
- WordPress is easy to install.
- Thousands of extensions make WordPress flexible.
- Online support in the WordPress Codex is very good.
- Easy to update.
- Easy back-end navigation.
- You don’t need to know much PHP.
Getting a site out of idea land and into code is very easy with WordPress. After you run through the short install process, you have thousands of choices on ways to extend your WordPress install by using any number of extensions, some of which even make WordPress act more like a CMS. Take, for example, Sitemap Generator, a plugin that builds a site maps for WordPress sites. Developers would tell you that having a site map ready for Google to consume is essential. Other CMS-like plugins available for WordPress include user permissions extenders and plugins that give you hierarchical page navigation.
One thing you don’t need to worry about is WordPress’ lack of support. Their support site is very thorough. Even learning about WordPress’ specific functions is quite easy. One more note about WordPress’ positive aspects: since WordPress 2.8, you’ve been able to update the platform very easily. Literally with the click of a button, WordPress can get a new back-end.
The Negatives
- WordPress is too popular, and thus a major target for spammers.
- Limited scope.
The reason I mentioned the ease of being able to update WordPress is because, if left in a legacy state your Worpress install will eventually get hacked. Because of its popularity and its core blogging focus, spammers actively try to take advantage of WordPress to post spam comments and posts. But as long as you update your platform, the spammers stay at bay. Using Akismet also helps.
WordPress, too, when compared to other online content platforms, has a very limited scope. Its purpose is really to blog. So, if you are planning to build a site with multiple blogs, each of which have multiple authors, then look for a different platform. Or if you are planning to build a more dynamic site, one which frequently interacts with a database or collects data online, then WordPress probably isn’t for you.
Drupal
Do you look at a page of PHP and release a high-pitched squeal of excitement? If so, Drupal might throw you into cardiac arrest. While that might sound bad to WordPress lovers, Drupal is, in fact, very similar to WordPress in a number of ways. It too has good and bad properties.
The Positives
- Drupal is easy to install.
- You can theme everything, including the back-end.
- Online support is is very good.
- Thousands of extensions are available.
- You can build large sites.
Since version 5, Drupal (which is in version 6 now) has had a similar step-though installation process to that of WordPress. But some call it more challenging. The install processes of both platforms seemed equal to me, neither of which were too complicates. As long as you know your database login information, you are fine.
Similarly too, Drupal has plenty of extensions. Installing extensions, too, is just like installing them in WordPress. Download the files and copy them into a plugin directory.
The major advantage you get from Drupal over WordPress is that you can build sites that go far beyond the blogging scope, though you can blog with Drupal too. Everyone from large corporations to small businesses use Drupal to give themselves a usable web space. Shopping cart systems, for example, are much more common in Drupal than in WordPress. If you use Drupal, however, don’t expect the ride to be as easy as it is on the WordPress train. Getting Drupal to do what you want can sometimes take writing your own PHP or modifying extensions, even though it gives you an excellent framework for adding content and pages to your site. And it comes with more robust architecture for you to exploit in sites, like the ability to add pages in a hierarchy.
The Negatives
- Building extensions requires a thorough knowledge of Drupal’s hook system.
- You must be very well versed in HTML, CSS, and PHP.
- Back-end navigation isn’t as friendly.
- Less clear distinction between front-end and back-end.
Drupal, unlike WordPress, just isn’t as user friendly. There is less of a distinction between the back-end and the front-end of a Drupal site, which often made me feel confused about my location. I kept looking for a back-end, which is why I recommend skinning the back-end and front-end differently. Also, Drupal’s back-end navigation isn’t as friendly. More clicking is involved to get you into CMS settings and content creation, whereas WordPress has everything conveniently organized in their back-end menu.
Those are some basic differences between Drupal and WordPress. Here’s what you should take to the bank: each of these systems can be used to blog, so take that as an excuse to learn both. Once you start blogging in Drupal, you may just turn into a PHP whiz that will never resort to simple blogging again. Or you might find yourself prepared to build more complicated sites for larger clients.

Drupal and WordPress both have their pro’s and con’s, that’s for sure. However, there are CMS’s out there that are way more robust and offer many more features.
Take for instance, Preation’s Eden Platform offers an easy to use, drag and drop WYSIWYG editor.
Also, their platform has an SEO rules module built right in, and that translates to higher levels of qualified traffic. The rules module coaches you through the page creation process, detailing how to build your content around the specific keyphrases you’re targeting.
Hey Ryan,
Thanks for your comment. You are right, there are a number of CMS platforms out there that can do way more than Drupal and WordPress. I happen to love Typo3, which works very well for very large websites, though it is harder to learn.
WordPress, too, when compared to other online content platforms, has a very limited scope. Its purpose is really to blog. So, if you are planning to build a site with multiple blogs, each of which have multiple authors, then look for a different platform. Or if you are planning to build a more dynamic site, one which frequently interacts with a database or collects data online, then WordPress probably isn’t for you.
This piece of information is simply not true. There is a specific production for multiple sites called WordPress MU. Same power and flexibility but for more people. Combined with the buddypress plug-in, this is the leader of the pack.
With regards to database calls I see no water for your argument as it is all php calls to a database.
Thanks for the great explanation Zac. I haven’t read a more detailed post specifically on Drupal and WordPress. It looks like I will be testing Drupal in the near future :)
I don’t have advanced skills in PHP, do you think it would be a steep learning curve to learn how to use Typo3?
Typo3 is probably the hardest CMS I’ve ever had to learn. It really is a giant, but that’s because it’s good at handling giant web sites. Once you learn how to template, everything else seems easy. After you learn Typo3, you really see how powerful it is.
You don’t need a very advanced knowledge of PHP to get Typo3 running, but you do have to learn the Typo3 template language called Typoscript. Knowing advanced PHP comes in handy if you want to write Typo3 extensions.
I think the biggest problem with drupal is the fact that you need to know so many things about its hook system – the learning curve is just so high that it requires a big commitment for development.
I would totally agree with that! To be honest, I’m not so sure why Drupal is so popular. Hooking the system is something I didn’t want to spent the time to learn. Expression Engine is a good alternative.
It’s going to be a while before we pick up any CMS cloud offering from the likes of Oracle. Acquia have recently set up Drupal Gardens which is a cloud based service which feels very rosy. There are a host of causes why we are not traveling onto the cloud more quickly, the main reason is organisational change where budgets and contracts are set and granted years for 3, 4 even 5 years. Come replacement time some customers are asking CMS in the cloud but then have to debate some other topics such as integrating with CRM & some other back office systems. I suppose it will come about eventually.