Simple for the owner. Explicit underneath.
Technical structure supports the story. It is not the story site owners should have to learn.
A small, inspectable architecture
Content contracts
Authored JSON describes pages and reusable content with a known vocabulary.
Renderers
QP turns that vocabulary into semantic, accessible, responsive output.
Themes
A formal theme contract coordinates design decisions while extension CSS handles real art direction.
Content can evolve without reauthoring the implementation
Defined does not mean rigid
The vocabulary supplies reliable pieces and relationships. Themes, composition, plugins, and authored content still create sites with distinct purposes and identities.
Static does not mean disposable
QP produces deployable static sites with portable content and reproducible builds. The result remains legible to future tools and people.
The contracts are part of the product
Components, content, themes, discovery knowledge, and runtime behavior are formalized instead of living only in examples or source-code assumptions.
That work is still evolving during alpha. Technical users can inspect it today, but QP is not asking third-party developers to treat every contract as permanently stable yet.
The contracts are public. The renderer isn't—yet.
The public documentation exposes QP's authoring schema, architecture, discovery contracts, class contract, theme system, icon registry, and other machine-readable resources. The renderer and complete build system are not currently public.