Between sessions
Within a day of each session, a few lines from us: what we heard, and one thing worth noticing before next time.
A voice note or an email if something comes up. We reply within a working day, never with a form letter.
Something to try, chosen together. A boundary, a conversation, a morning left empty on purpose.
Not a crisis line, but a person. If the week goes sideways, twenty minutes on the phone is part of the work.
A four-step process on one horizontal line that draws itself across the page as the steps arrive in turn, each with a ringed icon, a numeral, a serif title and a description, under a serif heading that settles in word by word beside the intro and a pill action.
Four things that happen between sessions, strung along a line that draws itself across the row as the steps arrive, each with a circled icon, a number, a title and a paragraph.
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/workflow58?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/workflow58?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/workflow58.tsx plus the button22 sliding-marker pill and the text1 word stagger it uses.
The installed file exports workflow58Demo alongside the block: the exact props behind the preview above. Spread it to get a working process row in one line.
import { Workflow58, workflow58Demo } from "@/components/beste/block/workflow58";
export default function Page() {
return <Workflow58 {...workflow58Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Workflow58 } from "@/components/beste/block/workflow58";
export default function Page() {
return (
<Workflow58
eyebrow="Between sessions"
heading="The week is where most of the work happens."
description="An hour a week is not much. What we do around it is what makes it enough."
button={{ label: "See a sample week", href: "/week", tone: "outline" }}
steps={[
{ icon: NotebookPen, title: "A short note", description: "Within a day of each session, a few lines from us." },
{ icon: Phone, title: "A call if you need it", description: "Not a crisis line, but a person." },
]}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
eyebrow | string | – | Small-caps line above the heading |
heading | string | – | Section heading, rendered as an h2 through Text1 |
description | string | – | Intro beside the heading |
button | ActionButton | – | Pill action under the intro |
steps | Step[] | [] | Steps, four across from md |
className | string | – | Extra classes for the outer <section> |
type Step = {
icon: LucideIcon;
title: string;
description: string;
};
type ActionButton = {
label: string;
href: string;
tone?: "primary" | "light" | "dark" | "outline";
};scaleX over 2.4s, so the line appears to be drawn along the row while the track shows where it is going.0.35s stagger, unusually wide for this set, so they land roughly in time with the line reaching them rather than all arriving before it does.hidden md:block, since a horizontal connector has no meaning once the steps stack into a single column on a phone.bg-background, which is what lets them sit on the line without it showing through the middle of each mark.icon takes the Lucide component itself, not a name string, so icons are tree-shaken with your bundle and there is no map to maintain.tabular-nums, and the list is an ol, so the sequence is real rather than decorative.md, which is what keeps the line and the circles aligned; a fifth step wraps to a new row and leaves the connector behind.workflow57
A how-it-works section: serif heading settling in word by word beside the intro and a pill action, three numbered steps whose top rules draw themselves in one after another, and a wide photograph drifting inside its frame to close.
workflow59
A vertical process: a sticky column with a serif heading that settles in word by word, an intro and a pill action, beside numbered ringed steps down a line that draws itself in ink as the page scrolls, each with a small-caps timing, a serif title and a description.
workflow38
Process steps cascading in a diagonal staircase with connecting markers.
workflow46
Left-aligned intro with eyebrow, heading and CTA beside a four-column band of numbered process steps linked by a connector line.