Warning: include(/home/cfbauer/public_html/wp-content/themes/ChrisBauer.org2.0/l_sidebar.php) [function.include]: failed to open stream: No such file or directory in /home/cfbauer/public_html/wp-content/themes/ChrisBauer.org2.0/archive.php on line 5
Warning: include() [function.include]: Failed opening '/home/cfbauer/public_html/wp-content/themes/ChrisBauer.org2.0/l_sidebar.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/cfbauer/public_html/wp-content/themes/ChrisBauer.org2.0/archive.php on line 5
WordPress and Drupal: Which is the right tool for the job?
The following is an article intended for the more tech savvy among us.
I worked for a web agency that develops Drupal websites almost exclusively. I use WordPress to create websites for my own clients. I’ve worked with both content management systems extensively, creating a unique vantage point to compare the two.
The most noticeable difference between WordPress and Drupal, at least initially, is the administration interface. In a nutshell, Drupal’s interface is powerful yet confusing. It is intended for website administrators and technically proficient folks to configure many aspects of a website. WordPress, on the other hand, uses an admin interface intended for those less experienced in website development to modify website content and settings. This trade off means less power.
Digging deeper yields more interesting notes. While not available in the standard admin interface, a great deal of power and customization opportunities exists in WordPress’ theme layer. This power means web designers and developers familiar with html, css, and a little PHP can use these technologies in conjunction with WordPress and its template tags quite easily. Developers use these technologies to quickly build WordPress websites their way, integrating well documented WordPress code with languages they already know.
In contrast, Drupal requires users to learn how it operates before a developer can do much. Standard fare for Drupal sites uses a point and click interface, while developers install and configure contributed modules. Drupal’s approach means that once a user gets inside the mind of Drupal, advanced functionality becomes easier to implement. Rather than requiring a user to write PHP code, he or she can point and click–with powerful results.
As a user becomes familiar with Drupal, adding marginal functionality becomes easier. Knowledgeable web designers and developers, by contrast, have an easy time getting started with WordPress. As additional functionality becomes required, the developer must find a way to fit advanced features into a platform not built for those uses. It’s not impossible, just difficult. I made an oversimplified chart to illustrate:

Looking at the history of each project, these differences are not surprising. WordPress was built as a blogging engine, while Drupal was built from the ground up to support more complex websites. While WordPress is moving towards robust content management applications, Drupal is making strides toward intuitive usability.
In order to determine the best tool for a project, look at your needs and resources. WordPress is an excellent solution for a quick, simple website or blog. Drupal makes sense for providing functionality with different content types, views, and integrated features. Of course, this discussion omits other obvious options like Joomla, as I am less familiar with them.
If you’re only familiar with one content management system and have a project with different needs, I encourage you to consider other options. There is a learning curve, but building a website isn’t a one-size-fits-all endeavor.
