Choosing Drupal

So today we hired our first full time engineer. (for those of you who expressed interest in the job, thank you!) And in doing so we came to a resolution about technology, and then some actually. We decided to choose Drupal as our platform of choice for the future Citysquares.com. After much deliberation, debating, discussing, and consulting with ourselves and with others, about going with an MVC framework (e.g., CakePHP, Symfony) vs. Drupal, we finally opted for Drupal. The primary reasons are as follows:

  • Body of work and knowledge. There’s a huge Drupal community, and it continues to grow and grow.
  • Modules, modules, modules. Holy crap there’s a lot of modules.
  • My blog is built on Drupal. Ok, that had nothing to do with our decision, but I’m just a big Drupal fan from experience.
  • Scalability. Time Warner’s media sites are all built on Drupal. Sony Music sites are all built on Drupal. US magazine’s site is built on Drupal. ‘Nuff said.

There are many technical reasons too, many many many. But I won’t get into that – that’s very boring and this blog isnt meant to be boring.

What’s interesting about our decision is that by choosing Drupal, and choosing to work with the Drupal community that unavoidably comes with it, we are, in essence, choosing community. We are allowing ourselves to tap into a community, while bringing communities online, and eventually enabling other communities to bring themselves online. Argh!

This is actually deep stuff, to me anyway. In a more idealogical sense, choosing to go with Drupal is an indication of who we are as people, and as a company, and not just an indication of technical choices and skill sets.

I’m really starting to get into this whole concept of open source in business practice, in management, and almost as a mantra.

I don’t know, it’s heavy stuff and I’m really wrestling with it right now. More to come on all this, as I sort it out better in my head.