UX Review: Current Behavior

Long Read

I have enabled OAuth2 for GitHub

I’ve also changed my theme so that Login with GitHub is prominent.

When a user clicks to Login with GitHub (or any OAuth2 provider) for the first time, they are dropped at a screen that asks them to login or create an account.

I’ve watched people then attempt to sign in using their GitHub username and password because it isn’t clear to them that they’re continuing an account creation process.

I think that this could be simplified if the Login / Create Account page were laid out side-by-side, or if the order were reversed.

Better yet, have them enter their email or login, then click “next” and then, based on whether or not that account exists, present them with the appropriate “login” or “create account” screen.

I’m going to try and get some help from a friend of mine who does frontend to modify the theme and provide a suggestion and potentially a pull request.

Templates for Reference

• https://github.com/go-gitea/gitea/blob/master/templates/user/auth/link_account.tmpl
• https://github.com/go-gitea/gitea/blob/master/templates/user/auth/signin_inner.tmpl
• https://github.com/go-gitea/gitea/blob/master/templates/user/auth/signup_inner.tmpl

Potential Conflicts

The "inner" templates are also used on these pages:

• https://github.com/go-gitea/gitea/blob/master/templates/user/auth/signin.tmpl
  • See https://try.gitea.io/user/login
• https://github.com/go-gitea/gitea/blob/master/templates/user/auth/signup.tmpl
  • See https://try.gitea.io/user/sign_up