Menu
Guides
Grammar
Formatting
Interface copy
Documentation
Glossary
How-to guide
4 min read

A how-to guide is a type of documentation that provides specific instructions on how to perform a task. It's focused on the practical aspects of a process, often with step-by-step instructions and visual aids. How-to guides are for users who want to accomplish a specific goal and are familiar with the product or module.

In this guide, you’ll see the available template, general guidelines, and examples of how-to guides.

Make sure to review the guidelines in the Best practices for writing documentation.

Differences between a tutorial and a how-to guide

While both tutorial and how-to guide are instructional resources, they have some differences in their structure and purpose:

Purpose
TutorialHow-to guide
Learning-oriented. Teaches a broader concept, skill, or process in detail.Task-oriented. Focus on helping the user complete a specific task or goal.

Scope
TutorialHow-to guide
Covers a series of steps or concepts, often related to learning a new skill.Narrow in scope, typically covering one task or process divided into steps.

Content
TutorialHow-to guide
Educational, offering context, background, and explanations.Practical, with direct, task-oriented instructions.

Audience
TutorialHow-to guide
Users who want to learn a skill or understand a concept deeply.Users who need to quickly achieve a specific goal, usually with prior knowledge.

Writing a how-to guide

TopicTutorial
TitleDirectly states the guide's goal and uses a verb in the gerund form. Consider your target audience and the specific action you want them to take. For example: Setting up your development environment
Before you begin (optional)Lists all necessary prerequisites the user must have or complete before following the steps in the guide, including:
  1. Tools and software requirements: Specifies the minimum system requirements, such as operating system versions, specific software installations, and hardware configurations.
  2. Account creation or setup: If the user needs to create an account or set up specific configurations, it provides clear instructions or links to relevant resources.
  3. Basic knowledge or skills: If the guide assumes a certain level of familiarity with specific concepts or tools, it briefly outlines those prerequisites or provides links to additional learning resources.
Instructions
  1. Provides detailed instructions for completing the task or achieving the goal.
  2. Breaks down the process into steps, ensuring each step is clear and actionable.
  3. Considers what the user needs to accomplish by the end of the guide and outlines every necessary task to get there. For example, if the goal is to set up a development environment for building a storefront, consider each task the user needs to complete to achieve that.
  4. If a guide requires only one step, omit the Step 1 - Step title, and in the section Instructions, list the action(s) in an ordered list.
  5. Each step should guide the user from one point to the next in a logical sequence. Where relevant, it includes examples, media, or warnings to help users.
  6. The last step should illustrate the outcome so the user can compare it with their results.
Content of the instructions
  1. Each line of the procedure must correspond to an action to be taken by the user.
  2. Don’t assume user knowledge. For example, if the user must press Enter in a step, include that instruction as part of the step.
  3. Use angle brackets (>) to break down complex steps or combine simple ones for sequential actions. For example: 1. In the VTEX Admin, go to Storefront > Site Editor.
  4. Maintain consistent verb tense throughout the instructions by using imperative verbs. For example: 1. Click File > New > Document..

How-to guide template

Announcement template
# Title

[Describe in this section the goal of the guide and what the user will be able to do after following it.]

## Before you begin
[List any necessary tools, software, accounts, required knowledge or skills that the user must have before beginning to follow the guide.]

## Intructions

### Step 1 - Step 1 title
[Provide instructions for this step.]

### Step 2 - Step 2 title
[Provide instructions for this step.]

### Step 3 - Step 3 title
[Provide instructions for this step.]

Examples of how-to guides

Contributors
0
Was this helpful?
Yes
No
Suggest edits (Github)
Contributors
0
On this page
GithubComunityFeedback