Style guides for Google-originated open-source projects
HTML Python XSLT CSS JavaScript Emacs Lisp Other
Latest commit b282a74 Jan 5, 2017 @geoffromer geoffromer committed on GitHub Merge pull request #210 from roooooooot/patch-1
Fix a typo
Permalink
Failed to load latest commit information.
cpplint Revert "Fix the `cpplint.py` `build/endif_comment` check." Sep 30, 2016
docguide Replaced HTTP where HTTPS been awailable. Apr 1, 2016
include Update and replace JavaScript style guide. Nov 18, 2016
README.md Update and replace JavaScript style guide. Nov 18, 2016
Rguide.xml Reverted XML namespace name changes Apr 28, 2016
angularjs-google-style.html Update and replace JavaScript style guide. Nov 18, 2016
cppguide.html Fix a typo Dec 31, 2016
cppguide.xml Update C++ style guide to 4.45. Sep 8, 2014
eclipse-cpp-google-style.xml Add Google C++ Eclipse style config. Jun 29, 2012
eclipse-java-google-style.xml java style guide and eclipse configuration update Feb 3, 2014
google-c-style.el Add autoload magic comments for the functions exposed by google-c-style. Sep 29, 2014
google-r-style.html Restore redirect to Rguide.xml from r105. Jul 18, 2013
google_python_style.vim New file google_python_style.vim. Nov 29, 2010
htmlcssguide.xml Replaced HTTP where HTTPS been awailable. Apr 1, 2016
intellij-java-google-style.xml Update the IntelliJ style to the latest version from Google. Dec 22, 2016
javaguide.css Updated Java Style Guide to reflect current internal version. Jun 29, 2016
javaguide.html Update Java and C++ style guides with various changes since the last … Nov 18, 2016
javaguidelink.png initial commit for java style guide Dec 17, 2013
javascriptguide.xml Restore ES5 styleguide Dec 22, 2016
jsguide.html Update and replace JavaScript style guide. Nov 18, 2016
jsoncstyleguide.html Update look and feel of the style guides Jul 12, 2010
jsoncstyleguide.xml Replaced HTTP where HTTPS been awailable. Apr 1, 2016
jsoncstyleguide_example_01.png Adding first iteration of the JSON-C Style Guide for JSON APIs Feb 22, 2010
jsoncstyleguide_example_02.png Adding first iteration of the JSON-C Style Guide for JSON APIs Feb 22, 2010
lispguide.xml Replaced HTTP where HTTPS been awailable. Apr 1, 2016
objcguide.xml Replaced HTTP where HTTPS been awailable. Apr 1, 2016
pyguide.html Update shebang line Jun 24, 2016
shell.xml Fix broken link May 19, 2016
styleguide.css Update look and feel of the style guides Jul 12, 2010
styleguide.xsl Reverted XML namespace name changes Apr 28, 2016
vimscriptfull.xml Removed link shortening. Apr 1, 2016
vimscriptguide.xml Removed link shortening. Apr 1, 2016
xmlstyle.html Replaced HTTP where HTTPS been awailable. Apr 1, 2016

README.md

Google Style Guides

Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style.

“Style” covers a lot of ground, from “use camelCase for variable names” to “never use global variables” to “never use exceptions.” This project holds the style guidelines we use for Google code. If you are modifying a project that originated at Google, you may be pointed to this page to see the style guides that apply to that project.

Our C++ Style Guide, Objective-C Style Guide, Java Style Guide, Python Style Guide, R Style Guide, Shell Style Guide, HTML/CSS Style Guide, JavaScript Style Guide, AngularJS Style Guide, Common Lisp Style Guide, and Vimscript Style Guide are now available. We have also released cpplint, a tool to assist with style guide compliance, and google-c-style.el, an Emacs settings file for Google style.

If your project requires that you create a new XML document format, our XML Document Format Style Guide may be helpful. In addition to actual style rules, it also contains advice on designing your own vs. adapting an existing format, on XML instance document formatting, and on elements vs. attributes.

These style guides are licensed under the CC-By 3.0 License, which encourages you to share these documents. See https://creativecommons.org/licenses/by/3.0/ for more details.

Creative Commons License