Command Search Navbar

Navbar68: Command Search Navbar

Search-forward navbar with a wide pill-shaped search field centered between the wordmark and the nav/CTA cluster. The field's submit control is a circular icon button whose arrow animates: on focus, the resting arrow slides out to the right while a second, off-screen arrow slides in from the left to take its place, giving the submit affordance a continuous directional swap instead of a static icon.

Installation

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://ui.beste.co/r/navbar68?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

npx shadcn add "https://ui.beste.co/r-base/navbar68?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/navbar68.tsx, the button12 component it uses for the CTA pill, and its dependencies.

Quick start

The installed file exports navbar68Demo alongside the block: the exact props behind the preview above. Spread it to get a working navbar in one line.

import { Navbar68, navbar68Demo } from "@/components/beste/block/navbar68";

export default function Layout() {
  return <Navbar68 {...navbar68Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

import { Navbar68 } from "@/components/beste/block/navbar68";

export default function Layout() {
  return (
    <Navbar68
      brand="Auralis"
      links={[
        { label: "Work", href: "/work" },
        { label: "Journal", href: "/journal" },
      ]}
      button={{ label: "Tell us more", href: "/contact" }}
      labels={{ searchPlaceholder: "Search projects, journal, people…" }}
    />
  );
}

Props

NavLink: { label, href }. labels.searchPlaceholder is optional to set (the input renders with no placeholder if labels is omitted).

Behavior notes

• The search field is defined once and reused in two places: centered between wordmark and actions from md upward, and again inside the mobile menu (visible only below md, via md:hidden) — there is a small overlap window between md and lg where both the header search and the nav links are hidden/shown independently.
• The submit button's double-arrow swap is driven purely by CSS group state: group-focus-within/search68:translate-x-[160%] moves the visible arrow out while the hidden absolute-positioned arrow (-translate-x-[160%] at rest) translates to translate-x-0, both on a 300ms ease-out transition triggered by focusing the input.
• The search input itself has no onChange/onSubmit wiring in the block; it is a presentational field meant to be connected to real search logic by the consumer.
• The nav links and CTA only show at lg and up; the mobile menu (conditionally rendered while open) stacks the search field (on screens below md), then the links, then the full-width CTA button.