I guess I lied in my penultimate post.

I’m planning on migrating my primary blog (again), off WordPress to a static site hosted somewhere. I might just throw everything onto GitHub Pages, or might follow any of the zillions of tutorials on how to host static sites off a cheap Amazon S3 bucket — I haven’t decided yet, but no longer having to rely on the free part of freemium services is fairly liberating.

Why? Lots of small reasons.

I like having full control over my HTML/CSS/JavaScript and my post-processing (pun intended) pipeline. Whereas before I could not justify wanting that control beyond gaining the ability to bikeshed, now I think that web design is enough of a thing I do that it’s not a bad idea to make a visually distinctive blog that coheres with my overall Online Identity™. There are also a few specific pain points with WordPress, e.g. it doesn’t handle code formatting or HTML escapes all that well. To some extent this is preventing me from blogging about more technical things, which I want to do, both because it would be interesting and because it would make me feel less awkward about putting my blog on my résumé and showing it to potential employers and the like. (Once again, with style, while looking dapper: if you’re a recruiter reading this, please hire me :)

It’s also nice to always have all my posts with me as simple, flexible Markdown files that support attaching arbitrary front-matter metadata. This lets me perform blog-wide searches or modifications easily with simple scripts and command-line tools. Perhaps more importantly, although I haven’t fully fleshed out my ideas here yet, I might find a solution to one of my most awkward blogging scenarios, where I abandon posts about events that are far in the past because the post date will seem wrong. If I can develop a system and schema that explicitly supports posting about events weeks or months or even years after they occur, maybe I will feel more comfortable pulling more drafts out of limbo. This is very much a technical solution to a psychological problem, but who knows.

Finally, I guess it’s really time to move past my old posts. “Emotional baggage from another era” is right. Deleting stuff pains me — the internet archivist in me doesn’t want to delete anything for fear of disrupting old links, pingbacks, and conversations; the surveillance nut in me figures it’s futile because copies of the post will probably persist in some cache or mirror forever anyway; and personally, a huge motivation for why I blog is that I’ve always enjoyed reading my old posts and marveling at my past selves and how far I’ve come, so this just feels like I’m destroying old versions of me, even if I’m definitely keeping all my old posts locally. But the ruthlessly pragmatic side of me is louder than any of these voices. The Internet really does not need to know about every painstaking detail of my fourth-grade life. This migration is the perfect opportunity to archive all my old posts for personal perusal, and then decide which ones to cull or put more carefully in context before public display. Maybe I’ll even consolidate posts from my other blogs into this new one. The sky is the limit.

There are lots of things I’ll miss, of course — comments, pingbacks, analytics, automatic seasonal easter eggs and reminders from the Internet Defense League. But I’m sure I’ll be able to get some of those things back by investing some amount of time and money, eventually. Static sites are fairly popular because hosting them is cheap and it looks like the tooling around them is very mature, so I won’t be on my own. And maybe some of my readers will miss being able to subscribe through WordPress or via email (to which I would respond, read my last post and get an RSS reader already — it’s good for the health of the Internet — or if you’re really desperate, put “RSS to email” into your favorite search engine.) But overall I think it’s worth it.

Of course, this migration is far more complicated than exporting a nice XML file from one system and importing it into another, so it will take time, which is not something I have in abundance right now. However, it also appears that migrating this blog is very much the sort of task I procrastinate other things in order to do, so that’s a reason for cautious optimism.

(note: the commenting setup here is experimental and I may not check my comments often; if you want to tell me something instead of the world, email me!)