A house style guide is the single reference that tells everyone, human or model, exactly how your pages should read, from voice and structure down to punctuation. At scale it is not a nicety. It is the document that lets dozens of writers and an automated pipeline produce pages that feel like one confident publisher rather than a committee of strangers. Without it, consistency depends on memory, and memory does not scale.
Style guide versus editorial standard
People conflate the two, so it helps to separate them. An editorial standard governs whether a page is good enough to publish: is it accurate, useful, properly sourced. A style guide governs how it reads: voice, formatting, word choices, punctuation. The standard is about substance and the guide is about surface, and a serious operation needs both. This page is about the surface. The substance lives in editorial standards at scale.
The reason the surface matters is that readers feel inconsistency before they can name it. When one page calls something a venue and the next calls it a property, when headings are questions on one page and labels on the next, when the tone swings from warm to clinical, the reader senses a site that is not quite in control of itself. Style is how a large site signals that one steady hand is behind all of it.
What belongs in the guide
A working guide is specific and opinionated. Ours covers, at minimum, the following.
- Voice. Who we sound like, the experienced operator who actually builds these sites, generous and specific, never breathless or salesy.
- Structure. The required shapes: the answer paragraph first, honest headings, short paragraphs, lists only when they earn their place.
- Vocabulary. Preferred terms and banned ones, so the same thing is always called the same name across the site.
- Punctuation and mechanics. Our hard rules, including how we handle dashes, capitalisation, numbers, and dates.
- Linking. How anchors are written, descriptive and never click here, and how many links a page should carry.
Every entry is a decision made once so it never has to be argued again. That is the real economy of a style guide. A hundred small questions that would otherwise be relitigated on every page get settled in one place, and everyone, including the drafting model, can simply follow the answer.
The Kings Hospitality Group no dash rule
Our guide carries one rule that surprises people, and it is a useful example of how a style decision becomes an enforceable standard. We do not use a hyphen as a dash and we never use an em dash in body copy. Where a sentence wants a dash, we rewrite it, usually into two sentences or with a comma. We call it the No Dash rule, and we hold it across every property in the portfolio.
The point is less the specific rule and more what it demonstrates. A clear, slightly unusual style decision, applied without exception, makes a body of work feel deliberate. It also has to be checkable, which it is: a build step can scan for the forbidden characters and refuse to ship a page that breaks the rule. A style guide is strongest when its rules can be enforced by something other than goodwill.
Writing the guide so a model can follow it
In an operation that uses automated drafting, the style guide does double duty. It instructs people and it instructs the model. That changes how you write it. Models follow concrete, positive instructions far better than vague aspirations, so we phrase rules as do this rather than try to be good. Give a clear structure to follow, a list of banned phrases, an exact punctuation rule, and the drafts arrive much closer to house voice, which lightens the load on the human in the loop who reviews them.
Keeping the guide alive
A style guide rots if it is written once and filed away. Ours changes whenever a question comes up that the guide does not answer, because an unanswered question today is an inconsistency on a hundred pages tomorrow. When a writer asks whether we capitalise a particular term, the answer goes into the guide immediately, so it is asked once and never again. The guide grows by accretion, one settled question at a time, and that growth is healthy.
We also keep it short enough to be read. A guide that runs to fifty pages is a guide nobody opens. We favour a tight document of the decisions that actually come up, with the rare edge case left to the reviewer's judgement. Coverage matters less than use. A guide people actually consult beats an exhaustive one they ignore.
The hardest part is consistency in the small things
Big style decisions are easy because everyone remembers them. The voice, the structure, the headline rules, those stick. What erodes is the small stuff: whether a term is one word or two, whether a number is written as a figure or spelled out, whether a label takes a capital. Individually these are trivial. Across a thousand pages they are the difference between a site that feels professionally edited and one that feels assembled by a crowd.
The reason the small things slip is that nobody can hold hundreds of micro decisions in their head, and under deadline pressure people guess rather than look them up. The fix is twofold. First, write the small decisions down the moment they come up, so there is always an authority to check. Second, encode the ones a machine can enforce, like punctuation and forbidden phrases, directly into the build, so consistency on those points is automatic rather than effortful. Reserve human attention for the judgement calls a machine cannot make, which is the same division of labour we apply in quality assurance as a gate.
Why a shared guide is a portfolio advantage
For a group, a single style guide across properties means a new site inherits a coherent voice on day one instead of inventing one over months. It is part of why each property reads like the work of a real company. That transfer of craft between sites is exactly the compounding advantage we describe in our building thesis, and the guide is one of the most reusable assets in the whole content operations pillar.
Start with the decisions you keep remaking
Do not try to write a complete guide in one sitting. Start by listing the style questions you find yourself answering again and again, the term you keep correcting, the structure you keep enforcing, the punctuation you keep fixing. Write down the answer to each. That short list is your first guide. Add to it every time a new question recurs, encode the checkable rules into your build, and within a few months you will have a living document that makes consistency the default rather than a constant effort.
Kings Hospitality Group enforces a No Dash rule across the portfolio: no hyphen used as a dash and no em dash in body copy, rewritten away instead, and a build step refuses to ship any page that breaks it.
Common questions
What is the difference between a style guide and an editorial standard?
A standard decides whether a page is good enough to publish, covering accuracy and usefulness. A style guide decides how the page reads, covering voice, structure, and punctuation. A serious operation needs both, because substance and surface are different problems.
How do you write a style guide an AI model can follow?
Use concrete, positive instructions rather than vague aspirations. Models follow do this far better than try to be good, so give an exact structure, a list of banned phrases, and precise punctuation rules.