Content Style Guide
A content style guide records shared language conventions so contributors write consistent, understandable product content.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/content-style-guide/
01What it means
A content style guide documents editorial choices such as terminology, capitalization, punctuation, voice, tone, and recurring interface wording. It turns common writing decisions into reusable guidance with examples. A visual design system governs presentation and components; a content style guide governs language choices, though the two should work together.[1][2]
02Why it matters
Inconsistent labels can make one concept seem like several and create extra review work. Shared conventions help writers, designers, engineers, and translators make routine choices without repeatedly reopening the same debate.
03When to use it
Use it when several people create interface text, help material, or notifications. Start with recurring decisions and observed confusion. A guide should allow context-sensitive judgment rather than enforce a brand voice at the expense of clarity during errors or sensitive tasks.
04How it works
- Collect recurring language decisions and inconsistent terminology from real content.
- Define audience, voice, tone adjustments, and preferred terms.
- Provide concise rules with relevant before-and-after examples.
- Make guidance searchable and connect it to design and review workflows.
- Assign ownership and update rules when research or product changes reveal a better choice.
05A practical example
A payment product uses “workspace,” “organization,” and “team” for the same account container. Its style guide selects the product’s canonical term, explains exceptions, and supplies examples for invitations and errors. Reviewers then apply one clear vocabulary across flows.
06Where it breaks
Consistency alone does not guarantee comprehension. A guide can grow into an unsearchable rulebook, and conventions may need adaptation for different languages. Examples must remain aligned with actual product behavior.
Common mistakes
- Writing abstract voice adjectives without usable examples.
- Applying playful tone to stressful errors.
- Treating the guide as permanent and rejecting evidence-based exceptions.
07Sources
- Style guidesGovernment Digital Service · Government guidanceStyle guides
- Welcome to the Microsoft Writing Style GuideMicrosoft · Official documentationWelcome to the Microsoft Writing Style Guide