WordPress vs Drupal: Todd Zeigler’s opinions on whether to use Drupal or WordPress to accomplish various publishing tasks depending on the relative ability of each software to excel in particular tasks. Though I agree with some of the premises, saying WordPress Mu is not quite ready for prime time is a very bad generalization and dependent on Todd’s experiences with a very particular need (developing a network of blogs that share content and is centrally managed) that he tried to fill with Mu.
I write the same post in spanish 😉 in Carrero.es
wordpress.com wordpress mu.
it shares developers, and much of the same codebase, but just because wordpress.com does it, doesn’t mean you can do it with MU.
And it wasn’t even a fair generalization as he was apparently trying to use MU for something it wasn’t intended to do.
Even since then, the community has made leaps and bounds in terms of available plugins, and the aggregated content he was looking for really isn’t all that hard for a developer to whip up. Especially if you’ve got recent posts.
It really comes down to picking the right tool for the job, and possibly be willing to code up extras that you want.
I also agree with Adam – expecting the cool & global features of wp.com to be in wpmu is just… I dunno. But I am still surprised at the amount of people who show up in the support forums thinking they can get rich with a quick install and be competition for wp.com. They’re not gonna give away all the goodies.
I am currently setting up a WPMU site. This isn’t a “traditional” site. We are taking a rather popular political blog that is already on standard WP and adding in a few other blogs. I am using WPMU to handle this. Commenters will sign up for an account. While a lot is true in this article, it can be done with WPMU. It has taken quiet a bit of coding to get done, and testing has been going great. On the flip side of the coin, Drupal is not as easy to learn as WP and that presents downfalls.
WPMU could use some better documentation.
Yes Drupal is a lot easier to create different content types too. You have to code in new content types into WP, but atleast wp_posts does have a post_type field that isn’t constrained by an enum, so it is possible (this same site I have done exactly that. 2 new content types – newsitems and stickyposts). I ended up doing a minor core hack to put a drop down on the manage posts pages for content_type (beats writing a seperate page), but overall it was very simple.
I’ve recently switched from MU to multiple WP installs, and I’m MUCH happier. The plugin choices are much richer, the database load is MUCH less, and my bloggers are MUCH happier with the site overall. MU does a lot of things, but doesn’t do many of them well.
We were using WP as the CMS for our site and recently switched over to Drupal. Ultimately it comes down to a question of what you need – WP is quick and dirty using a blog-style approach to content while Drupal has a higher learning curve but more flexibility in its content model and better suited for sites that need personalization features. If you’re evaluating them a good approach is to download the jumpbox for each and compare them side-by-side. This way you can do an “apples-to-apples” comparison and not get spun out on setup of each->
http://www.jumpbox.com/jumpbox.....ing-system
http://www.jumpbox.com/jumpbox.....ent-system
sean
I use drupal for my site and wordpress for my blog.
Well you are right. But I think Todd’s right also. Isn’t it better to use a system that is designed to do Q than to use a system that is designed to do M but can be extended by plugins to do like Q?
What’s so bad on being the number one in blogging? WordPress is not a CMS and Drupal is not a blogging engine. Both are winners in their wide niche.