Just determining which to make use of. MovableType or Wordpress. MT has one important strength is static posting. Since wordpress has super cache, can there be any reason to us MT?
You are not telling enough regarding your must tell which might fit them better. Nevertheless the MT posting model and Wordpress super cache aren't actually comparable. The previous provides you with as they are a number of posting models (static, dynamic, batch queue) As well as other cache systems which you'll mix with respect to the content, while Wordpress Super Cache is really a wordpress plugin that's here to relieve the performance problems natural towards the always-dynamic character of Wordpress.
Let say you are serving HTML pages, say with items of PHP inside them to create the comparison even closer (posting static HTML is not WP's strength whatsoever), here the way the two systems compare:
Movable Key in static posting mode: - add/change content -> MT will publish only individuals files that should be reconstructed, around the filesystem. The database is solicited only at this time And just for that templates which were not already pre-calculated and cached. - customer demands an origin (HTML, XML, PHP, whatever) -> web server brings the file (possibly interpretation it through PHP, server-side includes etc.) and serves it. MT and also the database don't get in the manner here.
Wordpress + Super Cache: - add/change content -> Wordpress updates the database - customer demands a webpage (a PHP script) -> web server launches Wordpress through PHP, Wordpress pulls content either from the database (then cache it) or from the cache (which requires additional CPU and memory), transmits it back to the net server which transmits it to the customer. A lot more layers and assets involved at every request.
The important thing talents of MT WRT to Wordpress are that:
- MT enables you to chose, template by template, whether a webpage must be released 1) statically (either soon after a big change or put into a publish queue) or dynamically (tugging this content from the database at each request).
- MT offers a multitude of cache configurations for every template as they are, not needing any wordpress plugin to optimize your website.
- MT can publish anything, it simply does not impose any format when it comes to output. E.g. you can handle and publish HTML, CSS, JS, PHP pages statically within the same site, the Content management systems submissions are drawn in the database limited to posting time, plus they can contain scripts or server-side includes handled through the web server.
- MT is indeed a cms decoupled on the internet server (serving webpages may be the job of the web server along with a good web server understands how to serve pages effectively without extra layers of caches or Content management systems/database dependancies).
- MT templates are made utilizing a markup language, MTML, simple to learn and other alike to HTML (means they are much simpler for designers the ones uncomfortable with finding out how to code in PHP).
- The lack of code and direct hooks towards the database in templates also causes it to be a lot more secure than Wordpress (I've not heard about one malicious MT wordpress plugin in ten years).
- Lastly, MT is extremely foreseeable when it comes to server assets, and may handle a lot of traffic (even on the cheap plan) when posting static assets as well as PHP pages. I haven't yet visit a scenario where Wordpress could be more effective than MT when it comes to operating costs.
Basically may rephrase the question (additionally, it may help answer yours), can there be any reason to make use of Wordpress? (You will find, but I'm not sure your actual needs -)