concept-explainer

4 Content Style Guide Examples, With Before-and-After Edits

This article shows four public style guides in action through original before-and-after edits from a fictional report-export help article. Mailchimp guides tone by dropping humor when users are frustrated, Atlassian adds a concrete recovery step, GOV.UK makes the final day inclusive with on or before, and Microsoft rewrites click here as a descriptive link label. It ends with a test for adopting borrowed rules.

November 20, 2026
·
6
min read
A man and a woman are reviewing a document at a wooden table with a laptop and notebook.

Four public style guides and the edits they help you make

Content style guide examples worth keeping on hand include Mailchimp for adjusting tone, Atlassian for explaining how to recover from an error, GOV.UK for wording a deadline, and Microsoft for naming a link's destination. Each maps to a specific editorial decision: Mailchimp tells you when to drop a joke, Atlassian tells you how to give a reader a next step, GOV.UK tells you how to word a cutoff date, and Microsoft tells you how to label a link so it means something on its own. A content style guide governs the words readers see, rather than the page's colors or layout.

Mailchimp, for instance, gives voice and tone a dedicated section you can turn to when a line sounds wrong even though it's accurate. The edits below are original examples from a fictional help article about exporting a report. When the export fails, the same line has to acknowledge what went wrong and tell the reader what to do next.

Mailchimp and Atlassian: Edit a failed-export message twice

"We couldn't export your report. There goes our perfect record!" jokes about a failed export and leaves the reader without a next step. Mailchimp's style guide helps an editor adjust the tone for a frustrated reader; Atlassian's error-message guidance helps the editor explain what the reader can do next.

In this fictional help article, the message appears after someone selects Export report and no file is created. The sample copy in both passes is original; neither Mailchimp nor Atlassian wrote it.

Mailchimp: Drop the joke

Mailchimp's Voice and Tone guide distinguishes a steady brand voice from a tone that shifts with the reader's emotional state. The guide puts clarity ahead of entertainment and recommends keeping a straight face if you're unsure whether humor fits.

Before: "We couldn't export your report. There goes our perfect record!"

After: "We couldn't export your report."

The edit removes the punch line and keeps the same information. A conversational brand can still sound like itself when it speaks plainly. A reader who just completed an export might welcome a playful aside; someone waiting for a file that never arrived has a different reason to pay attention. The calmer line respects that difference, but it still leaves the reader stuck.

Atlassian: Give the reader a way forward

Atlassian's guidance on error messages asks writers to say how the reader should respond after an action fails. If the cause is unknown, the guide says to acknowledge the problem and offer a way forward without inventing a reason.

In the fictional app, the error message includes a Retry export button. Selecting it starts a fresh export with the same report filters. The app has no reliable explanation for the failure.

Before: "We couldn't export your report."

After: "We couldn't export your report. Select Retry export to try again with the same filters."

This edit keeps the calmer line intact and names the control the reader can use right there. It also tells them what they can leave alone: their filters. The instruction promises another attempt, so it holds true even if the next export fails.

GOV.UK: Make the last day to export unmistakable

The Dates entry in GOV.UK's A to Z style guide, part of its content and publishing guidance, tells writers to use "on or before" when stating a deadline. That wording makes clear that the named date is included.

A hand writes a circle on a calendar page with a red pen.
Clarifying whether the final day is included prevents missed exports.

A friendly export notice still has to tell readers when their access ends. Start with what the service allows, then check whether the draft says the same thing.

Intended cutoff in this fictional example: Readers can still export their report on 2 June. That's the final calendar day; the exact cutoff time and time zone are unconfirmed.

  • Before: "You can export your report until 2 June."
  • After: "Export your report on or before 2 June."

"Until" leaves readers to guess whether they can come back on 2 June and still export. "On or before" answers yes without promising that access lasts the whole day. Before publishing, ask the team that controls access what time exports stop and which time zone the service uses. If the cutoff is tied to a clock time, put the confirmed time and zone beside the date rather than assuming midnight.

The date format is a separate choice. The GOV.UK example follows its day-before-month convention and leaves off the ordinal suffix. Use the format your readers expect, but keep the final day explicitly included. Once readers know when to act, they still need to spot the link to the export instructions.

When a help article sends readers to a separate page for export steps, Microsoft's guidance on link text recommends using the page title or a brief description instead of a generic phrase like "click here." In the report export article, the label should tell readers they'll get instructions before they follow the link.

Both versions below point to the same fictional help page. Bold marks the linked words.

  • Before: For step-by-step instructions on exporting your report, click here.
  • After: Follow the report export instructions.

The before version gives the purpose in the surrounding sentence. The after version puts that information in the label itself: "report export" names the task, and "instructions" tells readers to expect a guide rather than a file download. The label still makes sense if someone encounters it in a list of links without the rest of the sentence.

