…waiting for MovableType to rebuild 800 posts is but one more reason to wake up and join the WP crowd (yes I will James, no need to spur me on, it’s a matter of time). MT is like, so…. 2002. Tired. — Alan Levine
In a few minutes I’m going to a meeting which should push forward the long-overdue upgrade to UBC-OLT’s weblog and wiki hosting environments. As of now, our plan is to install the latest release of http://www.sixapart.com/movabletype/”>Movable Type as our weblog system, and most likely Wikka Wiki for the free-text crowd (though our pilot with PMWiki has been quite successful).
The decision on a weblog platform has been tough. I can’t really disagree with Mr. Levine’s assessment of MT — especially the point about rebuilding (though the dynamic publishing option with the new version may address that). I’ve been underwhelmed by our test intallations of MT 3.1x — it’s okay, but hardly revolutionary. I had hoped that version 3 would have had more useful user administration features for large numbers of users. And it would be sexier to do something open source.
So why are we sticking with a ‘tired’ system? You may also be asking…
Why not WordPress?
I’m impressed with what I’ve seen and heard about WordPress. And if I followed one of my personal maxims on technology use (just do what the coolest, smartest people you know are doing) this would seem to be where the mojo is (no offence to everybody else). If I was just picking a system for myself, it would probably be my choice. But the standard WordPress requires a fresh install for every new weblog, which renders it unsuitable for us. My read on WP Multi-User is that it is presently too buggy, and the office techies have some serious reservations concerning the way that it is built.
Why not Drupal?
This one ranks pretty high on the cool scale as well, and I know lots of very groovy people doing very groovy stuff with it. I had initially eliminated Drupal from consideration because it did not allow for individual templates for weblogs, though it looks as if that is becoming less of an issue with the latest and pending releases. Ultimately, the uniform branding issue points to the essential purpose of the system, with aggregation features promoting a “communal blogging” approach, as opposed to MT’s more “author-centric” one. It may merely be an indication of UBC’s culture, but my read on our users here is that they like the stand-alone qualities and easy personalisation that MT offers. Then again, we’ve been running MT for the past two years, so it’s hard to guage if there is an untapped potential market for the more social, systemic approach.
If we had unlimited resources, I’d try to run MT and Drupal concurrently to support both these approaches. But obviously we don’t… and to be frank part of the reason we are likely sticking with MT is because our people already know it. I am hopeful that in the near future we will be able to establish some sort of partnership with another organization to allow us to begin using Drupal without doing a full-on installation of our own, but that’s another story to be told at another time.
Why not b2evolution?
We gave b2evolution a good test run — there are a few things I like about it, mostly having to do with user management, which is nicely set up to support a large number of bloggers. Ultimately I don’t feel like we can make the jump for two reasons: a) our test migration of MT blogs to b2 was a little screwy in places (especially comments and trackbacks) and b) I found the user interface a bit cluttered and confusing — a few of our testers also expressed this concern (it strikes me as a case of an application trying to do too much).
Part of the reason we are looking to stick with MT is sheer momentum (or lack of it, depending how you look at it). We have a couple hundred active weblogs on the old system… and moving to MT 3 should be the simplest option in terms of migration, training and user adaptation. The relative lack of change from MT 2 to 3 is a positive in this respect, I would expect that most users will notice little difference between the versions, and most of the stylesheets and mini-codehacks we have developed over the past couple years should also be salvagable. By my estimation, these issues outweigh the costs of licensing. For the short term, at least, MT 3 feels like the lowest risk option.
It’s quite likely I am demonstrating my ignorance with this snapshot overview of our options. And I am more than willing to listen to my peers with regards to factors (or other systems) I have not taken into account. The thoughts expressed and work performed by others has already moved my soul to confused upheaval. By all means, pile onto my delirium.