# Names

Product names, trademarks, and filenames. From the Google developer
documentation style guide; each section names its source page. Example domains,
people, and IP addresses are in `code.md`.

Guide content © Google, used under CC BY 4.0
(https://creativecommons.org/licenses/by/4.0/).

## Contents

- [Product and feature names](#product-and-feature-names)
- [Trademarks](#trademarks)
- [Filenames and file types](#filenames-and-file-types)

## Product and feature names

Source: https://developers.google.com/style/product-names

Title case for product names, unless you're matching a UI label or the official
name starts lowercase: "You can use macOS to run the app". Don't start a
sentence with a lowercase official name; rearrange the sentence.

Feature names are lowercase unless the official name or a UI label
capitalizes them.

Use the full trademarked name and don't abbreviate it, except to match a UI
label. Where repetition gets heavy, switch to a general term such as "the service
mesh" rather than inventing a short form.

No *the* before a product name unless the name modifies something else; *the*
before tool and API names: "Using Cloud Datastore with Cloud Dataproc", "the
Transcoder API".

Never use a product or feature name as a verb.

## Trademarks

Source: https://developers.google.com/style/trademarks

A trademark modifies a noun; it isn't a noun or a verb on its own: "a Chromebook
notebook computer", not "a Chromebook". Don't make a trademark possessive, don't
pluralize it, and don't alter it in any way.

Follow the owner's usage guidelines and include whatever attribution they
require. Google's are at https://www.google.com/permissions/trademark/.

## Filenames and file types

Source: https://developers.google.com/style/filenames

These are rules for documentation files. Source files follow their language's own
convention: `retry_queue.py` stays `retry_queue.py`.

Lowercase, with hyphens between words: `query-data.html`, not
`query_data.html`. Search engines read a hyphen as a space; case-sensitive
filesystems make mixed case a liability. Standard ASCII alphanumerics only. No
generic names like `document1.html`.

Match an existing directory's convention over the rule: in a directory of
`lesson_1.jd`, `lesson_2.jd`, add `lesson_4.jd`. Tool-generated names that follow
a product or API convention also stand.

In prose, put a filename in code font, keep its exact spelling, and name the kind
of thing it is: "In the following `build.sh` file, modify the default values."

Refer to a file type by its formal name, not its extension: "a PNG file", not "a
`.png` file". Don't turn an extension into a verb: "extract a zip file", not
"unzip a zip file".