Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
User guide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Technical communication document}} {{for|a full guide to an item owned by its operator|Owner's manual}} {{Merge from|Owner's manual|talk=Talk:User guide#Merge from Owner's manual|date=March 2025|reason=Conceptually one is a subset of the other, and content-wise these are simply [[WP:CONTENTFORKS]] covering the exact same scope.}} [[File:Dulcitone users manual page 2,3.jpg|thumb|User's guide for a [[Dulcitone]] keyboard]] A '''user guide''', also commonly known as a '''user manual''', is intended to assist users in using a particular product, service or application. It is usually written by a technician, product developer, or a company's customer service staff. Most user guides contain both a written guide and associated images. In the case of computer applications, it is usual to include [[screenshot]]s of the human-machine interface(s), and hardware manuals often include clear, simplified [[diagram]]s. The language used is matched to the intended [[audience]], with [[jargon]] kept to a minimum or explained thoroughly. ==Contents of a user manual== The sections of a user manual often include: *A cover page *A title page and copyright page *A preface, containing details of related documents and information on how to navigate the user guide *A contents page *A Purpose section. This should be an overview rather than detail the objective of the document *An Audience section to explicitly state who is the intended audience who is required to read, including optionals *A Scope section is crucial as it also serves as a disclaimer, stating what is out-of-scope as well as what is covered *A guide on how to use at least the main function of the system *A [[troubleshooting]] section detailing possible errors or problems that may occur, along with how to fix them *A [[FAQ]] (Frequently Asked Questions) *Where to find further help, and contact details *A [[glossary]] and, for larger documents, an [[index (publishing)|index]] == History == [[File:Antikythera mechanism clockface, 1st-2nd century BC, Greece (model).jpg|thumb|The user guide engraved into a model of the Antikythera Mechanism]] User guides have been found with ancient devices. One example is the [[Antikythera mechanism|Antikythera Mechanism]],<ref>{{Cite news|url=https://www.theregister.co.uk/2016/06/15/antikythera_mechanism_inscriptions_deciphered/|title=Boffins decipher manual for 2,000-year-old Ancient Greek computer|access-date=2018-11-29|language=en}}</ref> a 2,000 year old Greek analogue computer that was found off the coast of the Greek island [[Antikythera]] in the year 1900. On the cover of this device are passages of text which describe the features and operation of the mechanism. As the software industry was developing, the question of how to best document software programs was undecided. This was a unique problem for software developers, since users often became frustrated with current help documents.<ref name=":0">{{Cite book|last=Chafin|first=Roy|title=Proceedings of the 1st annual international conference on Systems documentation - SIGDOC '82 |chapter=User manuals: What does the user really need? |date=January 1982|pages=36β39|doi=10.1145/800065.801307 |isbn=089791080X |s2cid=6435788 |doi-access=free}}</ref> Some considerations for writing a user guide that developed at this time include: * the use of [[plain language]]<ref name=":0" /> * length and reading difficulty<ref name=":0" /> * the role of printed user guides for digital programs<ref name=":1">{{Cite journal|last=McKee|first=John|date=August 1986|title=Computer User Manuals in Print: Do They Have a Future?|journal=ACM SIGDOC Asterisk Journal of Computer Documentation|volume=12|issue=2 |pages=11β16|doi=10.1145/15505.15507 |s2cid=35615987 }}</ref> * user-centered design<ref name=":1" /> ==Computer software manuals and guides== Before [[Unix]], for example, [[General Comprehensive Operating System|GCOS]], mainframe documentation were printed pages, available [[on-premise]] to users (staff, students...), organized into steel binders, locked together in one monolithic steel reading rack, bolted to a table or counter, with pages organized for modular information updates, replacement, errata, and addenda. {{cn|date=January 2024}} User manuals and user guides for most non-trivial PC and browser [[software application]]s are book-like documents with contents similar to the above list. They may be distributed either in print or electronically. Some documents have a more fluid structure with many internal links. The ''[[Google Earth]] User Guide''<ref>{{cite web |title=Google Earth User Guide |url=http://earth.google.com/userguide/v4/ |date=4 June 2009 |access-date=13 August 2009}}</ref> is an example of this format. The term ''guide'' is often applied to a document that addresses a specific aspect of a software product. Some usages are ''[[Installation (computer programs)|Installation]] Guide'', ''Getting Started Guide'', and various ''How to'' guides. An example is the ''[[Picasa]] Getting Started Guide''.<ref>{{cite web |title=Getting Started with Picasa: Getting Started Guide |url=http://picasa.google.com/support/bin/answer.py?hl=en&answer=93183 |date=15 June 2009 |access-date=13 August 2009}}</ref> In some [[business software]] applications, where groups of users have access to only a sub-set of the application's full functionality, a user guide may be prepared for each group. An example of this approach is the ''[[Autodesk]] Topobase 2010 [[Online help|Help]]''<ref>{{cite web |title=Autodesk Topobase 2010 Help |url=http://docs.autodesk.com/TOPOBSCLNT/2010/ENU/Autodesk%20Topobase%202010%20User%20Documentation/index.html?url=WSfacf1429558a55de9af080101d7e8b304-7c61.htm,topicNumber=d0e342 |publisher=Autodesk|access-date=13 August 2009}}</ref> document, which contains separate ''[[System administrator|Administrator]] Guides'', ''[[User (computing)|User]] Guides'', and a ''[[Software developer|Developer's]] Guide''. == See also == * [[Owner's manual]] *[[Release notes]] *[[Moe book]] *[[Technical writer]] *[[Manual page (Unix)]] *[[Instruction manual (gaming)]] *[[Reference card]] *[[RTFM]] *[[HOWTO articles]] ==References== {{Reflist}} {{Authority control}} [[Category:Technical communication]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Authority control
(
edit
)
Template:Cite book
(
edit
)
Template:Cite journal
(
edit
)
Template:Cite news
(
edit
)
Template:Cite web
(
edit
)
Template:Cn
(
edit
)
Template:DMC
(
edit
)
Template:For
(
edit
)
Template:Mbox
(
edit
)
Template:Merge from
(
edit
)
Template:Merge partner
(
edit
)
Template:Reflist
(
edit
)
Template:Short description
(
edit
)