Measured entry
efferd-faqs-4
faqminimal-flatmotion on file
A client-side React FAQ section that filters hardcoded questions by topic and reveals answers in a single-open accordion. It ships as a shadcn registry block styled with Tailwind utilities and relies on shadcn Button and Accordion primitives, Lucide icons, React state, and the shared cn utility.



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 | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 41.4 KB (106.8 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 1m 25s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/faqs/4/faqs-section.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A sound pick for a categorized support page: it builds, mounts, adapts cleanly across the tested layouts, and keeps the interaction understandable. It needs a shadcn-style setup, so teams outside that stack should expect integration work rather than a drop-in component.
Use it if
- Your help page has enough questions to benefit from topic filters.
- Your product already uses shadcn components, Tailwind theme tokens, and Lucide icons.
- You want a responsive sidebar-to-wrapped-filter layout with collapsible answers.
Skip it if
- Your FAQ is short enough that category controls would add needless navigation.
- Questions must come from a CMS or API and you do not want to adapt the hardcoded data model.
- Your design system does not use shadcn primitives or Tailwind utility classes.
- You need search, deep links to answers, or multiple answers open at once.
Install
| Declared dependencies | radix-ui |
|---|---|
| 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 |
In a non-shadcn project, add compatible Accordion and Button primitives backed by Radix, a cn class-merging helper, Tailwind utilities and the expected theme tokens, plus Lucide React icons. Preserve the client-component boundary and map the alias imports to your project structure.
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-uiAlternatives
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