Historical documentation Bundle v1.1.11 Core v1.1.11 Distribution v0.3.24 Verified 2026-08-30
Release history
Foundry product model Review the system vocabulary and the relationship between reusable Foundry layers. v1.1.11 docs current site-builderscore-developersintegratorsai-agents

docs · Current reference

Foundry product model

Review the system vocabulary and the relationship between reusable Foundry layers.

Applies to v1.1.11

Component pins for v1.1.11
ComponentRoleVersion
coreruntimev1.1.11
theme-shieldthemev0.1.15
docsreferencev0.1.6
distributiontoolingv0.3.24

Content Contract

Each page defines a sections array. Each item must include:

  • block key
  • content payload 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.classes defines shared tokens (card, panel, chip, badge).
  • components/button.html defines 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.

  • Build: hugo --minify
  • Registry validation: no unknown block keys in content
  • Schema validation: required block keys exist (see data/foundry/block-schemas.json)
  • Version pinning for site safety
  • FOUNDRY-HUGO-FIRST-CONTRACT.md
  • FOUNDRY-FRAMEWORK-SPEC.md
  • FOUNDRY-CLI-SPEC.md
  • FOUNDRY-BLUEPRINT-SPEC.md
  • FOUNDRY-BLOCK-ARCHITECTURE.md

Static Pagefind search

Search Foundry documentation

Type at least two characters
Search the full documentation system

Results stay inside this build profile and can be filtered by version, component, audience, and lifecycle.

By LikeStyle
Site details
Site release
Foundry Documentation 1.3.9
Foundry bundle
v1.1.11
Foundry Core
v1.1.11
Credit
Powered by Foundry, a LikeStyle product.