`::accordion` around
[`::accordion-item`](/reference/mdc-components/accordion-item) blocks.

## Usage

::preview
::::accordion
:::accordion-item{label="Does a consumer write content.config.ts?" icon="lucide:file-question"}
No. `duxt.sources` in `app.config.ts` is the only declaration; the layer's own
`content.config.ts` reads it.
:::

:::accordion-item{label="Is a native SQLite driver needed?" icon="lucide:database"}
No. The database is read through `node:sqlite`, which is why the build needs
Node 24.
:::
::::

#code
```mdc
:::accordion
  ::accordion-item{label="Does a consumer write content.config.ts?" icon="lucide:file-question"}
  No. `duxt.sources` in `app.config.ts` is the only declaration.
  ::
:::
```
::

## API

No props.

### Slots

| Slot      | What goes in it          |
| :-------- | :----------------------- |
| `default` | `::accordion-item` blocks |

## Notes

`type="multiple"` on purpose: a FAQ where opening one answer closes the one you
were half-way through is a worse FAQ.

On reka-ui's primitives, like the tree and the tabs, for the same reason — a
hand-rolled disclosure has no keyboard handling, no `aria-expanded` and no
relationship between the trigger and the region it opens.