Measured entry
tailark-veil-faqs-5
A client-side Next.js FAQ block that groups answers into category cards with single-item collapsible accordions and a contact link. It ships through the Tailark shadcn registry and depends on Tailark Card and Accordion components, Lucide icons, Tailwind theme classes, and next/link.



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 | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 58.9 KB (124.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 729ms error during build: [vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-de75157fc374/src/cut/components/faqs-5.tsx".
Verdict
A sensible categorized FAQ layout, but it does not currently build because the Tailark Card registry dependency returns a not-found response. It needs a shadcn-style setup and manual dependency repair, so avoid it when you need a drop-in install.
Use it if
- You want a categorized help-center section instead of one long accordion.
- Your Next.js app already uses shadcn-style registry components and Tailwind theme tokens.
- You are prepared to supply or repair the Tailark Card dependency before installation.
Skip it if
- You need a component that installs from the published registry without dependency repair.
- Your project is not based on Next.js or cannot use next/link and client components.
- You want FAQ search, deep links, or content loaded from a CMS rather than a static local data array.
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 |
In a non-shadcn project, add compatible Card and Accordion primitives, Lucide React, Tailwind utilities and matching theme tokens, then replace the path aliases and Next.js Link if your framework uses different conventions. The Tailark Card registry reference must also be corrected or implemented locally.
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