Partner Marks Bar

About this block

Partner Marks BarPRO

A co-branded bar: the wordmark, a thin vertical rule and a partner mark, then links and a button. Programmes drops a floating card of dated programme rows with a calendar link, and the phone menu is an overlay under the bar that ends in a contact footer. Every panel stays in the markup and is toggled with CSS.

A sticky co-branded bar: your wordmark, a thin vertical rule and a partner mark ("with Northwind"), then links and a button. Programmes drops a floating card of dated programme rows, each with a date, a title and a line, closed by a calendar link; on a phone the menu is an overlay under the bar that ends in a contact footer with email, phone and address.

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.

Upgrade Now

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

bash
npx shadcn add "https://beste.dev/r/navbar111?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

bash
npx shadcn add "https://beste.dev/r-base/navbar111?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/navbar111.tsx plus the shadcn button primitive it uses.

Quick start

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

tsx
import { Navbar111, navbar111Demo } from "@/components/beste/block/navbar111";

export default function Page() {
  return <Navbar111 {...navbar111Demo} />;
}

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

tsx
import { Navbar111 } from "@/components/beste/block/navbar111";

export default function Page() {
  return (
    <Navbar111
      brand="Fieldnote"
      partner={{ label: "with", name: "Northwind", href: "/northwind" }}
      programmes={{
        label: "Programmes",
        heading: "Upcoming programmes",
        items: [
          { date: "Nov 4", title: "Founders residency", description: "Six weeks with a cohort of twelve teams.", href: "/residency" },
          { date: "Nov 18", title: "Climate data sprint", description: "Two days building open tools.", href: "/sprint" },
        ],
        viewAll: { label: "See the full calendar", href: "/calendar" },
      }}
      links={[
        { label: "Partners", href: "/partners" },
        { label: "About", href: "/about" },
      ]}
      actions={[{ label: "Apply now", href: "/apply" }]}
      contact={{ heading: "Talk to the programme team", email: "[email protected]", phone: "+1 415 555 0142", address: "88 Harbor Street, San Francisco" }}
      labels={{ open: "Open menu", close: "Close menu" }}
    />
  );
}

Props

PropTypeDefaultDescription
brandstring–Wordmark on the left
partnerPartner–Partner mark shown after the vertical rule
programmesProgrammeMenu–The item that opens the dated programme card
linksNavItem[][]Plain links beside it
actionsActionButton[][]Buttons on the right, repeated in the mobile overlay
contactContact–Contact footer at the bottom of the mobile overlay
labels{ open?: string; close?: string }{}Accessible names for the mobile toggle
classNamestring–Extra classes for the outer <header>
ts
type Partner = {
  label: string;
  name: string;
  href: string;
};

type ProgrammeMenu = {
  label: string;
  heading: string;
  items: Programme[];
  viewAll?: NavItem;
};

type Programme = {
  date: string;
  title: string;
  description: string;
  href: string;
};

type Contact = {
  heading: string;
  email: string;
  phone: string;
  address: string;
};

type NavItem = {
  label: string;
  href: string;
};

type ActionButton = {
  label: string;
  href: string;
  variant?: "default" | "outline" | "ghost" | "secondary";
};

Behavior notes

  • The programme card and the mobile overlay are always rendered and toggled with CSS classes, so every link is in the server-rendered HTML. Closed panels carry aria-hidden and inert, which keeps their links out of the tab order.
  • The Programmes trigger opens on hover and on click, with aria-expanded and aria-controls; the card closes when the pointer leaves the header, on Escape and on a pointer down outside the header.
  • The mobile overlay is fixed under the bar and locks body scroll while open; it is restored on close and on unmount.
  • The contact footer turns the email into a mailto: link and the phone into a tel: link with spaces stripped.
  • Links inside the mobile overlay close it on click, and Escape closes it too.

More Navigation blocks

View all Navigation
PRO

navbar116

Brand Switcher Bar

PRO

navbar91

Store Categories Mega

PRO

navbar104

Word Menu Panel

Get Pro