An app-style bar with the brand, a thin rule and a chevron switcher showing the current section; the switcher drops a floating list of sections with descriptions and a check on the current one, and actions sit on the right. On a phone the same list rises as a bottom sheet behind a scrim. Both panels stay in the markup and are toggled with CSS.
An app-style bar for products split into sections: the brand, a thin rule, and a switcher button that names the section you are in. The switcher drops a list of every section with a one-line description and a check on the current one, while the actions stay on the right. On a phone the same list rises from the bottom as a sheet.
Upgrade to Pro
Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.
Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.
Radix flavor
npx shadcn add "https://beste.dev/r/navbar106?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://beste.dev/r-base/navbar106?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/navbar106.tsx plus the shadcn button primitive it uses.
The installed file exports navbar106Demo alongside the block: the exact props behind the preview above. Spread it to get a working navbar in one line.
import { Navbar106, navbar106Demo } from "@/components/beste/block/navbar106";
export default function Page() {
return <Navbar106 {...navbar106Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Navbar106 } from "@/components/beste/block/navbar106";
export default function Page() {
return (
<Navbar106
brand="Orbit"
sections={[
{ label: "Analytics", description: "Traffic, funnels and retention.", href: "/analytics", current: true },
{ label: "Billing", description: "Plans, invoices and usage.", href: "/billing" },
{ label: "Settings", description: "Members, roles and API keys.", href: "/settings" },
]}
actions={[
{ label: "Invite", href: "/invite", variant: "outline" },
{ label: "New report", href: "/reports/new" },
]}
labels={{ switch: "Switch section", close: "Close", heading: "Go to" }}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
brand | string | – | Wordmark on the left, followed by a thin vertical rule |
sections | Section[] | [] | Entries in the switcher; the one with current: true is shown on the button |
actions | ActionButton[] | [] | Buttons on the right; on small screens only the last one stays visible |
labels | { switch?: string; close?: string; heading?: string } | {} | Screen reader name for the switcher, the sheet close button and the sheet heading |
className | string | – | Extra classes for the outer <header> |
type Section = {
label: string;
description: string;
href: string;
current?: boolean;
};
type ActionButton = {
label: string;
href: string;
variant?: "default" | "outline" | "ghost" | "secondary";
};pointerType check keeps touch taps from opening and closing it in one go) or click, and on a phone the floating list is hidden and the sheet takes over.current: true, or the first entry.translate-y-full, is capped at 80vh with its own scroll, and carries a heading and a close button above the list.