-
Notifications
You must be signed in to change notification settings - Fork 42
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
[client styling] Create and place auth widget #264
Comments
Note: Colors/HexValues will be added-in to Zeplin spec & here, following 14 March's VisDe review. |
If possible to implement this WITH lowercase letterforms in the ID badge, and with a TBD font, that would be awesome. I've been wavering between the necessity to do uppercase vs lowercase based on prior studies I did 13 years ago when at Yahoo!, but there are many more digital fonts available today... and based on how nicely the GitHub's chicklet labels look in this test Issue, I'm going to try to find a font that might work to keep these lowercase. Can't do until Thursday afternoon, tho. |
^ BUMP @creviera... added into spec the "Sign In" pane w/ error message. Per the acceptance criteria, "placement" is this Issue's goal—all styling optional, and a separate Issue will be created to nail that, after everything's been placed & made functional. 😃 |
This issue can be closed by this PR: #278 I captured things left to do in these tickets:
If I missed anything please add more tickets or update any of those. |
Epic: UX Parity between prototypes & coded client (#261)
This Story: Create and place auth widget
Within the "Functional Regions" mapping, is a widget to sign-in/sign-out, which is different from today's static button. This Issue is to simply get a widget in place; styling may be as rich or as basic as is deemed necessary to get the Epic satisfactorily complete.
Reference materials: Static spec uploaded to Zeplin (and shown in below PNGs)
Design Spec: See flat multi-state spec above! :)
"Active" Button Animation: LDS Ripple
The text was updated successfully, but these errors were encountered: