Reference overview

Overview

Reference is the home for compact, rule-oriented documentation that does not belong inside a step-by-step setup article. Use it for durable facts, constraints, terminology, and product behavior summaries that users or support teams may need to check quickly.

This section should not become a second guide system. Guides remain separate from Docs. Reference should support product documentation by making important facts easy to retrieve.

What belongs in Reference

Good Reference topics include:

• Workflow behavior matrices
• Plan, usage, or limit summaries
• Calendar scheduling rules
• Order and payment verification rules
• Glossary-like product terminology when it is specific to Interlinked docs
• API or webhook references if those surfaces are documented later

Reference pages should be factual, scannable, and stable. If a topic teaches a user how to complete a task, it probably belongs in a product section instead.

How Reference supports LLM retrieval

Reference pages are useful for search and LLM exports because they concentrate exact rules in one place. For example, the facts in Calendar - important notes and behaviors are easier to retrieve when users or LLMs need a concise scheduling behavior summary.

When adding new Reference pages, keep titles explicit and avoid vague names such as “Notes” or “Miscellaneous.” Prefer titles that name the product area and rule type.

Maintenance guidance

Reference pages should be reviewed when product behavior changes. They often summarize rules that other articles rely on, so inaccurate reference content can create confusion across the docs system.

Related docs

Use this page with Workflows overview, Calendar - important notes and behaviors, and Payment verification and security.