Measured entry

tripled-faq-accordion-block-shadcnui

faqminimal-flatmotion on file

A client-side FAQ section with an animated, single-open-item accordion and a support callout. It ships as a shadcn registry block with its sample content inline, and depends on React, Framer Motion, Lucide icons, Tailwind theme tokens, and shadcn Badge, Button, and Card primitives.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of tripled-faq-accordion-block-shadcnui at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-faq-accordion-block-shadcnui at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-faq-accordion-block-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-accordion-block-shadcnui
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal73.1 KB (138.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 4s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/button.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A polished, working block for teams already committed to the same UI stack, but heavier and less reusable than a basic FAQ needs to be. It needs a shadcn-style setup; the bare project fails because the copied Button expects the shared utility module.

Use it if

  • Your product needs a ready-made FAQ section with one answer visible at a time and a support callout below it.
  • Your app already uses shadcn primitives, Tailwind theme tokens, Lucide icons, and Framer Motion.
  • You are comfortable replacing inline sample questions and wiring the callout buttons yourself.

Skip it if

  • Your FAQ content must come from a CMS or localization files without refactoring the component API.
  • You need disclosure controls that expose expanded state and panel relationships to assistive technology out of the box.
  • You are minimizing client-side JavaScript for a simple content section or do not otherwise use Framer Motion.
  • Your motion policy requires reduced-motion behavior without additional implementation.

Install

Installation record for tripled-faq-accordion-block-shadcnui
Declared dependenciesframer-motion, react, radix-ui
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 Tailwind and the expected theme variables, configure the at-sign import alias, provide the shared class-name utility module, and install or recreate the Badge, Button, and Card primitives. Also add React, Framer Motion, Lucide React, and any Radix packages used by those primitives.

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.