About this guide | Google developer documentation style guide | Google for Developers
developers.google.com · 590 words · saved by 1 readers
Editorial style guidelines for public-facing Google developer documentation.
About this guide This style guide provides editorial guidelines for writing clear and consistent technical documentation for an audience of software developers and other technical practitioners. If you're new to the guide and looking for introductory topics about our style, then start with Highlights, Voice and tone, and Text-formatting summary. Otherwise, use the guide as a reference document for specific questions. For example, you can look up terms in the word list. Editorial resources We recommend using the following editorial resources. Reference hierarchy Use the following…
saved by
related reading
- styleguide | Style guides for Google-originated open-source projectsgoogle.github.io
- Google Style Guidesgoogle.github.io
- styleguide | Style guides for Google-originated open-source projectsgoogle.github.io
- Command Line Interface Guidelinesclig.dev
- Design Docs at Googleindustrialempathy.com
- Technical Writing: a bibliography, tips, and tricks — Niklas's blogpivic.blog
- DevDocs API Documentationdevdocs.io
- How to Write an Effective Software Design Documentrefactoringenglish.com
- Rules of Machine Learning: | Google for Developersdevelopers.google.com
- Say precisely what you mean.index.how
- Google C++ Style Guidegoogle.github.io
- GitHub - google-research/tuning_playbook: A playbook for systematically maximizing the performance of deep learning models.github.com