Practicalities
An FAQ with nothing to open: a serif heading that settles in word by word beside the intro and a pill action, then six questions and answers laid out in a three-column ruled grid that arrive in turn.
An FAQ with nothing to open: six short answers printed straight onto the page in a ruled grid, under a heading and a pill for anything that is not covered.
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/faq96?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/faq96?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/faq96.tsx plus the button22 sliding-marker pill and the text1 word stagger it uses.
The installed file exports faq96Demo alongside the block: the exact props behind the preview above. Spread it to get a working FAQ grid in one line.
import { Faq96, faq96Demo } from "@/components/beste/block/faq96";
export default function Page() {
return <Faq96 {...faq96Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Faq96 } from "@/components/beste/block/faq96";
export default function Page() {
return (
<Faq96
eyebrow="Practicalities"
heading="Six short answers before you book."
description="The things people email about most, answered without a form to open."
button={{ label: "Something else?", href: "mailto:hello@beste.co", tone: "outline" }}
items={[
{ question: "Where are the rooms?", answer: "Rua da Prata 12, second floor. There is a lift." },
{ question: "What if I am late?", answer: "Come anyway. The session ends at the usual time." },
{ question: "Which languages?", answer: "English, Portuguese and Spanish, in the room and online." },
]}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
eyebrow | string | – | Small-caps line above the heading |
heading | string | – | Section heading, rendered as an h2 through Text1 |
description | string | – | Short intro beside the heading |
button | ActionButton | – | Pill action under the intro |
items | FaqItem[] | [] | Questions and answers, up to three across |
className | string | – | Extra classes for the outer <section> |
type FaqItem = {
question: string;
answer: string;
};
type ActionButton = {
label: string;
href: string;
tone?: "primary" | "light" | "dark" | "outline";
};dl with dt/dd pairs, so each question stays bound to its answer for a screen reader even though they are laid out as a grid.(index % 3) * 0.1, so each row of three staggers left to right and the delay resets on the next row rather than growing to a second by the sixth item.sm and three at lg, and the modulo stagger stays keyed to three, so on a two-column layout the rhythm is a small irregularity rather than a wrong one.dt set in serif at text-2xl while answers stay in the muted body size, which is what keeps a wall of six answers scannable.md:items-end, so the intro and its button sit on the same baseline as the foot of the heading.border-t above the grid separates it from the header rather than a rule per item, since a ruled grid with visible answers would read as a table.faq80
An always-open FAQ laid out as a two-column grid of numbered, hairline-separated question and answer entries, closing with a soft support panel that pairs a short prompt with two actions.
faq93
A two-column question grid with every answer already visible on a hairline, so nothing is hidden behind a toggle, closed by a soft panel pointing at a direct reply.
faq8
Questions with answers displayed below in a simple list. Best for FAQs with shorter answers that don't require expansion.
faq9
Q&A pairs arranged in a responsive grid layout. Ideal for displaying concise answers in a scannable, multi-column format.