Markdown Blockquote: Quotes, Multiple Paragraphs, and Lists

A Markdown blockquote starts with > followed by a space. Put the marker at the beginning of each quoted line to keep the source easy to read and edit.

> The revised installation guide is ready for review.

The result is a quoted paragraph, not a code block. Its border, indentation, and color depend on the page or document theme. The quote's text remains ordinary Markdown, so it can contain emphasis, links, lists, and other document structure.

Use the Markdown viewer to try the examples, then export a document through the Markdown to Word converter when it needs an editable review copy.

Quote a Paragraph Across Several Source Lines

For a longer quotation, repeat the marker:

> The revised installation guide is ready for review.
> Please check the prerequisites before approving the release.

These two source lines form one paragraph in this site's preview. A newline in the source does not necessarily force a displayed line break. When the wording must stay on two lines, add an explicit break:

> Documentation review\
> Assigned to the release manager

The backslash belongs before the newline; the next line still begins with the quote marker. See Markdown line breaks for the difference between hard breaks and paragraph breaks.

Include Several Paragraphs in One Quote

Put a quote marker on the otherwise empty line between paragraphs:

> The first draft describes the installation process.
>
> The second draft adds troubleshooting steps and examples.

This creates one blockquote containing two paragraphs. Keeping > on the separator makes the intended grouping visible, especially when somebody edits the passage later.

To resume your own text, leave a blank line and continue without the marker:

> The review requested a shorter installation section.

We moved the detailed configuration notes into an appendix.

Avoid removing > from a continuation line without adding a blank line. Some Markdown parsers treat that as a lazy continuation of the quoted paragraph. The CommonMark blockquote specification describes this behavior. Explicit markers and a clear empty line are easier for collaborators to maintain.

Add Emphasis, Links, and Attribution

Blockquote content can use normal inline formatting:

> **Review note:** The migration steps need a working example.
> See the [release checklist](https://example.com/checklist).
>
> Feedback from the documentation review, September 2026.

Markdown does not assign a special citation role to the last line. It is ordinary paragraph content within the quote. Include the source, author, and link when they are needed, and verify permissions before reproducing someone else's passage.

A blockquote also does not add literal quotation marks. Type the marks yourself if the final document requires them. For a short quotation embedded in your own sentence, plain quotation marks may be sufficient without creating a separate block.

Nest a Quote or Include a List

Use another > level for quoted material inside the outer quotation:

> The reviewer summarized the earlier request:
>
> > Add a complete example of the configuration file.
>
> The updated draft now includes that example.

Keep nesting shallow in a report. Deeply nested quotes reduce the width available for text, which can make PDF and Word layouts harder to read.

A list inside a quote keeps the marker on every line:

> The review identified two changes:
>
> - Explain the required permissions.
> - Add a troubleshooting section.

For the opposite structure, a quote inside a list, indent it beneath the list item's text:

- Documentation feedback

  > Add a troubleshooting section before publication.
- Release checklist

If the quote appears outside the item, compare its indentation with the examples in the Markdown indentation guide.

GitHub Alerts Need Destination Support

GitHub supports special alerts built on quote syntax, including this form:

> [!NOTE]
> Back up the configuration before changing it.

GitHub documents the supported types in its alerts reference. Alert colors and icons are platform features, rather than a property of every Markdown quote.

This site's renderer does not add GitHub's alert styling. The example remains a blockquote with a visible [!NOTE] label. For a document that must read cleanly across destinations, use an explicit bold label:

> **Note:** Back up the configuration before changing it.

This keeps the meaning understandable without a special alert extension. The same approach works for a warning, a review decision, or an editorial note.

Troubleshoot Quotes Before Exporting

If > appears literally, check whether the example is inside backticks, a fenced code block, or an indented code block. Those contexts are meant to show source text. A backslash before the marker also escapes it.

If too much text becomes quoted, add a blank line before the paragraph that should resume outside the quote. If nested material is difficult to follow, reduce the nesting and add attribution as an ordinary paragraph.

Finally, open the exported DOCX and inspect long quotes and quoted lists. A browser's left border and a Word document's paragraph styling may differ. Use the Markdown to HTML tool to inspect the intermediate structure when you need to distinguish a source-formatting problem from an export-style problem.