Blueprints vs templates
How blueprints, templates, and reusable sections differ when you edit them later: a blueprint copies blocks once, while a template and a reusable section stay in sync.
Basker gives you three ways to reuse structure across your site, and they behave differently when you edit them later. The difference comes down to one thing: a blueprint is a copy, while a template and a reusable section are shared.
- A blueprint gives a new page a head start. Its blocks are copied in once, and from then on the page is yours to change. Editing the blueprint later only affects pages you create afterwards.
- A template controls how a kind of page looks on the live site. It is defined by your theme and shared by every page of that type — change it once and every page using it changes.
- A reusable section is a block of content built once and embedded on many pages. Edit the section and every page that embeds it updates.
The one rule to remember
If you want a head start you'll then change freely, use a blueprint — you get a copy. If you want one change to ripple everywhere, use a template for the overall look, or a reusable section for a chunk of content.
Side by side
| Blueprint | Template | Reusable section | |
|---|---|---|---|
| What it gives you | A starting arrangement of blocks for a new page | The look a kind of page renders through | A block of content embedded on many pages |
| How it attaches | Copied in once | Shared and referenced live | Shared and referenced live |
| Edit it later → existing pages | Not affected (only future pages) | Every page using it updates | Every page embedding it updates |
| Editable per page afterwards | Yes, fully independent | Per-page appearance overrides only; the structure stays shared | No — edit it in its own area |
| Where it lives | Blueprints, under Design | Comes from your theme | Sections, under Website |
| Applies to | One content type you choose | A content type, often with a default | Any page |
Blueprints copy, once
When you start a page from a blueprint, Basker copies the blueprint's blocks into the new page. The blueprint area even tells you this directly: These blocks will be copied into new items when this blueprint is applied. Editing blocks here will not change any existing items.
After that, the new page is independent. You can add, remove, and rewrite its blocks without touching the blueprint — and updating the blueprint later won't reach back into pages already created from it. Only future pages pick up the change.
Reach for a blueprint when teams keep rebuilding the same opening arrangement of blocks and each page then diverges.
See Blueprints for creating one, choosing which content type it applies to, and showing or hiding it in the picker.
Templates stay in sync
A template defines how a whole kind of page looks — for example, the banner area at the top of every event page. Templates come from your theme, so you don't build one from scratch; you adjust the one your theme provides. Because every page of that type renders through the same template, one change updates them all at once.
One template per content type can be marked Set as Default Template. New pages of that type then use it automatically and stay in sync with it.
Per-page appearance
A template fixes the shared structure, but you can still override the look of a single page without breaking the link to the template. See page theme settings.
Templates and global appearance are theme-level work — see themes for what a theme controls and theme settings for site-wide colours, fonts, and navigation.
Reusable sections stay in sync
A reusable section carries a chunk of content you embed on many pages. Build a section once — a contact block, a sponsor strip, a standard call to action — embed it across your pages, and editing it once updates every page that embeds it.
See reusable sections for building and embedding them.