v0.2.2
docs
current
Public
Foundry product model
Review the system vocabulary and the relationship between reusable Foundry layers.
- Owner
- Foundry product documentation
- Source
docs/docs/SYSTEM-SPEC.md- Ref
v0.1.4- Policy
- release-bound
Component pins for v0.2.2
| Component | Role | Version |
|---|---|---|
| core | runtime | v0.1.16 |
| theme-shield | theme | v0.1.15 |
| restricted-component-1 | brand-theme | v0.1.5 |
| dark-mode | runtime-addon | v0.1.0 |
| i18n | runtime-addon | v0.1.0 |
| starter | reference | v0.1.3 |
| docs | reference | v0.1.4 |
| distribution | tooling | v0.3.1 |
| restricted-component-2 | consumer-reference | v0.1.5 |
| restricted-component-3 | consumer-reference | v1.1.21 |
Content Contract
Each page defines a sections array. Each item must include:
blockkeycontentpayload Optional:id,design
Renderer
render-sections.html resolves each block via site.Data.foundry["block-registry"].
Unknown block keys are warned at build time.
UI Primitives
site.Data.foundry.classesdefines shared tokens (card, panel, chip, badge).components/button.htmldefines button variants.
Variants
Variants live in design.variant and must be documented in BLOCKS.md.
Data-driven Sections
Blocks may reference shared data using data (string or map). Section values override data values.
Reliability Checks (recommended)
- Build:
hugo --minify - Registry validation: no unknown
blockkeys in content - Schema validation: required block keys exist (see
data/foundry/block-schemas.json) - Version pinning for site safety