What a style guide is
A style guide is a short written record of the choices you make about how your content looks and sounds. It answers the small questions that otherwise get decided again every time you write: Is it “email” or “e-mail”? Do headings use title case? Do you write “10” or “ten”? Do you address the reader as “you”?
None of these choices is objectively right. What matters is that you make them once and apply them consistently. Readers rarely notice consistency, but they do notice when it is missing. A page that spells a name two ways or switches tone halfway through can make the whole piece feel less careful.
Who needs one
Anyone who publishes more than occasionally benefits. If you work alone, a style guide saves you from rethinking decisions and from forgetting what you decided six months ago. If you work with others, it keeps several writers sounding like one voice and gives editors something specific to point to instead of arguing over personal preference.
It does not need to be long. A single page that people actually use is better than a forty-page manual that no one opens.
Start from your audience and purpose
Before listing rules, think about who you are writing for and what impression you want to create. A guide for beginners might call for friendly, plain language and short sentences. A technical reference might favor precision and a more formal tone. Your reader profile and any existing audience research can inform these decisions. Style choices should come from the reader’s needs, not from habit.
What to include
Keep the first version small. These areas cover most everyday questions.
Spelling and language
Pick a regional spelling standard, such as American or British English, and say which dictionary you follow if you want a tiebreaker. List words you use often that have more than one acceptable form, such as “website” or “web site,” and record your choice. Add the names of people, places, products and organizations you mention frequently, spelled exactly as they should appear.
Voice and tone
Describe how the writing should sound in a few plain sentences or short bullets. For example: “Direct and friendly. Explains terms the first time they appear. Avoids hype.” You might also note whether you use contractions, whether you address the reader as “you,” and whether humor is welcome. Include a short example of a sentence that fits and one that does not.
Capitalization
Decide how to capitalize headings: either title case (most major words capitalized) or sentence case (only the first word and proper nouns). Sentence case is easier to apply consistently.
Numbers, dates and units
Choose a rule for numbers, such as spelling out one through nine and using numerals for 10 and above, and note exceptions such as measurements or percentages. Set one date format and one way to write times. If you use units, decide whether to spell them out or abbreviate them.
Punctuation
Note any choices that vary between writers: whether you use the serial comma, how you write dashes, and whether you put one space or two after a period (one is standard in current practice).
Formatting
Record how you use headings (how many levels, whether they are descriptive), when to use bulleted lists versus paragraphs, how to style emphasis, and how long paragraphs should typically be. Include how you write link text and how you label images. If accessibility matters, which it should, note your standards for alternative text and heading structure here.
Sources, credits and corrections
Write down how you credit sources and collaborators, how you mark sponsored material, and how you handle corrections. A consistent approach to these builds trust over time.
Keep it findable and short
Format the guide so people can skim it. Use headings, short bullets and a few examples. Put the most common questions first. Store it somewhere easy to reach, such as the same folder as your drafts, and mention it in your workflow so it gets used. A guide hidden in a forgotten document does not help anyone.
Grow it from real edits
You do not need to predict every decision in advance. A good method is to begin with a handful of rules, then add to the guide whenever you catch yourself making a decision for the second time. If you fix the same inconsistency in two different drafts, that is a sign it belongs in the guide.
When you do an editing pass and spot a recurring issue, write down the rule and an example. Over time you end up with a guide that matches how you actually work.
When to break your own rules
A style guide is a tool, not a law. If a rule produces an awkward result in a particular case, it is fine to make an exception, ideally one you note so others understand it. Review the guide now and then, remove rules nobody follows, and update ones that no longer fit. Changing a rule is fine; just apply the new rule consistently going forward, and note the date or version.
Using it in the editing process
A style guide fits best in the consistency pass, after structure and wording are settled and before the final proofread. Use it as a checklist: search for variant spellings, check capitalization in headings, scan number formats. Searching for specific terms is much faster than trying to spot inconsistencies by eye.
If you work with others, the guide also makes feedback easier, since a comment like “per the style guide, we use sentence case for headings” is specific and carries no personal criticism.