MT 3.0 is going into expanded alpha testing. Huzzah.
Features on-tap:
The official 3.0 release will contain a significant change to the existing interface that embraces web standards, usability and localization. This will also be reflected in a new set of default templates that will implement more of the best practices that both Movable Type and TypePad have become known for.
I’ve been diddling around with my templates, and coming to the conclusion that I really need to consider starting over fresh with them. Too much stuff that’s getting harder and harder to maintain. Something to consider.
With a suite of comment management features and versatile comment registration–utilizing a centralized authentication service we’re calling TypeKey–Movable Type 3.0 will give you more control than ever before over the public face of your website. We’ve spent a lot of time planning a comment registration system that will fit the needs of different types of webloggers, and we have focused our attention on a system that will encourage registration and open communication.
I have mixed feelings on comment registration. My inclination is against it, particularly if it provides any delays for folks actually leaving comments.
On the other hand, damn, that comment spam crap is annoying.
On the gripping hand, do I really want to be tied nito what sounds like a centralized comment registration service? That sounds like asking for trouble (unless the default is to allow comments unless not authorized by TypeKey, i.e., if TypeKey can’t be reached, allow the comment).
In addition to providing authentication for comment registration, TypeKey’s open nature will enable developers to build applications upon the infrastructure, utilizing its authentication hooks. Since TypeKey and comment registration are such a significant addition to Movable Type 3.0, we’ll be going into more detail about these features later this week.
Good.
In addition, our support for the Atom API and syndication feeds will allow Movable Type users to utilize the richer content model offered by the new format, including the use of clients that communicate through the API.
Atom looks to be the fancy RSS that folks have been clamoring for. I’m not an RSS guy, but I suspect that I could be pretty quickly, depending on circumstances.
And for developers who like to get under the hood, we’ve added many new hooks into the application, allowing plugins more control over data, configuration, and user interface.
I tend to avoid plug-ins that require screwing with the actual MT code. The more hooks that are provided that can avoid that, the better.
As an editorial comment, MT 3.0 has been a loooooong time getting on the starting line. That’s not so bad, but SixApart has not done a good job of communicating status — even just to say, “Hey, we’re working on it, we’ll let you know more Real Soon Now” more often than quarterly.
Communication is important, and frequency of communication is essential for maintaining interest. The blogging community, of all folks, should know that.
(via Les)
I am just happy to see the gripping hand part of the argument being taken seriously.