Skip to content
The craft of making ideas visible, audible and shareable.
Making

Before the Brand Book: A Short History of Style Guides

Style guide history traces how editors and organisations recorded shared choices. See how these guides changed and what their different forms are for.

Creative News Bulletin desk6 min read
Open notebooks and binder with handwritten and printed style guide notes on wooden desk with pen, coffee cup, and sticky notes

The most common mistake in style guide history is treating today’s brand book as the guide’s natural destination. That narrows a varied story into a design timeline and hides the practical work behind it: helping people make consistent choices when they edit, publish or communicate together.

There is no single origin point or straight line of development. The term “style guide” covers different tools made for different settings. Editorial reference works, a publisher’s house rules and an organisation’s identity manual may all guide style, but they answer different questions.

Style guide history

Before the term became common in organisational design, printers, editors and publishers had reasons to record preferred spellings, punctuation and ways to present information. The details varied by workplace and publication. A rule sheet could help an editorial team avoid revisiting the same decision on every page, while a reference book could offer guidance to a broader group of writers.

It is safer to describe this as a gradual, uneven development than to claim one invention began it. Printing made repeated decisions visible across editions: names, headings, dates and punctuation could look inconsistent if each contributor made them independently. Local conventions helped editors and compositors coordinate, though the exact records and practices differed.

Over time, editorial guidance took recognisable forms. Newspapers and publishers established house styles; scholarly communities developed conventions for citations and specialist writing. General reference works, such as dictionaries and manuals of usage, offered guidance beyond one organisation. These forms overlap, but a house style usually records a publication’s preferences, while a reference work serves a wider readership.

From editing to identity

Editorial guides focus on language and presentation: spelling, capitalisation, dates, quotations, captions or references. They make recurring choices easier to apply. They do not settle every question of meaning or replace an editor’s judgement.

As organisations developed more visual public materials, guidance could include logos, typefaces, colour, image treatment and page layouts. A visual identity guide helps contributors use these elements coherently across different formats. The shift was not a simple replacement of editorial rules by visual ones; many organisations still need both.

“Style guide” remains a broad label. A brand book often adds an account of an organisation’s identity, positioning and character alongside practical visual rules. A guide may be much narrower, such as a page of preferred spellings or instructions for using a logo. Names vary, so judge a document by what it explains and who needs it.

Different kinds of guides

  • Reference work: Check whether writers need guidance on general usage or citation conventions; if they do, choose a suitable external reference, but if they need organisation-specific decisions, add a house style alongside it.
  • House style sheet: Check whether a publication repeatedly makes the same editorial choices; if it does, record preferred names, spellings and formats, but if questions are rare, keep the record brief rather than building a large manual.
  • Editorial style guide: Check whether several writers produce recurring articles or notices; if they do, include rules and examples for headings, dates, quotations and specialist terms, but if contributors work in unrelated formats, separate the sections they do not share.
  • Visual identity guide: Check whether contributors use shared logos, colours, type or imagery; if they do, provide the approved files and show their use, but if no visual assets recur, avoid adding specifications that nobody needs.
  • Brand book: Check whether teams need both practical asset rules and a broader account of the organisation’s identity; if they do, connect those elements in one resource, but if users mainly need a quick production rule, provide a short reference they can reach directly.
  • Layered guide: Check whether different teams need different levels of detail; if they do, offer a concise starting point with linked specialist sections, but if one small group shares the same tasks, use a simpler document.

Say a community arts project has a coordinator, volunteer writers and a designer. The project’s invented starting point is two recurring confusions: writers alternate between “the studio” and “the workshop” for the same venue, and notices show dates in different forms. The coordinator records the official venue name and one preferred date format on a shared page, then adds a sample notice. The resulting decision is a short house style sheet, not a brand book; if the designer later needs recurring logo or colour rules, those can be linked as a separate visual section.

What guides contain

A guide is useful when its entries answer questions contributors actually face. Editorial sections might cover the organisation’s name, audience-facing terms, spelling, capitalisation and tone. Visual sections might link to approved logo files and explain type hierarchy, colour use, image treatment and how text sits with graphics.

Examples make abstract instructions easier to apply. Instead of “use a friendly tone”, show a short passage with direct wording and familiar terms, then note why it suits the audience. A sample layout can show a heading, caption and body text together, making their relationship clearer than isolated descriptions.

Mark which decisions are fixed and which depend on context. An official name may need to stay unchanged, while the tone of an event invitation can differ from that of a formal notice. Distinguishing requirements from suggestions helps contributors make sound choices without mistaking every example for a rule.

Maintaining a usable guide

Guides become hard to trust when they are difficult to find or contain decisions that no longer apply. Give someone responsibility for updates, put the document where contributors already work, and make revisions easy to spot. A shared document with clear headings may be more useful to a small team than a polished file that is cumbersome to change.

Repeated questions are useful signals. If contributors keep asking how to name a programme, credit an image or format a date, add a clear answer. If a rule causes confusion or rarely affects the work, reconsider it rather than preserving it for completeness.

For visual guidance, make the relevant assets available beside the instructions. A logo description cannot replace an accessible approved file. State who can approve exceptions too, so contributors know where to take a format that does not fit the usual rules.

Which guide fits your work?

Do small teams need a style guide?

They may need one if the same decisions keep recurring or materials require repeated corrections. A shared page can settle names, spelling and a few visual conventions without turning a small project into an administration task.

Is a style guide the same as a brand book?

No fixed definition applies to every organisation: a style guide may cover editorial or design rules, while a brand book often includes broader identity guidance. Look at the questions the document answers rather than relying on its title.

Should writing and visual rules be combined?

Combine them when the same contributors regularly need both kinds of guidance. If separate teams own the work, keep the sections distinct but linked through a shared contents page or index.

Guides for shared work

Style guide history is better understood as a set of responses to recurring coordination problems than as a march towards one standard format. Editorial teams needed ways to record language choices; organisations producing visual materials needed ways to make shared assets recognisable. The forms differ because the work differs.

When choosing a guide, start with the decisions that contributors repeat and the materials they actually make. A concise record of those choices, with an owner and a route for exceptions, gives the next person a usable starting point while leaving room for judgement.