Architecture and Design

This section explains the overall system shape, design rationale, model fit, and example-driven architecture guidance.

Use this section when you need to understand why Site Pipeline has its current boundaries, models, and execution shape. If you are trying to build your first site, start with Getting Started instead.

Start with the system boundary

Follow execution and source materialization

Review the model and its rationale

  • Design review records design choices, boundaries, and open trade-offs.
  • Model-fit cross-check tests the model against sites of different shapes and explains the size bands used in Getting Started.

For exact types, schemas, and validation rules, use the unreleased development reference. Those contracts have not yet been published as release documentation.


Site Pipeline architecture overview

This document is the entry point for the current design docs.

Source resolution and materialization

For maintainer-facing notes about planning-layer ownership, effective input resolution, watch-root derivation, and shared execution boundaries, see ../maintenance/code-maintenance.md.

Recommended staging-engine implementation architecture

This document describes the recommended internal architecture for the staging engine and watch loop.

Provider integration end-to-end example

This example shows one way a component catalog, artifact model, and provider snapshot could combine into staged metadata.

Pipeline model fit cross-check

This document cross-checks the current Site Pipeline publication model against public documentation and release topologies used by prominent OSS projects.

Design review

This document reviews the current docs as a design set.