Going Static

You may have noticed a change in the graphics design and slight functionality changes. That’s because today I moved on from Wordpress to a fully static website. The website now is generated from the collection of layouts and articles every time I change something and then deployed to the server as a bunch of HTML, CSS and JavaScript files along with some assets.

There are several reasons I eventually went “static”:

  • There’s no easy way to hack the system. You won’t believe how frequently I had to update Wordpress and remove trojans planted in this blog. It’s a low traffic personal blog, and still there are people trying to hack in. What’s up with you guys?
  • It doesn’t need PHP. To run this blog I’m using a super small Linode box. Since everything is static, serving the content doesn’t take much effort for the system. As the result – better user performance, low resource usage – a win-win.
  • Everything is version-controlled. There’s no database with posts or anything else. Everything that I’ve got is a plain text editable in any text editor (which is actually great). I’m using Git to store, version and back up posts.
  • System updates (I’m using Octopress) are more than simple. All custom stuff sits in their own folder and so all I need to do is to overwrite files with new versions.

That’s about all reasons I had in mind when moving, and I think it’s totally worth it.