Markdown Blockquotes: Syntax, Nesting & Citations

> Single blockquote
>
> > Nested blockquote

Blockquotes are an essential compositional tool in writing and documentation. Originating in early email clients to quote previous message threads, blockquotes in Markdown designate external citations, verbatim interview transcripts, customer testimonials, and highlighted excerpts.

In CommonMark and modern knowledge management tools like Oyma, blockquotes also serve as the structural foundation for modern visual callout boxes and alert banners.

Basic blockquote syntax

To create a blockquote in Markdown, begin the line with a greater-than character (>), followed by an optional space and your text:

> Simplicity is a prerequisite for reliability.
> — Edsger W. Dijkstra

This compiles directly to the HTML <blockquote> element, rendering an indented text block typically accented by a subtle vertical border along the left margin.

Lazy continuation vs explicit quoting

CommonMark allows “lazy continuation,” where lines belonging to the same paragraph do not strictly require a leading >:

> This is the first line of a long quotation that spans multiple lines
and continues onto this second line without a leading greater-than marker.

Recommended best practice: Always prefix every line with >:

> This is the first line of a long quotation that spans multiple lines
> and continues onto this second line with clear visual boundaries.

Explicit prefixing ensures your text remains instantly recognizable as a quote when opened in raw terminal editors, Git diffs, or plain text viewers.

Multi-paragraph blockquotes

To write multi-paragraph blockquotes, preserve blank lines by including a bare > on the empty separating line:

> First paragraph of the quoted statement providing historical background.
>
> Second paragraph of the statement elaborating on the core technical proposal.
>
> Third paragraph concluding the argument with recommended next steps.

Omitting the > on the blank line can cause some strict parsers to terminate the quote prematurely, splitting your thought into disconnected blocks.

Nested blockquotes

Blockquotes can be nested infinitely by prepending additional greater-than characters (>>):

> Level 1: Primary quote discussing software architecture.
>
> > Level 2: Nested quote responding to the primary point with a counter-example.
> >
> > > Level 3: Deeply nested note citing an external research paper.
>
> Back to Level 1 discussion.

Nested blockquotes are invaluable for documenting threaded debates, legal deposition transcripts, and customer feedback retrospectives.

Embedding other Markdown elements in blockquotes

Blockquotes are container blocks in CommonMark, meaning they can enclose almost any other Markdown element:

Headers, lists, and bold text inside quotes

> ### Team Discussion Notes
>
> During the architecture review, the team agreed on three principles:
> - **Sovereign storage:** Files must remain local on disk.
> - **Zero telemetry:** No background analytics without explicit consent.
> - **Open formats:** Standard CommonMark without lock-in.
>
> For implementation details, consult the project README.

Code blocks inside quotes

You can embed fenced code blocks inside a blockquote by indenting the fences:

> To configure the local server, run:
> ```bash
> pnpm install && pnpm dev
> ```

Obsidian and Oyma Callouts (Admonitions)

In Oyma and Obsidian, blockquotes can be upgraded into rich visual callouts by adding an archetype tag to the first line:

> [!NOTE]
> This is an informational callout with custom styling and an icon.

> [!WARNING]
> Critical warning: Verify database backups before running migrations.

For a comprehensive guide to callout types, icons, and collapsing behaviors, see our Callouts reference.

Formatting blockquotes in Oyma

In Oyma, typing > instantly indents the current line with a refined vertical accent line. As you type, pressing Shift+Enter inserts a new quoted line automatically. Pressing Return twice cleanly exits the blockquote, returning your cursor to standard paragraph text. All text remains 100% portable CommonMark Markdown.

Frequently asked questions

Do I need a greater-than symbol (>) on every line of a blockquote?

CommonMark supports 'lazy continuation', meaning you only need the `>` on the first line of a paragraph. However, best practice is to prefix every line with `>` to maintain visual clarity in plain-text editors and prevent ambiguous line breaks.

How do I create a multi-paragraph blockquote in Markdown?

To create multiple paragraphs within a blockquote, separate the paragraphs with a blank line that contains only the `>` character (`> > > Second paragraph`).

Can I include other Markdown elements inside a blockquote?

Yes. Blockquotes can contain headings, bold text, bullet lists, numbered sequences, inline code, fenced code blocks, and even nested blockquotes.

What is the difference between a standard blockquote and an Obsidian callout?

Standard blockquotes display indented quotation styling. Obsidian and Oyma callouts extend this syntax by adding an archetype tag on the first line (`> [!NOTE]` or `> [!WARNING]`), transforming the quote into a colorful structured card with icons.