Initial skeleton of of course creation process broken out into components: models_api.py is the data access layer that abstracts us from calling on the Django models directly, controller.py is where the business logic happens, views.py is now just an API endpoint.  We may add another layer with helper methods that might massage some of the data, but we're hoping to rely mostly on a Proxy model.  Unit testing and filling in the structure will follow.
Merge pull request #11 from Harvard-University-iCommons/feature/component_architecture_skeleton

Initial skeleton of of course creation process broken out into component...