Directory

Improve the Register/Login experience on WordPress.org · Issue #565 · WordPress/wporg-mu-plugins · GitHub
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

Improve the Register/Login experience on WordPress.org #565

Closed
ndiego opened this issue Feb 1, 2024 · 5 comments
Closed

Improve the Register/Login experience on WordPress.org #565

ndiego opened this issue Feb 1, 2024 · 5 comments

Comments

@ndiego
Copy link
Member

ndiego commented Feb 1, 2024

There are sections of WordPress.org where the user may need to Register/Login to perform certain actions. Examples include Forums, News, Plugins, Learn WordPress, etc.

On these sites, the Register/Login appears in the top-right of the screen like this:

image

The layout is not ideal and creates unnecessary extra space at the top of the page. How could we fix this?

Perhaps these links are integrated into the header? This would introduce other mobile issues that would need to be figured out 🤔

image

Removing this Register/Login bar when the user is logged out would also resolve #426

@dd32
Copy link
Member

dd32 commented Feb 1, 2024

Having the Toolbar present, purely for login/register links is really a vestige of the previous design.

One question I have for the proposed design here though; is whether the logged in state for regular users should continue to have the toolbar, or whether that should be combined with the header here too.

For example, a user who has no elevated access on the site will have this experience (Note, I've added a border to the toolbar for obviousness)

Screenshot 2024-02-02 at 9 10 02 am

And in some classic themes, it seems they also get a link back to the current sites homepage, which for /support/ will actually land them on /documentation/...

Screenshot 2024-02-02 at 9 11 30 am

I guess my question here; after changing the login links, are we then also going to want to combine the User menu into the header too?

For example; really badly styled.. (edit: or probably to the left of the search icon, like your example of the Login/Register link)

Screenshot 2024-02-02 at 9 16 25 am

Edit: https://learn.wordpress.org/ also uses the Toolbar for a Locale Switcher

@jasmussen
Copy link
Collaborator

When you're logged in, it seems fine to have the full adminbar. Agree when logged out it should not be there.

Integrating login/register into the main bar is an option, but it both comes with the tradeoff of consuming a great deal of space, and it becomes present on every single section. The last part, past feedback by, I believe, @Otto42 (see also here) suggests giving this level of prominence to the login/register buttons is a bad idea, because it causes people to sign up in droves thinking they have to in order to get WordPress.

To that end, a previous suggestion is to integrate the login better in every single section that needs one, with this given as a previous example. That is, you only ever see your login/signup links in context of where you need it.

Taking a fresh look today, here are my best instincts, and I welcome sanity checks and corrections for others that might have better insights in what is useful. Note, in the following review, I'm ignoring the adminbar login/signup links, and only looking at other links on the page.

Don't show:

  • Homepage
  • News (this assumes this doesn't have broad community access/contributors)
  • Hosting
  • Blocks
  • About
  • Enterprise
  • Search
  • Get WordPress

Has it, can be improved:

  • Showcase: (header)
  • Documentation: (in context of each page)
  • Developers: this is unique in its GitHub integration, let's talk about this one

Has it, needs improvement:

  • Themes: has it (Add your theme)
  • Plugins: has it (Add your plugin)
  • Patterns: has it (Submit your pattern)
  • Learn: has it (Apply/submit)
  • Photos: has it (Contribute)
  • Five for the Future

Does not have it:

  • Forums
  • Make: maybe don't show on the index page?
  • Make P2
  • Events: doesn't have it, unclear it needs to

Depending on the feedback of the above, and considering the sections that do benefit from login/register links, my best suggestion would be to always keep a "Sign in" link as the last item in the secondary navigation bar, like so:

Screenshot 2024-02-05 at 09 27 27

This would be a pattern we can repeat across all the sections that should have the link. Just as an example in case we choose to update the Showcase for consistency and uniformity:
Screenshot 2024-02-05 at 09 28 06

By being a single link, it is space efficient, and that single page can contain a "Sign up" link as well. There are previous login page mockups in the GH here, here with only small updates to the verbiage:

Log in flow

This single "Sign in" link we could show across themes, plugins, patterns, learn, photos, fftf, forums, make, make p2s, and events if need be, thus omitting the major sections where such a link would be confusing.

Copy link

I'm also interested in unifying the quantity of places teaching folks how to create profiles and connect to GitHub. I see many duplicates, but centralizing and focusing updates in a single place (Learn) seems most practical so that content isn't quickly outdated.

@ndiego
Copy link
Member Author

ndiego commented May 1, 2024

Thanks for the discussion, folks. I am going to close this out in favor of WordPress/wporg-main-2022#420, which is more recent and provides additional information. Let's keep the discussion going over there!

@ndiego
Copy link
Member Author

ndiego commented May 13, 2024

I am going to close this out in favor of WordPress/wporg-main-2022#420

Oops, forgot to actually close this 😅

@ndiego ndiego closed this as completed May 13, 2024
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

4 participants