The first weeks are for laying things out without sorting them. You talk, we listen, and nothing gets labelled yet.
Patterns start to show themselves. Not because we point at them, but because there is finally room to see them.
Small experiments between sessions: a boundary, a conversation, a morning left empty. We look at what happened together.
Endings are planned, not abrupt. We slow the rhythm, name what has changed, and leave the door on the latch.
A scroll-led feature: a serif heading settling in word by word beside a pill action, then numbered chapters that scroll past a pinned photograph, each one swapping the image with a soft blur and brightening its own title as it reaches the centre of the viewport.
Chapters read down a ruled column while one photograph stays pinned beside them, swapping to match whichever chapter is currently in the middle of the screen and dimming the titles that are not.
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.
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/feature276?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/feature276?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/feature276.tsx plus the button22 sliding-marker pill and the text1 word stagger it uses.
The installed file exports feature276Demo alongside the block: the exact props behind the preview above. Spread it to get a working chapters section in one line.
import { Feature276, feature276Demo } from "@/components/beste/block/feature276";
export default function Page() {
return <Feature276 {...feature276Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Feature276 } from "@/components/beste/block/feature276";
export default function Page() {
return (
<Feature276
eyebrow="What a season looks like"
heading="The work has a shape, even when it does not feel like it."
button={{ label: "Begin your season", href: "/book" }}
chapters={[
{
title: "Arriving",
description: "The first weeks are for laying things out without sorting them.",
image: { src: "/photos/lake.jpg", alt: "Morning mist lifting off a still lake" },
},
{
title: "Leaving well",
description: "Endings are planned, not abrupt.",
image: { src: "/photos/dock.jpg", alt: "A wooden dock reaching into a still lake at dusk" },
},
]}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
eyebrow | string | – | Small-caps line above the heading |
heading | string | – | Section heading, rendered as an h2 through Text1 |
button | ActionButton | – | Pill action beside the heading |
chapters | Chapter[] | [] | Chapters, numbered in the order given |
className | string | – | Extra classes for the outer <section> |
type Chapter = {
title: string;
description: string;
image: { src: string; alt: string };
};
type ActionButton = {
label: string;
href: string;
tone?: "primary" | "light" | "dark" | "outline";
};-45% 0px -45% 0px margin, so a chapter counts as current only while it occupies the middle band of the viewport. That narrow strip is what makes the swap feel decided rather than twitchy.AnimatePresence, so the outgoing picture cross-fades under the incoming one instead of being replaced in a single frame.text-foreground/40 and lift to full over 700ms, so the column reads as one chapter at a time without anything being hidden.md the sticky column is dropped entirely and each chapter renders its own image inline, because a pinned photograph on a phone would take the whole screen.01, 02 stay correct as chapters are added or removed.ol with divide-y and a border at both ends, so the sequence is a real ordered list for a screen reader.blur(24px) on decode, with a complete check on mount so a cached file is not left blurred.