Measured entry
tripled-faq-section-shadcnui
faqminimal-flatmotion on file
A centered FAQ section whose cards reveal one answer at a time, with entrance, chevron, and expand-collapse motion. It ships as a client-side shadcn registry page and depends on React, Framer Motion, Lucide icons, shadcn Card primitives, Tailwind utilities, theme variables, and the usual path alias.



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 | 70.1 KB (135.5 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 5s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/card.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A sound choice for an existing shadcn app: the responsive layout, disclosure controls, and motion work cleanly. It needs a shadcn-style setup, and the hardcoded content plus Framer Motion dependency make it less attractive for a lightweight or reusable FAQ primitive.
Use it if
- You want a single-open FAQ with animated entry and answer transitions.
- Your app already has shadcn Card primitives, Tailwind theme variables, and the standard source alias.
- You are comfortable replacing the hardcoded questions and answers in the component source.
Skip it if
- You need several answers to remain open at once or want a reusable data-driven API without refactoring.
- You are avoiding Framer Motion for a small disclosure section.
- Your non-shadcn stack needs a paste-ready component with no aliases, utility helper, or theme plumbing.
Install
| Declared dependencies | framer-motion, react |
|---|---|
| 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 React, Framer Motion, and Lucide React, then provide compatible Card, CardHeader, and CardContent primitives. Also add the source path alias, the class-name utility used by the Card implementation, Tailwind processing, and matching card, foreground, muted, accent, and background theme variables.
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/moumen-soliman/uitripledAlternatives
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