Mailchimp, compiled

Mailchimp publishes the most complete openly licensed content style guide there is. It is written for people, like every guide of its kind, and nobody has shown what it looks like once the machine-actionable parts are pulled out of it.

So this page does that, on somebody else's guide rather than a convenient invented one, and reports what would not convert as carefully as what would.

It sits under brand voice guidelines, and the same compilation runs automatically when you answer the eleven questions about your own voice.

What does Mailchimp's guide actually specify?

More mechanically than almost any other published guide. Its grammar and mechanics section is unusually direct, and this is the part that converts without argument.

Mechanical rules stated in the guide, checked 17 August 2026
RuleWhat the guide says
Serial commaUse the serial comma, also known as the Oxford comma, when writing a list
Exclamation marksUse them sparingly and never more than one at a time, and never in failure messages or alerts
ContractionsEncouraged, for an informal and friendly tone
NumbersSpell out a number that begins a sentence, otherwise use the numeral, including ordinals; numbers over three digits take commas
RangesA hyphen indicates a range or span of numbers, and a period between times
DatesSpell out the day and the month; abbreviate only where space demands it
TimesNumerals with am or pm and a space between, and no minutes on the hour
AbbreviationsSpell out on first use where a reader might not recognise it
AmpersandsDo not use one unless it is part of a company or brand name
EmojiInfrequently and deliberately
File extensionsAll uppercase without a full stop, lowercase s to pluralise
Job titlesCapitalised for a specific role, lowercase for the role in general

What do those become once compiled?

Almost all of them map straight onto a checker without interpretation. That is the test of whether a rule is really a rule: two people implementing it independently produce the same check.

The same rules as machine-checkable constraints
RuleWhat a checker does with it
Serial commaA consistency check across the document
Never more than one exclamation markA count within a scope, raised to an error in alerts
AmpersandsA pattern match with an exception list for brand names
Numbers over three digits take commasA pattern match
Times formatted as numerals with am or pmA pattern match
File extensions uppercaseA capitalisation check
Spell out abbreviations on first useA conditional check: require the expansion before the short form
Contractions encouragedReportable but not enforceable, because encouraged is not a threshold

Note the last row. Encouraged is the softest word in any style guide and it is where compilation starts to strain: you can count contractions, but the guide never says how many is enough, so any threshold would be ours rather than theirs.

Which checks these map onto covers the mechanics of that, and this tool ships the same shape of file with every download.

Which of its rules could not be compiled?

The honest half. These are real instructions, followed daily by the people who wrote them, and none of them survives conversion into a check.

That is not a failure of the guide, and it is not a failure of compiling. It is the boundary: about a fifth of a good style guide is rules and the rest is context that makes the rules make sense, and the fifth is the part a model can act on.

What does compiling it reveal about the original?

Two things, and both are compliments.

First, how much of it is decided. Most published guides talk about personality and leave the mechanics implicit; this one commits, in writing, to the serial comma and to how a time is formatted. That is why it compiles at all.

Second, how much a guide relies on the reader being a person. The tone-varies-with-context idea is the best thing in it and the least convertible, which is a fair summary of the whole exercise: the parts a file cannot carry are named rather than pretended away.

Licence and attribution

The Mailchimp Content Style Guide is published by Mailchimp under a Creative Commons Attribution-NonCommercial 4.0 International licence, verified from the licence file in its own repository on 17 August 2026. The licence permits adaptation with credit and forbids commercial use.

This page is that adaptation and this is the credit. It carries no advertising: the article template on this site has no advertisement slot at all, which is what keeps the non-commercial condition true rather than merely claimed.

The rules above are quoted and summarised for the purpose of demonstrating compilation. If Mailchimp would rather this page did not exist, it comes down and the demonstration is rebuilt on the GOV.UK style guide, which carries no non-commercial condition.

Where these come from

Every claim above is quoted from one of these, and each was read on the date beside it. If one of them has changed since, the page is wrong and we would like to know.

That was somebody else's guide. For yours, answer eleven questions and get the compiled version.