Reference Pages
Overview
Use a reference page when the reader needs exact, neutral, complete, and scannable facts.
Reference pages should mirror the system they describe. They are not the place for long rationale or guided walkthroughs.
The primary reader question is: "What are the exact supported contracts, defaults, constraints, and failure behaviors?"
Use This Page Type When
- the reader needs an API contract
- the reader needs configuration details
- the reader needs exact defaults, allowed values, constraints, or compatibility notes
Reference Template
Use the relevant sections from this template:
- one-sentence summary
## Applies to## Syntax,## Contract, or## Configuration## Parameters,## Properties, or## Options## Defaults## Allowed valuesor## Constraints## Behavior## Errors,## Exceptions, or## Failure behavior## Compatibilityor## Version notes## Example## Summary## Next Steps
Content Rules
- Stay factual and concise.
- Document side effects, cancellation behavior, ordering implications, and idempotency expectations when relevant.
- Every example must be verified.
- Use comments, not ellipses, if you intentionally omit code.
Minimal Frontmatter Example
---
title: Brook Storage Configuration Reference
description: Reference the supported configuration keys, defaults, scopes, and constraints for Mississippi brook storage providers.
sidebar_position: 50
sidebar_label: Brook Storage Config
---
Page Skeleton Example
# Brook Storage Configuration Reference
This page documents the exact configuration contract for brook storage providers.
## Applies to
## Configuration
## Options
## Defaults
## Constraints
## Behavior
## Failure behavior
## Summary
## Next Steps
Summary
- reference pages are for exact facts, not guided teaching
- they should document contracts, defaults, constraints, and failure behavior with verified examples
- long rationale belongs in concept pages, not here