Document editor

Callout syntax

`> [!note]` form. Supports note / tip / warning / danger / success.

What is a callout

A callout is a semantic upgrade of the blockquote (>) — declare a type on the first line with [!type] and the renderer turns it into a colored, icon-prefixed box. Visually louder than a plain quote, great for risks, TODOs, key takeaways.

Kition’s callout syntax is fully compatible with Obsidian and GitHub Flavored Markdown — the same content roundtrips across all three.

Basic syntax

markdown

> [!NOTE] Title (optional)
> First line of content
> Second line of content

> [!WARNING]
> Heads up: this is a warning callout

> [!SUCCESS] Done
> Operation succeeded

Available types

note — blue default, neutral info
tip — green, best practices or hard-won lessons
warning — yellow, careful but not fatal
danger — red, irreversible or destructive
success — green, confirms something landed
important — purple, key takeaway (GFM-compatible alias)

Advanced usage

Callouts fold — add + after the type for default-open, - for default-closed. Useful for long checklists you want collapsed by default and one-click expanded.

The body accepts full Markdown — lists, code blocks, tables, wikilinks, even nested callouts work.

markdown

> [!TIP]- Collapsed by default: click to see the full command
> ```bash
> kition export --format pdf --style academic
> ```

> [!DANGER] The drop-the-database trio
> 1. Back up `vault/Tables/*.kitable`
> 2. Turn off sync
> 3. Then delete the files
>
> Get this step wrong and there's no recovery.

When to use what

Tutorials: use warning for "watch out" steps, tip for best practices
RFCs: use danger for risk sections, success for acceptance criteria
Meeting notes: important for decisions, note for open questions
Don’t over-use danger — colors lose meaning when everything is red

Markdown basics

Headings, lists, bold, links, code — Markdown core in three minutes.