Restructures the project

We're going to follow a more Django-ish way of life now, rather than the
old backend/frontend split.  This is really done to satisfy my own
curiousity, more than anything.  I'd like to spark up a full frontend
webapp (using yo webapp or some such), and see how that meshes with
Django.
Makes the Django project top-level
Removes all styling from the project

We're retooling for PZ.  All the old stuff goes!

We'll need to separate this better too -- all styling belongs to the
project, rather than the app.
We no longer care about local_settings.py

This was an old way of separating development from production settings.
I prefer the Heroku 12-factor way now (whereby config is derived from
the environment) -- I'll complete the upgrade to that shortly.
Switches to Heroku/12-factor style development

Most settings are now derived -- either from the environment (and
therefore .env thanks to honcho etc.), or by using __file__ to figure
out whereabouts the project is located.  This should mean that both
developers should be able to clone the project, setup the environment,
and run it with no configuration (yay!).