Write step-by-step guides in Markdown

steps and step organize Markdown as a numbered tutorial. They present static content written by the author. A step has no action, data binding, or write behavior of its own.

This page is a live feature guide. Unit pages: steps, step.

Sample contract

Start with the fence rule

A step needs a body, so it must be a container directive with at least three colons. The wrapping steps directive uses one more. A two-colon ::step is a leaf directive with no body and cannot hold step content.

Source:

::::steps
:::step{title="Define the content boundary"}
Say what the page presents, and what it does not execute.
:::

:::step{title="Place source above the result"}
Let the reader see both the Markdown and its actual output.
:::

:::step{title="Inspect it in a browser"}
Confirm that the numbering, text, and narrow-screen layout all render normally.
:::
::::

Rendered:

1. Define the content boundary

   Say what the page presents, and what it does not execute.

2. Place source above the result

   Let the reader see both the Markdown and its actual output.

3. Inspect it in a browser

   Confirm that the numbering, text, and narrow-screen layout all render normally.

A step body can include ordinary Markdown blocks such as paragraphs, lists, code blocks, or GitHub-style callouts. The outer steps fence must have more colons than the deepest nested container, otherwise the parser reads the fence as a different directive structure.

Failure and limits

steps is a Web Device document structure produced by the content reader. It is not a separate cross-device AUP primitive promise. For the Web layout boundary in this site, see AUP layout boundary.

Verification evidence