VT Merge

[pernilje]

Description

This pull request contains image uploads to buckets, tool tips and a create course page that follows the new design.

• PBI: [Web Create] As a content creator, I want to be able to put general information on the new courses I'm creating.

• PBI: [Web Edit] As a content creator, I want to be able to edit the general info of the courses I haven't published yet

  • Now the user can upload a cover image when creating and also when editing a course.

• PBI As a course creator I want a unified course creation and editing experience.

  • The course creation is no longer a pop up, but is instead a page. The page follows the new design.
  • The course editing page, has been made but is not current being routed to, as the section creation page has not been implementet for the new course creation/editing page

• PBI: As a content creator I want a guide on the course page in form of small pop-ups.

  • Tool tips and an "i" icon have been added on the course page.

• As a content creator I want a guide on the section pages in form of small pop-ups

  • Tool tips and an "i" icon have been added on the section page.

• PBI As a content creator, I want an explanation/guide for creating a section or course (represented by the yellow thing in Figma) to make the process more intuitive.

  • The explanation is created on section edit.

• Issue: Exercises and lectures are not currently in order in a section.

  • Now all lectures and exersices are in one list called components.

• Besides the PBI's and the issue, there is also added the following things:

  • A iphone image which has to be used later on.
  • A new component "DraftCircle" which shows the circle displaying whether its published or a draft.
  • Be able to choose between uploading a video or an image - this is also something we have to use later on.

Checklist

• [x] Code has been tested locally and passes all relevant tests.
• [x] Documentation has been updated to reflect the changes, if applicable.
• [x] Code follows the established coding style and guidelines of the project.
• [x] All new and existing tests related to the changes have passed.
• [x] Any necessary dependencies or new packages have been properly documented.
• [x] Pull request title and description are clear and descriptive.
• [ ] Reviewers have been assigned to the pull request.
• [x] Any potential security implications have been considered and addressed.
• [x] Performance impact of the changes has been evaluated, if relevant.

If mobile/frontend pull request, what version of the backend is it stable, and running on?

Branch: VT-dev-bucket

[pernilje]

Got an error, trying to fix it! Just before any reviews it