Create client-rendered views for dynamic content

[Jimmy-Lin]

Issue Description

Users Affected:

All users

Functionality Requested:

This will be the first client-rendered components of our app. Your task will be building UI components using Vue.js and Bootstrap 4.

This is a great task if you're interested in front-end development, building UI components, want to learn about reactive rendering, or asynchronous/event-driven programming.

You're allowed to use anythings from the Boostrap library to get a head start on how the UI will look. After that, move the HTML, CSS, and JS into a self-contained Vue component. Vue will give you a clean way of specifying functions to trigger when parts of your UI are clicked, it will also re-render the UI based on how you update the data object in browser memory.

What this means is you'll mostly be focusing on piecing together Bootstrap UI, and connecting the Vue triggers to API calls and the responses to data for the templates. There is another issue for abstracting
the API calls into Model classes with asynchronous methods, so most of your work will be designing the triggers and templates.

Progress

Status: Complete

Pull Request: #83

Additional comments:

The core UI for courses is complete, however we should continue adding image uploads and attachments to this feature. So the styling is not final, however all the standard logic specific to courses is complete.

Implementation

Commit Hash: Not Yet Complete

Author: @Jimmy_Lin

Reviewer: @Jimmy_Lin

Prior Behaviour:

Currently we have work done on fetching data from the server into browser memory as well as pushing updates to the server, but need rendered views to attach to those things.

New/Modified Behaviour:

Users should be able to access the methods supported by our API by using these rendered views which connect to the client-side model (which connect to our server implementing the API)

Validation

Test Files:

Untested

Manual Validation Procedure:

Users can perform CRUD operations on courses (pending their authorization)

Follow-Up

Usage Documentation:

No Documentation

Requirements:

List Special Instructions Needed When Pulling/Deploying