Maintenance Model

Docs are release work.

Product pages should evolve in the same release cycle as app behavior changes.

Operational rule

If user-visible product behavior changes, the corresponding product page, screenshots, and copy should ship in the same release task.

Release checklist

  • Review changed app behavior against each public product guide.
  • Refresh screenshots for modules whose UI changed materially.
  • Verify interactive demos still map to current product logic.
  • Update story/character/feature pages with any new capabilities.
  • Run website tests, asset builds, and sitemap checks before deploy.

Ownership model

App implementation details stay in the iOS repo. Customer-facing product language stays in this site repo. Both should reference the same release truth.

When major workflows shift, update: Product overview, affected story pages, relevant character pages, and feature cluster details.

Cadence

Review product docs each release and run a deeper IA audit monthly.

Quality bar

Prefer clear client language, practical examples, and explicit outcomes over technical internals.

Definition of current

Pages are current when copy, visuals, and route structure match the shipping app behavior.