At this stage, you must have noticed that is-there.net has migrated from Drupal to WordPress. Why? Well, we have a number of reasons, some petty, to a few rather major ones:

1. Drupal’s anti-spam modules were failing on us. Even with both the Bad Behavior and Spam modules installed and activated, spam bots were still hitting on the site. Customizing the modules was possible, but…
2. Drupal wasn’t the most suitable CMS for a relatively non-group blog like this one. Generally, CMSes like Drupal are used for community sites and group blogs like Performancing, due to the multitude of features provided for such applications.
3. Drupal: Feed updating through cron jobs wasn’t working. Wierdly, the daily feed updates weren’t going through, forcing manual updates - which if you noticed, were occuring sporadically. WordPress offers plugins that work out-of-the-box, though it must be said that substantial effort was made in trying to get Drupal’s aggregator and aggregator2 modules to work properly.
4. Drupal was relatively CPU intensive - This isn’t really new if you’ve been keeping up with the Drupal forum. We’ve noticed a few threads addressing Drupal’s relatively high CPU usage as well. Of course, we’ll be the first to admit that WordPress isn’t the poster child for CPU usage either, but it’s still better than Drupal (in our experience, that is)
5. WordPress offers far more plugins - providing greater “one-click” customization. Now, this is probably still an understatement. Just subscribe to wp-plugins.net’s RSS feed to see the pace of updates in WordPress’ plugin community. And not all plugins go through wp-plugin-net.
6. Drupal’s admin interface just wasn’t cool enough. Admittedly, we place quite a bit of emphasis on GUI, and WordPress just won by a mile. Let’s not forget the wide range of admin skins that the WordPress community has created too (e.g. Tiger Admin).

That’s about it for now. We’re sure there are quite a few more, but they don’t come to mind at the moment. If we happen to remember more reasons why we switched from Drupal to WordPress, you’ll be the first to see the Part 2 of this series.