This blog runs on WordPress. I spend a whole lot of my time making Drupal (and teams of Drupalistas) do my bidding. (Another story that’s all over the front page.)
The reasons why I do this:
- WordPress is a CMS that’s built for blogging. This is primarily a blog.
- I create content here. I’m not trying to integrate a legacy system with lots of data and lots of users, I’m not trying to put a lot of media that needs to be very stable, and I’m not trying to create a completely search-optimised web presence. Yet. I’m working too hard doing that for other people to really do it for myself.
- I really like how WordPress ‘gets out of the way’ of your experience for creating good stories in text.
- I appreciate the experience of logging into my own site, swearing at it because ‘I can’t find X’, where X is something I’m very familiar with in one system, and forget all the time in others. It keeps me honest, and remembering what the content creation experience is like for the vast majority of CMS users.
So whenever you find me, and you want to know the answers about ‘Wait! You’re really involved in Drupal! Why does your own site run on WordPress?’
That’s why.
It probably won’t always be on WordPress; I may at some point decide to plan out msamye 2.0, and then I’ll start writing about the process of change, evaluating solutions to fit your needs, and actually doing it.