Skip to content
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

Sign In / Register Feedback #1608

Closed
jeffhandley opened this issue Sep 27, 2013 · 1 comment
Closed

Sign In / Register Feedback #1608

jeffhandley opened this issue Sep 27, 2013 · 1 comment
Assignees

Comments

@jeffhandley
Copy link
Member

  1. Change "Sign in" to "Register / Sign in" and add a tooltip that says "Register for an account or sign in with an existing account"
  2. Change "Email" label on Register to "Email (gravatar, notifications, and password recovery)" with "gravatar" being a link to gravatar.com
  3. On the "Thanks" page, above the "Now that you..." text, show the user's gravatar and username - and add a link to "View Profile" to drive people to that page and their API Key
  4. On the "Thanks" page, move the Confirm your account to be the 1st bullet
  5. On the "Thanks" page, remove the "set up your profile" link
  6. On the "Thanks" page, make "Upload Package" a link in the text
  7. On the "Thanks" page, change "Confirm your account" to "Confirm your email address so that you can publish packages or contact package owners" - this is more clear, and it also covers the "wrong email for gravatar" scenario
  8. Change Email Address page needs to show what the current email address is.
  9. [Next Sprint] Perhaps merge the Change Email Address page into the Edit Profile page, with the form hidden until you click the "change" link. Then the "Cancel" link would just hide the form again. The hard part will be managing state when the password is entered incorrectly.
  10. The link to gravatar.com on the Edit Profile page is coded directly to http://en.gravatar.com - it should just be www.gravatar.com
  11. Confirmation Required needs to say "upload a package or contact a package owner"
@ghost ghost assigned TimLovellSmith Oct 1, 2013
@TimLovellSmith
Copy link
Member

Re 11. currently thinking not fix as the message is actually context sensitive to the action you just took.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants