vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-veil-faqs-1

faqminimal-flat

A client-side FAQ section shipped as a Tailark shadcn registry block. Its TSX renders fixed question data inside single-open, collapsible accordion rows, with a support link below. It depends on Next.js Link, Tailwind and theme tokens, path aliases, and Tailark Card and Accordion registry components.

Specimen
Harness screenshot of tailark-veil-faqs-1 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-faqs-1 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-faqs-1 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-1
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal58.4 KB (123.8 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 975ms
error during build:
[vite]: Rollup failed to resolve import "class-variance-authority" from "<sandbox>re-bd3acd55338f/src/components/ui/card.tsx".

Verdict

Do not adopt it unchanged: installation and build fail because the Tailark Card registry dependency resolves to a missing resource. It also needs a shadcn-style setup. Teams unwilling to vendor or repair that dependency should avoid it.

Use it if

  • You already use the Tailark registry and can repair or supply its Card dependency.
  • You want a compact FAQ section with one answer open at a time.
  • Your app already provides Next.js routing, Tailwind utilities, and shadcn-compatible theme tokens.

Skip it if

  • You need a registry block that installs and builds without repairing an upstream dependency.
  • Your project is not based on Next.js or does not use alias-resolved UI components.
  • You need FAQ content driven by props, a CMS, or structured data without modifying the source.

Install

Installation record for tailark-veil-faqs-1
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 Tailwind and matching theme tokens, configure the component path alias, provide compatible Card and Accordion implementations, support client components and Next.js Link, and vendor or repair the unavailable Tailark Card registry item.

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.