mirror of
https://github.com/mintlify/docs.git
synced 2026-09-14 13:35:46 +08:00
Ethan Palm
6c53a28e3a
* 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>
37 lines
1.6 KiB
Plaintext
37 lines
1.6 KiB
Plaintext
---
|
|
title: "Tooltips"
|
|
description: "Add tooltips to display contextual definitions and explanations when users hover over terms, abbreviations, or technical concepts in your documentation."
|
|
keywords: ["tooltips", "hover help", "contextual information", "explanatory", "definitions"]
|
|
boost: 3
|
|
---
|
|
|
|
Use tooltips to provide additional context or definitions when a user hovers over a string of text. Tooltips can include optional call-to-action links.
|
|
|
|
**Example**: <Tooltip headline="API" tip="Application Programming Interface: a set of protocols for software applications to communicate." cta="Read our API guide" href="/api-reference">API</Tooltip> documentation helps developers understand how to integrate with your service.
|
|
|
|
```mdx Tooltip example wrap
|
|
<Tooltip headline="API" tip="Application Programming Interface: a set of protocols for software applications to communicate." cta="Read our API guide" href="/api-reference">API</Tooltip> documentation helps developers understand how to integrate with your service.
|
|
```
|
|
|
|
## Properties
|
|
|
|
<ResponseField name="tip" type="string" required>
|
|
The text displayed in the tooltip.
|
|
</ResponseField>
|
|
|
|
<ResponseField name="headline" type="string">
|
|
Text displayed before the `tip` text.
|
|
</ResponseField>
|
|
|
|
<ResponseField name="cta" type="string">
|
|
The call-to-action text for a link within the tooltip.
|
|
</ResponseField>
|
|
|
|
<ResponseField name="href" type="string">
|
|
URL for the call-to-action link. Required when using `cta`.
|
|
</ResponseField>
|
|
|
|
<ResponseField name="className" type="string">
|
|
Additional CSS classes to apply to the tooltip trigger.
|
|
</ResponseField>
|