Quail Pages Document
Quail Pages Document
Quail Pages is a contract-driven document and rendering system. The Documentation describes what authors can provide to Quail Pages through qp.schema.json.
Use it to understand the available document structures, elements, properties, constraints, composition rules, and authoring guidance.
What the Documentation covers
Site
Page
Layout
Rendered Content
Built Content
Custom Content
Supporting Object
Site Configuration
Using the reference
Each reference page documents one authored Quail Pages contract. Depending on the object, it may include properties, accepted shapes, relationships, examples, authoring guidance, and links to its corresponding Style Guide surface when one exists.
Documentation and Style Guide
Documentation asks: What can I ask Quail Pages to make? The Style Guide asks: What does Quail Pages emit that a theme can style?
The contracts are related, but are not mirrors: not every authored object has a class contract, and not every emitted surface is a directly authored primitive.
Responsive presentation widths
Canonical Quail Pages presentation-width vocabulary. These ranges describe available viewport inline size, not device detection. Rem boundaries are canonical; at the 16px reference size, 48rem corresponds to 768px and 64rem corresponds to 1024px. Component-owned container queries and content-fit breakpoints may use independent thresholds. The exact structured boundaries live in qp.architecture.json.
Machine-readable contracts
The Documentation is backed by machine-readable Quail Pages contracts used by the renderer, tooling, and documentation itself.
Architecture
qp.architecture.json
Defines how Quail Pages concepts are organized, names canonical responsive presentation-width ranges, and records keyless stylesheet infrastructure such as base.css.Authoring Schema
qp.schema.json
Defines what can be authored in Quail Pages, including document structures, elements, properties, constraints, and composition rules.Site Discovery Knowledge Contract
qp.site-discovery.json
Defines optional, provenance-aware knowledge gathered before creative direction; discovery seeks sufficiency rather than completeness.Site Discovery Interview Contract
qp.site-discovery-interview.json
Defines declarative guidance for asking only questions whose answers can materially change subsequent work.Icon Registry
icons.json
Defines canonical icon names, human descriptions, discovery keywords, and renderer-owned SVG path geometry.