Style guide starters

Don't want to think too much about your style guide? We've created a template covering the most common style guide elements. Copy and paste what you need and adapt it to fit your needs.

Voice and tone

1. Voice: Friendly, professional, and clear.
2. Tone: Supportive and helpful. Avoid jargon where possible.
3. Use active voice (e.g., "Click the button" instead of "The button should be clicked").

Writing style

1. Write in short, concise sentences.
2. Use plain language whenever possible.
3. Explain acronyms and abbreviations the first time they appear.
4. Use consistent terminology.

Formatting and structure

1. Headings:
   1. Use clear, descriptive headings.
   2. Use sentence case (e.g., Configuring your account).
2. Paragraphs: Keep paragraphs short (2–4 sentences)
3. Lists:
   1. Use bullet lists for options and steps.
   2. Use numbered lists for sequences.
4. Links: Embed links in descriptive text (Learn more about billing settings).

Terminology

1. Refer to your product or service consistently by its proper name.
2. Use customer-centric language (e.g., "you" and "your" instead of "the user").
3. Example terms (customize as needed):
   1. Sign in instead of log in
   2. Account settings instead of user preferences
   3. Help Center instead of knowledge base

Capitalization and punctuation

1. Use sentence case for headings.
2. Capitalize product names and feature names.
3. Use the Oxford comma in lists.
4. Avoid exclamation points unless celebrating something (Congratulations!).

Screenshots and images

1. Use clear, high-resolution images.
2. Crop images to focus on relevant areas.
3. Add captions where helpful.
4. If including steps, highlight the UI elements.

Examples and code

1. Format code snippets in monospace font.
2. Use consistent indentation.
3. Provide example outputs.

Accessibility

1. Use alt text for all images.
2. Avoid color as the only means of conveying information.

You can also search for other style guide templates that might work well for you. 

Thursday Bram has a nice template available in .docx format on her blog, available at: Download My In-House Style Guide Template to Use However You Want or as a Google Doc you can copy.

This is one of the fastest and most powerful approaches. Tell Owl Intelligence to follow an established style guide, then document only your exceptions or additions

For example, use something like the Google developer documentation style guide as a base. Then add style guide details for any specific additions or exceptions to that guide you'd like to use.

Your style guide might say:

Follow the Google developer documentation style guide.
Exceptions: Use "Help Center" instead of "knowledge base"; write out numbers one through nine instead of using numerals (1-9); use "email" as both a noun and verb (not "e-mail"); always capitalize "Internet."

Another example prompt:

Follow the Microsoft Writing Style Guide.
Exception: Use title case for all headings instead of sentence case (e.g. "Getting Started With Your Account" instead of "Getting started with your account").

The AI model that Owl Intelligence uses is already trained on many major style guides, so you don't need to copy and paste their full content—you can just reference them by name and note where your organization differs.

Commonly recognized style guides:

We built Owl Intelligence to recognize these major style guides:

• Google developer documentation style guide
• Google's Material Design Style guide
• Microsoft Writing Style Guide
• Apple Style Guide
• Chicago Manual of Style
• Associated Press Stylebook

Let us know if there's a common style guide we should include!

For more guidance on creating effective style guides, check out these resources:

•  The Write the Docs Style Guides page.
• A Write the Docs Portland 2021 talk: Deanna Thompson - Building a style guide from the ground up: lessons learned from a lone writer