A page builder that stays a design system
BuildSpace Sites is the template every BuildSpace client site is stamped out of — a block library, a theme system, and an admin panel an editor can be handed without training.
Most site builders make you choose. Webflow gives you total design control and no way to stop a client breaking it. Squarespace and Wix keep the design safe and cap what you can build. Both answers leave somebody unhappy.
This template picks a third one: an editor composes pages from a fixed library of blocks, and every block reads its colour, spacing and type from theme presets rather than from whatever the last person typed. You cannot make an ugly page here, and you also cannot make a page that looks like everyone else’s.
- 30
- Blocks in the library
- 18
- Page kits
- 8
- Whole-site kits
- 6
- Theme presets
How the template got here
Each of these is a real commit in this repository. A timeline is chronology — dated, backward-looking — which is what makes it a different block from Steps.
- 2026
A resource hub for one client
It started as a single ministry site: bespoke routes, a hardcoded homepage, and a content model full of fields only that client needed.
- Pass one
The seam
Everything split into template core and project surface. `site.config.ts` became the one file a new site edits, so a template update could merge cleanly instead of fighting a fork.
- Pass two
Plugins and AI
Redirects, search, import/export, a blog and three AI features arrived as `CorePlugin`s — collections, blocks and endpoints in one directory behind one flag.
- Now
Blocks and kits
Seven blocks closed the gaps a template marketplace exposed, and page kits turned the library into starting points instead of an empty page and a picker with thirty entries in it.
The Team block, doing its job
People are on nearly every template of every category — about, agency, local service, medical, legal. This is that block with three entries and no portraits, which is what most sites start with.
A person
Role, or what they do here
A bio is one or two sentences. The block offers rich text so a link can go in one, and no heading levels, so a bio cannot compete with the name above it.
Another person
Role
Links are icon-first because that is how a team card reads. The label is still required — it becomes the accessible name, since an icon on its own is silent to a screen reader.
A third person
Role
Three across is the default. Two reads better for a leadership row; four suits a larger team with short roles.
Start from a kit
Eighteen page kits and eight whole-site kits, in the admin panel under “Start from a kit”.