We've had several clients recently chafing at how confining Drupal sites can be -- it can be a lot more work to make individual pages vary from the template, and if you have build web sites using a tool like Dreamweaver, you can't tweak the layout the same way.

We call these hand-built sites brochure, or static, because they are a collection of files you build once, and then don't change very often. Drupal is a Content Management System (CMS), a program that helps you manage content.

So what's the difference? Why would you want Drupal over a static brochure site?

Last weekend I had the good fortune of being able to attend TEDxRainer. The event could best be summed up in one word:

Passion.

Everybody there seemed passionate about being there, sharing ideas, looking for ways to make the world a better place. And after spending a solid 10 hours among such passionate, engaged people, it's hard to come away without being inspired.

A couple weeks ago I wrote a post on why customers complain about Drupal -- the short version is that they either had incorrect expectations, or "developers" who were in over their heads. Nothing wrong with Drupal there. There are some very legitimate downsides to Drupal from a technical perspective, however. Here are our top 6, and why they're not enough to keep us from recommending and using Drupal for nearly all our work:

At Freelock, we're huge fans of Drupal. But we keep running into customers (or potential customers) who are terrified of it. So here's our take on why.

5. I just want a web site! It's too complicated!

Drupal is not just another web site builder. In experienced hands, it's easy for a Drupal developer to spin up a simple web site on Drupal -- I've done it in a matter of a couple hours, complete with initial content. But if you're not experienced with Drupal, the learning curve to get something useful is steep.