I’ve been thinking I ought to give MovableType a fair trial before switching to “a different tool”:http://peter.mapledesign.co.uk/weblog/archives/other_weblog_tools.html, as many others seem to use it successfully. Here’s a few articles I turned up:
* “Beyond the Blog and other links on making MovableType a Content Managment System”:http://www.healyourchurchwebsite.com/archives/000913.shtml
* “Beyond the blog”:http://a.wholelottanothing.org/features.blah/entry/007162 - a whole lot of information
* “Doing your whole site with MT”:http://www.bradchoate.com/past/001656.php#comments
1 comment so far ↓
My main gripes with MT were the way it generated content - having a CGI essentially rewrite your HTML to the server’s disk felt like a horrible kludge - and the fact that it had no easy way to cross-reference entries. A Wiki (despite the usual criticisms that it is unstructured, difficult to navigate, etc.) provided all the inter-linking I wanted, and with some constraints (like constrained navigation, removal of the multi-user bits and adding better page locks) provided all the MT features I needed and more.
Mind you, I don’t go in for comments or trackback (I rely on referrals, which are much more standard across weblogging tools), but those are easy to add (or customize). Categories are simply bunches of interrelated entries (and you can use the URL path to do implict categorization), indexing is automatic (or you can roll your own, like http://mac.against.org/space/Index - inspired on http://snipsnap.org/space/snipsnap-index)
If PhpWiki proves too big and bulky for your taste, allow me to suggest ErfurtWiki (http://erfurtwiki.sf.net), which can be easily tacked on to any PHP site.
Leave a Comment