So MovableType’s latest catch-up-with-WordPress edition is coming soon, and I could not resist mentioning that it is only still catching up with WordPress, with regards to features. The idea is interesting, isn’t it? The market leader catching up with the upstart, but in terms of features, WordPress is a step or two ahead of MovableType, when it comes to managing all things related to a single weblog (notice how I nimbly step around the multiple weblog feature MovableType has, that WordPress does not ), and making sure that your content is accessible in several ways, according to the readers’ preferences.
In short, if I had to chose a Manager for the content of my weblog, I would hire WordPress. For one, the manager is slimmer (download file: 310 KB versus 1.29 MB + lower usage of server space), will work for free, and then also takes care to get the message across effectively, with minimal loss-in-transit, which is most important. Conforming to standards and providing the content in different formats and feeds sure helps with all this.
Indeed, MT doesnâ€™t have this (RSS feeds for comments to a post) by default, but itâ€™s trivial to add – you just need to create another Individual Entry Archive that displays comments in RSS format.
With WordPress, you don’t have to create another archive (with the associated cost of webspace for storing the archive pages), and your readers can keep track of comments to specific posts, or all the posts on your weblog, by default. There are links for the RSS feed for comments to specific posts, as well as the whole blog, available on the default template. Just one example where WordPress outshines MovableType. I am sure there may be some cases where MovableType upstages WordPress, and i wish to state that I don’t mean to say that WordPress is better than MovableType in all aspects. Some folks might just find MovableType a better tool, with good reason.
Sorry, the comment form is closed at this time.