portal · Current reference
Why Foundry
Use the canonical mission and seven ordered v1 goals: delivery, creative range, ownership, safe evolution, measured quality, human-first operability, and convergence.
Applies to v1.1.8
Component pins for v1.1.8
| Component | Role | Version |
|---|---|---|
| core | runtime | v1.1.8 |
| theme-shield | theme | v0.1.15 |
| docs | reference | v0.1.6 |
| distribution | tooling | v0.3.22 |
Foundry is for people who want a site to feel authored without making it fragile. It turns a brief into a credible starting point, gives a team a wide creative range, and keeps the result in source that remains understandable and useful after the first launch.
Mission
Make Foundry the best and most flexible way to quickly build unique websites for every customer — sites that evolve as needs grow, and that the customer owns outright instead of being locked into a platform.
This is the framework’s decision filter, not a campaign line. Read the canonical mission and ordered goals whenever a feature, tool, or managed service makes the product direction unclear.
The seven v1 goals
Foundry Core v1 is a portable professional site platform for quickly delivering distinctive, durable, high-quality sites that customers own outright. The ordered goals are:
- Fast professional delivery. Move from a brief to a credible, branded, reviewable site through a discoverable, repeatable path.
- Genuine creative range. Produce materially different structures and art directions—not palette or font swaps.
- Customer ownership and portability. Keep the finished site visible and useful in a normal Hugo repository the customer can take elsewhere.
- Safe long-term evolution. Keep shared changes bounded, inspectable, reversible, compatible, and resistant to drift.
- Measured quality. Track accessibility, performance, security, progressive enhancement, authoring clarity, and consumer proof separately.
- Human-first, machine- and AI-operable. Give every essential job a direct human path; stable reports and optional AI accelerate rather than control it.
- Convergence before expansion. Finish, simplify, adopt, and prove the existing system before adding broad inventory.
What that feels like in practice
- A site owner can understand what they are buying and what they will keep.
- A designer can choose a direction with visible examples instead of guessing from a token list.
- A builder can use governed sections and blocks without starting from a blank canvas or fighting an opaque editor.
- A maintainer can see the exact bundle, source pins, checks, and upgrade impact before changing a live site.
Explore Visual Review for the creative range, Start with Foundry for the first build, and Operate Foundry for the proof and maintenance path.
Control, when a team needs more
Foundry Control is the managed workflow layer around a portable Core site. It can provide accounts, roles, private context, drafts, approvals, review history, previews, publishing, integrations, analytics, contacts, and automation. These capabilities help a team coordinate safely; they are not silently part of Core and they are not required to render or own the site.
Control note: Choose Control for collaboration and managed operations. Choose Core for the portable source and runtime. A healthy Foundry system keeps both responsibilities explicit.
Version truth
This portal is version 1.3.6. Distribution’s current stable pointer names
Foundry bundle v1.1.2, pinning Core v1.1.2, reference docs v0.1.6, and
Distribution v0.3.19. Foundry bundle v1.0.1 remains the LTS line.
Release history remains the source of truth for current and
older immutable bundles.