On the Irony of Using Static Site Generators
As I've mentioned before, I've recently switched to pelican as my blogging engine.
Pelican is a static site generator. This means that it generates static HTML files using templates and content as input, which can be then uploaded (via rsync, for example) to a plain vanilla web server (I use nginx).
So far the experience has been fairly smooth. The web server setup is much simpler, since there's no application to run. And it's forced me to re-think what kinds of information I want on my pages. For example, in an effort to avoid regenerating the entire site every time I publish an article, I created standalone index pages for tags, categories and archives rather than display the counts on every page.