vibecodng.com

Free MCP betaIndex and tools live

Measured entry

efferd-faqs-5

faqminimal-flatmotion on file

A client-side React FAQ section shipped as a copy-in shadcn registry block. It combines category filters, text search, a single-open accordion, an empty state, and a contact prompt around static in-file content. It depends on shadcn UI primitives, Radix UI, Lucide icons, Tailwind theme classes, the usual path alias, and a cn utility.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of efferd-faqs-5 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-faqs-5 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-faqs-5 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 efferd-faqs-5
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate1
Axe minor0
Gzip marginal42.9 KB (108.3 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 1m 21s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/faqs/5/faqs-section.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A practical fit for an established shadcn codebase that needs more navigation than a basic FAQ. It builds, mounts, and adapts across the tested layouts, but it needs a shadcn-style setup and its heading hierarchy should be corrected before release. The static copy and placeholder link also make it a starting point, not a finished drop-in.

Use it if

  • You want searchable, categorized FAQs rather than a plain accordion list.
  • Your app already uses shadcn UI conventions and compatible theme tokens.
  • You are comfortable replacing the bundled copy and placeholder contact link with product content.

Skip it if

  • Your FAQ content comes from a CMS and you do not want to refactor the embedded data model.
  • You need the component to drop into a bare React project without shadcn plumbing.
  • Your accessibility bar requires a clean audit before adoption, since the rendered example has a heading-order issue.
  • Your bundle budget is tight and the added UI dependency footprint is not justified by search and filtering.

Install

Installation record for efferd-faqs-5
Declared dependenciesradix-ui
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

For a non-shadcn project, add client-side React support, Tailwind utilities and matching design tokens, the path alias, and a cn class-merging helper. Provide compatible accordion, button, input-group, and empty-state primitives, plus Radix UI and Lucide icons, or rewrite those imports against your own component system.

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/shabanhr/efferd-ui
License
MIT
Record published
2026-08-14

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.