Capabilities
What Foundation provides, and where it deliberately stops.
Foundation is a reusable website base. Everything on this page exists in the project and is configurable by a deployment — and the boundaries below are just as deliberate as the capabilities.
- Six capability families, each configurable rather than coded
- Repository evidence behind every claim on this page
- Boundaries stated as architecture scope, not as missing features
What is included
Each family states what a business notices first, the machinery that produces it, and what stays yours to supply.
Identity and content
Your name, tagline, description, navigation, pages and collections live in configuration and files you own — not in code scattered across templates, so a change happens in one place.
Under the hood
Strictly validated site configuration and Markdown pages with frontmatter, read through a content repository interface; navigation order and page existence stay separate concerns, so a menu cannot invent a page.
Yours to supply
Your identity values, your words, your collections, your choice of optional capabilities.
Presentation
Your site looks consistent and deliberate from day one, because the layout, spacing and typography system is already built — and re-branding is a defined set of named artwork roles.
Under the hood
A design-token presentation layer with light and dark schemes and a single accent value; logos, favicon, social preview, banners, backgrounds and graphic roles are configuration, and an absent role renders nothing at all.
Yours to supply
Your branding artwork, your accent choice, any bespoke presentation you extend.
Internationalisation
Adding a language is content work rather than a development project: a dictionary file plus a content directory, with the site staying coherent while translations are incomplete.
Under the hood
Path-based locales with locale negotiation, one schema-validated interface dictionary per language, per-page content fallback to the default language, and language annotations generated only for languages that genuinely have a destination.
Yours to supply
Your translations and your locale set.
Discovery
Search engines and social previews receive correct titles, canonical addresses and structured data without anyone remembering to add them page by page.
Under the hood
Per-route metadata derived from configuration and content, a sitemap generated from the actual content model and language set, robots output referencing it, Open Graph and Twitter cards, and schema.org structured data built from configuration.
Yours to supply
Your domain, your descriptions, any campaign or analytics metadata you add.
Connections
The services you already use stay where they are. Foundation presents the visitor's intent and hands it to them, so swapping a provider is a configuration change rather than a rebuild.
Under the hood
Provider-neutral integration seams behind per-capability factories, selected from configuration, with explicit off states so an unused capability costs nothing.
Yours to supply
Your accounts with those providers, and whatever they cost.
Engineering quality
Changes are checked automatically, so a later edit is far less likely to quietly break a page nobody looked at.
Under the hood
Schema validation of configuration and dictionaries, architecture boundaries asserted by tests, a committed real-browser verification matrix, automated contrast checks for the documented token pairs, and asset, type, lint, test and build gates.
Yours to supply
Nothing — this is the part you inherit, and it is what makes the rest of the list trustworthy.
What Foundation does not try to replace
Foundation presents your business and hands visitor intent to your systems. It deliberately stops before the systems themselves.
- Your CRM and customer records
- Your accounting and invoicing
- Your payment ledger and card processing
- Your operational booking or scheduling database
- Your customer accounts and sign-in
- Your inventory and wider business operations
These are boundaries, not gaps. A website that tried to become all of them would be harder to own, harder to change and harder to hand on to someone else.
Where this page's claims come from
Every capability above is checkable in the repository rather than asserted here. These are the maintained documents behind it.
Architecture
The layers, the dependency direction and the boundaries the tests enforce.
Customising
How configuration, content, dictionaries and assets are changed without touching platform code.
Brand assets
The named visual roles, so replacing identity artwork is a defined task rather than a hunt.
Deployment
How a built site is deployed to the adopter's own account and domain.
Instruction manuals
The full adoption path, from obtaining Foundation through to troubleshooting.
The website summarises these documents; it never becomes a second copy of them.
See it working
Two different businesses run on this foundation. Look at what it produces, then read how the pieces fit together.