WordPress vs. Movable Type template development

I have used Movable Type (MT) for a few years now, and I finally gave WordPress a test. There are several things that are similar, but there are some factors of differentiation key that I want to emphasize.

Here are the similarities between WordPress and Movable Type.

A UI nice for the toolEasy admin to install on a logical model organization of remote server (more on this below) with a series of includes for easy maintainability

Syntax of the MT model takes some getting used, but it is very intuitive and thorough. Everything you can think of that you would ever like to do a blog entry is available. If you a category list of if to d' des d' une liste des des d' une liste d' une d' une liste list, you is to use the tag template category, give it a des si vous une catégorie liste des Si d' des d' une liste, vous est utiliser la balise de modèle de catégorie, donnez_ lui des vous est vous is use la la de de, de de de de de, WordPress, allows you to manage the loop PHP. You have access to a variety of things, but you are limited to the current loop of PHP that you are. So if you want to display the latest 10 articles for each category on a given page, you must establish a new loop that provides access to this kind of data. It is quite the maze contexts, PHP functions and attributes to customize these functions. I think that the tags from Movable Type to be much more intuitive and portable model.

This may not necessarily be a bonus using movable type, but if your site is very popular and you want to run on cheap, shared hosting, then static publishing is a great way to go. It creates essentially an HTML page for each article once when you publish your site. Subsequently, whenever a user accesses an article, it is available without having to search in a database. Unfortunately, this feature is also fall in the MT, which I will refer later.

When you work on a new blog model (aka the WordPress theme), and adjust you some markup and CSS, you simply refresh your browser and WordPress instantly shows the result. When do the same with Movable Type, you must republish your templates in the administration tool. To navigate to the correct page, click on publish, wait and then refresh your browser is a minimum of 5 - 6 seconds. Updating just the WordPress page in your browser takes about a second. Why even a small amount of time significant? It depends on your style of development, but I like to tweak not peek. I make a few small changes, and then refresh in the browser to see what it looks like. Repeat this process for hundreds, even thousands of times in a design model. That really adds when it takes 5 seconds more to do with mobile characters.

You can get Movable Type install locally on a Mac, but it is not trivial (this article may help). WordPress to run locally is just as easy that it is on a remote server. I really like to be able to fully develop my template/theme locally and then just push to the server when it is ready. This saves much time, especially with how much faster your local server is more remote.

In recent versions of WordPress (2.9 +), to upgrade to the next version of WordPress is fantastic. Just a few clicks in your administration tool, and it is done. It is the same for plugins. Movable Type has so far been much more involved, and you need to exit your application FTP and rework things. Newer versions may have changed this, but I was off the coast of Movable Type for almost a year now.

Overall, I like WordPress better because its theme more rapid development. When it comes to the use of the blog on a daily basis, they are essentially equal, but when you build themes custom all the time, the ease of development is a key factor.