Standard Navigation
Section Subheader Nav
SectionSubheaderNav — thin sticky bar that docks directly under a main header: a breadcrumb trail on the left, and either a section's own sub-nav or a single "Back to X" link on the right.
$ velocityx add section-subheader-navBuilt for astro.
Full docs for Section Subheader Nav →
Needs a licence key — buy lifetime access here, then
velocityx login once.
Section Subheader Nav
SectionSubheaderNav — thin sticky bar that docks directly under a main header: a breadcrumb trail on the left, and either a section's own sub-nav or a single "Back to X" link on the right.
Preview failed to render
- Framework
- astro
- Source
- 94 lines
- SectionSubheaderNav.astro
- Runtime
- Static markup
- zero client JS
- Theme
- 4 tokens
- re-themes from your scale
- Responsive
- sm · lg
- 2 breakpoints
- Dark mode
- Built in
- dark: variants
- Accessibility
- 3 ARIA
- attributes and roles
Props
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| homeLabel | string | No | 'Home' | |
| homeHref | string | No | '/' | |
| crumbs | Crumb[] | Yes | ||
| sectionNav | SectionLink[] | No | [] | |
| backLink | { label: string; href: string } | No | ||
| activeHref | string | No | ||
| className | string | No | '' |
Using it
The smallest call that compiles — required props only. The import is
written for your own file at src/components/Example.astro;
adjust the relative import if yours sits elsewhere.
Everything optional is in the table above, with its default.
---
import SectionSubheaderNav from './velocity/section-subheader-nav/SectionSubheaderNav.astro';
---
<SectionSubheaderNav
crumbs={[]}
/>Built from Section Subheader Nav's own prop signature and the path the CLI installs it to, so it can't drift from either.
Accessibility
- ARIA attributes
- aria-current, aria-hidden, aria-label
- Keyboard
- Built on native controls — Enter/Space work as standard
Read from the source, not asserted — anything not listed simply isn't in this component's markup.
Behaviour
- Ships client JS
- No — renders to static markup
- Breakpoints
- sm: lg:
- Dark mode
- Carries its own dark: variants
Theming
This component paints from 4 steps of
your theme scale — no hardcoded colours, and no font-family of
its own, so your type cascade wins. Override the variables and it follows.
primary-300primary-400primary-600primary-700Get the Velocity preset and CSS theme from the public source guide. The CLI theme command is not available on npm yet.
File this creates
The CLI writes this path into your project — nothing
else moves. Paths are under your source root, which defaults to
src/; pass
--dest if yours is elsewhere.
-
src/components/velocity/section-subheader-nav/SectionSubheaderNav.astro94 lines
Copy the paths
src/components/velocity/section-subheader-nav/SectionSubheaderNav.astroSection Subheader Nav — questions
How do I install Section Subheader Nav?
Run velocityx add section-subheader-nav . The CLI writes the source straight into your project — it is not a runtime package dependency.
Do I need a licence for Section Subheader Nav?
Yes. It is part of the lifetime library — buy access at https://aidxn.com/shop/velocity-x-component-library/, authenticate once, and install it. Your lifetime licence includes future component updates.
Can I edit Section Subheader Nav after installing it?
Yes — the files are yours once written. The CLI compares its lockfile hash before upgrades and refuses to overwrite code you changed.
Does Section Subheader Nav ship JavaScript to my users?
No. It renders to static markup with no client-side JavaScript of its own.
Will Section Subheader Nav match my brand colours?
Yes. It paints entirely from your theme scale — 4 steps of primary-* / accent-* — with no hardcoded hex values and no font-family of its own. Override the theme CSS variables and it follows your design system instead of ours.
Does Section Subheader Nav work on mobile?
It carries its own responsive rules at the sm, lg breakpoints, so it re-flows rather than relying on the page around it to do the work.
Does Section Subheader Nav pull in any dependencies?
No external ones. Every component in the library is built with react/react-dom or plain Astro only — no GSAP, Radix, Swiper or Headless UI — which is what makes dropping it into an existing project safe.
Set up & reference
All docs →Install this component:
$ velocityx add section-subheader-nav- 2. Install the theme — run this first, once per project Do this once per project, before your first component.
- The palette gotcha — this one bites silently Silent failure — the component renders, just unstyled.
- Your edits are safe by default What happens to your changes when you upgrade.
- You own the code What you are actually buying.
Related components
More from Standard Navigation.
End-of-page block of onward destinations — a heading and a responsive grid of fully-clickable cards, each with a short description and a hover arrow. Static markup, no client JS, built for "related articles" and "keep exploring" footers.
astroThe "skip to content" links keyboard and screen reader users expect as the first stop on a page, styled to match your brand instead of showing as an unstyled browser-default blue link when focused.
astroA persistent app-shell identity menu: avatar trigger, profile header, nav links with aria-current and a pinned sign-out. Reads the current route per render so it never remounts on navigation.
reactIn-page section links that highlight themselves as the reader scrolls, so a long docs or landing page always shows where you are without you having to hunt for it. Tracks visibility with IntersectionObserver, never a scroll handler, so it costs nothing on long pages.
react