Callouts
Callouts let you set important information apart from the rest of a document without breaking the reading flow. A tip, a warning, an open question, or a worked example can get its own colored, labeled box so a reader can scan a page and immediately spot what needs their attention. Zelares currently supports contiguous callouts, case-insensitive types and aliases, custom titles, explicit +/- fold state, nested block ownership, and fallback styling. The body remains bounded by the supported Markdown ownership contract.
Creating a callout
Add [!type] to the first line of a blockquote, where type is one of the supported callout types. Every line below it that starts with > becomes the body of the callout, and the body supports standard Markdown such as links and headings. Zelares-specific links and embeds inside a callout follow the current supported syntax, not the full target parity contract.
> [!tip] Here's a callout title
> Here's a callout body. It supports **Markdown** and [links](/help/editor/markdown).You don't need to remember the syntax to add one. Open Insert from the context menu and choose Callout to drop in a default callout with the cursor already placed on the title. To wrap content you've already written, a paragraph, a list, even a code block, select it first and run the same Insert, then Callout action; the selection is enclosed automatically. Once a callout exists, right-click its title to change its type without retyping anything.
Changing the title
A callout's title defaults to its type name. Add your own text right after the type identifier to override it, or leave the body empty entirely to create a title-only callout, useful for short labels that don't need supporting text.
> [!warning] Don't skip this step
> Deleting a project removes it for every collaborator.
> [!todo] Follow up with designFoldable callouts
Add + to an expanded callout or - to a collapsed callout. The editor exposes that state through an accessible fold control; changing it updates the preview without rewriting the callout source.
> [!faq]- Are callouts foldable?
> Yes. In a foldable callout, the body is hidden until it's expanded.Nested callouts
Add an extra > for each nested level. The editor gives nested callouts independent ownership and fold controls while preserving the surrounding source structure.
> [!question] Can callouts be nested?
> > [!todo] Yes, they can.
> > > [!example] You can even stack multiple levels.Nested callouts remain within the bounded editor contract: broader downstream rendering parity and unusual mixed block structures may differ outside the editor preview.
Callout types
Every type below renders with its own accent color and heading color. Types listed together share a color, so pick whichever name reads best in context, tip and hint, for example, look identical.
| Color | Types |
|---|---|
| Blue | note, info, abstract, summary, tldr |
| Yellow | tip, hint, important, warning, caution, attention, todo |
| Green | success, check, done |
| Red | danger, error, bug, failure, fail, missing |
| Purple | question, help, faq |
| Violet | example |
| Gray | quote, cite |
Type names are case-insensitive, and any type Zelares doesn't recognize falls back to the default note styling, so a typo in a type identifier won't break the callout, it will just lose its custom color.
Context menu support
- Use Insert, then Callout to add a note callout.
- Select text first to wrap the selected lines in a callout.
- Right-click inside a callout to edit it, change its type, or remove the callout wrapper.
Related pages
Callouts are built on top of the editor's standard Blockquotes. For the full range of insert and formatting actions, see Context Menu. For a full overview of supported Markdown formatting, see Syntax.