Content of User Guides<\/h2>\r\n![\"\"](\"https:\/\/s3-us-west-2.amazonaws.com\/courses-images\/wp-content\/uploads\/sites\/5366\/2020\/07\/22141555\/140-225x300.jpg\")
\r\n\r\nMany user guides contain the following content, as appropriate.\r\nInstructions<\/h3>\r\nThe most obvious user guide contents are those step-by-step directions on how to assemble, operate, or troubleshoot a product. Instructions in a user guide should generally be task-oriented, written for specific tasks that users must perform. Instructions should generally use vertical numbered lists for actions that must be performed in a required sequence. Similar or closely related instructions in user guides should be grouped into chapters.\r\nPrecautionary Information<\/h3>\r\nYou'll see notes, warning, caution, and even danger notices in user guides. These represent liability concerns for the manufacturer of the product.\r\nGetting Started \/ About the Product<\/h3>\r\nSome user guides include brief tutorials that will help new users get acquainted with using the product. User guides also provide some description of the product, a review of its essential features or its new features. Sometimes this information also gets put into a separate volume, if it is extensive. Typically, the volume will be called something like \"Introducing New Product...\"\r\nTechnical Background<\/h3>\r\nSometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can't operate them without understanding the concepts of brightness, saturation, and hue.\r\nReference Information<\/h3>\r\nUser guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.\r\nAdditional Components of User Guides<\/h2>\r\n![\"\"](\"https:\/\/s3-us-west-2.amazonaws.com\/courses-images\/wp-content\/uploads\/sites\/5366\/2020\/07\/22132756\/138-300x225.jpg\")
\r\n\r\nUser guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.\r\nFront and Back Covers<\/h3>\r\nOn the front cover, you will typically see some or all of the following:\r\n\r\n \t- Company name, company or product slogan and logo<\/li>\r\n \t
- Product name<\/li>\r\n \t
- Book title<\/li>\r\n \t
- Trademark symbols<\/li>\r\n \t
- Artwork<\/li>\r\n<\/ul>\r\nThe back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You'll also find bar codes on the back cover.\r\n
Title Page<\/h3>\r\nThe title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.\r\nEdition Notice<\/h3>\r\nThe edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.\r\n\r\nEdition notices usually include the following:\r\n\r\n \t- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\r\n \t
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\r\n \t
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\r\n \t
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\r\n \t
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\r\n \t
- Copyright symbol and statement<\/strong> \u2013 you'll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\r\n \t
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company's own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\r\n \t
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\r\n<\/ul>\r\n
Warranties<\/h3>\r\nThese are the \"guarantees\" that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company's standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.\r\n\r\nAs a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.\r\nPreface<\/h3>\r\n![\"\"](\"https:\/\/s3-us-west-2.amazonaws.com\/courses-images\/wp-content\/uploads\/sites\/5366\/2020\/07\/22142112\/2-300x300.png\")
The function of the preface is to get readers ready to read the book. It does so by:\r\n\r\n \t- characterizing the content and purpose of the book<\/li>\r\n \t
- identifying or even briefly describing the product the book supports<\/li>\r\n \t
- explaining the type of reader for whom the book is meant<\/li>\r\n \t
- outlining the main contents of the book<\/li>\r\n \t
- explaining any special conventions or terminology used in the book<\/li>\r\n<\/ul>\r\nIn traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.\r\n
Appendixes<\/h3>\r\nAppendixes are for material that doesn't fit in the main part of a book but is necessary in some way to readers' understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named \"Appendix A\" and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.\r\nGlossary<\/h3>\r\nSome technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.\r\nIndex<\/h3>\r\nIndexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.\r\nOther Considerations for User Guides<\/h2>\r\n![\"\"](\"https:\/\/s3-us-west-2.amazonaws.com\/courses-images\/wp-content\/uploads\/sites\/5366\/2020\/07\/21205749\/5109-300x169.jpg\")
You may encounter the following when creating a user guide:\r\nDocumentation Plan<\/h3>\r\nUser guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).\r\nPrototype and Specifications<\/h3>\r\nImportant planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses \"Greeked\" text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.\r\n\r\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.\r\n\r\n<\/div>","rendered":"![\"\"](\"https:\/\/s3-us-west-2.amazonaws.com\/courses-images\/wp-content\/uploads\/sites\/5366\/2020\/07\/22134415\/139-300x210.jpg\")
A\u00a0user guide\u00a0is essentially a book-length set of instructions. It can be relatively brief, for example, 10-20 pages on installing, using, or troubleshooting a new software product. Or it can be a full-length book of 100 pages or more. User guides can provide operating instructions on practically anything – lawnmowers, microwave ovens, dishwashers, and more.<\/p>\n
\nThe more complex the product, the greater the page count in the accompanying user guide. If needed, you can create separate user guides for different aspects of the instructions, e.g., installation procedures, troubleshooting procedures, and commands for a new software product. A user guide can even contain a brief tutorial, getting users started using the product, but if there is too much tutorial, it too goes into a separate user guide.<\/p>\n
Note that user guides need visuals, but may be relatively bland in terms of those visuals, since black and white illustrations are cheaper to print. This is especially important to note if the product updates frequently.<\/p>\n
Content of User Guides<\/h2>\n
<\/p>\n
Many user guides contain the following content, as appropriate.<\/p>\n
Instructions<\/h3>\n
The most obvious user guide contents are those step-by-step directions on how to assemble, operate, or troubleshoot a product. Instructions in a user guide should generally be task-oriented, written for specific tasks that users must perform. Instructions should generally use vertical numbered lists for actions that must be performed in a required sequence. Similar or closely related instructions in user guides should be grouped into chapters.<\/p>\n
Precautionary Information<\/h3>\n
You’ll see notes, warning, caution, and even danger notices in user guides. These represent liability concerns for the manufacturer of the product.<\/p>\n
Getting Started \/ About the Product<\/h3>\n
Some user guides include brief tutorials that will help new users get acquainted with using the product. User guides also provide some description of the product, a review of its essential features or its new features. Sometimes this information also gets put into a separate volume, if it is extensive. Typically, the volume will be called something like “Introducing New Product…”<\/p>\n
Technical Background<\/h3>\n
Sometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can’t operate them without understanding the concepts of brightness, saturation, and hue.<\/p>\n
Reference Information<\/h3>\n
User guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.<\/p>\n
Additional Components of User Guides<\/h2>\n
<\/p>\n
User guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.<\/p>\nFront and Back Covers<\/h3>\n
On the front cover, you will typically see some or all of the following:<\/p>\n
\n- Company name, company or product slogan and logo<\/li>\n
- Product name<\/li>\n
- Book title<\/li>\n
- Trademark symbols<\/li>\n
- Artwork<\/li>\n<\/ul>\n
The back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You’ll also find bar codes on the back cover.<\/p>\n
Title Page<\/h3>\n
The title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.<\/p>\n
Edition Notice<\/h3>\n
The edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.<\/p>\n
Edition notices usually include the following:<\/p>\n
\n- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\n
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\n
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\n
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\n
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\n
- Copyright symbol and statement<\/strong> \u2013 you’ll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\n
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company’s own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\n
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\n<\/ul>\n
Warranties<\/h3>\n
These are the “guarantees” that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company’s standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.<\/p>\n
As a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.<\/p>\n
Preface<\/h3>\n
The function of the preface is to get readers ready to read the book. It does so by:<\/p>\n
\n- characterizing the content and purpose of the book<\/li>\n
- identifying or even briefly describing the product the book supports<\/li>\n
- explaining the type of reader for whom the book is meant<\/li>\n
- outlining the main contents of the book<\/li>\n
- explaining any special conventions or terminology used in the book<\/li>\n<\/ul>\n
In traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.<\/p>\n
Appendixes<\/h3>\n
Appendixes are for material that doesn’t fit in the main part of a book but is necessary in some way to readers’ understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named “Appendix A” and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.<\/p>\n
Glossary<\/h3>\n
Some technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.<\/p>\nIndex<\/h3>\n
Indexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.<\/p>\nOther Considerations for User Guides<\/h2>\n
You may encounter the following when creating a user guide:<\/p>\n
Documentation Plan<\/h3>\n
User guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).<\/p>\n
Prototype and Specifications<\/h3>\n
Important planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses “Greeked” text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.<\/p>\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.<\/p>\n<\/div>\n\n\t\t\t \n\t\t\t Candela Citations<\/h3>\n\t\t\t\t\t \n\t\t\t\t\t\t \n\t\t\t\t\t\t\t CC licensed content, Original<\/div>- User Guide. Authored by<\/strong>: Susan Oaks, adpted from Online Technical Communication; see attribution below. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>CC licensed content, Shared previously<\/div>
- User Guides. Authored by<\/strong>: David McMurrey & Tamara Powell. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- image of user guide. Authored by<\/strong>: Alexas_Fotos. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of two people discussing a document. Authored by<\/strong>: CUsai . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of user guide set next to a computer. Authored by<\/strong>: Fabrizio Van Marciano . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of instructions in user manual. Authored by<\/strong>: Gerd Altmann. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of front page of user guide. Authored by<\/strong>: mohamed Hassan . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li><\/ul><\/div>\n\t\t\t\t\t\t <\/div>\n\t\t\t\t\t <\/div>\n\t\t\t <\/section>","protected":false},"author":81366,"menu_order":5,"template":"","meta":{"_candela_citation":"[{\"type\":\"original\",\"description\":\"User Guide\",\"author\":\"Susan Oaks, adpted from Online Technical Communication; see attribution below\",\"organization\":\"Empire State College, SUNY\",\"url\":\"\",\"project\":\"Technical Writing\",\"license\":\"cc-by-nc\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"User Guides\",\"author\":\"David McMurrey & Tamara Powell\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide\",\"author\":\"Alexas_Fotos\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of two people discussing a document\",\"author\":\"CUsai \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide set next to a computer\",\"author\":\"Fabrizio Van Marciano \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of instructions in user manual\",\"author\":\"Gerd Altmann\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of front page of user guide\",\"author\":\"mohamed Hassan \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"}]","CANDELA_OUTCOMES_GUID":"","pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-175","chapter","type-chapter","status-publish","hentry"],"part":84,"_links":{"self":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/users\/81366"}],"version-history":[{"count":16,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions"}],"predecessor-version":[{"id":1643,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions\/1643"}],"part":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/parts\/84"}],"metadata":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/media?parent=175"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapter-type?post=175"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/contributor?post=175"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/license?post=175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Precautionary Information<\/h3>\r\nYou'll see notes, warning, caution, and even danger notices in user guides. These represent liability concerns for the manufacturer of the product.\r\nGetting Started \/ About the Product<\/h3>\r\nSome user guides include brief tutorials that will help new users get acquainted with using the product. User guides also provide some description of the product, a review of its essential features or its new features. Sometimes this information also gets put into a separate volume, if it is extensive. Typically, the volume will be called something like \"Introducing New Product...\"\r\nTechnical Background<\/h3>\r\nSometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can't operate them without understanding the concepts of brightness, saturation, and hue.\r\nReference Information<\/h3>\r\nUser guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.\r\nAdditional Components of User Guides<\/h2>\r\n\r\n\r\nUser guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.\r\nFront and Back Covers<\/h3>\r\nOn the front cover, you will typically see some or all of the following:\r\n\r\n \t- Company name, company or product slogan and logo<\/li>\r\n \t
- Product name<\/li>\r\n \t
- Book title<\/li>\r\n \t
- Trademark symbols<\/li>\r\n \t
- Artwork<\/li>\r\n<\/ul>\r\nThe back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You'll also find bar codes on the back cover.\r\n
Title Page<\/h3>\r\nThe title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.\r\nEdition Notice<\/h3>\r\nThe edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.\r\n\r\nEdition notices usually include the following:\r\n\r\n \t- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\r\n \t
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\r\n \t
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\r\n \t
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\r\n \t
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\r\n \t
- Copyright symbol and statement<\/strong> \u2013 you'll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\r\n \t
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company's own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\r\n \t
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\r\n<\/ul>\r\n
Warranties<\/h3>\r\nThese are the \"guarantees\" that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company's standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.\r\n\r\nAs a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.\r\nPreface<\/h3>\r\nThe function of the preface is to get readers ready to read the book. It does so by:\r\n\r\n \t- characterizing the content and purpose of the book<\/li>\r\n \t
- identifying or even briefly describing the product the book supports<\/li>\r\n \t
- explaining the type of reader for whom the book is meant<\/li>\r\n \t
- outlining the main contents of the book<\/li>\r\n \t
- explaining any special conventions or terminology used in the book<\/li>\r\n<\/ul>\r\nIn traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.\r\n
Appendixes<\/h3>\r\nAppendixes are for material that doesn't fit in the main part of a book but is necessary in some way to readers' understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named \"Appendix A\" and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.\r\nGlossary<\/h3>\r\nSome technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.\r\nIndex<\/h3>\r\nIndexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.\r\nOther Considerations for User Guides<\/h2>\r\nYou may encounter the following when creating a user guide:\r\nDocumentation Plan<\/h3>\r\nUser guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).\r\nPrototype and Specifications<\/h3>\r\nImportant planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses \"Greeked\" text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.\r\n\r\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.\r\n\r\n<\/div>","rendered":"A\u00a0user guide\u00a0is essentially a book-length set of instructions. It can be relatively brief, for example, 10-20 pages on installing, using, or troubleshooting a new software product. Or it can be a full-length book of 100 pages or more. User guides can provide operating instructions on practically anything – lawnmowers, microwave ovens, dishwashers, and more.<\/p>\n
\nThe more complex the product, the greater the page count in the accompanying user guide. If needed, you can create separate user guides for different aspects of the instructions, e.g., installation procedures, troubleshooting procedures, and commands for a new software product. A user guide can even contain a brief tutorial, getting users started using the product, but if there is too much tutorial, it too goes into a separate user guide.<\/p>\n
Note that user guides need visuals, but may be relatively bland in terms of those visuals, since black and white illustrations are cheaper to print. This is especially important to note if the product updates frequently.<\/p>\n
Content of User Guides<\/h2>\n
<\/p>\n
Many user guides contain the following content, as appropriate.<\/p>\n
Instructions<\/h3>\n
The most obvious user guide contents are those step-by-step directions on how to assemble, operate, or troubleshoot a product. Instructions in a user guide should generally be task-oriented, written for specific tasks that users must perform. Instructions should generally use vertical numbered lists for actions that must be performed in a required sequence. Similar or closely related instructions in user guides should be grouped into chapters.<\/p>\n
Precautionary Information<\/h3>\n
You’ll see notes, warning, caution, and even danger notices in user guides. These represent liability concerns for the manufacturer of the product.<\/p>\n
Getting Started \/ About the Product<\/h3>\n
Some user guides include brief tutorials that will help new users get acquainted with using the product. User guides also provide some description of the product, a review of its essential features or its new features. Sometimes this information also gets put into a separate volume, if it is extensive. Typically, the volume will be called something like “Introducing New Product…”<\/p>\n
Technical Background<\/h3>\n
Sometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can’t operate them without understanding the concepts of brightness, saturation, and hue.<\/p>\n
Reference Information<\/h3>\n
User guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.<\/p>\n
Additional Components of User Guides<\/h2>\n
<\/p>\n
User guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.<\/p>\nFront and Back Covers<\/h3>\n
On the front cover, you will typically see some or all of the following:<\/p>\n
\n- Company name, company or product slogan and logo<\/li>\n
- Product name<\/li>\n
- Book title<\/li>\n
- Trademark symbols<\/li>\n
- Artwork<\/li>\n<\/ul>\n
The back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You’ll also find bar codes on the back cover.<\/p>\n
Title Page<\/h3>\n
The title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.<\/p>\n
Edition Notice<\/h3>\n
The edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.<\/p>\n
Edition notices usually include the following:<\/p>\n
\n- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\n
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\n
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\n
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\n
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\n
- Copyright symbol and statement<\/strong> \u2013 you’ll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\n
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company’s own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\n
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\n<\/ul>\n
Warranties<\/h3>\n
These are the “guarantees” that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company’s standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.<\/p>\n
As a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.<\/p>\n
Preface<\/h3>\n
The function of the preface is to get readers ready to read the book. It does so by:<\/p>\n
\n- characterizing the content and purpose of the book<\/li>\n
- identifying or even briefly describing the product the book supports<\/li>\n
- explaining the type of reader for whom the book is meant<\/li>\n
- outlining the main contents of the book<\/li>\n
- explaining any special conventions or terminology used in the book<\/li>\n<\/ul>\n
In traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.<\/p>\n
Appendixes<\/h3>\n
Appendixes are for material that doesn’t fit in the main part of a book but is necessary in some way to readers’ understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named “Appendix A” and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.<\/p>\n
Glossary<\/h3>\n
Some technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.<\/p>\nIndex<\/h3>\n
Indexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.<\/p>\nOther Considerations for User Guides<\/h2>\n
You may encounter the following when creating a user guide:<\/p>\n
Documentation Plan<\/h3>\n
User guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).<\/p>\n
Prototype and Specifications<\/h3>\n
Important planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses “Greeked” text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.<\/p>\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.<\/p>\n<\/div>\n\n\t\t\t \n\t\t\t Candela Citations<\/h3>\n\t\t\t\t\t \n\t\t\t\t\t\t \n\t\t\t\t\t\t\t CC licensed content, Original<\/div>- User Guide. Authored by<\/strong>: Susan Oaks, adpted from Online Technical Communication; see attribution below. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>CC licensed content, Shared previously<\/div>
- User Guides. Authored by<\/strong>: David McMurrey & Tamara Powell. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- image of user guide. Authored by<\/strong>: Alexas_Fotos. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of two people discussing a document. Authored by<\/strong>: CUsai . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of user guide set next to a computer. Authored by<\/strong>: Fabrizio Van Marciano . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of instructions in user manual. Authored by<\/strong>: Gerd Altmann. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of front page of user guide. Authored by<\/strong>: mohamed Hassan . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li><\/ul><\/div>\n\t\t\t\t\t\t <\/div>\n\t\t\t\t\t <\/div>\n\t\t\t <\/section>","protected":false},"author":81366,"menu_order":5,"template":"","meta":{"_candela_citation":"[{\"type\":\"original\",\"description\":\"User Guide\",\"author\":\"Susan Oaks, adpted from Online Technical Communication; see attribution below\",\"organization\":\"Empire State College, SUNY\",\"url\":\"\",\"project\":\"Technical Writing\",\"license\":\"cc-by-nc\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"User Guides\",\"author\":\"David McMurrey & Tamara Powell\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide\",\"author\":\"Alexas_Fotos\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of two people discussing a document\",\"author\":\"CUsai \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide set next to a computer\",\"author\":\"Fabrizio Van Marciano \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of instructions in user manual\",\"author\":\"Gerd Altmann\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of front page of user guide\",\"author\":\"mohamed Hassan \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"}]","CANDELA_OUTCOMES_GUID":"","pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-175","chapter","type-chapter","status-publish","hentry"],"part":84,"_links":{"self":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/users\/81366"}],"version-history":[{"count":16,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions"}],"predecessor-version":[{"id":1643,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions\/1643"}],"part":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/parts\/84"}],"metadata":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/media?parent=175"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapter-type?post=175"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/contributor?post=175"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/license?post=175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Technical Background<\/h3>\r\nSometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can't operate them without understanding the concepts of brightness, saturation, and hue.\r\nReference Information<\/h3>\r\nUser guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.\r\nAdditional Components of User Guides<\/h2>\r\n\r\n\r\nUser guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.\r\nFront and Back Covers<\/h3>\r\nOn the front cover, you will typically see some or all of the following:\r\n\r\n \t- Company name, company or product slogan and logo<\/li>\r\n \t
- Product name<\/li>\r\n \t
- Book title<\/li>\r\n \t
- Trademark symbols<\/li>\r\n \t
- Artwork<\/li>\r\n<\/ul>\r\nThe back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You'll also find bar codes on the back cover.\r\n
Title Page<\/h3>\r\nThe title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.\r\nEdition Notice<\/h3>\r\nThe edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.\r\n\r\nEdition notices usually include the following:\r\n\r\n \t- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\r\n \t
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\r\n \t
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\r\n \t
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\r\n \t
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\r\n \t
- Copyright symbol and statement<\/strong> \u2013 you'll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\r\n \t
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company's own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\r\n \t
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\r\n<\/ul>\r\n
Warranties<\/h3>\r\nThese are the \"guarantees\" that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company's standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.\r\n\r\nAs a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.\r\nPreface<\/h3>\r\nThe function of the preface is to get readers ready to read the book. It does so by:\r\n\r\n \t- characterizing the content and purpose of the book<\/li>\r\n \t
- identifying or even briefly describing the product the book supports<\/li>\r\n \t
- explaining the type of reader for whom the book is meant<\/li>\r\n \t
- outlining the main contents of the book<\/li>\r\n \t
- explaining any special conventions or terminology used in the book<\/li>\r\n<\/ul>\r\nIn traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.\r\n
Appendixes<\/h3>\r\nAppendixes are for material that doesn't fit in the main part of a book but is necessary in some way to readers' understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named \"Appendix A\" and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.\r\nGlossary<\/h3>\r\nSome technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.\r\nIndex<\/h3>\r\nIndexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.\r\nOther Considerations for User Guides<\/h2>\r\nYou may encounter the following when creating a user guide:\r\nDocumentation Plan<\/h3>\r\nUser guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).\r\nPrototype and Specifications<\/h3>\r\nImportant planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses \"Greeked\" text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.\r\n\r\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.\r\n\r\n<\/div>","rendered":"A\u00a0user guide\u00a0is essentially a book-length set of instructions. It can be relatively brief, for example, 10-20 pages on installing, using, or troubleshooting a new software product. Or it can be a full-length book of 100 pages or more. User guides can provide operating instructions on practically anything – lawnmowers, microwave ovens, dishwashers, and more.<\/p>\n
\nThe more complex the product, the greater the page count in the accompanying user guide. If needed, you can create separate user guides for different aspects of the instructions, e.g., installation procedures, troubleshooting procedures, and commands for a new software product. A user guide can even contain a brief tutorial, getting users started using the product, but if there is too much tutorial, it too goes into a separate user guide.<\/p>\n
Note that user guides need visuals, but may be relatively bland in terms of those visuals, since black and white illustrations are cheaper to print. This is especially important to note if the product updates frequently.<\/p>\n
Content of User Guides<\/h2>\n
<\/p>\n
Many user guides contain the following content, as appropriate.<\/p>\n
Instructions<\/h3>\n
The most obvious user guide contents are those step-by-step directions on how to assemble, operate, or troubleshoot a product. Instructions in a user guide should generally be task-oriented, written for specific tasks that users must perform. Instructions should generally use vertical numbered lists for actions that must be performed in a required sequence. Similar or closely related instructions in user guides should be grouped into chapters.<\/p>\n
Precautionary Information<\/h3>\n
You’ll see notes, warning, caution, and even danger notices in user guides. These represent liability concerns for the manufacturer of the product.<\/p>\n
Getting Started \/ About the Product<\/h3>\n
Some user guides include brief tutorials that will help new users get acquainted with using the product. User guides also provide some description of the product, a review of its essential features or its new features. Sometimes this information also gets put into a separate volume, if it is extensive. Typically, the volume will be called something like “Introducing New Product…”<\/p>\n
Technical Background<\/h3>\n
Sometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can’t operate them without understanding the concepts of brightness, saturation, and hue.<\/p>\n
Reference Information<\/h3>\n
User guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.<\/p>\n
Additional Components of User Guides<\/h2>\n
<\/p>\n
User guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.<\/p>\nFront and Back Covers<\/h3>\n
On the front cover, you will typically see some or all of the following:<\/p>\n
\n- Company name, company or product slogan and logo<\/li>\n
- Product name<\/li>\n
- Book title<\/li>\n
- Trademark symbols<\/li>\n
- Artwork<\/li>\n<\/ul>\n
The back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You’ll also find bar codes on the back cover.<\/p>\n
Title Page<\/h3>\n
The title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.<\/p>\n
Edition Notice<\/h3>\n
The edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.<\/p>\n
Edition notices usually include the following:<\/p>\n
\n- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\n
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\n
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\n
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\n
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\n
- Copyright symbol and statement<\/strong> \u2013 you’ll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\n
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company’s own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\n
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\n<\/ul>\n
Warranties<\/h3>\n
These are the “guarantees” that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company’s standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.<\/p>\n
As a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.<\/p>\n
Preface<\/h3>\n
The function of the preface is to get readers ready to read the book. It does so by:<\/p>\n
\n- characterizing the content and purpose of the book<\/li>\n
- identifying or even briefly describing the product the book supports<\/li>\n
- explaining the type of reader for whom the book is meant<\/li>\n
- outlining the main contents of the book<\/li>\n
- explaining any special conventions or terminology used in the book<\/li>\n<\/ul>\n
In traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.<\/p>\n
Appendixes<\/h3>\n
Appendixes are for material that doesn’t fit in the main part of a book but is necessary in some way to readers’ understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named “Appendix A” and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.<\/p>\n
Glossary<\/h3>\n
Some technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.<\/p>\nIndex<\/h3>\n
Indexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.<\/p>\nOther Considerations for User Guides<\/h2>\n
You may encounter the following when creating a user guide:<\/p>\n
Documentation Plan<\/h3>\n
User guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).<\/p>\n
Prototype and Specifications<\/h3>\n
Important planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses “Greeked” text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.<\/p>\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.<\/p>\n<\/div>\n\n\t\t\t \n\t\t\t Candela Citations<\/h3>\n\t\t\t\t\t \n\t\t\t\t\t\t \n\t\t\t\t\t\t\t CC licensed content, Original<\/div>- User Guide. Authored by<\/strong>: Susan Oaks, adpted from Online Technical Communication; see attribution below. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>CC licensed content, Shared previously<\/div>
- User Guides. Authored by<\/strong>: David McMurrey & Tamara Powell. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- image of user guide. Authored by<\/strong>: Alexas_Fotos. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of two people discussing a document. Authored by<\/strong>: CUsai . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of user guide set next to a computer. Authored by<\/strong>: Fabrizio Van Marciano . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of instructions in user manual. Authored by<\/strong>: Gerd Altmann. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of front page of user guide. Authored by<\/strong>: mohamed Hassan . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li><\/ul><\/div>\n\t\t\t\t\t\t <\/div>\n\t\t\t\t\t <\/div>\n\t\t\t <\/section>","protected":false},"author":81366,"menu_order":5,"template":"","meta":{"_candela_citation":"[{\"type\":\"original\",\"description\":\"User Guide\",\"author\":\"Susan Oaks, adpted from Online Technical Communication; see attribution below\",\"organization\":\"Empire State College, SUNY\",\"url\":\"\",\"project\":\"Technical Writing\",\"license\":\"cc-by-nc\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"User Guides\",\"author\":\"David McMurrey & Tamara Powell\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide\",\"author\":\"Alexas_Fotos\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of two people discussing a document\",\"author\":\"CUsai \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide set next to a computer\",\"author\":\"Fabrizio Van Marciano \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of instructions in user manual\",\"author\":\"Gerd Altmann\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of front page of user guide\",\"author\":\"mohamed Hassan \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"}]","CANDELA_OUTCOMES_GUID":"","pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-175","chapter","type-chapter","status-publish","hentry"],"part":84,"_links":{"self":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/users\/81366"}],"version-history":[{"count":16,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions"}],"predecessor-version":[{"id":1643,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions\/1643"}],"part":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/parts\/84"}],"metadata":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/media?parent=175"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapter-type?post=175"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/contributor?post=175"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/license?post=175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Additional Components of User Guides<\/h2>\r\n\r\n\r\nUser guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.\r\nFront and Back Covers<\/h3>\r\nOn the front cover, you will typically see some or all of the following:\r\n\r\n \t- Company name, company or product slogan and logo<\/li>\r\n \t
- Product name<\/li>\r\n \t
- Book title<\/li>\r\n \t
- Trademark symbols<\/li>\r\n \t
- Artwork<\/li>\r\n<\/ul>\r\nThe back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You'll also find bar codes on the back cover.\r\n
Title Page<\/h3>\r\nThe title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.\r\nEdition Notice<\/h3>\r\nThe edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.\r\n\r\nEdition notices usually include the following:\r\n\r\n \t- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\r\n \t
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\r\n \t
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\r\n \t
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\r\n \t
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\r\n \t
- Copyright symbol and statement<\/strong> \u2013 you'll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\r\n \t
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company's own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\r\n \t
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\r\n<\/ul>\r\n
Warranties<\/h3>\r\nThese are the \"guarantees\" that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company's standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.\r\n\r\nAs a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.\r\nPreface<\/h3>\r\nThe function of the preface is to get readers ready to read the book. It does so by:\r\n\r\n \t- characterizing the content and purpose of the book<\/li>\r\n \t
- identifying or even briefly describing the product the book supports<\/li>\r\n \t
- explaining the type of reader for whom the book is meant<\/li>\r\n \t
- outlining the main contents of the book<\/li>\r\n \t
- explaining any special conventions or terminology used in the book<\/li>\r\n<\/ul>\r\nIn traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.\r\n
Appendixes<\/h3>\r\nAppendixes are for material that doesn't fit in the main part of a book but is necessary in some way to readers' understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named \"Appendix A\" and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.\r\nGlossary<\/h3>\r\nSome technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.\r\nIndex<\/h3>\r\nIndexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.\r\nOther Considerations for User Guides<\/h2>\r\nYou may encounter the following when creating a user guide:\r\nDocumentation Plan<\/h3>\r\nUser guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).\r\nPrototype and Specifications<\/h3>\r\nImportant planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses \"Greeked\" text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.\r\n\r\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.\r\n\r\n<\/div>","rendered":"A\u00a0user guide\u00a0is essentially a book-length set of instructions. It can be relatively brief, for example, 10-20 pages on installing, using, or troubleshooting a new software product. Or it can be a full-length book of 100 pages or more. User guides can provide operating instructions on practically anything – lawnmowers, microwave ovens, dishwashers, and more.<\/p>\n
\nThe more complex the product, the greater the page count in the accompanying user guide. If needed, you can create separate user guides for different aspects of the instructions, e.g., installation procedures, troubleshooting procedures, and commands for a new software product. A user guide can even contain a brief tutorial, getting users started using the product, but if there is too much tutorial, it too goes into a separate user guide.<\/p>\n
Note that user guides need visuals, but may be relatively bland in terms of those visuals, since black and white illustrations are cheaper to print. This is especially important to note if the product updates frequently.<\/p>\n
Content of User Guides<\/h2>\n
<\/p>\n
Many user guides contain the following content, as appropriate.<\/p>\n
Instructions<\/h3>\n
The most obvious user guide contents are those step-by-step directions on how to assemble, operate, or troubleshoot a product. Instructions in a user guide should generally be task-oriented, written for specific tasks that users must perform. Instructions should generally use vertical numbered lists for actions that must be performed in a required sequence. Similar or closely related instructions in user guides should be grouped into chapters.<\/p>\n
Precautionary Information<\/h3>\n
You’ll see notes, warning, caution, and even danger notices in user guides. These represent liability concerns for the manufacturer of the product.<\/p>\n
Getting Started \/ About the Product<\/h3>\n
Some user guides include brief tutorials that will help new users get acquainted with using the product. User guides also provide some description of the product, a review of its essential features or its new features. Sometimes this information also gets put into a separate volume, if it is extensive. Typically, the volume will be called something like “Introducing New Product…”<\/p>\n
Technical Background<\/h3>\n
Sometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can’t operate them without understanding the concepts of brightness, saturation, and hue.<\/p>\n
Reference Information<\/h3>\n
User guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.<\/p>\n
Additional Components of User Guides<\/h2>\n
<\/p>\n
User guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.<\/p>\nFront and Back Covers<\/h3>\n
On the front cover, you will typically see some or all of the following:<\/p>\n
\n- Company name, company or product slogan and logo<\/li>\n
- Product name<\/li>\n
- Book title<\/li>\n
- Trademark symbols<\/li>\n
- Artwork<\/li>\n<\/ul>\n
The back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You’ll also find bar codes on the back cover.<\/p>\n
Title Page<\/h3>\n
The title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.<\/p>\n
Edition Notice<\/h3>\n
The edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.<\/p>\n
Edition notices usually include the following:<\/p>\n
\n- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\n
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\n
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\n
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\n
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\n
- Copyright symbol and statement<\/strong> \u2013 you’ll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\n
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company’s own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\n
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\n<\/ul>\n
Warranties<\/h3>\n
These are the “guarantees” that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company’s standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.<\/p>\n
As a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.<\/p>\n
Preface<\/h3>\n
The function of the preface is to get readers ready to read the book. It does so by:<\/p>\n
\n- characterizing the content and purpose of the book<\/li>\n
- identifying or even briefly describing the product the book supports<\/li>\n
- explaining the type of reader for whom the book is meant<\/li>\n
- outlining the main contents of the book<\/li>\n
- explaining any special conventions or terminology used in the book<\/li>\n<\/ul>\n
In traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.<\/p>\n
Appendixes<\/h3>\n
Appendixes are for material that doesn’t fit in the main part of a book but is necessary in some way to readers’ understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named “Appendix A” and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.<\/p>\n
Glossary<\/h3>\n
Some technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.<\/p>\nIndex<\/h3>\n
Indexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.<\/p>\nOther Considerations for User Guides<\/h2>\n
You may encounter the following when creating a user guide:<\/p>\n
Documentation Plan<\/h3>\n
User guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).<\/p>\n
Prototype and Specifications<\/h3>\n
Important planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses “Greeked” text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.<\/p>\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.<\/p>\n<\/div>\n\n\t\t\t \n\t\t\t Candela Citations<\/h3>\n\t\t\t\t\t \n\t\t\t\t\t\t \n\t\t\t\t\t\t\t CC licensed content, Original<\/div>- User Guide. Authored by<\/strong>: Susan Oaks, adpted from Online Technical Communication; see attribution below. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>CC licensed content, Shared previously<\/div>
- User Guides. Authored by<\/strong>: David McMurrey & Tamara Powell. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- image of user guide. Authored by<\/strong>: Alexas_Fotos. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of two people discussing a document. Authored by<\/strong>: CUsai . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of user guide set next to a computer. Authored by<\/strong>: Fabrizio Van Marciano . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of instructions in user manual. Authored by<\/strong>: Gerd Altmann. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of front page of user guide. Authored by<\/strong>: mohamed Hassan . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li><\/ul><\/div>\n\t\t\t\t\t\t <\/div>\n\t\t\t\t\t <\/div>\n\t\t\t <\/section>","protected":false},"author":81366,"menu_order":5,"template":"","meta":{"_candela_citation":"[{\"type\":\"original\",\"description\":\"User Guide\",\"author\":\"Susan Oaks, adpted from Online Technical Communication; see attribution below\",\"organization\":\"Empire State College, SUNY\",\"url\":\"\",\"project\":\"Technical Writing\",\"license\":\"cc-by-nc\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"User Guides\",\"author\":\"David McMurrey & Tamara Powell\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide\",\"author\":\"Alexas_Fotos\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of two people discussing a document\",\"author\":\"CUsai \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide set next to a computer\",\"author\":\"Fabrizio Van Marciano \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of instructions in user manual\",\"author\":\"Gerd Altmann\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of front page of user guide\",\"author\":\"mohamed Hassan \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"}]","CANDELA_OUTCOMES_GUID":"","pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-175","chapter","type-chapter","status-publish","hentry"],"part":84,"_links":{"self":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/users\/81366"}],"version-history":[{"count":16,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions"}],"predecessor-version":[{"id":1643,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions\/1643"}],"part":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/parts\/84"}],"metadata":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/media?parent=175"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapter-type?post=175"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/contributor?post=175"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/license?post=175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- \r\n \t
- Company name, company or product slogan and logo<\/li>\r\n \t
- Product name<\/li>\r\n \t
- Book title<\/li>\r\n \t
- Trademark symbols<\/li>\r\n \t
- Artwork<\/li>\r\n<\/ul>\r\nThe back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You'll also find bar codes on the back cover.\r\n
Title Page<\/h3>\r\nThe title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.\r\n
Edition Notice<\/h3>\r\nThe edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.\r\n\r\nEdition notices usually include the following:\r\n
- \r\n \t
- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\r\n \t
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\r\n \t
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\r\n \t
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\r\n \t
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\r\n \t
- Copyright symbol and statement<\/strong> \u2013 you'll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\r\n \t
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company's own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\r\n \t
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\r\n<\/ul>\r\n
Warranties<\/h3>\r\nThese are the \"guarantees\" that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company's standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.\r\n\r\nAs a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.\r\n
Preface<\/h3>\r\n
The function of the preface is to get readers ready to read the book. It does so by:\r\n- \r\n \t
- characterizing the content and purpose of the book<\/li>\r\n \t
- identifying or even briefly describing the product the book supports<\/li>\r\n \t
- explaining the type of reader for whom the book is meant<\/li>\r\n \t
- outlining the main contents of the book<\/li>\r\n \t
- explaining any special conventions or terminology used in the book<\/li>\r\n<\/ul>\r\nIn traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.\r\n
Appendixes<\/h3>\r\nAppendixes are for material that doesn't fit in the main part of a book but is necessary in some way to readers' understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named \"Appendix A\" and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.\r\n
Glossary<\/h3>\r\nSome technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.\r\n
Index<\/h3>\r\nIndexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.\r\n
Other Considerations for User Guides<\/h2>\r\n
You may encounter the following when creating a user guide:\r\nDocumentation Plan<\/h3>\r\nUser guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).\r\n
Prototype and Specifications<\/h3>\r\nImportant planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses \"Greeked\" text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.\r\n\r\nSpecifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.\r\n\r\n<\/div>","rendered":"
A\u00a0user guide\u00a0is essentially a book-length set of instructions. It can be relatively brief, for example, 10-20 pages on installing, using, or troubleshooting a new software product. Or it can be a full-length book of 100 pages or more. User guides can provide operating instructions on practically anything – lawnmowers, microwave ovens, dishwashers, and more.<\/p>\n\nThe more complex the product, the greater the page count in the accompanying user guide. If needed, you can create separate user guides for different aspects of the instructions, e.g., installation procedures, troubleshooting procedures, and commands for a new software product. A user guide can even contain a brief tutorial, getting users started using the product, but if there is too much tutorial, it too goes into a separate user guide.<\/p>\n
Note that user guides need visuals, but may be relatively bland in terms of those visuals, since black and white illustrations are cheaper to print. This is especially important to note if the product updates frequently.<\/p>\n
Content of User Guides<\/h2>\n
<\/p>\nMany user guides contain the following content, as appropriate.<\/p>\n
Instructions<\/h3>\n
The most obvious user guide contents are those step-by-step directions on how to assemble, operate, or troubleshoot a product. Instructions in a user guide should generally be task-oriented, written for specific tasks that users must perform. Instructions should generally use vertical numbered lists for actions that must be performed in a required sequence. Similar or closely related instructions in user guides should be grouped into chapters.<\/p>\n
Precautionary Information<\/h3>\n
You’ll see notes, warning, caution, and even danger notices in user guides. These represent liability concerns for the manufacturer of the product.<\/p>\n
Getting Started \/ About the Product<\/h3>\n
Some user guides include brief tutorials that will help new users get acquainted with using the product. User guides also provide some description of the product, a review of its essential features or its new features. Sometimes this information also gets put into a separate volume, if it is extensive. Typically, the volume will be called something like “Introducing New Product…”<\/p>\n
Technical Background<\/h3>\n
Sometimes, user guides will include technical explanations of how the product works, what physical or chemical principles are essential to its operation, and so on. For example, you may see considerable background in user guides for graphic or audio programs, since you can’t operate them without understanding the concepts of brightness, saturation, and hue.<\/p>\n
Reference Information<\/h3>\n
User guides typically contain reference information, but only up to a certain point. For example, if there are numerous commands for a new software product, you might have a separate user guide for commands. Reference information in user guides is often presented in tables, with columns of settings, descriptions, variables, parameters, flags, and so on.<\/p>\n
Additional Components of User Guides<\/h2>\n
<\/p>\nUser guides have tables of contents, headings, lists of figures, and all of the characteristics of technical documents and reports. The following list additional<\/em> components of user guides, since they are books. User guides may incorporate all or some of these components.<\/p>\n
Front and Back Covers<\/h3>\n
On the front cover, you will typically see some or all of the following:<\/p>\n
- \n
- Company name, company or product slogan and logo<\/li>\n
- Product name<\/li>\n
- Book title<\/li>\n
- Trademark symbols<\/li>\n
- Artwork<\/li>\n<\/ul>\n
The back cover of hard copy user guides and manuals is usually very simple. Typically, it contains the book order number, the name of the company with appropriate trademark symbols, a copyright symbol and phrasing as to the ownership of the book, and a statement as to which country the book was printed in. You’ll also find bar codes on the back cover.<\/p>\n
Title Page<\/h3>\n
The title page is typically a duplicate of the front cover, but with certain elements omitted. Typically omitted are the artwork, company or product logos, and slogans. Some technical publications omit the title page altogether because of the duplication.<\/p>\n
Edition Notice<\/h3>\n
The edition notice occurs on the backside of the title page. If the technical publisher eliminates the title page, then the edition notice appears on the backside of the front cover.<\/p>\n
Edition notices usually include the following:<\/p>\n
- \n
- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\n
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\n
- Product applicability <\/strong>\u2013\u00a0if the product is computer hardware or software, the edition notice typically indicates which platform, version, and release number of the product the book applies to<\/li>\n
- Full title of the book <\/strong>\u2013\u00a0in italics<\/li>\n
- Disclaimers<\/strong> \u2013 product manufacturers may state that they do not guarantee the book is technically correct, complete, or free from writing problems. that the product is free from minor flaws, or that it meets the needs of the customer<\/li>\n
- Copyright symbol and statement<\/strong> \u2013 you’ll see the circle-C copyright symbol \u00a9 and some statement about permissions, or a creative commons license<\/li>\n
- Trademarks<\/strong> \u2013 some technical publications list known trademarks in the edition notice, including the company’s own trademarks and the trademarks of other companies referenced in the book. Or they may insert a statement that any references to trademarked product names are owned by their respective companies.<\/li>\n
- Reader responses<\/strong> \u2013 sometimes, the edition notice will include some encouragement to customers to contact the company about product or documentation concerns. Instructions on how to contact the company are sometimes included in the edition notice.<\/li>\n<\/ul>\n
Warranties<\/h3>\n
These are the “guarantees” that the company will support concerning its product. Sometimes these are published in the front matter of the book but, more appropriately from a book-design standpoint, they are printed on a separate card and inserted in the book or the product. As with edition notices, this is a company’s standardized text you simply insert into the book\u2014do not change the text that you are given, which usually has been approved by company attorneys.<\/p>\n
As a technical writer, be aware that companies sometimes maintain multiple versions of edition notices, safety notices, warranties, and communication statements. Make sure that you are using the right version.<\/p>\n
Preface<\/h3>\n
The function of the preface is to get readers ready to read the book. It does so by:<\/p>\n- \n
- characterizing the content and purpose of the book<\/li>\n
- identifying or even briefly describing the product the book supports<\/li>\n
- explaining the type of reader for whom the book is meant<\/li>\n
- outlining the main contents of the book<\/li>\n
- explaining any special conventions or terminology used in the book<\/li>\n<\/ul>\n
In traditional book publishing, the preface comes before the table of contents, but technical guides may place the table of contents earlier in the book for usability reasons.<\/p>\n
Appendixes<\/h3>\n
Appendixes are for material that doesn’t fit in the main part of a book but is necessary in some way to readers’ understanding. Appendixes are often the place for big tables. An appendix is just like a chapter, except that it is named “Appendix A” and the headers and footers use are A-1, A-2, and so on for pages in Appendix A.<\/p>\n
Glossary<\/h3>\n
Some technical publications include a section of specialized terms and their definitions. Notice that most glossaries use a two-column layout for the term and its definition. Definitions are typically not complete sentences. Multiple definitions are typically identified by Arabic numbers in parentheses. Glossary paragraphs also contain See also<\/em>\u00a0references to related terms.<\/p>\n
Index<\/h3>\n
Indexes are also typically two-column and contain\u00a0See also<\/em> references to related terms.<\/p>\n
Other Considerations for User Guides<\/h2>\n
You may encounter the following when creating a user guide:<\/p>\nDocumentation Plan<\/h3>\n
User guides need documentation plans, which are internal supporting documents that specify content, audience, design, format, production team members, schedule, and other such information about a documentation project and its deliverables. The documentation plan represents an established plan agreed upon by everybody involved in the production process (both the user guide and the product it documents).<\/p>\n
Prototype and Specifications<\/h3>\n
Important planning tools, which also serve as useful reference tools during a documentation project, include the prototype of the user guide and the specifications for the user guide. The prototype is a dummy version of the book with all planned components of the book (see the list on book-design components) and all planned elements (see the list under format and style). However, the prototype uses “Greeked” text (also known as\u00a0Lorem ipsum<\/a>). Typically, the prototype of the user guide is very brief: it needs to include only as many pages as it takes to illustrate every unique textual component and textual element that will be used in the user guide.<\/p>\n
Specifications\u00a0are descriptions of a book design in table form. Specifications describe every unique component or element of a book, so that it can be recreated by someone who might not have access to the electronic files, templates, or styles of that book.<\/p>\n<\/div>\n\n\t\t\t
\n\t\t\t Candela Citations<\/h3>\n\t\t\t\t\t
\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tCC licensed content, Original<\/div>- User Guide. Authored by<\/strong>: Susan Oaks, adpted from Online Technical Communication; see attribution below. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>CC licensed content, Shared previously<\/div>
- User Guides. Authored by<\/strong>: David McMurrey & Tamara Powell. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- image of user guide. Authored by<\/strong>: Alexas_Fotos. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of two people discussing a document. Authored by<\/strong>: CUsai . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- image of user guide set next to a computer. Authored by<\/strong>: Fabrizio Van Marciano . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of instructions in user manual. Authored by<\/strong>: Gerd Altmann. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li>
- image of front page of user guide. Authored by<\/strong>: mohamed Hassan . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/<\/a>. License<\/strong>: Public Domain: No Known Copyright<\/a><\/em><\/li><\/ul><\/div>\n\t\t\t\t\t\t <\/div>\n\t\t\t\t\t <\/div>\n\t\t\t <\/section>","protected":false},"author":81366,"menu_order":5,"template":"","meta":{"_candela_citation":"[{\"type\":\"original\",\"description\":\"User Guide\",\"author\":\"Susan Oaks, adpted from Online Technical Communication; see attribution below\",\"organization\":\"Empire State College, SUNY\",\"url\":\"\",\"project\":\"Technical Writing\",\"license\":\"cc-by-nc\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"User Guides\",\"author\":\"David McMurrey & Tamara Powell\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide\",\"author\":\"Alexas_Fotos\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of two people discussing a document\",\"author\":\"CUsai \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/the-labour-code-human-resources-3520806\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of user guide set next to a computer\",\"author\":\"Fabrizio Van Marciano \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/web-design-laptop-html-design-2038872\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of instructions in user manual\",\"author\":\"Gerd Altmann\",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/illustrations\/instructions-user-manual-76729\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of front page of user guide\",\"author\":\"mohamed Hassan \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/vectors\/user-guide-instructions-text-sheet-2702483\/\",\"project\":\"\",\"license\":\"pd\",\"license_terms\":\"\"}]","CANDELA_OUTCOMES_GUID":"","pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-175","chapter","type-chapter","status-publish","hentry"],"part":84,"_links":{"self":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/users\/81366"}],"version-history":[{"count":16,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions"}],"predecessor-version":[{"id":1643,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/revisions\/1643"}],"part":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/parts\/84"}],"metadata":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/175\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/media?parent=175"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapter-type?post=175"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/contributor?post=175"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/license?post=175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- image of user guide. Authored by<\/strong>: Alexas_Fotos. Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/nikon-d3200-camera-manual-642153\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li>
- User Guides. Authored by<\/strong>: David McMurrey & Tamara Powell. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/zijKIklcQaCR1f\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- User Guide. Authored by<\/strong>: Susan Oaks, adpted from Online Technical Communication; see attribution below. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\n
- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\n
- Edition number<\/strong> \u2013 whether the book is a first, second, or third edition.<\/li>\r\n \t
- Date of publication<\/strong> \u2013 the year and sometimes the month that the book was published<\/li>\r\n \t