Start with Foundry

Immutable release snapshot. Bundle v0.2.3 pins every component shown below.

This historical manifest was reconstructed from a committed Distribution object because it was not present at its declared Distribution tag. Its first published checksum is locked here.

Bundle components

Bundle notes

• Stable bundle metadata no longer advertises the retired standalone dark-mode and i18n modules.
• A restricted proof consumer completed the bundle verification path.
• Stable consumers should resolve appearance and language capabilities through core-owned runtime paths.

Foundry is a portable, Hugo-native system for assembling, styling, validating, and evolving sites from explicit repository contracts. Foundry Core supplies the runtime and machine-readable contracts. Distribution pins compatible releases. Foundry Control adds managed workflows without becoming a requirement for owning the site.

Choose a path by role

• Site owners: begin with the first-site guide, then read compatibility and versioning before choosing an upgrade.
• Site builders: follow Learn, then use Build for sections, blocks, themes, motion, SEO, forms, and tracking.
• Theme and Core developers: start with Architecture, then use the shipped reference and validation contracts for the selected bundle.
• Integrators and AI agents: use Reference and treat schemas, manifests, and CLI JSON as higher authority than prose or chat memory.
• Foundry operators: use Operate for public procedures and the restricted handbook for readiness and managed runbooks.
• Foundry maintainers: inspect Releases and Evidence before changing a contract or promoting a bundle.

Stable, preview, and history

The release badge above identifies the bundle documented by this page. /docs/next/ contains unreleased material and may change. Historical release routes are immutable and never borrow newer source content.