Marketing
FAQ accordion
A full marketing page section, not an atomic control - an animated question/answer accordion (motion/react) plus a 'still have questions?' avatar CTA. Composed entirely from real DEW components.
What lives in this section
Pre-built landing-page sections - hero, FAQ, pricing, and similar - as opposed to components/base/**/components/application/**'s atomic controls. A marketing section takes no configuration props (its copy and layout are fixed), so unlike a component page there's no live Playground here - just the real section, rendered, plus how it's composed.
Live example
Click a question to expand it - the height/opacity transition is a real spring animation (motion/react), not a CSS transition.
Composition
Every real control inside this section is a real DEW component, not a lookalike:
- Accordion (
components/base/accordion/accordion.tsx) - the question/answer list itself. Extracted out of this section into its own component rather than hand-rolling expand/collapse state locally - this section just maps its FAQ data intoAccordionItemType[]and renders<Accordion items={...} />. Avatar(components/base/avatar/avatar.tsx) - the three support-contact photos in the "Still have questions?" card.Avatar's owncountprop, which wires inAvatarCount(components/base/avatar/base-components/avatar-count.tsx) - the small red corner badge on the last avatar. It's a notification-style badge, not a "+N" overflow indicator, so it reads as "3 new replies" rather than a headcount - the honest use for what that component actually renders.Button(components/base/buttons/button.tsx) - the "Get in touch" CTA.
Only the FAQ copy, the heading/intro, and the "Still have questions?" CTA card are local to this section - everything interactive is a real, independently-documented component.
Usage
import { FAQAccordion01 } from "@/components/marketing/faq/faq-accordion-01";
<FAQAccordion01 />No props - questions/answers and the CTA copy are fixed content in the component itself.
Figma
No linked Figma file yet - this component was pulled in via the Untitled UI CLI, not designed in Figma first.