[wp-trac] [WordPress Trac] #45003: Modernize Admin Nav
WordPress Trac
noreply at wordpress.org
Wed Sep 26 21:57:40 UTC 2018
#45003: Modernize Admin Nav
-------------------------+-------------------------------------------------
Reporter: s3w47m88 | Owner: (none)
Type: defect | Status: new
(bug) |
Priority: normal | Milestone: Awaiting Review
Component: General | Version: 4.9.8
Severity: normal | Keywords: 2nd-opinion ux-feedback ui-feedback
Focuses: |
-------------------------+-------------------------------------------------
This is apart of a bigger project for my staff and I, you can find the
context here https://www.theportlandcompany.com/2017/09/10/proposed-
improvements-to-the-wordpress-ui/.
Our goal is to clean up the UI with two principles in mind:
- Context Visibility - Only show something when it's in context.
- Add With Purpose - If something, such as padding or margins, don't serve
a purpose, don't add them.
- Simplify Number of Actions - If a step can be avoided in a process,
avoid it.
This ticket pertains to enhancing, modernizing, the existing admin
navigation.
For context, visit our website, shrink to mobile dimensions and select the
nav in the upper right, then a sub nav item. Also review ShiftNav -
https://shiftnav.io/pro.
Then compare this to the current wp admin menu, *especially* on mobile.
It's pretty painful! Here's the problems we see (followed with some
solutions):
- Currently the WP admin menu is single-tier.
- - This forces many developers to create a parent-level menu when they
would prefer, or could otherwise, place it under a more appropriate
context.
- - It also forces developers to move their navigation entirely out of the
menu and into the main body. This varies from page and Plugin creating
*massive* confusion for Users.
- Every new menu item increases the required amount of scrolling.
- On mobile, there is no sub item indicator beside parent pages that have
sub items.
- There is no transition effect when expanding sub menus, leaving a "jolt"
feeling, sometimes resulting in people thinking they're waiting or it's
broken (especially on mobile where the expanded menu can expand below the
viewable area.
- Expanding one sub menu does not collapse another. We can't think of a
use case where having both is necessary, but it does require the user to
scroll to the other menu(s) and click collapse, creating extra steps that
could be avoided it they automatically close when another item is
expanded.
We propose introducing a similar experience to Shiftnav on the back end.
We would be happy to provide designs and built this as a feature-as-Plugin
if the Core leadership are willing to approve it.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/45003>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list