Blog
Sticky Contents
An article layout with a sticky table of contents: the active item is marked with an accent bar and colour, and on a narrow block the column becomes a plain list before the text.
React + Tailwind, shadcn-compatible: press “Copy for AI” and your Cursor or Claude Code agent installs it with the shadcn CLI.
What you can change
- the sections array: ids, headings and paragraphs
- activeId — which item is highlighted
- eyebrow and title above the layout
Built from
The install command brings these components too. The block only passes them props: their palette and behaviour stay their own.
A link for your AI agent: preview, code and instructions.
Preview
Use it with AI
- 1. Copy the link.
- 2. Write to your agent in your own words and drop the link into the sentence.
- 3. The agent opens the link and installs the component from the registry.
put this on the home page as the hero:
https://vibeui.club/c/blog-010?lang=en&theme=dark
Not sure where to paste it? Step-by-step guide
Show the full instructions
What the link says, spelled out. Use it when your agent cannot open links — paste this text instead.
Loading…
How to use
<Blog010 title="A block's journey" activeId="copy" sections={[{ id: "copy", heading: "What Copy for AI copies", paragraphs: ["…"] }]} />A sample call. The agent installs the component itself from the registry via the “Copy for AI” link.
Settings
- Heading
title· default: A block's journey: from catalogue to your site- Contents heading
tocTitle· default: Contents- Accent
accent· default: theme colour- Background
background· default: theme colour
More in Blog
FAQ
- How do I add Sticky Contents with Cursor or Claude Code?
- Press “Copy for AI” on this page and paste it into your agent's chat. The instruction contains the shadcn CLI install command, the dependencies and what to keep, so the agent installs this exact component instead of recreating a lookalike.
- What does Sticky Contents depend on?
- No npm packages beyond React and Tailwind CSS. It also installs catalog components: heading-001.
- What can I change in Sticky Contents?
- Adapt: the sections array: ids, headings and paragraphs; activeId — which item is highlighted; eyebrow and title above the layout. Keep as installed: the heading-001 imports from @/components/vibeui/ — do not inline their code into the block or swap in your own; the parts receive props only; the local --vibeui-blog-010-* palette — do not swap it for your theme tokens; the contents built from the same sections as the text: a hand-written list drifts from the content.
- Is Sticky Contents free?
- Yes. The preview is open without an account; with a free account you can copy up to 20 components a month.
For developers
npx shadcn@latest add https://vibeui.club/r/pro/blog-010.jsonThis command needs a signed link: sign in and open “Component source” below — it issues a working link valid for 30 minutes. All install options
Technical notes
A composite block: imports heading-001 from @/components/vibeui/ — the install command brings them along with the block. The block owns the layout and its own text, passes the parts props only and leaves their --vibeui-<name>-* palettes alone. The block is self-contained: one file, no npm dependencies, its own palette in local variables --vibeui-blog-010-*. A server component: the active item is set by the activeId prop and marked with aria-current — there is deliberately no intersection observer. The contents are a nav with aria-label, the items sit on a shared left line, and the active one overlays it with an accent bar. Stickiness is turned on by a container query at 56rem, the headings carry an id and scroll-margin-top, and the text measure is limited in ch.
Tags
- blog
- toc
- sticky
- article
- navigation
- composite
Component source
The same file your agent installs. Here in case you would rather copy it by hand.
Loading…