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

[UX] Improve settings for simplified login page #6806

Open
jenlampton opened this issue Jan 3, 2025 · 15 comments · May be fixed by backdrop/backdrop#4986
Open

[UX] Improve settings for simplified login page #6806

jenlampton opened this issue Jan 3, 2025 · 15 comments · May be fixed by backdrop/backdrop#4986

Comments

@jenlampton
Copy link
Member

jenlampton commented Jan 3, 2025

Description of the bug

This is a follow-up to #6799 which was a follow-up to #6570.

  1. we would like to add a checkbox to the Appearance page to enable the simplified login page for the admin theme.

In accordance with our "put the setting everywhere people might expect to find it" policy, we should duplicate the setting for Use the administration theme for simplified login pages by also placing this checkbox on the Appearance page.

  1. Including "simplified login page" in radio buttons with "Use tabs" and "Use tabs" is probably not the best UI to ask and answer this question.

This is the current UI on the "Login settings" page
Screenshot 2025-01-03 at 12 48 57 PM

Login page options does not adequately describe the question we would like to have answered. Under this label, we have three options that do not answer the same question. I would like to propose another UI pattern for these options, as follows:

  • A single checkbox for Simplify login pages as follows

    • Label: Use simplified login pages
    • Description: Simplified login pages hide all layout regions such as headers, footers, and sidebars.
    • when checked, does three things
    1. disables the "tabs" option for the Navigation question
    2. and sets the value for the Navigation question to links
    3. Reveals the Use the administration theme for simplified login pages checkbox
  • A set of radio options as follows:

    • Label: Navigation between login pages
    • Description: Login pages include "Create new account", "Log in", and "Reset password" pages.
    • Options:
      • Links below the form
      • Tabs above the form (not available with simplified login pages)
Screenshot 2025-01-03 at 4 27 20 PM
@jenlampton jenlampton added this to the 1.30.0 milestone Jan 3, 2025
@docwilmot
Copy link
Contributor

I saw this issue coming a mile away!

@jenlampton
Copy link
Member Author

Iterating:
Screenshot 2025-01-03 at 3 50 36 PM

@jenlampton
Copy link
Member Author

jenlampton commented Jan 4, 2025

Thinking about this more -- why is there even an option to choose "Tabs"? Is there a use-case for someone with a new install choosing tabs?

I thought this setting was something we were including only for backwards compatibility, and if that's the case, there doesn't need to be an option for it at all. Let me see what that might look like....

edit: I tried this, but I ended up not liking it very much. Posting a screenshot here in case others feel differently.
Screenshot 2025-01-03 at 4 24 20 PM

@jenlampton
Copy link
Member Author

This is where I am stopping for now on the admin/config/people/login page. I'm going to switch to the Appearence page and wait for feedback so I don't end up going in circles by myself :)
Screenshot 2025-01-03 at 4 27 20 PM

@argiepiano
Copy link

argiepiano commented Jan 4, 2025

The problem with this last screenshot is that, if you choose "simplified" appearance, you really should not be able to select navigation between login pages. The simplified look uses only links. I don't think anyone intended for tabs to be used there.

EDIT: I realize that you have a parenthesis that explains this, but this seems very wordy (and I missed it at first sight). I like what we currently have there, which was the result of a lot of discussion: the three options (tabs, links, simplified) are presented at an equal level, with the theme question only appearing when you select simplified.

@jenlampton
Copy link
Member Author

jenlampton commented Jan 4, 2025

The problem with this last screenshot is that, if you choose "simplified" appearance, you really should not be able to select navigation between login pages.

Yes, exactly -- the form adjusts so that the value is changed to "Links" -- which is what you get with Simplified. I added the note on tabs about that option not being available -- but I am open to other suggestions on how to make that more clear. I don't love this

@jenlampton
Copy link
Member Author

jenlampton commented Jan 4, 2025

the three options (tabs, links, simplified) are presented at an equal level,

This is the problem with the current form though, these should not be at the same level, because the user is not choosing between three options.

They are choosing: 1) Simplified or not?

And if not: 2) Tabs or Links?

How do we show that clearly in the UI?

Edit: maybe I just answered this for myself.... two sets of radio buttons?

@jenlampton
Copy link
Member Author

okay Here's another go... thank you for helping me work through this :)

With standard pages selected:
Screenshot 2025-01-03 at 5 37 01 PM

With simplified pages selected:
Screenshot 2025-01-03 at 5 37 53 PM

@stpaultim
Copy link
Member

@jenlampton I think your UI suggestions are good and do make the form a bit easier to understand.

The only thing I have a slight reservation about is "Page Complexity". It's accurate, but feels a bit awkward to me. Possible options:

  1. Do we need that label at all? Doesn't "Login page display" set the stage enough. Standard login page display or Simplified login page display. I think it would work by just removing "Page complexity," as I'm not sure it adds anything to the page.

  2. If we need or want to keep it, Could it simply be "Appearance" or "Display option"?

  3. Stick with "Page complexity". It's not a dealbreaker.

@avpaderno
Copy link
Member

I would use Style instead of Page Complexity, but I also think it is not necessary to add a title there.

@jenlampton
Copy link
Member Author

jenlampton commented Jan 9, 2025

Do we need that label at all?

We need a label for accessibility. (We cannot have any form element without a label.)

I would use Style instead of Page Complexity

"Style" is also accurate, but that word has so many other meanings unrelated to Layouts, hmm...

I ended up going with Regions and branding (but this could use feedback!)
Screenshot 2025-01-09 at 1 48 25 PM
Screenshot 2025-01-09 at 1 49 54 PM

And here's a PR for testing so you can see how it feels:
backdrop/backdrop#4986

@jenlampton
Copy link
Member Author

jenlampton commented Jan 9, 2025

I've also added the checkbox to the theme settings page.
The description on that chackbox only appears if the user has permission to visit the login settings page (since that permission is separate from this page).

Screenshot 2025-01-09 at 2 15 40 PM

@indigoxela
Copy link
Member

indigoxela commented Jan 11, 2025

I can see, there's good progress here, but currently UserLoginAppearanceTestCase fails - it needs to get updated according to the new form element structure.

And we'd probably need test coverage for changing the theme in system_themes_admin_form().

@indigoxela
Copy link
Member

I just tested changing the theme via admin/appearance and it doesn't work. Only after flushing all caches manually (via admin bar) the changed setting takes effect.
I've added a PR comment.

Personally, I'm no fan of having that setting also on the themes page. But if there's consensus that this is a good idea... 🤷

@herbdool
Copy link

Regarding login page settings:

  • How about "Login style" rather than the wordier "Regions and branding"?
  • Since the "simplified" login is default on new installations, I don't think the non-simplified should be called "Standard". It's no longer the standard.

@quicksketch quicksketch modified the milestones: 1.30.0, 1.30.1 Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants