* 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>
* docs: boost search ranking for single-word title pages
Apply `boost: 3` to English pages whose H1 / frontmatter title is a single word (e.g. "Assistant", "Quickstart", "Cards"). Short titles tend to be canonical landing pages for a topic, so users searching the exact term should land on them first.
* docs: drop boost on websocket-playground stub to keep canonical Playground ranking
`api-playground/websocket-playground.mdx` is an auto-generated AsyncAPI stub with no body content but shares the title "Playground" with `api-playground/overview.mdx`. Boosting both equally diluted the canonical overview page in search for the query "playground". Drop the boost on the stub.
* Clarify that view component should be used once per page.
Customers were creating multiple view components on the same page, causing duplicate menu items. The component is designed to be used once per page since the multi-view dropdown is shared across the entire page.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
* add tip
---------
Co-authored-by: Claude <noreply@anthropic.com>
mintlify[bot]