Disclosure group

Stack expandable sections for FAQs, setup notes, and optional details that should stay available without crowding the page.

Usage

Use a disclosure group when related answers should be easy to scan, but only one or two details are needed at a time. Each disclosure needs a stable id, a trigger, and a panel.

Usage is calculated per workspace at the end of each billing period. Seats, storage, and deployment minutes are grouped into a single invoice.

<DisclosureGroup>
  <Disclosure id="billing">
    <DisclosureTrigger>How is usage billed?</DisclosureTrigger>
    <DisclosurePanel>
      Usage is calculated per workspace at the end of each billing period.
    </DisclosurePanel>
  </Disclosure>
 
  <Disclosure id="limits">
    <DisclosureTrigger>Can I set spending limits?</DisclosureTrigger>
    <DisclosurePanel>
      Add a monthly limit from workspace settings to pause new deployments when the limit is reached.
    </DisclosurePanel>
  </Disclosure>
</DisclosureGroup>

When to use

Disclosure groups work best for short supporting answers, troubleshooting steps, and configuration details that do not need to be visible all the time.

Keep panel content focused. If an answer needs headings, tables, or multiple code samples, it should probably be its own section instead.

Writing tips

Use trigger text that reads like a question or clear task. Avoid vague labels such as "More details" because readers cannot tell what they will reveal.

Was this page helpful?