Flow

Use docspress/flow for a connected, automatically numbered procedure. It gives a multi-step task more visual continuity than a normal ordered list while preserving semantic list markup.

When to use it

Choose Flow when readers must perform the steps in order. Use ordinary bullets for independent choices, Audience Paths for branching destinations, and Interactive Troubleshooter for a decision tree.

Edit the block

Add, remove, and reorder steps in Gutenberg. Give each step a concise action title and put the explanation, commands, or expected state in its formatted content. Set start when this Flow continues numbering from an earlier sequence.

Attributes

Reference

Flow attributes

Numbering and steps accepted by docspress/flow.

2 fields

start number

First visible step number, clamped to 1–99.

Default1 Values1–99

steps array required

One to 20 ordered step objects.

DefaultThree starter steps Values1–20 items

Each step has a formatted title and formatted content. Empty or invalid step data falls back to the three starter steps so the block never publishes as an unexplained empty shell.

Creative examples

Configure and verify

1. 1

   Choose

   Select the option that matches your project.

2. 2

   Configure

   Set the values required by your environment.

3. 3

   Verify

   Run the check and confirm the expected result.

Continue a release checklist

4. 4

   Freeze content edits

   Tell editors when the release window begins and where urgent corrections should go.

5. 5

   Publish the migration

   Apply the reviewed change to the staged target before production.

6. 6

   Observe the first readers

   Watch error rate, search exits, and support messages for fifteen minutes.

Restore service during an incident

1. 1

   Name the impact

   Record which readers, routes, and regions are affected.

2. 2

   Protect evidence

   Capture the failing request and relevant logs before changing the system.

3. 3

   Reduce the blast radius

   Disable the smallest unsafe surface or route traffic to the known-good version.

4. 4

   Confirm recovery

   Repeat the original failing journey and document the observed result.

Published behavior and accessibility

The block renders as an ordered list with an explicit starting value. Numbers are part of the procedure’s semantics, not decorative text, and remain meaningful without CSS or JavaScript.

Start each title with an imperative verb. Keep one reader action per step, and place the observable success condition at the end of the step.