Split course_manager into multiple apps

[dmuhs]

Problem

At the moment, all the project functionality is contained in the course_manager app. The templates are all contained in a central folder. The same goes for the url mappings, which don't include other urlconf files but lists all paths in a central blob. Also the views are stored in a central place. This makes the project hard to read, maintain and practically unextensible.

Possible Solution

Django's manage.py offers the options to create multiple apps. It is recommended to transfer some of the existing code into encapsulated apps to make them swappable. Those apps should mostly work on their own, so they should all contain their views, templates and a urlconf that maps only to their respective paths. This Stackoverflow answer gives some good recommendations on how to separate your apps. What code goes into which app is up to the developer's choice. However, it should be kept in mind that the apps should be as little dependent on each other as possible. A good recommended project layout and explanations can also be found here.

Severity

Due to the importance of extensibility and the reduction of code density, this issue should be marked as a release blocker. Other issues are highly dependent on this one as work on other parts of the code will be greatly facilitated.