Start with Foundry

Foundry is a portable way to make fast, distinctive websites from ordinary Hugo, Markdown, YAML, CSS, and assets. It gives builders a governed design and quality system while leaving the finished site understandable, reviewable, and owned by the people who commissioned it.

Why use Foundry?

• Start faster without looking generic. Site Foundations and page blueprints provide a coherent beginning; Theme Families and Brand Systems create materially different outcomes.
• Make choices humans can understand. Select a section by the visitor job, then choose the block and presentation that solve it.
• Know what is proven. Contracts, validation, and Visual Review evidence distinguish an attractive demonstration from a release-ready result.
• Avoid lock-in. The source remains ordinary and portable. Managed Foundry Control workflows are optional rather than a condition of ownership.

Read why Foundry exists for the v1 promise in plain language, then use Foundry Control when you need the managed workflow layer around a portable site.

What can I build?

Foundry supports clear service sites, editorial publications, creative portfolios, campaigns, product stories, destinations, and other marketing systems. Explore Visual Review to compare Theme Families, Brand Systems, Site Foundations, Section Families, and source-backed examples.

Which Theme Family fits?

• Structured Clarity suits services, operational information, and direct decision paths.
• Editorial Narrative suits studios, publications, essays, archives, and authored work.
• Immersive Atmosphere suits destinations, hospitality, products, and media-led stories.

A Theme Family controls art direction and composition behavior. A Brand System controls identity. Keeping those responsibilities separate lets the same portable structure feel genuinely different for each organization.

How do I start?

1. Build the first site with the current stable bundle.
2. Choose a theme direction and inspect its evidence before adopting it.
3. Compose the page by responsibility, family, and block.
4. Validate the result before publishing or upgrading.

What you own

Your content, configuration, templates, styles, media, and history remain in a normal repository. Foundry Core supplies portable build and render contracts. Distribution pins a compatible release. Foundry Control can add permissions, review, and managed publishing without becoming necessary to render the site.

Control note: Control is the managed product around the site repository: accounts, roles, approvals, private context, previews, publishing, and operational state. It is deliberately separate from the portable Core runtime, so a site can be built and hosted without a Control account.

Stable, preview, and history

The status line above identifies the bundle documented by this page. Preview documentation can change and names the exact Core commit it is based on. Historical releases are immutable and never borrow newer source content.

Stable is a release channel. Standard and LTS are support tiers within that channel. LTS means a named maintenance window and backport promise; it does not mean “newest.” Releases made before this contract are shown as Not classified rather than assigned invented support dates.

Owners should use the bundle version as the site-level identity. Component versions explain the technical pins inside that bundle, while the Distribution version identifies the release tooling that assembled it. Upgrade impact is always declared from the installed bundle to a target bundle: verify only, optional adoption, migration required, or breaking.