Drupal has much to offer, such as the ability to define content types, their structure, required fields, and assignment of accessing and editing content as defined by user roles is nearly as simple as it is in WordPress (now). Consistent content input removes inconsistencies associated with multi users sites. The resultant is web pages that look neater. Drupal Filters can strip off any undesired formatting – but without loosing the authors intent as this is retained in the database for future reference. This is cumbersome in WordPress. Drupal also opens up opportunities to write mySql reports using the Drupal friendly Views Add in component and extract this content and place anywhere on a page or peripheral area such a left side bar.
The new version Drupal 7 does provides easier access in the backend. (It used to be more annoying to access.) You can slap up a Drupal site in about the same time as a WordPress site, but often choice comes down to which has the most amazing free templates for new users.
From Dries Buytaert, Founder and Project Lead of Drupal
WordPress looks better on the outside (administration UI); Drupal looks better on the inside (architecture, API design).
WordPress is better than Drupal at blogging, but Drupal excels when you have more sophisticated needs. Non-technical people tend to like WordPress better because it is easier to use. People with a formal background in engineering seem to like Drupal better because it is better to develop on/for. There is a gray area in the middle that I would describe as follows:
- Designers that developed some PHP coding skills tend to like WordPress because they can quickly ‘hack’ WordPress and get their job done.
- Developers that developed some CSS/PS skills tend to like Drupal because they don’t want to hack Drupal — they want clean code that is maintainable and upgradeable. (I know it is dangerous to generalize and I recognize that there are many exceptions.)
- For the past 3 years, the number one stated objective for Drupal is improving usability. The result of that collective effort is a completely new administration backend, improved information architecture, and more. It will soon be available as Drupal 7. I expect Drupal 7 to have a positive impact on Drupal’s adoption, both with a non-technical and a technical audience.
- If you don’t want to deal with installing, upgrading or scaling your Drupal 7 site, take a look at http://drupalgardens.com — it is free, and allows you to build a Drupal 7 site similar like you would on WordPress.com or SquareSpace. It is designed to take additional complexity out of Drupal.
- I think Drupal Gardens could be a game changer for Drupal as it eliminates many barriers to adoption for Drupal. If you previously discarded Drupal because it was too hard to use, I recommend looking at Drupal Gardens. It is early (we’re still in beta) but keep an eye on it (we have 25,000 sites already)
From Stanton Champion, Marketing Manager at uTest
WordPress is a terrific blogging tool, and we use it for our blog sites. It works very smoothly for rapid content creation, and it’s easy enough that I can allow get in the company to write without having to spend time training them. Creating original content is a big part of our strategy, and having a platform that makes that easy is a plus for us.
Drupal, on the other hand, is a powerful but difficult tool. It requires more training for even basic content creation, and it takes a lot of time to get it up and working correctly. For big sites with lots of moving parts, Drupal is a great system. But for blogs, it’s overkill. In the time it would take me to properly train everyone to use Drupal, they could already be publishing from a WordPress.
- fast easy content creation platform
- low training overhead
- easy to setup and get going
- simple to add new sites and blogs as our content needs expand
- sophisticated CMS that can do anything
- high training overhead
- difficult to setup and get going
- great for complex sites that need to do a lot of different things