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.
A theme extends Base; it does not replace the system
Authored decisions stay sparse
Base supplies the complete component foundation. A theme records coordinated identity decisions in its variable contract, inherits the rest, and uses extension CSS only for composition and art direction that semantic variables cannot honestly express.
Theme registration and component stylesheet ownership remain separate from the variable contract. Compiled CSS, copied fonts, and copied assets are reproducible deployment output—not a second authored source of truth.
A site can carry its own private theme
QP resolves a registered shared theme first, then a matching theme packaged inside the site. Either source is composed with Base through the same build machinery and produces the same complete deployable stylesheet.
A site-local theme remains private to that site. It is not published into the shared theme catalog or exposed through the public theme switcher.
The contracts are the interface for AI
QP makes its content vocabulary, components, themes, discovery knowledge, and behavior explicit so an AI does not have to reverse-engineer the system before it can use it.
The intelligence does not have to belong to QP. Any capable agent can inspect the documentation and contracts, reason about what to build, and produce work against the same defined system.
When an agent finds an ambiguity or a path QP should not allow, the durable fix is not another instruction telling that agent to behave differently. The contract, validator, renderer, or system boundary should improve so the next agent encounters a better-defined system.
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.