How To Make A Website User Manual

May 22, 2016  GNU Make Manual Free Software Foundation last updated May 22, 2016. This manual (make) is available in the following formats: HTML (1012K bytes) - entirely on one web page. HTML - with one web page per node.; HTML compressed (204K gzipped characters) - entirely on one web page. HTML compressed (256K gzipped tar file) - with one web page per node. Welcome to the official blog for the WordPress Support team. Need help with a WordPress issue? You can find help with your WordPress problem by posting in.

Think about the last time that you consulted a manual. Did you start at the beginning and read the whole manual? Probably not. You probably looked first at the index or the table of contents. Once you found the right page or topic, you probably scanned the page first to see if it contained the information you needed. This is how most people read manuals.

No one wants to read your user manual. No one will read your user manual from front to back savoring every word and phrase. Technical documents are not novels. Readers want user manuals to answer their questions quickly so that they can get back to whatever they were doing.

A successful user manual provides users with quick answers to the questions that they might have about a particular product. Users searching for information don’t want to know about the latest and greatest features of a product. Users want to know how to complete tasks. Technical writing focuses on user tasks and the concepts that support the tasks.

Below are some practical tips on writing user manuals that will help you to write content that adapts to the needs of users.

Think like a user

When writing a manual, you need to put on a “user’s hat” and think like a user. You should have a good understanding of your users so you can understand the information they need to know, their background, and their knowledge of the product. Once you think like a user, you can write content that the users need to know.

If you have the opportunity, you will find it very useful to watch users actually using the product. When you watch users interacting with the product, you will get a better idea of what the users need to do, how they approach each task, and when they might use approaches to tasks that are unexpected.

Use active voice

Active voice emphasizes the user and is easier to read and understand. In most cases, especially in user manuals, you should use active voice. In active voice, the subject and verb in the sentence are clear. In passive voice, the subject is unknown and is acted upon by something that is not known or not stated. Passive voice uses verbs that include a form of “to be”.

Compare the two sentences below.

Passive voice: Supplies that will be needed to complete this project include a hammer, a screwdriver, and a rubber mallet.

Active voice: To complete this project, you will need a hammer, a screwdriver, and a rubber mallet.

The sentence that uses active voice makes it clear that the reader is the person who will complete the action. By using the active voice, you will make your writing more clear, concise, and direct.

User

Focus on the reader

User manuals should always focus on the reader. When writing information that involves the reader, such as instructions, use “you” and the active voice. Speaking directly to the reader will:

  • Reinforce the message that the information is intended for the reader
  • Pull readers into the document and make it relevant to them
  • Help to avoid passive voice by focusing on the reader

Compare the two sentences below.

Lack of reader focus: There are three options for viewing content in the editor.

Reader focus: You can choose from one of three options for viewing content in the editor.

The sentence that uses “you” focuses on the reader and makes it clear that the reader is the person doing the action. You should aim to use “you” in your writing to make the content more relevant to the reader.

Write clear instructions

The primary objective of user manuals is to help users complete tasks. Below are some guidelines to help you write clear and concise instructions.

  • Use numbered lists for instructions unless the instruction includes a single step.
  • Use parallel construction for each step. Usually, you should start each step with an imperative word, such as “Enter”, “Click”, “Select”, etc. When you start each step with an imperative word, you are providing the user with clear cues on the required action for each step.
  • Avoid using a system response as a step. For example, don’t say, “The Info dialog window opens” as a step. You can incorporate system responses (when necessary) in the step that initiated the system response or you can mention the system response at the beginning of the following step, e.g. “In the Info dialog window, …”.
  • Provide just enough information so that the user can complete a task or understand a concept. Omit any extraneous information that the user does not need to know. Concise content makes it easier to understand concepts and tasks.

Establish standards

When creating documentation, there will be areas where there may be more than one way to spell a word, refer to an object, caption graphics, punctuate sentences, lay out a page, and organize information. These are just a few of the decisions that writers must make when they create documents. By establishing standards, the writer’s job becomes much easier since most of those decisions will have been already made.

The Chicago Manual of Style and Microsoft Manual of Style are two popular style guides. If you use an established style guide, you may still need to establish some specific guidelines for your writing project. As you encounter any issues with styles, you can create your own additional style rules that address the specific needs of your project.

If you would like to become a technical writer, you may want to consider registering for our Professional Technical Writing Course. It is an online course where you will learn how to write and revise instructions, technical reports, and software manuals (key technical writing documents).

What is a User Guide? A User Guide explains how to use a software application in language that a non-technical person can understand. In general, user guides are part of the documentation suite that comes with an application for example, Data Sheets, Release Notes,Installation Guides andSystem Administration Guides.

Technical Writers will often create a Documentation Plan before writing their user guide. This defines the scope, size, delivery format and resources required to produce the actual user guide.

As the name implies, User Guides are written to help people understand an software application or IT system. They are also called User Manuals. When writing a User Guide, use simple language with short sentences. This writing style helps the user understand the application.

Our User Guide templates can be used to create user guides, user manuals, getting started guides and other types of technical documents. A User Guide is an online or printed book that describes how to use a software application.

User Guides are the first port of call when something needs to be read. As many people read user guides when frustrated and after having lost patience with the software, you need to write your material to address their concerns quickly.

User Guides are often written for non-technical individuals. The level of content and terminology differs considerably from, for example, a System Administration Guide, which is more detailed and complex.

This rest of article offers some guidelines to consider when writing your User Guide, such as:

  • Identifying your audience
  • Writing sections
  • Defining style guide and standards
  • Delivery formats

Identifying Your Audience

As with all types of writing, the first step is to define your TARGET AUDIENCE. Your target audience are the people who will user your document. As different readers have different requirements, you need to consider their specific requirements. Use this template to learn more about the target audience for your projects and what they want to achieve, for example, read your user guide, visit your website or buy your product.

The worksheets include 130 points you can use to capture demographic date so that you have a more holistic view of their wishes, desires, fears, and preferences.
  • Identify the target audience
  • Identify their level of technical knowledge
  • Identify how they will use the guide

Audience Definitions

In the planning process, develop an audience definition that identifies:

  • The user
  • The system
  • The tasks

Software is used to do specific things. Users want to know what the software can do for them, for example, how to print a page in landscape.

They are generally not interested in the nitty-gritty technical details; they want to click a button and get a result. The User Guide is to teach them how the software helps them to do something.

Depending on the guide in question, you may need to address several audiences. For example:

  • Programmers who will troubleshoot the program
  • IT Managers who want to know the resources the program requires
How to make instruction manual
  • Project Managers who want to confirm that the original requirements were met.

If you are writing for more than one audience, develop an audience definition for each one. Examine the definitions and see if you can address all audience types with one document. In many situations, you may need to write a number of documents, of which the users guide is only one.

  • When planning, use the audience definition to focus your decisions.
  • When writing, the audience definition serves as a guide for the documentation team and as a benchmark for evaluating the results.

Here are some questions that will help define your audience's needs:

  • Where will they use the document, for example, in the office, at home, in their car?
  • How much experience have they of using your application?
  • Is this guide an upgrade to an existing application?
  • Is your application new? If so, you may want to include a Getting Started document to introduce the software.
  • How will they use the user guide?
  • Will they install the software by themselves or do so over the internet?
  • What level of detail is required?
  • Will graphics help their understanding of how to use your product?

Writing the User Guide

Each user guide is comprised of front page, body sections, and a back page. The following section describes what each of these needs to contain.

Front Page (cover pages)

How To Make A User Manual For Website

Include a cover page, table of contents, and a preface, if necessary.

Cover and Title Page

If the user guide is copyrighted, include a copyright notice.

Copyright © 2020 The Name Of Your Company.

Place the copyright notice on the cover (and also the title page).

Disclaimer

Include a standard disclaimer inside the front cover that outlines the Terms and Conditions for using this guide.

Preface

Use this section to reference other documents related to the software. Make sure you refer to the correct release number for all software and documents that you refer to. If necessary, include a section on 'How to use this guide' as an introduction.

Contents

You must include a table of contents. the only exception is if your guide is less than ten pages, in which case you should probably refer to it as a Getting Started guide or Reference Guide.

If this user guide is more than twenty pages, include an index at the end of the document.

Body of the guide

This is the heart of the guide. In the main body, separate the procedures (also called instructions) from reference materials. This will help the user navigate their way through the guide much faster.

Procedures

Procedures help the user perform specific tasks. They are also known as instructions or tasks. Examples of these may include:

  • When, why, and how you can perform a task, for example, printing a document, cropping an image, uploading a file.
  • What the screen will show after you perform a task, for example, an updated view of your bank balance.
  • Examples of tasks and program operation.

Writing procedures

Writing procedures involves the following tasks:

  • Identifying the major tasks
  • Separating each major task into subtasks
  • Writing a series of steps that walk the user through each subtask
  • Using an 'if-then' approach when explaining decisions that users can make.

Chunking text

Breaking large pieces of information into smaller piece of information is called 'chunking.'

When writing user guides, you can separate information by menu options and their respective consequences, for example, showing the user the results of each action.

How To Create A Website User Manual

Subtasks that need to be performed can be divided into chunks. Each chunk can form a new chapter or section within the guide.

Use a consistent format for each section, for instance:

  • Introduce each section with an overview of the task to be performed
  • Describe the inputs and outputs. In other words, what the user must enter into the system and what the system will do as a result.
  • Describe the procedures for accomplishing these tasks.

Number your steps

When writing procedures, number each step and use the imperative form of verbs, for example:

Press ENTER

or

Click 'Yes' and press ENTER to submit your details.

Using the If-Then Approach

When users are allowed to make decisions, use an If-Then approach to show the different result for each decision they make.

If you choose 'Yes,' the program will make Firefox your default web browser. If you choose 'No,' it will set Opera as your default browser.

Use diagrams to illustrate more complicated procedures.

Reference Materials

User turn to reference material when they need detailed information on a specific topic, for example, settings or parameters they must enter.

Reference materials can include:

  • Program options, for example, different menus and buttons that are presented to the user
  • Keyboard options, for example, hold AltGr and 4 to show the Euro symbol
  • Error messages that may arise when you use the application

Creating Manuals And User Guides

  • Troubleshooting tips to resolve these issues
  • Frequently asked questions that the user may have about the software

Back Matter

Add a Glossary of Terms and an Index towards the end of the document.

Glossary

The glossary should cover all acronyms and industry terms used in the document. Help the user understand your material. Do not alienate them by using jargon and assuming that they know the meaning on these words.

  • A short glossary can appear at the front before the table of contents
  • A larger glossary should appear in the back matter.

Highlight glossary terms (by italics, for instance) the first time they appear in text.

Index

Any guide longer than 20 pages benefits from an index. An index helps users locate specific items very fast without having to search through the entire document manually. Large documents without an index are impossible to use efficiently.

Establishing Standards

As well as writing the guide, you also need to consider how the document will be delivered, for example, as a book, online or a PDF.

Areas that need consideration include:

  • Format (the design and layout of the pages)
  • Style (elements affecting readability, such as font, size, color)
  • Other requirements that are specific to each delivery format. For example, PDFs may need security settings applied so material cannot be copied; partner logos may need to be added; terms and conditions may need to be updated.

Document Format and Structure

If you are writing a user guide for a client, rather then your own company, check if they use a specific style guide or have a preference for how the document should be presented. Check this with the client during the planning phase.

Manually

Use a document map to organize the guide. To do this:

  • Use headings for organizing information.
  • Include page numbers and section titles on every page, either in footers or headers.

How To Make A Manual

  • Consider using dual columns. This lets you put headings in the left-hand column and the text in the right-hand column.

Style

Use an appropriate style. Decide on the technical level of your language, how you address the user, and conventions that are required.

Technical Language

Match the level of technical language with the audience ¯s level of proficiency. Always underestimate the knowledge of your readers rather than overestimate it.

Limit technical terms to those the user will encounter. If you must define a large number of terms, use a glossary to supplement definitions in the text.

Addressing the User

When writing procedures, use the active voice (e.g. Click this) and address users directly (write 'you' rather than 'the user').

When explaining an action, use the 'command' form of the verb:

'Choose an option from the menu and press [ENTER].'

Presenting your material

You can improve the readability of your documents by using specific formats to distinguish different types of information.

For example, you can distinguish the user's input from the system's response by:

  • Indenting text
  • Using columns to layout text
  • Providing illustrations or photographs that highlight key areas

Create A How To Manual

  • Using different fonts and type features (bold, italics and underline)

Nonverbal devices, such as icons or diagrams, help supplement verbal instructions.

Special Requirements

How To Make Instruction Manual

If the guide is to be used outdoors, in a car, or on the move, make sure the font size is large enough to read easily.

Use spiral biding so the book does not to break easily, and high-quality paper so the text does not smudge or leave stains on the reader's hands.

PS - Download the User Guide Templates here