Measured entry

tailark-veil-faqs-4

faqminimal-flat

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.

Specimen
Harness screenshot of tailark-veil-faqs-4 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-faqs-4 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-faqs-4 at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

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.

Harness measurements recorded for tailark-veil-faqs-4
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious1
Axe moderate0
Axe minor0
Gzip marginal49.0 KB (114.4 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten 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

Installation record for tailark-veil-faqs-4
Declared dependenciesclsx, tailwind-merge
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno 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/blocks
License
MIT
Record published
2026-08-15

Alternatives

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.