Google developer docs

Produce developer documentation that helps a reader understand or complete a technical task without decoding the prose.

Protect the source material

• Preserve facts, code, commands, names, URLs, prerequisites, and constraints.
• Do not invent product behavior, defaults, compatibility, or results.
• Mark a missing fact as a question or placeholder instead of guessing.
• Follow a project-specific terminology or API guide before this style.

Plan the page