A thin template style guide for product, technical and user-facing documentation: structure, templates, language standards and accessibility requirements a team can actually apply without a style council.
Download the PDFMost style guides fail the same way. They grow into a reference nobody opens, policed by a committee nobody wants to convene, and the documentation goes on being inconsistent anyway.
A style guide only works if applying it is cheaper than ignoring it. That means it has to be short enough to read once, specific enough to settle real arguments, and structured so a writer can find the answer without hunting.
This one covers structure, reusable templates, language standards and accessibility requirements, and it stops there. It is deliberately a starting point to adapt rather than a finished policy to adopt, which is why it is short.
Great tech doesn't sell itself.
Let's meet. It's free.
