Onboarding - Content Creator Application: Creation, Viewing, Rejection, Approval

[Adachigaming]

Description

This PR is mostly about the creation, viewing, rejection, and approval of freelance Content Creators, with some additional design changes.

Changes

New Features

• Updated Signup flow, allowing for creation of application after making a user
• Login now checks whether or not Content Creators are approved or rejected
• Error messages on the Login page will also inform the user if they are rejected or not approved
• Modernized Admin page to match current database
• Modernized SingleApplicantView to match current database
• Can now either reject or approve a Content Creator application, with the ladder making the account eligible for logging in

New Design

• Updated colors and text to match new Figma design
• Updated error messages in Signup and Login: they are now displayed under the field from which the error originates
• Updated Navbar to now also include user information
• Slightly updated design of the Admin and SingleApplicantView pages to be more inline with the modern design. Approved by Luiza

Related Issues

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.
• [x] 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.

Screenshots (if applicable)

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

Runs on the "Onboarding-devMerge" backend, commit id: 146ad37

Notes for Reviewers

The backend has an active PR that this version can run on.

[Jatewo]

Notes for Reviewers

The backend has an active PR that this version can run on. Additionally, we take no blame in the cypress tests failing, as the certificates do not even load on dev

It absolutely works. You have to run it with backend cert-get-user/cert-get-user-merge and with the cert-certificates-info in the certificate service. It is in the process of being merged into dev and staging. Furthermore, please note that failed tests are always your responsibility - not something you can just ignore / pass the blame on.

Edit: Backend can now use dev

[Adachigaming]

It absolutely works. You have to run it with backend cert-get-user/cert-get-user-merge and with the cert-certificates-info in the certificate service. It is in the process of being merged into dev and staging. Furthermore, please note that failed tests are always your responsibility - not something you can just ignore / pass the blame on.

Yes, I was not aware of the fact that the certificates were on a different repository entirely. Still, that does not excuse the dismissive way the note was written, and for that I apologize.

[Jatewo]

You can make a new PR from this branch and make sure you have addressed all requested changes, then rerequest reviews. I do not want to see another merge without approvals.