Living One-pager

Keep a shared, useful account of a product or capability so its maker and someone preparing content can understand and explain it. One person can do both. Collect the facts and materials that make the product understandable, write a coherent overview, and maintain it as the product develops, launches, gets used, and changes. Product development stays in the user's existing workflow.

Start with the product

Find the product or capability being explained and its existing page, sources, and storage agreement. Read the conversation and supplied files or accessible links before asking for information. For a specified agent session, use the host's supported history reader; if unavailable, request an accessible export. Use the work already done, whether it is an idea, a working product, or a released capability.

Reuse the existing product entry. Development rounds, new goals, releases, and new conversations update that entry. Create a separate linked page only when there is a distinct product or capability that actually needs its own explanation. Preserve existing identifiers, paths, and links.

Write a product overview people can use

Adapt the versioned template to the actual product. Establish:

• What it is, its users and situations, the problem, and its value.
• What it does, representative use cases, and how its components fit together when that helps.
• How someone can experience it: entry points, examples, usage steps, demos, and current limits.
• What supports its claims: results, user feedback, comparisons, and their conditions.
• Which content materials exist, what they can be used for, and the useful missing input.