Once UI Handbook
Beginner Guides
What is Once UI?
Install & config
Page skeleton
Your first page
Build And Launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Vibe Coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Common Patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Design Tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Block updates
Block updates changelog
Agent Resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles
TrademarkTrademark
Ctrl k
Search...
Sign up
Once UI Handbook
Beginner Guides
What is Once UI?
Install & config
Page skeleton
Your first page
Build And Launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Vibe Coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Common Patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Design Tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Block updates
Block updates changelog
Agent Resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles
TrademarkTrademark
Once UIDocumentationBlog
© Once UI. All rights reserved.
Built with Aveiro

Accordion & FAQ

AccordionGroup for FAQ sections, split-column layouts, autoCollapse behavior, and standalone Accordion usage.
Updated 19d ago
Pricing & plans
Media & uploads
4 min · Pattern
AccordionGroup wraps multiple Accordion items with shared borders, dividers, and smart corner radius. Use it for FAQ sections, settings help, and collapsible docs.

What this pattern covers

Grouped collapsible content appears everywhere:
  • Pricing page FAQ at the bottom
  • Product docs with expandable answers
  • Settings panels with help text per section
  • Mobile navigation sub-menus (see MobileMegaMenu in core)
Once UI provides AccordionGroup for multi-item groups and standalone Accordion for one-off collapsible blocks. Gold reference: packages/core/src/components/AccordionGroup.tsx and the pricing example's FAQ section.

Item shape

AccordionGroup takes a plain items array — each entry has title and content:
Field
Type
Notes
`title`ReactNodeQuestion label or section name
`content`ReactNodeAnswer body — usually Text, sometimes a short Column
const faqItems = [
  {
    title: "Can I change plans later?",
    content: (
      <Text onBackground="neutral-weak">
        Yes — upgrade or downgrade anytime from billing settings.
      </Text>
    ),
  },
  {
    title: "Do you offer refunds?",
    content: (
      <Text onBackground="neutral-weak">
        We offer a 14-day money-back guarantee on annual plans.
      </Text>
    ),
  },
];
Keep answers concise. Use Text variant="body-default-s" with onBackground="neutral-weak" for answer body copy.

Basic FAQ section

Wrap the group in a section Column with a heading:
<Column fillWidth maxWidth="m" gap="32">
  <Heading as="h2" variant="display-strong-xs">
    Frequently asked questions
  </Heading>
  {/* AccordionGroup with items={faqItems} */}
</Column>
Pass items={faqItems} to AccordionGroup. The component handles borders, Line dividers between items, and corner radius on the first/last accordion automatically.

autoCollapse behavior

`autoCollapse`
Behavior
`true` (default)Opening one item closes the others — best for FAQ
`false`Each accordion manages its own open state — best for independent settings sections
For marketing FAQ pages, keep the default autoCollapse={true} so the list stays scannable.

Split FAQ layout

On wide screens, split questions into two columns for long FAQ lists:
<Grid columns="2" gap="24" s={{ columns: 1 }}>
  <Column gap="16">
    {/* AccordionGroup with first half of items */}
  </Column>
  <Column gap="16">
    {/* AccordionGroup with second half of items */}
  </Column>
</Grid>
Slice your items array in half. Each column gets its own AccordionGroup so borders and radius render correctly per group.

Size variants

AccordionGroup accepts size — condensed t-shirt sizes (s, m, l):
Size
Use for
`s`Dense settings sidebars, mobile nav
`m` (default)Marketing FAQ, docs pages
`l`Hero-adjacent feature lists with long titles
Match accordion size to surrounding heading scale. FAQ under display-strong-xs headings works well at m.

Standalone collapsible block

For a single collapsible block (not a group), use the standalone accordion component directly. Pass a title string and child content:
Do not wrap a single collapsible item in a group — the group adds outer borders and dividers meant for multiple items.

Write this / not this

✅ Once UI way
❌ Common mistake
AccordionGroup for 2+ related itemsSeparate Accordions with manual borders
`title` + `content` item objectsNesting arbitrary JSX as children of the group
`autoCollapse` for FAQ pagesAll items open simultaneously on marketing pages
Text with `onBackground="neutral-weak"` for answersRaw `<p>` tags with inline color
Split into two groups for two-column FAQOne group stretched across two Grid cells

Check yourself

  • Items array has both title and content on every entry
  • Answer text uses Text component with neutral-weak color
  • autoCollapse matches the UX (true for FAQ, false for independent sections)
  • Section heading above the group, not inside it
  • Two-column layout uses two separate AccordionGroups

Related

→ Pricing & plans → Settings & split panels → Full reference: docs.once-ui.com — AccordionGroup
// Single collapsible block — not wrapped in a group
// title="Advanced options" size="m"
// children: Text with onBackground="neutral-weak"