SIGNUP #6: Implement Password Flow & Alter Password Design

[AbigailDawson]

This is a continuation of Signup #5.

The task is to refactor the sign up form to incorporate the password flow we are aiming for. You are also tasked to make sure your password requirement section matches the wireframes below. Please consult JP Escobari if you have any questions about the current signup form and password requirement component, as he originally created it.

For the password flow:

1. Upon entering page, password requirements should not be visible!
2. When the user clicks on the password field, the password requirements should pop up and be visible! (note, if the password field is clicked on, but the field is still empty, the color of the text for the password requirements should remain BLACK)
3. When the user starts typing into the password field, the password requirements should turn red or green depending on whether or not that specific requirement is fulfilled.
4. When a user clicks on the “confirm password field”, there should be a check whether the values in “confirm password” and “password” are equal. If not, a message (“passwords don’t match”) underneath the confirm password field should be displayed. Refer to the confirm password example attached.

Note: signup functionality currently works. Make sure that when you refactor, the functionality of the signup form is retained.

[huly-for-github]

Connected to Huly®: GITHB-195