Callout
Callout is part of the Actions and feedback group. Structured message block for info, warning, success, and error content.
Installation
Section titled “Installation”npx bambiui add callout --framework reactnpx bambiui add callout --framework solidnpx bambiui add callout --framework sveltenpx bambiui add callout --framework vueimport { Callout, CalloutIcon, CalloutTitle, CalloutDescription } from "@/components/ui/callout";
export function Example() { return <Callout />;}import { Callout, CalloutIcon, CalloutTitle, CalloutDescription } from "~/components/ui/callout";
export function Example() { return <Callout />;}<script lang="ts"> import { Callout, CalloutIcon, CalloutTitle, CalloutDescription } from "$lib/components/ui/callout";</script>
<Callout /><script setup lang="ts">import { Callout, CalloutIcon, CalloutTitle, CalloutDescription } from "@/components/ui/callout";</script>
<template> <Callout /></template>Preview
Section titled “Preview”
Callout preview should be verified in the target framework after copying the component source. Interactive behavior comes from generated public artifacts, not docs-only mock behavior.
Behavior
Section titled “Behavior”Use when prose needs stronger emphasis than a paragraph.
Generated output uses serializable data-* attributes for state and styling. Controlled components fire bambi:<event-name> events and expect application state to update externally; uncontrolled components manage local source state and still fire events.
Accessibility
Section titled “Accessibility”Use semantic labels, visible focus states, and keyboard interaction patterns appropriate for Callout. Do not hide required instructions in transient UI. Verify focus movement and disabled states in the installed framework output.
Exports
Section titled “Exports”Callout, CalloutIcon, CalloutTitle, CalloutDescriptionTokens
Section titled “Tokens”Customize tokens after installing and previewing the component. Relevant tokens include:
--bambi-danger--bambi-success--bambi-warning--bambi-border