Sprint backlog: October 16th to October 21st

[ghost]

Note: All implementation details, such as model fields and views are completely up for debate. If you think it makes sense to create a new page for a specific task or something along those lines, then feel free to create an issue.

User stories to implement:

As Max or Professor Sara, I want to be able to login so I can utilize the forum. [1] [B]
As Max or Professor Sara, I want to be able to register so that I can create an account.[1] [C]
As Max or Professor Sara, I want to post a message to a specific topic so that I can participate in discussions. [1] [C]
As Max or Professor Sara, I want to create topics so that I can start new discussions. [1] [C]
As Max or Professor Sara, I want to subscribe to topics so that I can highlight topics of interest. [1] [C]

Relevant tasks

General

• create barebones Django framework so that work can begin.

Easiest implementation flow will probably be the following:

• Topics
• Messages
• Users
• Subscriptions

Models

• Topics (User stories 3, 4)
  • name
  • time/date created
  • creator (many-to-one relationship, a user can create many topics) (after user implementation)
• Messages (User stories 3, 4)
  • content
  • time/date created
  • topic (many-to-one relationship, a topic can have many messages)
  • creator (many-to-one relationship, a user can create many topics) (after user implementation)

NOTE: For authentication purposes, its probably going to be far easier to take advantage of Django's authentication application. See: https://docs.djangoproject.com/en/dev/topics/auth/default/

On the other hand, it may be difficult to integrate user authentication with our own model of users, so it may be preferred to spoof the login with unprotected username/password fields for now.

• Users (user stories all)
  • subscriptions (low priority)

Views and Templates (AKA: controllers and views respectively, ENJOY THE CONFUSION)

• View all topics and their messages (as a starting point)
  • controller
  • template
• Create a topic
  • controller
  • template
• Register
  • controller
  • template
• Login
  • controller
  • template

URLs

• Create appropriate URL paths for each view.