Two-Column FAQ with Help Rail
Questions on the right against a sticky rail that keeps a route to a human in view — for the visitor whose objection is not on the list.
Exclusive accordion behaviour from named <details> elements — no state, no hooks, no JavaScript, full keyboard support for free.
components/faq-accordion.tsxnpx hoverlab add faq-accordion
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
Start a page with this section — add more, order them, and leave with the page source.
Everything people ask before getting started.
Yes. Everything here is yours to ship in client work and paid products, with no attribution required.
No. The markup is plain HTML and the styling is utility classes, so it drops into any stack that can render an element.
Copied code is yours — nothing reaches back into your project. Pull a newer version whenever you want it.
There is. A large part of the catalog is free forever; the paid plan unlocks the rest and removes usage limits.
Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.
/**
* <FaqAccordion> — a frequently-asked-questions list.
*
* Built on <details>/<summary> with a shared `name`, which gives real
* accordion behaviour — opening one closes the rest — with no state, no
* effect hook and no JavaScript at all. Keyboard support and the
* open/closed state exposed to screen readers come free from the elements.
*
* Pass `exclusive={false}` for an list where several answers can sit open
* at once.
*/
import * as React from 'react'
import { Plus } from 'lucide-react'
export interface FaqItem {
question: string
answer: string
}
export interface FaqAccordionProps {
items?: FaqItem[]
heading?: string
subheading?: string
/** Only one answer open at a time. */
exclusive?: boolean
className?: string
}
const DEFAULT_ITEMS: FaqItem[] = [
{
question: 'Can I use this in a commercial project?',
answer:
'Yes. Everything here is yours to ship in client work and paid products, with no attribution required.',
},
{
question: 'Do I need a specific framework?',
answer:
'No. The markup is plain HTML and the styling is utility classes, so it drops into any stack that can render an element.',
},
{
question: 'How do updates work?',
answer:
'Copied code is yours — nothing reaches back into your project. Pull a newer version whenever you want it.',
},
{
question: 'Is there a free tier?',
answer:
'There is. A large part of the catalog is free forever; the paid plan unlocks the rest and removes usage limits.',
},
]
/*
A stable id suffix derived from this instance's own content.
`useId` is the right answer and is not available here: this is a server
component and hooks are not. Hashing what makes one copy different from
another gives each its own name without a hook, a prop or a counter — and
it stays stable across server and client renders, which a counter would
not.
*/
function instanceId(...parts: (string | undefined)[]): string {
const text = parts.filter(Boolean).join('|')
let hash = 0
for (let i = 0; i < text.length; i++) hash = (Math.imul(hash, 31) + text.charCodeAt(i)) | 0
return (hash >>> 0).toString(36).slice(0, 6)
}
export function FaqAccordion({
items = DEFAULT_ITEMS,
heading = 'Frequently asked questions',
subheading = 'Everything people ask before getting started.',
exclusive = true,
className = '',
}: FaqAccordionProps) {
/*
* The exclusive-<details> group name, derived rather than written down.
*
* `name` on <details> is DOCUMENT-global: every <details> sharing it is
* one accordion, wherever on the page it sits. A literal therefore fuses
* two copies of this block into a single accordion — opening a question
* in one silently closes a question in the other — and a page rendering
* several of these at once is exactly what the catalog hubs do.
*/
const group = `faq-${instanceId(heading, subheading, items[0]?.question)}`
return (
<section className={`mx-auto w-full max-w-3xl px-4 py-16 sm:px-6 ${className}`}>
<div className="mx-auto mb-10 max-w-2xl text-center">
<h2 className="text-balance text-3xl font-bold tracking-tight sm:text-4xl">
{heading}
</h2>
{subheading ? (
<p className="mt-3 text-muted-foreground">{subheading}</p>
) : null}
</div>
<div className="divide-y divide-border/60 overflow-hidden rounded-2xl border border-border/60 bg-card/60">
{items.map((item) => (
<details
key={item.question}
name={exclusive ? group : undefined}
className="group px-5 py-1 [&_summary::-webkit-details-marker]:hidden"
>
<summary className="flex cursor-pointer list-none items-center justify-between gap-4 py-4 text-start font-semibold transition-colors hover:text-foreground/80">
{item.question}
<Plus
aria-hidden
className="h-4 w-4 shrink-0 text-muted-foreground transition-transform duration-200 group-open:rotate-45"
/>
</summary>
<p className="pb-5 pe-8 text-sm leading-relaxed text-muted-foreground">
{item.answer}
</p>
</details>
))}
</div>
</section>
)
}
bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.Drop it at components/faq-accordion.tsx and import it where you need the section:
import { FaqAccordion } from '@/components/faq-accordion'3 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.
Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.
| Prop | Type | Default |
|---|---|---|
items | FaqItem[] | DEFAULT_ITEMS |
heading | string | 'Frequently asked questions' |
subheading | string | 'Everything people ask before getting started.' |
exclusiveOnly one answer open at a time. | boolean | true |
className | string | '' |
The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.
<!--
No-JS FAQ Accordion — markup from the Hoverlab catalog.
This is the block rendered once to HTML and wrapped as a component
file. It is not a port of the React source: the Tailwind classes carry
the design, which is the part that took the work, and they are the same
in every framework.
This block has no interactive behaviour, so nothing is missing.
-->
<section class="mx-auto w-full max-w-3xl px-4 py-16 sm:px-6 ">
<div class="mx-auto mb-10 max-w-2xl text-center">
<h2 class="text-balance text-3xl font-bold tracking-tight sm:text-4xl">Frequently asked questions</h2>
<p class="mt-3 text-muted-foreground">Everything people ask before getting started.</p>
</div>
<div class="divide-y divide-border/60 overflow-hidden rounded-2xl border border-border/60 bg-card/60">
<details name="faq-192xqq" class="group px-5 py-1 [&amp;_summary::-webkit-details-marker]:hidden">
<summary class="flex cursor-pointer list-none items-center justify-between gap-4 py-4 text-start font-semibold transition-colors hover:text-foreground/80">Can I use this in a commercial project?<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-plus h-4 w-4 shrink-0 text-muted-foreground transition-transform duration-200 group-open:rotate-45" aria-hidden="true"><path d="M5 12h14"></path><path d="M12 5v14"></path></svg></summary>
<p class="pb-5 pe-8 text-sm leading-relaxed text-muted-foreground">Yes. Everything here is yours to ship in client work and paid products, with no attribution required.</p>
</details>
<details name="faq-192xqq" class="group px-5 py-1 [&amp;_summary::-webkit-details-marker]:hidden">
<summary class="flex cursor-pointer list-none items-center justify-between gap-4 py-4 text-start font-semibold transition-colors hover:text-foreground/80">Do I need a specific framework?<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-plus h-4 w-4 shrink-0 text-muted-foreground transition-transform duration-200 group-open:rotate-45" aria-hidden="true"><path d="M5 12h14"></path><path d="M12 5v14"></path></svg></summary>
<p class="pb-5 pe-8 text-sm leading-relaxed text-muted-foreground">No. The markup is plain HTML and the styling is utility classes, so it drops into any stack that can render an element.</p>
</details>
<details name="faq-192xqq" class="group px-5 py-1 [&amp;_summary::-webkit-details-marker]:hidden">
<summary class="flex cursor-pointer list-none items-center justify-between gap-4 py-4 text-start font-semibold transition-colors hover:text-foreground/80">How do updates work?<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-plus h-4 w-4 shrink-0 text-muted-foreground transition-transform duration-200 group-open:rotate-45" aria-hidden="true"><path d="M5 12h14"></path><path d="M12 5v14"></path></svg></summary>
<p class="pb-5 pe-8 text-sm leading-relaxed text-muted-foreground">Copied code is yours — nothing reaches back into your project. Pull a newer version whenever you want it.</p>
</details>
<details name="faq-192xqq" class="group px-5 py-1 [&amp;_summary::-webkit-details-marker]:hidden">
<summary class="flex cursor-pointer list-none items-center justify-between gap-4 py-4 text-start font-semibold transition-colors hover:text-foreground/80">Is there a free tier?<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-plus h-4 w-4 shrink-0 text-muted-foreground transition-transform duration-200 group-open:rotate-45" aria-hidden="true"><path d="M5 12h14"></path><path d="M12 5v14"></path></svg></summary>
<p class="pb-5 pe-8 text-sm leading-relaxed text-muted-foreground">There is. A large part of the catalog is free forever; the paid plan unlocks the rest and removes usage limits.</p>
</details>
</div>
</section>
What each framework gets across the whole catalog — effects convert properly; this rung is markup.
The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Want the whole screen instead of this one section? Open a page and copy it entire.
All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.
Browse FAQCopying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.
Questions on the right against a sticky rail that keeps a route to a human in view — for the visitor whose objection is not on the list.
Every answer rendered and visible in a two-column description list — the FAQ shape for a marketing page, where collapsed text is text a search engine will not quote.
Anchor-linked topic pills over per-topic details groups with the first answer open — for the FAQ that outgrew a single list, working with JavaScript disabled.
A search that narrows the list across answers and keywords, announces the count, and turns an empty result into the contact route it should always have been.
An FAQ written from the objections that stop a sale rather than from the questions that are comfortable to answer.
The security questions a buyer's IT reviewer asks, answered with scope and dates rather than with the word "enterprise-grade".