38 lines
2.0 KiB
Markdown
38 lines
2.0 KiB
Markdown
|
---
|
||
|
|
title: "Procedural topic"
|
||
|
|
---
|
||
|
|
|
||
|
|
Use a title that focuses on the task you are writing about... for example, "Add a new Group" or "Edit user profiles". For procedural docs, there should be a verb in the tilte, and usually the noun (the thing you are working on). For the title (and all headings) use the infinitive form of the verb (i.e. "add") not the gerund form (i.e. "adding").
|
||
|
|
|
||
|
|
In this first section write one or two sentences about the task. Keep it brief; if it goes on too long, then create a separate conceptual topic, in a separate `.md` file. We don't want readers to have to scroll through paragraphs of conceptual info before they get to Step 1.
|
||
|
|
|
||
|
|
## Prerequisites (optional section)
|
||
|
|
|
||
|
|
In this section, inform the reader of anything they need to do, or have configured or installed, before they start following the procedural instructions below.
|
||
|
|
|
||
|
|
## Overview of steps/workflow (optional section)
|
||
|
|
|
||
|
|
If the task is quite long or complex, it might be good to add a bullet list of the main steps, or even a diagram of the workflow, just so that the reader can first familairize themselves with the 50,000 meter view before they dive into the detailed steps.
|
||
|
|
|
||
|
|
## first several group steps
|
||
|
|
|
||
|
|
If the task involves a lot of steps, try to group them into simalr steps and have a Head3 or Hedad4 title for each group.
|
||
|
|
|
||
|
|
In this section, help the reader get oriented... where do they need to be (i.e. in the GUI, on a CLI, etc).
|
||
|
|
|
||
|
|
Have a separate paragraph for each step.
|
||
|
|
|
||
|
|
Start instructions with the desired outcome, followed by the instructions.
|
||
|
|
|
||
|
|
EXAMPLE: To define a new port number, navigate to the Admin interface, and then to the **Settings** tab.
|
||
|
|
|
||
|
|
## next step of grouped steps
|
||
|
|
|
||
|
|
Continue with the steps...
|
||
|
|
|
||
|
|
Use screenshots sparingly, only for complex UIs where it is difficult to describe a UI element with words.
|
||
|
|
|
||
|
|
## verify the steps
|
||
|
|
|
||
|
|
Whenever possible, it is useful to add verification steps at the end of a procedural topic. For example, if the procedural was about installing a product, use this section to tell them how they can verify that the install was successful
|