-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Navigation Screen] Broken first landing experience when no menus are present. #28124
Comments
Good ticket. There's some work to be done here:
Those are some of the issues that will all help to make clearer how to interact with this screen. I currently have to focus on the navigation block itself, but I hope I will have some time to take a stab at this, but no promises. Looking only in isolation at the problem described in this ticket: how do I name my first menu? I'd take inspiration from the existing menu editor:
Suggestion: Replace the "no menus available", with a "Create your first menu below" message. Remove the "Add new" button entirely, and make the menu name input field visible right on the menu box. Remove "select menu" and "manage locations" so long they are empty. Once you've saved your first menu, you get this: Note how it shows you can edit the currently selected menu, or create a new one. Manage locations also becomes visible. Like I said, I hope to be able to push some tweaks in the near future, and my instincts go towards reduction and moving a little towards the existing screen. Here's a very rough doodle: Hope that helps. |
I mocked up a sort of "first run" experience that looks something like this: Menus.First.Run.mp4It was mentioned that this could all be unnecessary if we create a new menu automatically (perhaps with a general "Menu" or "Menu 2" name) when you first visit the screen. That might be generally simpler, but I also like the opportunity to educate users — but maybe it isn't worth the time for this aging system and screen? |
I had a look into the idea of using an automatic name as a quick fix, and it seems to be more complicated, though I might be looking in the wrong place. It's not just the name that's a problem, but the way it's working at the moment is that the screen has a menu with a The way to solve it properly would be to create a menu post type on the server when the user has no menus, which is taking us towards what your mockup does anyway.
I also like this a lot. I don't think it'd be too much work and would offer a lot of value. From a dev point of view, I think we could potentially break this into two parts:
The first part generally seems straightforward to implement, and the second part is something we already need to do (#23953). |
Description
When first landing on the Navigation Screen, if the user has no menus they're presented with a screen that has the message 'No menus available'.
However, the user can still edit and save a menu without being given a way to name the menu.
Step-by-step reproduction instructions
Expected behaviour
Either:
Or:
Or something else entirely (this needs some design thoughts).
In tandem with this, we might want to think about what the user's first experience on this screen should be, how do we make it clear what the first step should be?
Actual behaviour
When there are no menus present, the user can still edit a navigation block in the editing area of the screen. The user can edit and save it, but has no way to name it, assign it to a location, or delete it (so this is very bad bug!).
Screenshots or screen recording (optional)
The text was updated successfully, but these errors were encountered: