Measured entry
tailark-mist-faqs-1
A client-side Next.js FAQ section shipped as a shadcn registry block. It renders a single-open, collapsible accordion, uses Tailwind theme utilities and Next.js Link, and expects Tailark's Mist accordion registry dependency to provide the local accordion primitives.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 1 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 57.9 KB (123.3 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 1.08s error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-accordion" from "<sandbox>re-cd0db2a29952/src/components/ui/accordion.tsx".
Verdict
Do not treat this as install-ready. The build fails because the Tailark accordion dependency resolves to a missing shadcn registry item. It needs a shadcn-style setup plus a manually supplied accordion, so teams seeking a dependable drop-in block should avoid it for now.
Use it if
- You want a compact FAQ section with one expandable answer at a time.
- Your app already has compatible accordion primitives and Tailwind theme tokens.
- You are comfortable replacing the sample questions and support link in source.
Skip it if
- You need a registry component that installs and builds without manual repair.
- Your project does not use Next.js or cannot replace the Next.js Link import.
- You need multiple answers to remain open at the same time without modifying the accordion configuration.
Install
| Declared dependencies | clsx, tailwind-merge |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
A non-shadcn project must add compatible accordion primitives, Tailwind styling, the referenced theme tokens, and the component alias, then replace or configure Next.js Link. Because the declared Tailark accordion registry item is unavailable, wire the accordion imports to a local implementation manually.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/tailark/blocksAlternatives
Other published entries for the faq pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-faq-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- hyperui-faq-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- hyperui-faq-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- meraki-faq-collapseminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- meraki-faq-centeredminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO
- meraki-faq-gridminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO