For when you don't need no stinkin' CMS

Makes things ever-so-slightly easier when you just want to serve a bunch of pages
that are just rendered templates (with no special views or context)

Routing autogeneration
----------------------

define STATICPAGES_TEMPLATES in your settings.py as a series of
(section_name, base_url, base_template_path) three-tuples:

STATICPAGES_TEMPLATES = [
    ('homesite', '', 'homesite'),
    ('subsite', 'url/of/subsite', 'staticpages/subsite'),
]

make a directory-and-page hierarchy within the given template directory,
and the files will be automatically served with properly-named urls

URL patterns are named by the site section name, and have a parameter for
the path: reverse('sectionname', args=('path/to/file/'))

For example:

$PROJECT_ROOT/templates/homesite/
  - index.html
  - pricing.html
  - about/
    - index.html
    - team.html
    - news.html

reverse('homesite', args=('about/team/') -> '/about/team/'


TODO
====

Menu activation
---------------


http://110j.wordpress.com/2009/01/25/django-template-tag-for-active-class/



Sitemaps
--------

http://minimoesfuerzo.org/2011/02/12/sitemaps-django-static-pages/