Community Guides
Community guidance should keep the operator path clear.
Community Guides collect practical entrypoints without replacing the canonical docs or the product story.
Community Guides
Community material should extend the system, not fork it.
Explain how examples, guides, and public contributions connect back to the canonical workflow.
Community Guides
What community guides are for
Use the route for onboarding, examples, and public learning paths that remain aligned with the docs.
Utility surface
Practical examples
Show applied workflows without inventing new semantics or new product surfaces.
Canonical alignment
Community material should still route back to docs, CLI, and product pages.
Contribution posture
Public contribution should preserve truth boundaries and naming discipline.