What Belongs in a Content Style Guide

Most style guides fail in one of two ways. Either they are forty pages nobody opens, or they are a Slack message that says “keep it casual and on brand.” Both produce the same result, which is that every writer invents the house voice from scratch and none of them invent the same one.

A style guide is not a branding artifact. It is the thing that lets more than one person write for you without the output splitting into that many house styles. When it works, a new writer reads it once and hits the voice on the first draft. When it fails, you find out in the edit, one comment at a time, forever.

The Guide Exists to Settle Arguments Once

The point of a style guide is not to sound official. It is to stop you from making the same decision over and over.

Every content operation has a handful of questions that come up on almost every piece. Do we use the Oxford comma. Is it “sign up” or “signup.” Do we write out numbers under ten. Do we allow second person. Do we let a writer open with a question. None of these has a right answer, which is exactly why they are worth deciding. An arbitrary rule applied consistently reads as a voice. The same rule left open reads as noise.

Without the guide, you settle each of these in the edit, on each draft, with each writer. That is not editing. That is retyping the same preference until you retire. Write it down once and the argument is over.

This is the same logic that makes a good brief cheaper than a revision round. A tight brief settles the per-piece decisions before writing starts. A style guide settles the decisions that repeat across every piece, so the brief does not have to carry them again and again.

Write Down the Things Writers Disagree On

Here is the test for whether an entry belongs in the guide. Would two competent writers plausibly do it differently? If yes, it belongs. If no, it is filler.

Nobody needs a paragraph telling them to spell words correctly. What they need is your position on the choices that are genuinely open. How formal is too formal. Do you allow contractions, and the answer for most modern content is yes. Are exclamation points banned, rationed, or fine. Do you want the writer to have a point of view or to stay neutral. Do you use “you” or keep it in the third person.

Most published style guides waste their first ten pages restating a grammar textbook, then run out of energy before they reach the decisions that actually vary. Invert that. Lead with the calls only your house makes, and skip the ones any professional already knows.

Show the Voice, Do Not Describe It

“Professional but approachable” means nothing. Every writer has heard it and every writer interprets it differently, which is how you end up with one draft that reads like a legal memo and another that reads like a group chat.

Voice does not survive being described in adjectives. It survives being shown. The single most useful section of any style guide is a short table of before-and-after rewrites, one flat sentence beside the version you would actually publish, with a line on what changed and why.

Give a writer three of those and they will infer more about your voice than from a page of guidance. They can see where you cut a hedge, where you swapped a category noun for a concrete one, where you let a sentence be short. That is a pattern a person can match. “Approachable” is not.

If you have already published pieces you are happy with, name two or three and say what you like about each. A live example beats an invented one, because the writer can see the whole thing in context instead of a fragment.

Include the Boring Operational Rules

Voice gets the attention, but consistency usually leaks somewhere less glamorous. Formatting, structure, and the mechanics of a finished piece are where a library slowly turns uneven, one small default at a time.

Put the unglamorous rules in writing.

• Heading style. Title case or sentence case, and how deep the hierarchy goes.
• Paragraph length. If you want short paragraphs, say so, because the default is long.
• Internal linking. How many, with real anchor text, and the rule against "click here."
• How you handle numbers, dates, currencies, and units.
• Formatting of lists, tables, and callouts, and when to reach for each.
• The full deliverable. Meta description, title tag, headings, and any schema, not just the prose.

None of this is exciting, and all of it is the difference between a set of pieces that feel like one publication and a set that feel like a folder of documents from different people. When you scale content across several writers, these rules are the part that quietly holds the standard together, because they travel with the work instead of living in one editor’s head.

Say What You Never Do

A short banned list does more work than a long approved one. It is faster to write, faster to read, and it removes ambiguity in the place where ambiguity costs the most.

List the words and constructions you do not want. The corporate filler you are tired of seeing. The tired phrases that show up in every second draft. The claims a writer is not allowed to make without a source. The formatting tics you find lazy. A writer can absorb a “never do this” list in a minute and apply it immediately, whereas a sprawling “always do this” list gets skimmed and forgotten.

This section also protects you from the average. Left alone, a lot of drafting drifts toward the safe middle of what everyone else publishes, and a banned list is how you pull it back toward something specific. It is the cheapest originality control you have, because it names the defaults before they reach the page.

Keep It Short Enough to Finish

A style guide only works if writers read it, and the longer it gets the fewer of them do. Past a certain length it stops being a guide and becomes a document you point to after the fact, which is not the same thing.

Aim for something a new writer can read in one sitting and keep open in a second tab. Put the sharpest, most house-specific rules at the top, where they get read, and push the reference material that people look up as needed toward the back. If a section has never once changed a draft, it is decoration, and decoration is what makes people stop reading the parts that matter.

Treat it as a living document. When the same correction shows up in three edits, that is a missing entry telling you where it goes. Add the rule, and you never make that correction by hand again. The guide should grow from the edits you actually keep making, not from a template of everything a style guide could theoretically cover.

Where the Style Guide Sits in the Stack

The style guide is one layer. It handles the decisions that repeat across every piece. The brief handles the decisions specific to one piece. The editor handles the judgment that neither document can fully encode. Confuse the three and each one gets bloated with work that belongs to another.

A guide that tries to specify every possible piece becomes a brief and stops being reusable. A brief that restates the house voice on every project is doing the guide’s job twice. Keep the standing rules in the guide, the per-piece decisions in the brief, and let the editor apply the judgment that lives between them. The named person on the byline still has to sound like a person, and attributing work to a real author only helps if the voice underneath is consistent enough to belong to one.

What to Do With This

If you commission writing from more than one person and you do not have a style guide, you have one anyway. It just lives in your head, and it only gets applied when you happen to catch a deviation in the edit. Writing it down moves the standard out of your memory and into a place every writer can reach before they draft.

Start small. Open the last five pieces you edited and write down every correction you made that was a preference rather than an error. That list, cleaned up, is the first useful draft of your guide, and it is built entirely from decisions you were already making by hand. A guide grown from real edits beats a borrowed template every time, because it addresses the arguments you actually have. That consistency is also what lets a content strategy hold together as it grows, since a plan is only as coherent as the pieces executing it.

At Postdex, every piece in the catalog is edited to a single standard before it is listed, and the commissioning desk writes to a house voice held steady across the set, so a cluster reads like one publication rather than a folder of near-misses.