Drupal

Mobile is hot right now. Most of our current clients are actively thinking about, if not proceeding with, mobile access to their web sites or building a mobile application. Guess what -- it turns out Drupal is a good platform for that, too!

When going mobile with Drupal, we're advocating one or more of three different approaches:

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:

Mavis asks,

I have already spent thousands of dollars on my [Zen Cart] website. What would be your advice for [a company] who wants to transfer their site to a new host but not redesign it?

Just like a physical store, the costs of running an e-commerce site very quickly exceed the costs of opening it. And any time you're handling money, you automatically become a target for thieves -- you need to take security seriously, or you're bound to get robbed.

A question came across the Drupal Developer's list today asking whether Drupal could auto-update itself, like WordPress. As someone who thinks about security a lot, the very thought of this horrifies me.

It's a bad idea for several reasons, but the biggest reason:

It could easily lead to the biggest most powerful bot-net on the planet.

This could just as easily happen to WordPress, too. It already has, in fact, to a small extent.

Short answer: it depends.

We still do most of our projects in Drupal 6, mainly because it's been around a few years, and modules we use on many sites are not yet stable for Drupal 7 (and some are still a ways off).

However, for sites that don't need particular modules, Drupal 7 at its core is a nice improvement.

My first Drupal 7 site is a personal one, http://www.hikeswithhazel.com. So far as a user, it doesn't seem that different from Drupal 6, especially if you turn off the "Overlay" module which pops open editing screens in what I find to be a highly annoying way.

How would losing your web site affect your business?

That might seem like a silly question, but a surprising number of small organizations don't think it can happen to them. Think again -- web sites get lost all the time, through a variety of means. The server hosting your site might have a hardware failure. Your site might get hacked. Your web developer might accidentally delete something critical. Your host might go out of business, leaving you stranded. If you're in the tech world, you hear about these incidents all the time.

Mike asks,

I came across your site as i'm a member of NWEN.  My current site is built on a wordpress template and I want to change it as it's pretty rough.  What are the pros/cons of having a site built with Drupal vs. word press?

The simple answer is, WordPress is for designers, and Drupal is for engineers. Kind of.

Like any simple answer, that's only part of the story.

Wesley at The Nubby Admin asks,

Drupal you say? I’m not too mid-stream to change horses if there’s a good reason to do so. If Ubercart has great digital content delivery features and the ability to sell URLs (and obfuscate the real directory structure), then I’d be all ears.

Oh, and your “About Freelock” page and subpages ROCK THE HECK OUT! =)

Drupal provides powerful tools that makes it easy to do all sorts of changes to your web site, but one change is difficult: changing the content type of a node after you've created it.

In general, once you create an item of a certain type, you cannot change that type without breaking it. But for one project, we needed to do exactly that.

Mel asks:

Why would I use Drupal instead of Microsoft Expression Web to create a website?

I actually had to look to find out what Expression Web is--I hadn't heard of it before. It looks like a successor to FrontPage, something similar to DreamWeaver for creating static web sites.

So to rephrase, why should I build a site on a content management system, instead of using a tool that lets me build a site directly?