Accordion part

Settings, help and docs lists where what is open should stand out.

Get Pro to installPro11 blocksReact, Vue and Figma
MCPConnect the MCP server

Open Members in workspace settings, add their email and pick a role. The invite stays valid for seven days.

Roles are editable at any time, and the change applies to every workspace that person belongs to.

Their seat frees up straight away, and anything they own is handed back to the workspace owner.

Directory sync is on the Enterprise plan.

Receipts go to the billing contact on the day the invoice clears, with the PDF attached and a link to the full history in Settings.

billing@studio.co

Sign-in follows the verified address on the account. Changing it sends a confirmation to both the old and the new inbox.

ava@studio.co

After two failed deliveries we fall back to the backup address and flag the account, so nobody loses an invoice.

ops@studio.co

Name it after the team, not the project: everything else hangs off it. You can rename it later without breaking links, and the URL follows along.

Paste a list of emails and pick one role for the whole batch. Anyone who hasn’t accepted after seven days gets a single reminder, then the invite lapses.

Figma, GitHub and Slack take a minute each. Every connection is scoped to this workspace, so removing one never touches the others.

Decide who can invite, who can publish and where exports may go. The defaults are the safe ones; loosen them as the team settles in.

Orvain ships React and Vue from the same tokens. Add the one your app uses, plus the tokens.

pnpm add @orvain/react @orvain/tokens

Import @orvain/tokens/dist/tokens.css at the root of the app. Every component reads its colours, radii and type from these variables.

Dark mode is opt-in. Set data-theme="dark" on the root, or data-theme="system" to follow the operating system.

Every export is written to the workspace drive first, then mirrored to whichever destination you connected. The copy on the drive is kept for thirty days, so a failed transfer never loses the file.

Nightly, weekly and monthly runs are all available, and each one can point at a different destination with its own retention window.

CSV and JSON for records, PDF for anything rendered. Large exports are split into parts and listed together under one job.

Attachment export is on the Enterprise plan.

More in Accordion blocks#

FAQ page

Knowledge bases and help centres: search, topics and answers on one page

FAQ chapters

Long help centres: topics as chapters of one page, with a rail that follows you

Settings sections

Account and workspace panels: grouped settings that fold away

Settings draft

Workspace settings that affect everyone: nothing applies until you save

Bordered items

Sidebars and narrow columns: a boxed row per question

Numbered items

Onboarding and setup guides: ordered steps that open in place

Split cards

Docs and changelogs: each step reads as its own card

Badge items

Account settings: a status per row and a value worth copying

Minimal items

Long-form pages: questions with nothing around them but the answer

Accordion part

Settings, help and docs lists where what is open should stand out

Accordion rail

Step-by-step guides and lists that should read as a sequence

When to use#

  • A page of independent questions where each reader has come for exactly one of them.
  • Settings grouped into sections, worked on one section at a time.
  • An ordered guide whose steps stay visible as a list while one of them is being read.
  • Reference rows that are mostly a value, where only some of them need explaining.

The whole set, with its codePro

Pro opens the Code tab on every block here, in React and Vue, plus the Figma file and the MCP server for your editor.