vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-veil-faqs-2

faqminimal-flat

A client-side FAQ section with a sticky heading, a single-open collapsible question list, and a contact link. It ships as a shadcn registry block for Next.js, imports Next Link, expects Tailwind theme and container utilities, and relies on Tailark's accordion registry component.

Specimen
Harness screenshot of tailark-veil-faqs-2 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-faqs-2 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-veil-faqs-2 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-2
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal57.8 KB (123.2 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 1.07s
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-accordion" from "<sandbox>re-088fe2f358c4/src/components/ui/accordion.tsx".

Verdict

A sensible FAQ layout, but the published registry chain is currently broken because the Tailark accordion dependency returns a missing-resource response. It needs a shadcn-style setup plus manual dependency repair, so teams expecting a clean registry install should avoid it for now.

Use it if

  • You want a compact FAQ section with one answer open at a time.
  • Your Next.js app already uses Tailwind theme tokens and container queries.
  • You are comfortable supplying the accordion component manually while the registry dependency is unavailable.

Skip it if

  • You need an installable registry block today; its accordion dependency resolves to a missing shadcn registry URL.
  • Your project does not use Next.js or its Link component and you do not want to adapt the import.
  • You need several answers expanded at once or externally controlled accordion state.

Install

Installation record for tailark-veil-faqs-2
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

In a non-shadcn project, add a compatible accordion with the same component API, provide the imported path alias, Tailwind theme tokens, container-query utilities, and client-side React support. Add Next Link or replace it with your router's link component. The broken Tailark registry dependency must be bypassed 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/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.