What is the standard syntax for creating a callout in Markdown?

Begin a blockquote with `>` and place an archetype tag on the first line inside square brackets (`> [!NOTE]`). The subsequent lines prefixed with `>` form the body of the callout.

What standard callout types are supported in Obsidian and Oyma?

Standard types include NOTE, TIP, IMPORTANT, WARNING, CAUTION, INFO, todo, SUCCESS, QUESTION, FAILURE, DANGER, BUG, and EXAMPLE. Each type features a dedicated accent color and icon.

How do I make a callout collapsible in Markdown?

Append a plus sign (`+`) or minus sign (`-`) immediately after the callout identifier: `> [!NOTE]+` creates an expandable callout that defaults to open; `> [!NOTE]-` creates a collapsible callout that defaults to closed.

Can I customize the title text of a callout?

Yes. Add your custom title on the first line following the callout identifier: `> [!WARNING] Production Migration Warning`. The custom title replaces the default 'Warning' label.

Markdown Callouts: Syntax & Admonitions Guide

Primary SyntaxObsidian Flavored Markdown

> [!NOTE]
> Useful context and informational background.

> [!WARNING]
> Critical operational caveat.

Callouts—also known as admonitions, alert boxes, or notification banners—allow writers to set critical context, operational warnings, best practice tips, and technical caveats apart from standard body text.

Popularized by Obsidian, adopted by GitHub Flavored Markdown, and natively rendered in Oyma, callout syntax builds upon standard blockquote syntax (>) with zero proprietary HTML tags, maintaining clean readability even in raw plain text.

Basic callout syntax

A callout is defined by placing a bracketed identifier on the first line of a blockquote:

> [!NOTE]
> This is an informational note highlighting background context.

In the rendered view, this outputs a styled container card featuring a subtle background tint, a left border highlight, an informational icon, and the title “Note”.

Custom callout titles

You can replace the default title by adding custom text directly after the bracketed type:

> [!NOTE] Architecture Context
> The local Whisper pipeline operates 100% on Apple Silicon Neural Engine.

Standard callout types and archetypes

Oyma and Obsidian support a comprehensive palette of semantic callout types, each styled with an appropriate color token and icon:

Informational and general callouts

> [!NOTE]
> Standard neutral informational note with a blue accent.

> [!INFO]
> Informational callout for additional background.

> [!TIP]
> Actionable tip, shortcut, or efficiency recommendation with a green accent.

Warning and caution callouts

> [!WARNING]
> Operational warning regarding potential pitfalls or breaking changes.

> [!CAUTION]
> High-risk warning signaling actions that could cause data loss or security issues.

> [!DANGER]
> Urgent alert regarding destructive commands or service outages.

Status, checklist, and success callouts

> [!SUCCESS]
> Positive outcome or successfully verified milestone.

> [!QUESTION]
> Open inquiry, research question, or unresolved team discussion.

> [!FAILURE]
> Documented test failure or broken prerequisite.

> [!BUG]
> Known software defect or tracked issue.

> [!EXAMPLE]
> Code sample, case study, or scenario walkthrough.

> [!QUOTE]
> Styled quotation card with quotation mark glyph.

Collapsible callouts (Foldable)

When writing extensive documentation or lengthy technical logs, callouts can be made collapsible to conserve vertical screen space:

Default open: `[!TYPE]+`

> [!NOTE]+ Click to collapse
> This callout defaults to an expanded state, but the reader can click
> the header to collapse it.

Default closed: `[!TYPE]-`

> [!INFO]- Detailed Raw Egress Packet Logs (Click to expand)
> ```json
> {
>   "timestamp": "2026-10-09T14:22:00Z",
>   "bytes_sent": 0,
>   "local_only": true
> }
> ```

In Oyma, collapsible callouts include smooth disclosure triangle animations.

Embedding rich content in callouts

Because callouts are built on top of CommonMark blockquotes, they can contain any other Markdown element:

> [!TIP] Keyboard Shortcuts
> - Press `⌘O` to open the Command Palette.
> - Press `⌘D` to jump to today's Daily Note.
>
> | Action | Shortcut |
> | :--- | :--- |
> | Search Vault | `⌘F` |
> | Toggle Task | `⌘Enter` |

Callouts in Oyma on macOS

In Oyma:

Callouts render as native macOS cards using system design tokens (--surface, --line, --accent, --ok).
The syntax conceals the leading > symbols, displaying a clean visual box.
Clicking any part of the callout header toggles collapsible states.
On disk, your notes remain standard plain-text Markdown fully compatible with Obsidian and GitHub.

Frequently asked questions

What is the standard syntax for creating a callout in Markdown?: Begin a blockquote with `>` and place an archetype tag on the first line inside square brackets (`> [!NOTE]`). The subsequent lines prefixed with `>` form the body of the callout.
What standard callout types are supported in Obsidian and Oyma?: Standard types include NOTE, TIP, IMPORTANT, WARNING, CAUTION, INFO, todo, SUCCESS, QUESTION, FAILURE, DANGER, BUG, and EXAMPLE. Each type features a dedicated accent color and icon.
How do I make a callout collapsible in Markdown?: Append a plus sign (`+`) or minus sign (`-`) immediately after the callout identifier: `> [!NOTE]+` creates an expandable callout that defaults to open; `> [!NOTE]-` creates a collapsible callout that defaults to closed.
Can I customize the title text of a callout?: Yes. Add your custom title on the first line following the callout identifier: `> [!WARNING] Production Migration Warning`. The custom title replaces the default 'Warning' label.