Sign in: Release new sign in page #2405
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ough both still supported
Contributor
Author
|
selfie |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current plan is to release this for the week of 2/18.
Who is this PR for?
educators
What does this PR do?
Uses new designs from @ciscomeneses that are more beautiful, make space for feeling more like each individual district, and simplify the multifactor flow. It also updates the login to remove full email addresses, and allow just usernames.
This updates specs, and in particular the JS and feature tests around sign in that relied on specifics of the previous multifactor flow or form elements.
Previewed to users in #2403.
Screenshot (if adding a client-side feature)
design
invalid login
browser validations
multifactor
Checklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?