Where the house rule goes further

The W3C's Understanding Link Purpose (In Context) explains that WCAG Success Criterion 2.4.4 allows the link text and its programmatically determined context to identify the purpose together. Text in the same sentence can supply that context, so "click here" doesn't automatically fail this criterion.

As a house rule for help articles, prefer a label that can stand on its own. Read the linked words without the sentence: if they sound like a download and the destination is a guide, name the guide or describe what it teaches.

Test a borrowed rule on a draft neither editor has seen

A borrowed style rule can look clear beside a worked example and still leave editors guessing on a new draft. Before adding the rule to your house guide, give two editors the same unmarked passage and check whether they independently agree on when it applies and can edit without changing the meaning.

Turn Your Blog into a Sustainable Organic Demand Engine with Structured Content

HarperFlow publishes highly structured articles featuring FAQs, data tables, and direct-answer blocks that meet the rigorous citation standards required by AI search engines. By continuously auditing and improving your content through AI answer analytics, HarperFlow helps your site build long-term authority and visibility that outlasts ad-dependent strategies.

Start Your Trial Today →

Pick a comment you keep leaving in reviews. Turn it into a rule by writing down what triggers the edit, what to change, and when to leave the copy alone. If your usual comment is "spell this out," the trigger might be the first use of an unfamiliar abbreviation. The preferred edit is to spell it out on first use. An exception might be an abbreviation in a product label that readers need to match exactly on screen.

Give both editors the rule and a fresh passage neither has seen. Leave out the model answer and ask each editor to mark where the rule applies, make the edit, and explain what changed for the reader. Compare their explanations alongside the edits.

Keep the rule if both editors make the same decision and preserve the same meaning. Equivalent wording counts.

If they disagree about where the rule applies, clarify the trigger or the exception and try again on another passage. If the edit depends on a fact the editors can't verify, name who can confirm it and record that handoff before adding the rule to the guide.

Sources

  1. Voice and Tone | Mailchimp Content Style Guide
  2. atlassian.design
  3. A to Z style guide
  4. learn.microsoft.com
  5. Overview - Error messages - Atlassian Design
  6. learn.microsoft.com
  7. Understanding Success Criterion 2.4.4: Link Purpose (In Context) | WAI

Frequently Asked Questions

How do I know when to drop humor from an error message?

Check the reader's emotional state first. Mailchimp's Voice and Tone guide notes voice stays steady but tone changes, clarity beats entertainment, and if unsure you should keep a straight face. A frustrated user waiting for a failed export needs plain language, not a joke.

What should I write if I don't know why an action failed?

Don't invent a cause. Atlassian's guidance says an error appears after an action and should state what happened, consequences, and next steps, and if the reason is unknown just say something went wrong while offering a solution.

Does using "click here" automatically fail WCAG?

No. The W3C explanation for 2.4.4 allows purpose to be determined from link text plus programmatically determined context, and G53 specifically allows the enclosing sentence. Assistive tech can list links out of context though, so a standalone meaningful label still helps users.

How specific should a retry instruction be?

Name the control the reader will use and what stays the same. For example, Select Retry export to try again with the same filters promises another attempt, not success, so it remains accurate even if the next try fails.

What is the difference between a content style guide and a visual style guide?

A content style guide governs the words readers see, like voice, error recovery, deadlines, and link labels. Visual guidance covers colors and layout, which do not tell you how to phrase a cutoff or a recovery step.

How do I write a deadline that leaves no doubt about the last day?

Use on or before instead of until to show the named date is included. The GOV.UK A to Z guide uses Submit the form on or before 6 September 2025 as an example and writes days without ordinal suffixes like 2 June rather than 2nd June.

Should I always copy GOV.UK's day-before-month date format?

No, format is a separate choice from inclusion wording. GOV.UK leaves off ordinal suffixes and shows day before month, but your guide should use the order your readers expect while keeping the phrase that makes the final day explicit.

Do I need to add a time and time zone to every deadline?

Add them only when you have a confirmed cutoff time. The article example notes the time and zone were unconfirmed, so you should ask the team that controls access what time exports stop and publish that confirmed time and zone beside the date.

Turn Your Blog into a Sustainable Organic Demand Engine with Structured Content

HarperFlow publishes highly structured articles featuring FAQs, data tables, and direct-answer blocks that meet the rigorous citation standards required by AI search engines. By continuously auditing and improving your content through AI answer analytics, HarperFlow helps your site build long-term authority and visibility that outlasts ad-dependent strategies.

Start Your Trial Today
Written by
Hesham Mashhour
Founder @HarperFlow

Lover of all things automation and all things content.