Files
Ethan Palm 6c53a28e3a Document className and Tailwind arbitrary value support (#7301)
* Document className and Tailwind arbitrary value support

All built-in components now accept a className prop (mint#10540), and
dynamic Tailwind utilities work in className on MDX components
(mint#6737). Two pages stated the opposite.

- Correct the claims that Tailwind arbitrary values are unsupported in
  customize/custom-scripts and guides/custom-layouts
- Add className and arbitrary value guidance to the Tailwind section of
  custom-scripts, including the runtime-class limitation and the Tab
  content-panel caveat
- Add a Style components section to the components overview
- Add className property rows to every component reference page that
  supports it, and note the three components that do not
- Document inline Markdown support in component title props
- Correct the callouts page, which said typed callouts accept only
  children
- Replace inline style resizing with Tailwind classes in image embeds
- Add a help center article for Tailwind classes not applying in the
  editor's live preview, and note the limitation in custom-layouts
- Point skill.md at className before custom.css
- Accept className, keyframes, and unstyled in the Vale vocabulary

Resolves DOC-316, DOC-317

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Apply batched suggestions from code review

Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>

* Apply batched suggestions from code review

Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-08 16:54:20 -07:00

29 lines
1.0 KiB
Plaintext

---
title: "Panel"
description: "Customize the right side panel content on documentation pages to display supplementary information, examples, or navigation elements."
keywords: ["sidebar"]
boost: 3
---
You can use the `<Panel>` component to customize the right side panel of a page with any components that you want.
If a page has a `<Panel>` component, any [RequestExample](/components/examples#requestexample) and [ResponseExample](/components/examples#responseexample) components must be inside `<Panel>`.
The components in a `<Panel>` replace a page's table of contents. Page modes that suppress the table of contents (`mode: "wide"`, `mode: "center"`, and `mode: "custom"`) also suppress the `<Panel>` component.
````mdx
<Panel>
<Info>Pin info to the side panel. Or add any other component.</Info>
</Panel>
````
<Panel>
<Info>Pin info to the side panel. Or add any other component.</Info>
</Panel>
## Properties
<ResponseField name="className" type="string">
Additional CSS classes to apply to the panel container.
</ResponseField>