Next steps
A next steps section closes a page by pointing the reader to where they should go after finishing. It turns a completed task into a path forward instead of a dead end.
When to use
Use a next steps section at the end of a tutorial or how-to, after the reader has a working result. For a broader set of related reading that is not a clear "do this next", use Additional resources instead.
Composed of
- Headings — an H2 titled Next steps.
- Links — each next step links to the page that continues the reader's path.
- List table — use card styling when the next steps benefit from short descriptions.
Technical details
- Use the heading Next steps (sentence case).
- Write each item as a link plus a short clause on why the reader would follow it.
- Keep the list short — three to five items. A long list is not a path.
Rules
- Every item links to a real page. Do not list a next step that has no destination.
- Order by what most readers will want next.
- Do not repeat links already given inline earlier on the page unless they are genuinely the next action.
Style
- Lead each item with a verb or the destination, not with "You can".
- Make the value clear: what the reader gets by following the link.
Template
Markdown
## Next steps
- [<Destination page>](path) — <why the reader would go there>.
- [<Destination page>](path) — <why>.
Examples
Next steps
- Schedule the job — run your pipeline automatically on a trigger.
- Add a notification — get alerted when a run fails.