Priority+ Navigation
More CSS-y. Inspired by
Ben Callahan
's talk at the
Frontend Design Conference
in Portland. Forked from
Brad Frost
's
original implementation
, which involved a bit more JavaScript.
The
Priority+ pattern
was coined by
Michael Scharnagl
(
@justmarkup
) to describe navigation that exposes what’s deemed to be the most important navigation elements and tucks away less important items behind a “more” link. The less important items are revealed when the user clicks the “more” link.
Pros
-
Relatively simple to implement
– The logic required to execute this technique isn’t terribly complicated. It’s just a basic show/hide toggle to reveal the hidden navigation items.
-
(hopefully) exposes the most accessed features
– it’s hopefully revealing the three or four things the majority of users frequently access anyways.
Cons
-
Hides potentially important nav items
– what you may deem most important may not be what’s important to your users. Burying nav items means having to make some assumptions, and while it hopefully works out for most users, it might also piss some people off.
-
Doesn’t work well with multi-level navigation
– The priority+ pattern seems good for navs that have a lot of items at the same hierarchy level, but unfortunately it doesn’t seem to solve the sub-nav dilemma.
Resources
In the Wild