Documentation Style Guide
The documentation style guide describes the public writing standard: explain product behavior directly, keep examples concrete, and avoid process filler.
How To Use It
- Start with the public docs page that matches the task.
- Use bundles to find the right section quickly.
- Use API reference pages for exact route and schema details.
- Use tool pages for required inputs, outputs, limits, and review behavior.
Quality Standard
Public documentation should read like a product and developer manual. It should not expose private credentials, private payloads, implementation-only notes, or documentation maintenance process.
Media To Add
- Table: bundle name, audience, included sections, and best next page. It helps readers choose the right machine-readable entry point. Source: public LLM bundle outputs.