Both Drupal and Wordpress have modules/plugins that produce static pages:
* Drupal: https://drupal.org/project/boost
* Wordpress: https://wordpress.org/plugins/wp-super-cache/
They're both quite mature and the standard practice for websites that get a lot of anonymous traffic using their respective CMSes.
An alternative (or supplement) to them would be something like Varnish: https://www.varnish-cache.org
http://leonstafford.com/wordpress-static-html-output-plugin/
http://github.com/skx/e-comments/
As used on http://tweaked.io/
https://github.com/stucchio/Stiletto
No idea if it works with the latest django, I haven't used it since roughly 1.4.
It renders to static files by default (as well as compiling+compressing assets etc) and you can define any number of separate outputs in multiple formats (e.g. HTML, JSON, Javascript, XML, RSS etc) which will also be rendered at the same time.
Plus a whole world of other features, some I consider to be relatively revolutionary. </IMHO>
It works well but lacks, (really, really seriously) lacks, documentation.
The hardest part is that we are going to have a build server that rebuilds the stale parts of the site every hour or so - I don't think that's been done with Middleman before, so we're building that from scratch.
I'll post the details on https://tech.bellycard.com when we're done with it.
So you get the best of both worlds.
The CMS is a crutch. It has its place in certain organizations. But it is overkill for many use cases.
In truth, however, we shouldn't be pitting the SSG against the CMS. I believe the next leap of content creation is a mixture of both SSG and classical CMS. Check out the following links:
https://github.com/thyb/contentify https://www.contentful.com/ https://prismic.io/
There is a convergence about to happen between "dynamic" content and the SSG. It could be called CMS as an API.
That way search and comments (and especially moderation for comments) would be easier to handle, but still it would be easy on the server.
For my own site I created something like this, https://github.com/Harri/Spage , but instead of DB, I used another set of flat files (serialized arrays containing the page content + some meta data) for management purposes.