-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update new "Get Codename" page in line with design recommendations #6311
Comments
eloquence
added a commit
that referenced
this issue
Mar 9, 2022
The previous language is ambiguous and overly verbose. Simpler language was workshopped, see #6311. This does not yet implement all the agreed upon design changes but gets us one step closer.
1 task
eloquence
added a commit
that referenced
this issue
Mar 9, 2022
The previous language is ambiguous and overly verbose. Simpler language was workshopped, see #6311. This does not yet implement all the agreed upon design changes but gets us one step closer.
eloquence
added a commit
that referenced
this issue
Mar 10, 2022
The previous language is ambiguous and overly verbose. Simpler language was workshopped, see #6311. This does not yet implement all the agreed upon design changes but gets us one step closer.
eloquence
changed the title
Implement revised "Get Codename" page
Update new "Get Codename" page in line with design recommendations
Mar 16, 2022
(Retitled issue since the language updates have landed now.) |
Fixed in #6315 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of the Source Interface design improvements (see #6210), we have broad consensus around language changes to the "codename" pages which could be made regardless of whether or not we ultimately fully reverse the password generation flow. This is "E1" in Figma:
The wording changes, which were collaboratively workshopped at a couple of UX meetings, in summary:
This does not change the word "codename" to "passphrase" yet, because a) that change needs to be carefully rolled out, given that the term has been used from the very beginning, b) we'll want to user-test the term "passphrase" before fully committing to that change, so we don't have to potentially change it twice.
The styling changes to the codename widget are the same as already implemented in @eaon's branch for #6211. The show/hide widget is also the same as implemented there (but the default state on this page would be "show", not "hide").
The text was updated successfully, but these errors were encountered: