I also do this, with a custom python script. Yeah, there are disadvantages, but right now I love its simplicity. I don't have to worry about keeping Wordpress u

I also do this, with a custom python script. Yeah, there are disadvantages, but right now I love its simplicity. I don't have to worry about keeping Wordpress updated; I just make a new static file and run the update script. If my needs ever change (needing more than static files provide), I'll probably put in a simple Python web server, but still use the static files to edit my content. Eh, we'll see. What I have now works, and I like it -- and that's all that's important. EDIT: In other words, the best part about a static site isn't that you don't need a web server to grab the content. It's that you have all of your blog posts, right there, in plaintext format. They're tangible and easily migratable into any future format. When the time comes to have dynamic comments, timed posts, and other features like that, you can write a tiny Python/Ruby web server that generates HTML for you to handle some of the simpler tasks. BUT: If you have Wordpress-like requirements, use Wordpress. If you don't, a static blog can be a real joy to work with. If you want a couple small niceties that a static blog can't have (delayed posts, etc), shove a quick homemade webserver in front. And in either of those cases, if you are doing more work than you wanted, switch to an easier option. Making a static blog can sometimes be an easy, low-mental-energy hobby project to work on, even if you reinvent the wheel just a little.