A Static Site
Why would anyone use a completly static website in this day and age?
I got tired of dealing with all the configuration on more complicated sites. I figured that my website was mine, not Wordpress's. I didn't want to spend the money or the time it takes to configure Wordpress or similar.
So, in 2013, I moved to a statically generated website which used Octopress. This was OK, but still had some problems. First of all, it wasn't pure Jeykll, so it took some doing to host on Github. And required re-generating the site constantly.
Most importantly, after I didn't touch the site for two years (during my mission), I realized I was having a hard time getting my Octopress site to work. Even though Markdown was elegant, I was actually more familiar with HTML and CSS.
Simply touching a file, changing it, saving it, and making a git commit was a pretty nice way to do things. Right now for any new post I need to update two pages, which is pretty managable. I may move that logic to Jeykll in the future.
HTML also has the benefit of allowing me complete control. I don't have to jury-rig a plugin to do anything, I can just touch the actual code. Now, this is an ugly way to do things, but it is a simple way to do things. And I don't need an overcomplicated system for a blog I plan on updating only a few times a year.
I may move some of the logic to a JS presentation layer later. Then I could just update one area - a JSON object of all the blog posts.