After twelve years of using Movable Type, I have just moved the blogs on sunpig.com to WordPress. For some time now, Movable Type has been failing two of my three tests for choosing a piece of platform software:<\/p>\n
I still like its architectural model of static publishing, and (partly because of that) it has a great security record, which is important if you’re running your own server. I’ve been using MT since version 1, and I’ve clung to it for sentimental and pseudo-practical reasons (“I know the templating language really well!”) for a long time, but the online world is a much different place now, and the fact is that compared to all other avenues for writing online, MT 5’s interface is poor, and I dislike using it. As a result, I don’t. I blogged less in 2013 than in any previous year.<\/p>\n
OpenMelody<\/a> was a fork of the open source version of MT 4, but it seems to be dead now.<\/p>\n I was considering using Jekyll<\/a>, which is a modern static site generator: write posts in your text editor, run a site generator from the command line, and `rsync` the generated html files to your server. This has lots of good points: it generates static files, and it plugs directly into my standard text editor workflow \u2014 with version control! This is great if you’re a programmer and always have access to a machine with a command line. Not so great if `bundle exec jekyll build` makes you twitchy, or if you like the idea of occasionally posting something from your phone. Also, no matter how you slice it, comments end up as a crazy hack. I can see myself using jekyll for other projects, just not for our main blogs.<\/p>\n Ghost<\/a> is new and shiny and looks like it pushes the standard blogging interface forward, but: node + sqlite. Really? They sat down and actually came up with that decision? Also, I mistrust an open source project that has a “sign up” link on its home page, but not a “download”.<\/p>\n Drupal<\/a> would probably do the job, but my impression is (perhaps incorrectly) that it is more geared towards sites<\/em> rather than blogs<\/em>.<\/p>\n So… WordPress. Big community, well documented, under active development. Used to have a bad rep for security, but is a lot better than it used to be, and since version 3.7 even features an automatic update process to apply maintenance and security patches. It also has well-established guidelines and practices for hardening an installation. It’s “the standard” these days. I have a general preference for “off-piste” solutions, but sometimes I just want to go with something that “just works”. Mostly.<\/p>\n It took me a few days to prepare the migration. I pulled the trigger yesterday evening, and by the (late) end of the evening, the new Death Star was mostly operational. Today has been mopping up and housekeeping. And so far, I’m feeling pretty good about it.<\/p>\n The new shiny:<\/p>\n I put together a GitHub repository with my notes, preparation, and migration scripts in case anyone else might benefit from the experience: https:\/\/github.com\/sunpig\/sunpig-mt-to-wp<\/a>. If you notice any problems, let me know.<\/p>\n","protected":false},"excerpt":{"rendered":" After twelve years of using Movable Type, I have just moved the blogs on sunpig.com to WordPress. For some time now, Movable Type has been failing two of my three tests for choosing a piece of platform software: Is it well documented? (Yes.) Is it under active development? (No, at least not in its open … <\/p>\n\n