The technical tenet
The cultural tenet gets people on board. The editorial tenet defines what good looks like. The technical tenet determines whether any of that actually reaches the people – and the machines – that need it.
This is the tenet that's changed most dramatically in recent years. A decade ago, the technical question was simple: what format should the guide be in? Today, it encompasses where the guide lives, how it's structured, who can access it and whether AI tools can read it.
Format and platform
Your style guide needs to be online. Not as a nice-to-have. As a baseline.
An online guide is searchable, linkable, always up to date and accessible to anyone who needs it. A PDF is none of these things. If your guide currently exists as a static document, the single most impactful thing you can do is move it online.
The platform matters too. Your guide should be easy to update (so it actually gets updated), easy to navigate (so people actually find what they need) and easy to brand (so it feels like part of your organisation, not a generic wiki page).
Structure and findability
A style guide is only useful if people can find what they're looking for. That means thoughtful information architecture:
- Clear navigation – logical categories, intuitive labels, not too many levels of hierarchy
- Search – fast, accurate, tolerant of different search terms for the same concept
- Cross-referencing – related topics linked together so people discover guidance they didn't know they needed
- Exemplar content – real examples that show what good looks like in practice, not just rules about what to avoid
Structure and machine-readability
Here's where the technical tenet intersects with AI. If your style guide is going to serve AI tools as well as human teams, it needs to be structured in a way that machines can parse.
That means moving beyond prose. A beautifully written paragraph about your voice is lovely for human readers, but an AI tool needs structured data: attributes, values, examples and rules it can query programmatically.
The best approach is both. Human-readable guidance and machine-readable structure, in the same place. Your voice definition as a warm, engaging narrative and as a set of structured attributes. Your tone guidance as helpful prose and as a lookup table of contexts, audiences and appropriate registers.
This dual approach – human-readable and machine-readable in the same guide – is the direction that the most forward-thinking style guide platforms are moving in. It's the technical foundation that makes everything else possible: consistent AI-generated content, automated quality checks, integration with your content tools and a style guide that genuinely serves every content creator in your organisation, human and machine alike.
Access and permissions
Who can see your style guide? The answer should almost always be: everyone who creates content on your behalf. That includes permanent staff, freelancers, agencies and – increasingly – AI tools.
Openness is a strength. A style guide that's locked behind an internal login is a style guide that freelancers can't access, that agencies don't reference and that AI tools can't query. Make it available. If there are genuinely sensitive sections, restrict those. But default to open.
Analytics
If your style guide is online, you can track how it's being used. Which pages get the most visits? Which search terms return no results? Where do people spend the longest? This data tells you what's working, what's missing and where to focus your next update.
Don't underestimate the power of analytics for demonstrating value, too. Being able to say "our style guide had 2,000 visits last month, and the most-searched term was 'tone of voice for social media'" is a compelling argument for continued investment.