Currently the only e2e test we are running is trying to fetch the main page. We have a couple more pages now and thus features to test.

https://www.cypress.io/

A possible solution is using a React portal.

Make sure the clown is contained in an element that occupies the entirety of the screen and hides overflow, so it doesn't spawn sliders when moving bottom or right.

Make sure to enlist all needs from the community and produce a layout that makes sense, is effective and good looking.

In the case that mail confirmation is nowhere to be found, users need a link in the login page to another page that will let them ask for a resend of the confirmation mail.

This page should include a form with:

• email: an email field for users to type their email.
• button: to send the request.

The page should then state that if the email exists, it will re-send confirmation to their inbox. No further information attached to avoid people trying to guess registered emails.

Currently it looks as good as I could make it look with the limited time I have.

First, make sure the issues are on the presentation layer and not the text formatting that comes from the backend.

Second, produce better looking components for the articles and sections.

it would be interesting to change some of the colours to make the page easier to read.

when someone has initiated the process of resetting their password, they will receive an email that links to /reset-password/<token>.

Here the user should see a form to reset their password. That form includes:

• password: a password field where they will type their new password.
• password2: a password field where they will confirm their password. This should validate that is identical to the firt field.
• token: hidden field that includes the token from the url. This will later be used in the backend request as part of the body.
• button: button to send this request to the backend.

Central command will then answer with the result of this operation, which should give some feedback to the user, particularly in the case of field errors.

Details

A new element should be added to our navbar, with a link to a Login or Sign up page that I will do in teh future.

This element should show conditionally, and when the user is logged in it should show a dropdown instead that says the user account name. The options in this dropdown are:

• My Account
• Log off

The elements shouldn't link to anywhere just yet.

and the following log in the backend:
Not Found: /accounts/resend-account-confirmation/asd

Currently changelog looks good enough, but with the right skills it could be a lot better.

First it would be good to get rid of that incredibly limiting container that makes it look like a mobile app on desktop.

Second, creating better components to properly display the builds and changes data.

URL: https://unitystation.org/changelog

Should be pretty straightfoward since the new version has no breaking changes in the API.