What does this control mean?
Exact field names, allowed values, behavior, validation, errors, defaults, and related explanations—after the behavior has been verified.
Use Docs for controls, settings, states, and product behavior. For step-by-step workflows, open How-Tos; for research concepts and assumptions, use Learn and Methods.

Users should not have to guess whether they need a definition, a workflow, or a control reference.
Exact field names, allowed values, behavior, validation, errors, defaults, and related explanations—after the behavior has been verified.
Goal-oriented steps, prerequisites, expected results, common mistakes, troubleshooting, and optional video.
Open How-Tos →Definitions, assumptions, visual explanations, mathematical reasoning, limitations, and what to inspect next.
Open Methods →In-app helper links can take you directly to the Concept, Method, How-To, or reference page that matches the thing you are looking at. You do not need to start at the documentation homepage or know where the page lives.
The destination can evolve as the documentation grows while the in-app link keeps opening the right topic.
In-app help links open the customer-facing guide, concept, or reference page for the task at hand.
As product areas are verified, exact reference pages can be added here without mixing product instructions with research education.