Key Point: Use this guide as a style reference
for our developer documentation.This style guide provides a set of editorial guidelines for anyone writing
developer documentation for Google-related projects.
Goals and audience
The primary goal of this guide is to codify and record decisions that
Google’s Developer Relations group makes about style. The guide can help you
avoid making decisions about the same issue over and over, can provide editorial
assistance on structuring and writing your documentation, and can help you keep
your documentation consistent with our other documentation.
This style guide doesn’t apply to all Google documentation; there
are multiple Google documentation groups that have their own style guides. This
particular guide is specifically for Google-related developer documentation, and
for any other project that wants to use it. But if your project is already using
another style guide, then you can continue to use that guide instead of this
This guide isn’t intended to provide an industry documentation standard, nor
to compete with other