Callouts
Highlight notes, warnings, success states, and critical guidance without interrupting the flow of a docs page.
Types
Use callouts for information readers should notice before they continue. Pick the type based on the weight of the message, not the visual style you prefer.
Info
Use info for supporting context, constraints, or behavior that explains how a feature works.
API tokens are scoped to a single workspace. Create a separate token for each environment that needs automated access.
Success
Use success to confirm a completed setup step or call out a recommended state.
Your domain is verified. New deployments can now use this domain without additional DNS changes.
Warning
Use warning when the reader can continue, but should understand a risk or dependency first.
Rotating the webhook secret invalidates all existing delivery signatures. Update every consumer before saving the new value.
Danger
Use danger for destructive actions, irreversible changes, or security-sensitive instructions.
Deleting a project permanently removes its deployments, environment variables, and activity history. This action cannot be undone.
Default
Use default for neutral notes that are useful but do not need a severity level.
Configuration changes are applied during the next deployment and do not affect the currently running version.
With Title
Add a title when the callout needs a clear heading or when readers may scan back to it later.
Environment variables
The previous variable names are no longer supported. Replace them before upgrading to the latest version.
With Badge
Use a badge inside a callout when the message needs a short status label.
Rotate the exposed key everywhere.