unreleased
portal
preview
Public
Start with Foundry
Understand what Foundry is, who it serves, and which path to follow first.
- Owner
- Foundry documentation portal
- Source
portal/portal/start.md- Ref
WORKTREE- Policy
- evergreen
Component pins for v0.2.6
| Component | Role | Version |
|---|---|---|
| core | runtime | v0.1.24 |
| theme-shield | theme | v0.1.15 |
| starter | reference | v0.1.3 |
| docs | reference | v0.1.4 |
| distribution | tooling | v0.3.4 |
| restricted-component-1 | consumer-reference | v0.1.22 |
| restricted-component-2 | consumer-reference | v1.1.21 |
Unreleased preview. This material resolves from current development commits and uses the stable bundle only as its compatibility baseline.
Bundle components
| Component | Role | Version |
|---|---|---|
| core | runtime | v0.1.24 |
| theme-shield | theme | v0.1.15 |
| starter | reference | v0.1.3 |
| docs | reference | v0.1.4 |
| distribution | tooling | v0.3.4 |
| restricted-component-1 | consumer-reference | v0.1.22 |
| restricted-component-2 | consumer-reference | v1.1.21 |
Bundle notes
- Promotes Foundry Core v0.1.24 with the Social & Presence family and the static-first social-preview-grid block.
- Keeps social/presence API sync optional; curated, embed, static-import, and api-materialized items all render as normal site-owned data.
- Includes the Creative validation/productization checkpoint, quality gates, scaffold contracts, and expanded compatibility fixtures from the core release.
- A restricted proof consumer completed the bundle verification path.
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.