Take the source and make it yours
ADOPTION
Foundation is public and self-serve. Obtain the repository, run it, replace its identity and content, validate it, and deploy it to an account you own. The public repository is the canonical technical source; this page is the shortest honest route through it.
- There is no Foundation account to create and no licence fee for the software. Your hosting and domain remain your own costs.
- Every document referenced here ships in the public repository, versioned beside the code it describes.
- Nothing on this page needs to be taken on trust: the repository is one click away.
Three legitimate ways to adopt it
Foundation does not require Provelopment, and it does not require you to work alone. These are the three routes adopters actually take, and they are equally valid.
Use Foundation yourself
For technically capable adopters: obtain the repository, run it locally, configure the identity, author the content, validate, and deploy. Everything needed is in the public repository, and nothing in it depends on Provelopment.
Use your own developer or agency
Your deployment's changes live in configuration, content and assets rather than in platform code, so any competent web developer can work on a Foundation site — including one who has never seen Foundation before.
Ask Provelopment for help
Provelopment can provide implementation help, technical assistance, support and managed services. That assistance is separate from the foundation and entirely optional.
None of the three is the recommended route: the site you end up with is the same one, and the source stays with you whichever you choose. Bringing in help — or going without it — is a service decision you can make, or reverse, at any time.
The path from repository to running site
This is the whole adoption sequence, in order. None of it is reproduced here: each step names the document that owns the detail, so this website never becomes a second, drifting copy of the repository's instructions.
Look at the running sites
Start with the demos. Compare one of them with this website and note what changed — identity, content, navigation, feature mix. Everything you observe there is available to configure on your own copy.
Review the project on GitHub
Read what the project is, what it includes and how the repository is laid out, then skim the architecture document before you commit your time to it.
Obtain the source
Clone or fork the public repository. You hold your own copy under your own control from the first minute — there is nothing to register, nothing to request and nothing to wait for.
Run it locally
The starter site renders immediately after a dependency install and a development server start: a working site rather than an empty folder to fill in.
Configure your identity and site settings
Replace the placeholder identity in the site configuration — URL, name, tagline and description — then decide which optional capabilities your site needs. Every capability has an explicit off state.
Author your content and assets
Your pages and your business content live in your own site directory as Markdown and configuration, and your artwork replaces the placeholder graphics role by role.
Connect external services where required
Only the capabilities you enable need destinations: an inquiry endpoint, a booking destination, a map location or an analytics provider. Credentials belong in your deployment environment, never in the configuration file.
Validate before you ship
Run the repository's documented gate. Configuration is checked at build time, and an enabled capability that was never finished fails loudly instead of pretending to work.
Deploy to your own account
Deploy to hosting you control and point your own domain at it. The deployment manual documents the first deploy, continuous-integration gating, the custom-domain step and the post-deployment checks.
Maintain and upgrade
Keep your copy connected to the repository so you can absorb upstream improvements deliberately. Your configuration, content, dictionaries and assets survive an update; platform code is replaced.
Ten steps, in the order a real deployment goes through them. The exact commands and settings stay in the repository, where they are reviewed, versioned and kept correct as the code changes.
What you need before you start
Foundation is a real codebase rather than a hosted website builder, so adoption has honest prerequisites. They are modest, and none of them involves a vendor you did not choose.
- Comfort with a modern web project: a configuration file, Markdown files and a few terminal commands.
- A hosting account you control, and a domain if you want your own address. The deployment manual documents Vercel end to end.
- Your own identity, content and imagery to replace the placeholders.
- Accounts with external services only where you enable an integration that needs one.
Nothing else is mandatory. Foundation requires no account with Provelopment, no paid tier, no particular hosting provider and no particular developer.
You own your website
Foundation is the software; the site is yours. Staying with Provelopment is a service choice, not a technical hostage situation.
The source is yours to keep
Your copy of the repository is your deployment. There is no activation step, no licence server and no account that a running site depends on.
Deployment is yours
You deploy to your own hosting account and your own domain, and the deployment instructions assume your accounts rather than ours.
Your developer choice is yours
Configuration, content and assets are yours to change, so the work can continue with any competent developer — no tribal knowledge and no dependency on whoever set it up.
Your provider choices are yours
Inquiry delivery, booking, map directions and analytics are configured per site, so you choose those providers rather than inheriting a set.
Downstream work stays separable
What you or your agency build on top of Foundation lives in your own configuration, content and assets, so upstream improvements can be absorbed without discarding it.
Foundation is open source under the Apache License 2.0. You may use, modify, distribute and commercially exploit the project's own code and documentation, including inside your own proprietary website, provided the licence terms are met — a copy of the licence and the attribution notices are retained, changes are not misrepresented, and the software is provided without warranty. The licence is a copyright licence: it grants no rights in the Provelopment name, logos or branding, and bundled third-party material keeps its own licence and attribution. This paragraph summarises the licence; the licence text governs.
Third-party marks and icons bundled with the project belong to their owners and are governed by their own terms, not by Foundation's licence.
The documents that own the detail
Foundation's documentation ships with the code, so it cannot drift away from it. Each document below is authoritative for its subject, including where this page would otherwise have to repeat it.
- README
What the project is, how to start, the repository layout and the real validation commands.
- CUSTOMIZING.md
The downstream user guide and the complete configuration reference, including the table that separates what is yours from what is the platform's.
- ARCHITECTURE.md
Architectural style, boundaries, dependency direction and integration patterns — the shortest path from never having seen Foundation to productive.
- BRAND_ASSETS.md
The brand-asset swap contract: every replaceable graphic role, in the order to replace them.
- DEPLOYMENT.md
The launch runbook: first deploy, continuous-integration gating, custom domain and the post-deployment verification list.
- instruction-manuals/
The procedures: adoption, customisation, content, branding, validation, deployment, upgrade and troubleshooting.
- LICENSE
The Apache License 2.0 text that governs use, modification and redistribution.
If this page and the repository ever disagree, the repository is correct. This page explains the shape of adoption; the repository performs it.
If you want help, it is available
Provelopment can provide implementation help, technical assistance, support and managed services. That is separate from the foundation and entirely optional.
- Adopting Foundation, deploying it yourself and never contacting Provelopment is a completely successful outcome.
- Nothing in the software depends on Provelopment, and no part of the documentation or the code is held back behind a paid tier.
- Assistance is arranged separately from the project, and this website does not run a sales or support channel.
The order matters: Foundation first, on its own terms; help afterwards, if you want it.
Start where you are
Open a demo to see what a finished Foundation site looks like, read the repository to see what you would actually be working with, and use the manuals when you are ready to build.