Navbars

A navbar is the strip across the top of a product that holds the brand mark, the top level of navigation and whatever controls depend on who is signed in. It is the one component every page shows, so it absorbs more state than its size suggests: a menu open or closed, a session signed in or out, a width wide enough for the links or not.

Both navbars here carry those axes as live state rather than as separate designs, which is the honest way to build one: drawn as static frames, a hover-open menu crossed with a signed-in avatar multiplies into a wall of pictures of two components. The part worth getting right is hover intent. A menu that opens the instant a pointer touches its trigger will open on the way past, and one that closes the instant the pointer leaves will close while the reader is moving diagonally toward it. A short delay on both edges fixes it; a click pins the menu open, and Escape returns focus to the trigger.

9 blocks

Marketing navbar

Marketing sites, product landing pages, brand-forward app shells

Marketing navbar – Glide

Marketing sites where one card should morph between menus

Marketing navbar – Ink

Dark brand-forward headers with a one-field sign-up

Compact navbar

SaaS dashboards, boxed app shells, product tools

Compact navbar – Glide

Compact bars where the open menu should be marked on the track

Compact navbar – Ink

Compact dark bars with search

App top bar

The bar across the top of a signed-in app

App top bar – Glide

Apps where news should arrive at the bell

App top bar – Ink

Apps with a command palette

01

Using Navbars

Reach for it when

  • A product whose top-level sections fit across one row
  • Landing pages where sign-up has to be reachable from any scroll position
  • App shells that need the account control in a fixed, predictable corner
  • When signed-out and signed-in visitors share a page but need different actions

Reach for something else when

  • A section tree several levels deep: a sidebar or a tree view shows depth that a mega-menu flattens
  • Checkout and other one-way flows: strip the header back to the mark and an exit
  • Switching between views of the same page. That is what tabs say
02

Where it shows up

01

Marketing site header

The header a first-time visitor meets: brand mark, a handful of section links, and the sign-up pair kept visible while they read, since that pair is what the page is for.

02

Product mega-menu

A panel wide enough to group what you sell into columns, each with its own heading and a short description per entry, so a visitor can tell two similar offerings apart without leaving the page.

03

Dashboard app shell

A boxed bar over a tool: a few nav pills, no marketing brand mark, and the account control in the corner where it stays put as the view beneath it changes.

04

Signed-in account state

The same bar has to serve a stranger and a member. One sees a log-in and a sign-up; the other sees their photo and a way to manage the account, in the same place on the same row.

03

Questions

Should navbar menus open on hover or on click?

Both, with rules. Open on hover after a short delay so the menu does not appear when the pointer is only passing, and close after a delay so it survives a diagonal trip into the panel. A click pins it open for anyone who prefers clicking, keyboard focus opens it, and Escape closes it and returns focus to the trigger.

What should a navbar do when the links no longer fit?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.