Navigation

FloatingNavbar

Pill-shaped floating navbar that hides on scroll-down and reappears on scroll-up.

Interactive Preview

↓ Scroll down to hide / scroll up to reveal

Content block 1

Content block 2

Content block 3

Content block 4

Content block 5

Content block 6

Content block 7

Content block 8

Content block 9

Content block 10

Fixed positioning in production: FloatingNavbar ใช้ position: fixed เวลาใช้จริงให้วางที่ root layout เพื่อให้ navbar ลอยเหนือทุก page

Installation

# Copy the component file
# src/components/navigation/FloatingNavbar.tsx

Usage

// app/layout.tsx
import FloatingNavbar from '@/components/navigation/FloatingNavbar'

const links = [
  { label: 'Components', href: '/components' },
  { label: 'Tracks', href: '/products' },
  { label: 'Guidance', href: '/services' },
]

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        <FloatingNavbar
          logo={<span className="font-bold text-primary">Nexus</span>}
          links={links}
          cta={{ label: 'Start Learning', href: '/products' }}
        />
        {children}
      </body>
    </html>
  )
}

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a navigation component named FloatingNavbar in React/Next.js.
Goal: recreate the same overall UI and behavior as the FloatingNavbar reference from a component gallery.
What it needs to communicate: Pill-shaped floating navbar that hides on scroll-down and reappears on scroll-up..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Handle hover, active, selected, keyboard, and mobile states with clear feedback.
- Keep structure tidy so it feels production-ready rather than demo-only.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- links: NavLinkItem[] — Array of {label, href}
- logo: React.ReactNode — Logo slot
- cta: { label: string; href: string } — Call-to-action button

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Hide on scroll-down
- Blur backdrop
- CTA button
- Mobile-friendly

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`links`	`NavLinkItem[]`	-	Array of {label, href}
`logo`	`React.ReactNode`	-	Logo slot
`cta`	`{ label: string; href: string }`	-	Call-to-action button