Major system overhaul

.gitignore

@@ -75,12 +75,4 @@ target/
 # Vim Swap File
 *.swp
 
-# node
-node_modules/
-
-# bower
-bower_components/
-
-.sass-cache
-
 static/css

README.md

@@ -1,25 +1,29 @@
 # A homegrown course management system
 
-This repository is the home of the [course management system](https://www.ifsr.de/kurse) source code, used by us to manage programming courses we provide to the students of our faculty.
+This repository houses the source code that runs the [course management system](https://kurse.ifsr.de) operated by the [student representatives](https://www.ifsr.de) of the computer science department. It can be used to manage programming courses or pretty much every other event that has a limited number of attendees and should therefore offer a registration.
+
+## Technical tidbits
+
+The course system is written in [Django](https://djangoproject.com/) and uses the [Litera](https://bootswatch.com/litera/) Bootstrap theme.
 
 ## Setting up a development environment
 
-1. In order to use this project, you need `python3` and [`sassc`](https://github.com/sass/sassc) on your system. Install them via your distributions' package manager.
+1. In order to use this project, you need `python3` and on your system. Install them via your distributions' package manager. If you want, you can use `virtualenv` to not pollute your working environment too much.
 2. Copy the example configuration and mail settings and customize them as you see fit:
 ```
 cp course/settings.py.example course/settings.py
 cp user/mailsettings.py.example user/mailsettings.py
 ```
-3. Compile the sass files and install any Python dependencies via `make`.
-3. Run `make migrate` to apply the database migrations and load a sample data set.
-4. Launch the program with `env/bin/python manage.py runserver`.
+3. Install any Python dependencies via `pip3 install -r requirements.txt`.
+3. Run `python3 manage.py migrate` to apply the database migrations and `python3 manage.py loaddata courses` to load a sample data set.
+4. Fire up the development server with `python3 manage.py runserver`.
 5. You now can login with the super user **foo** and password **bar**
 
 Another test user is available by logging in as `test: test`.
 
 ## Changing the database model
 
-When chaning the database model make sure that the fixture located in `course/fixtures/courses.yaml` still works.
+When changing the database model make sure that the fixture located in `course/fixtures/courses.yaml` still works.
 If not, export a new version of the fixture using the command
 ```
 python manage.py dumpdata --format yaml --exclude contenttypes --output course/fixtures/courses.yaml

course/admin.py

@@ -1,12 +1,15 @@
 from django.contrib import admin
 
-from .models import course, schedule, subject
+from .models import course, schedule, subject, news
 from user.models import UserInformation, Activation
 
 admin.site.register(course.Course)
+admin.site.register(course.Notification)
+admin.site.register(course.Participation)
 admin.site.register(schedule.Schedule)
 admin.site.register(schedule.WeeklySlot)
 admin.site.register(schedule.DateSlot)
 admin.site.register(UserInformation)
-admin.site.register(subject.Subject)
 admin.site.register(Activation)
+admin.site.register(subject.Subject)
+admin.site.register(news.News)