-
Notifications
You must be signed in to change notification settings - Fork 52
/
CreateAStyleGuide.rst
101 lines (64 loc) · 2.49 KB
/
CreateAStyleGuide.rst
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
********************
Create a Style Guide
********************
=================================================================
How to swim in the deep water - A lone writer’s guide to survival
=================================================================
Getting Started
================
when you're ready to start a company style guide, here are some general ideas about how to do it.
* Choose an external style guide (Microsoft Manual of Style, Chicago, etc.)
* Company product names, including correct trademark attribution, capitalization, and any allowed short forms.
* English, British, Australian, English?
* Style
* Present tense
* Second person
* Active voice
* Conversational tone
* Do not use courtesies (please, thank you, and so on)
* Decide whether to use contractions
* Title vs. sentence case for:
* Headings
* Figure captions
* Table titles
* Table column headings
* Consider global and ESL readers
* One word, one meaning
* Do not use colloquialisms
* Do not use idioms
* Parallelism in:
* Presenting all tasks the same way (e.g., start with a prerequisite, then numbered steps, then a postreq/what to do next)
* Bullet lists - Within a given list, all bullets should be phrases or sentences. (Note that this Style Guide doesn’t follow this recommendation. At times, such as for internal use only, it’s not worth the time to reach for perfection.)
* Same order of info/syntax/examples for all reference sections
* Basic graphics/screenshot guidelines:
* Source tool (e.g., Snagit, Visio, Omnigraffle, etc.)
* Output format (SVG, PNG, etc.)
* Callout style (wording and line color/width/style)
* Legalese page - get the Legal department to sign off:
* Third party references
* Disclaimers (use product at your own risk)
* Proprietary/confidentiality statements
* Copyright
* Progressive disclosure
* One idea per paragraph
* Paragraphs follow each other in a logical order
Copyedit checklist:
====================
* spell check
* punctuation:
** check for double spaces
** if you used the following correctly:
*** .. extra period - check for and delete
*** , comma
*** ; semi-colon
*** : colon
*** () parenthesis
*** ' apostrophe
* subject/verb agreement
* numerals
* fonts and capitalization
* headings - logical and in order
* tables - are table formats consistent?
* links - correct and working
* headers and footers, if you're using
* notes & peripheral data - footnotes, endnotes, appendixe