Skip to content

Guides

Write a style guide for your help center

When several people write help articles, the center slowly turns into several styles. A one-page guide keeps it consistent without slowing anyone down.

Last reviewed

Start from what customers see

Pick the names for features and plans that appear in your product and use only those in every article.

Set the voice in a few lines

Say whether you write you or we, how formal to be and what to avoid. Include two examples of a good sentence.

Standardize the structure

Decide the order: a one-line answer, numbered steps, then notes and related links. Customers learn where to look.

Write steps one action at a time

Each step has one action and starts with a verb. Put the expected result in a separate line.

Decide how to use screenshots

Use them where words are not enough and note who updates them. Out-of-date screenshots hurt more than none.

Keep it short and review it

One page that people read beats ten they do not. Revisit it when the product or tone changes.

Questions

How long should a style guide be?

One page is enough for most small teams. If nobody reads it, it is too long.

Do we need one for a small help center?

If more than one person writes articles, yes. It saves editing time and keeps the center consistent.

Who owns the style guide?

One person, who can make final calls on wording and structure.

Written by Flatdesk, a help desk for small support teams at one flat price per agent. Try it free for 14 days, no card.