Nav: Constraints

The following are a list of constraints and best practices that we’ll want to be mindful of when we choose to redesign the WP navigation:

  • Accessible – Navigation should be easy for any user to use despite their ability or particular device. This includes navigation vis keyboard, voice navigation, screen readers, and other assistive devices.
  • Responsive – Any solution we come up with should scale to mobile devices and smaller screens.
  • Obvious, Easy, Possible – Jason Fried shared this concept way back in 2011. It’s something that has stuck with me ever since. Making something obvious comes at a cost. Attempting to make everything obvious is a recipe for overwhelming navigation. We should aim to streamline our navigation where possible.
  • Concise, descriptive labels – Each label should be as short as possible, yet still descriptive and understandable at a glance.
  • Contextual – When possible, we should attempt to adapt what is shown within navigation based on what the use case of the user.
  • Extensible – Developers should be able to easily modify navigation.
  • Text descriptions + icons – We should attempt to preserve text descriptions next to icons whenever possible.
  • At-a-glance location awareness – A user should be able to easily see at a glance which portion of the app they’re in.
  • Minimize drop-downs – Where possible, we should attempt to reduce pop out menus.
  • Obvious clickable areas – It should be obvious at a glance which navigation items are clickable.
  • Consistent layout & organization – Navigation should not change as you navigate WP admin. It should remain consistent.
  • Consider breadcrumbs and search – Both search and breadcrumbs can supplement navigation to provide a better user experience.
  • Limit levels – The more levels deep we take things the more complicated any navigation will get.

Let me know in the comments if you can think of anything else that should be considered.