Design horizontal menu bar and decide what is displayed when #2244
Labels
Feature: Usability
Issues that make it easy for visitors to find the information they need quickly and easily
Role: Design UI/UX
User interface / user experience design
size: 2pt
The lift to complete this user story 3-4hrs
Milestone
We want to surface/show users the most important menu items that are currently hidden inside the hamburger menu
Overview
Currently we use a 'hamburger' menu which hides some useful links for food-seekers and those helping them.
We can surface the most important and useful links on devices that have the screen real estate.
This will help users get a better sense of what our site does, what they should be asking, and can help them contribute (both new listings and perhaps money or time). We can also use color and shape to draw attention.
For example:


Current:
Proposed concept:
Discussion
Due to the varying width of the screen and the number of menu items, we will still need a 'more menu options' affordance (which will probably still be a hamburger menu), but we can show the top menu items when there's space.
What to build
This is a typical hamburger menu-type thing where we want to show/surface the highest priority links on the available screen real estate, before moving those items to the hidden hamburger menu.
For example: Perhaps it’s this, in priority order:
Note that priority is different from position, so let’s make position along the top to be (left to right):
About Us, Suggest Listing, Contact Us, FAQ, Donate button, (and all the other links)
So as screen shrinks, items should move off the horizontal bar and into the hamburger menu in reverse-priority order (i.e. Volunteer Login disappears first, About Us disappears last)
Action Items
Related
The text was updated successfully, but these errors were encountered: