> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-accordion.md).
# AX - Accordion
## Overview
**AX - Accordion** is an Experience Cloud component that organizes content into collapsible sections on Experience Sites pages, letting users expand and collapse sections to focus on what they need.
Use it to present FAQs, detailed product information, help documentation, or any content that's easier to navigate when broken into expandable sections. Users can open multiple sections at once or configure it so only one section stays open at a time.
Perfect for knowledge bases, self-service help content, lengthy forms, or anywhere portal users need to scan and selectively view information without scrolling through everything.
## Configuration
The Accordion is a container: drop [AX - Accordion Section](/experience-cloud/experience-components/ax-accordion-section.md) components inside it, one per collapsible section.
### Properties
With the Accordion component settings, you can define to **`Allow Multiple Sections Open`**. When you turn on this setting, opening one Avonni Accordion won't close any other open Avonni Accordions.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-accordion.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
