Course pages, access and routing

This is a basic layout of the routes concerning the courses, following a recent meeting I had with @ej-choi .

Main course page

route: /course
access: public

Displays the full list of courses. I don't think we need to segregate any access on this page, but just list the courses and point a link to the course page.

Individual course page details

route: /course/[course-slug]
access: public

Detailed information about the individual course. Also keep this public.

But here we also create a menu of links that map on to each lesson of the course. We'll need to make the CourseDetails data model for this and add that as a one-to-one relation to Course model.
We should have a top button that leads the user straight to the first lesson.
We should have a purchasing option somewhere on the page (this needs to fetch user data).

Individual lesson page

route: /course/[course-slug]/[lesson-slug]
access: restricted

// Optionally if we're using parts, but let's save this for later
route: /course/[course-slug]/[part]/[lesson-slug]
access: restricted

The lesson page which renders data from Video, LessonContent and LessonTranscript.

Only at this point do we need auth restriction based on whether or not the user has purchased the course.
Here we must consider the possibilites: user is not signed in, user is signed in, user has purchased course. I think we can use the same UI for not signed in and signed in, but route them to log in/create account if they are not logged in when they hit purchase.
We can consider preview of some items, so we'll need a logic for that.
We'll need to carefully handle window reponsiveness here, but let's leave that for another issue.

Anything else to do with building the functionality and routing of these pages, comment below.

systemphil / symposia