{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "accordion-16",
  "type": "registry:component",
  "title": "Accordion 16",
  "description": "Accordion 16. A vertically stacked set of interactive headings that each reveal a section of content.",
  "dependencies": [
    "lucide-react"
  ],
  "registryDependencies": [
    "accordion",
    "collapsible"
  ],
  "files": [
    {
      "path": "components/watermelon/accordion-16.tsx",
      "type": "registry:component",
      "content": "import { ChevronDownIcon } from 'lucide-react'\n\nimport { Accordion, AccordionContent, AccordionItem, AccordionTrigger } from '@/components/base-ui/accordion'\nimport { Collapsible, CollapsibleContent, CollapsibleTrigger } from '@/components/base-ui/collapsible'\n\ntype FaqItem = {\n  title: string\n  content: string\n  open?: boolean\n}\n\ntype AccordionCategory = {\n  value: string\n  category: string\n  faqs: readonly FaqItem[]\n}\n\nconst items: readonly AccordionCategory[] = [\n  {\n    value: 'item-1',\n    category: 'Campaign Planning',\n    faqs: [\n      {\n        title: 'Why do campaign launches miss their original dates?',\n        content:\n          'Launches usually slip when approvals, asset production, and messaging changes happen in parallel without one shared timeline. Campaign planning works better when teams can see dependencies before launch week arrives.',\n        open: true\n      },\n      {\n        title: 'How detailed should a campaign brief be?',\n        content:\n          'A useful brief should clarify audience, objective, core message, and success criteria without becoming too long to revisit. The best briefs guide decisions instead of documenting everything.'\n      },\n      {\n        title: 'What helps teams align on launch priorities?',\n        content:\n          'Priorities become clearer when every activity is tied to a measurable objective. That makes it easier to decide what is essential for launch and what can wait.'\n      }\n    ] as const\n  },\n  {\n    value: 'item-2',\n    category: 'Content Workflow',\n    faqs: [\n      {\n        title: 'Why do content reviews take longer than expected?',\n        content:\n          'Content reviews slow down when feedback is spread across separate docs, messages, and presentations. Teams move faster when edits, comments, and approvals happen in one workflow.',\n        open: true\n      },\n      {\n        title: 'How do we avoid duplicate content requests?',\n        content:\n          'Duplicate requests usually happen when briefs are not visible across teams. Shared intake and clear ownership reduce overlap and make planning easier.'\n      },\n      {\n        title: 'What makes handoff to design smoother?',\n        content:\n          'Handoffs improve when narrative, hierarchy, and usage context are already clear before design begins. That reduces revision loops and keeps execution focused.'\n      }\n    ] as const\n  },\n  {\n    value: 'item-3',\n    category: 'Performance Tracking',\n    faqs: [\n      {\n        title: 'Why do teams struggle to interpret campaign results?',\n        content:\n          'Results feel harder to interpret when traffic, conversion, and retention metrics live in different dashboards. Better reporting connects outcomes back to the campaign goal that mattered most.',\n        open: true\n      },\n      {\n        title: 'How often should reporting be shared?',\n        content:\n          'Reporting should be frequent enough to catch problems early, but not so frequent that teams are reacting to noise. A simple weekly rhythm is often easier to sustain.'\n      },\n      {\n        title: 'What makes insights more actionable?',\n        content:\n          'Insights are more useful when they lead to a specific next step. Reporting should make it obvious what to continue, what to adjust, and what to stop.'\n      }\n    ] as const\n  }\n] as const\n\nconst Accordion16 = () => {\n  return (\n    <Accordion className='w-full rounded-xl border border-border/80' type=\"multiple\" defaultValue={[items[0].value]}>\n      {items.map((item) => {\n        return (\n          <AccordionItem\n            key={item.value}\n            value={item.value}\n            className='first:rounded-t-xl last:rounded-b-xl'\n          >\n            <AccordionTrigger className='items-center px-5 py-4 hover:no-underline focus-visible:ring-0'>\n              <span>{item.category}</span>\n            </AccordionTrigger>\n\n            <AccordionContent className='pb-0'>\n              {item.faqs.map((faq) => (\n                <Collapsible\n                  key={faq.title}\n                  className='border-t border-border/70 px-6 transition-colors has-[button[aria-expanded=true]]:bg-neutral-200/60 dark:has-[button[aria-expanded=true]]:bg-neutral-800'\n                  defaultOpen={faq.open}\n                >\n                  <CollapsibleTrigger className='group/collapsible focus-visible:ring-ring/50 flex w-full items-center justify-between gap-3 py-4 text-left text-sm font-medium outline-none hover:no-underline focus-visible:ring-[3px]'>\n                    <span>{faq.title}</span>\n                    <ChevronDownIcon className='invisible size-4 shrink-0 text-muted-foreground group-data-[state=open]/collapsible:visible' />\n                  </CollapsibleTrigger>\n                  <CollapsibleContent className='overflow-hidden pb-4 text-sm leading-6 text-muted-foreground'>\n                    {faq.content}\n                  </CollapsibleContent>\n                </Collapsible>\n              ))}\n            </AccordionContent>\n          </AccordionItem>\n        )\n      })}\n    </Accordion>\n  )\n}\n\nexport default Accordion16\n"
    }
  ]
}
