Measured entry
tailark-veil-faqs-4
A static FAQ section that ships as a shadcn registry block, with question-and-answer cards and a contact link. It depends on Next.js Link, Tailwind theme and container-query utilities, and Tailark's custom Card component with its mixed variant.



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 | 49.0 KB (114.4 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 873ms error during build: [vite]: Rollup failed to resolve import "class-variance-authority" from "<sandbox>re-855301a22682/src/components/ui/card.tsx".
Verdict
Do not adopt it from the registry in its current state: the referenced Tailark card entry is unavailable, so installation stops before compilation or rendering. It needs a shadcn-style setup plus a repaired or vendored Card dependency.
Use it if
- You already use Tailark's Veil card primitive and want a compact FAQ grid.
- Your site is built with Next.js and Tailwind theme tokens compatible with this block.
- You are prepared to vendor or repair the unavailable card dependency before integrating it.
Skip it if
- You need a registry block that installs and builds without repairing upstream references.
- Your project does not use Next.js, Tailwind theme tokens, or shadcn-style component aliases.
- You want collapsible FAQ disclosures rather than answers that are always visible.
- You cannot source and maintain Tailark's custom mixed Card variant yourself.
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 the path alias, Tailwind theme tokens and container-query support, provide a compatible Card component with the mixed variant, and replace Next.js Link when using another router. The missing Tailark card registry item must be supplied locally or corrected upstream.
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