django-medusa

* django-medusa https://github.com/mtigas/django-medusa * django-bakery https://github.com/datadesk/django-bakery * django-freeze https://github.com/fabiocaccamo/django-freeze * django-staticgen https://github.com/mishbahr/django-staticgen

Wagtail (our open-source Django CMS [1]) can generate a static HTML export of your site to the filesystem, Amazon S3 or Google App Engine, piggy-backing on the excellent django-medusa library [2]. This feature was commissioned by a security company who didn't want to risk an embarrassing exposure to new vulnerabilities in Drupal, Rails, Django etc. Search is an issue for static HTML sites. Swiftype [3] and Algolia [4] look like solid options - has anyone used these in production? [1] https://github.com/torchbox/wagtail [2] https://github.com/mtigas/django-medusa [3] https://swiftype.com/ [4] https://www.algolia.com

It's probably worthwhile to point out the distinction between general frameworks for static page generation and those that are designed for blogs. Overall the supported features are similar with the only difference being the amount of code that needs to be written and how opinionated the framework is regarding the project structure. This latter point pretty much defines whether a particular framework will work for your project. I have a static site, which is published in two languages, currently with over 5000 pages and about 50 page updates and new pages added per day. None of the static blog frameworks were flexible enough even though my requirements are pretty minimal. I ended up using https://github.com/mtigas/django-medusa/ with a custom app, https://github.com/StuartMacKay/django-sitepaths to manage all the pages and allow pages to

Nice work. I'd tinkered with the same thing and actually came up with https://github.com/mtigas/django-medusa but never got it clean/stable enough to talk about (though it now runs my blog to S3 where it's served now). Some of the same ideas, but very different execution of the concept. (Up to the apps to define a `renderer` to generate a list of URLs to render; management command then abuses the test client to fetch each one, which also allows storing header information like content-type when using a backend like S3.) Baking in the build bits as part of the generic class-based views = very cool. Pun intended.