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.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of tripled-faq-section-shadcnui at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-faq-section-shadcnui at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-faq-section-shadcnui 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 tripled-faq-section-shadcnui
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal70.1 KB (135.5 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 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

Installation record for tripled-faq-section-shadcnui
Declared dependenciesframer-motion, react
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 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.

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.