Content governance

Documentation needs operational rules of its own. Without them, it quickly turns into another archive of text that nobody trusts.

Ownership

Every important page should have:

• owner,
• audience,
• state,
• last verification date,
• source of truth.

Starlight frontmatter currently carries mostly navigation metadata. Domain metadata can be added later either by extending the content schema or by using a convention in the introduction of each page.

Review rhythm

Page type	Recommended rhythm
Client guides	On every larger UX change or quarterly.
API documentation	When OpenAPI/specs change.
Internal domain model	When models, interactions, or migrations change.
Runbooks	After an incident or operational change.

Quality bar

A page is useful when:

• the reader understands whether it is for them,
• core terms are clear,
• there is an example or scenario,
• common edge cases are described,
• the source of truth is explicit.

What to handle through feedback

• factual error,
• unclear paragraph,
• lack of trust in the source,
• missing client scenario,
• conflict between documentation and production behavior,
• broken link or outdated screenshot.