One Umbraco. Nine sites that do not look alike.

The Double Kit is the baseline every Double Shore website is built on. One block library, one compiled stylesheet, and a Design node that carries the brand. An editor picks a layout; nobody opens a Razor file.

See the nine templates

The Maison Lumiere template, seen at the top of its home page — Maison Lumiere

The Northgate Foundry template, seen at the top of its home page — Northgate Foundry

The Riverbank Trust template, seen at the top of its home page — Riverbank Trust

The Wild Fizz template, seen at the top of its home page — Wild Fizz

The Forno Vero template, seen at the top of its home page — Forno Vero

The Longshore template, seen at the top of its home page — Longshore

The Kirkwall template, seen at the top of its home page — Kirkwall

The Machair template, seen at the top of its home page — Machair

The Halftone Press template, seen at the top of its home page — Halftone Press

Blocks

Template sites

Self-hosted fonts

Stylesheet, for every site

The block library is the product

Every page is a Block Grid. Sections carry the background, the padding, the container width and the edge shape. Blocks carry the content.

Most blocks present themselves more than one way, and the choice is a picker rather than a class name, so the same block is a boxed stat row on one site and a divided one on the next.

Open the block guide

What a site gets on day one

A Design node

Two brand colours, the fonts, the corner radius, the container width, the animations. The stylesheet follows without anyone opening a CSS file.

Twenty-eight blocks

Hero, slider, gallery, table, timeline, FAQ, map, form, files, before and after. Most of them present themselves more than one way.

Seven header layouts

Centred logo, mega menu, side rail, floating bar. A picker on the settings node, not a rebuild.

Multisite

Several websites in one Umbraco, each with its own domain, its own brand and its own languages. This instance runs a dozen.

SEO built in

Per-page titles and descriptions, schema markup, a sitemap that knows which site it is on, and a 404 an editor can write.

Accessibility as a rule

Nothing under 16px, contrast checked before a palette is written, and an image will not publish without alt text.

E-commerce, when it is wanted

A separate package. Store, cart, checkout, Stripe, shipping, product import from a spreadsheet. Leave it out and nothing e-commerce appears.

Editor tooling

Content insights, content and media cleanup, a content calendar, page locking, and drag-and-drop in the content tree.

One upgrade path

The Kit ships as NuGet packages. A client site bumps a version and gets every block, fix and layout added since.

How a site gets built

Scaffold

A new site root scaffolds its own home page, settings, design, legal and system pages.

Brand

Colours, fonts, roundness and animation on the Design node. The stylesheet is compiled once for the instance.

Build the pages

Every page is a Block Grid. Sections carry the band, blocks carry the content.

Go live

One domain per site, per language. Deploys follow the same container runbook every client uses.

What ships, and what is still being built

The second half of this table is honest work in progress. It runs on branches, not on a client site.

Feature	What it is	State
Block library	28 blocks	Shipping
Design node	Colours, fonts, roundness, animation	Shipping
Multisite	Domain, brand and language per site	Shipping
E-commerce	Optional package	Shipping
Editor tooling	Insights, cleanup, calendar, locking	Shipping
AI page generation	Landing pages and SEO copy	In progress
Analytics and heatmaps	Own section, no third party needed	In progress
CRM	Deals, inbox, forms into deals	In progress
Bookings	Availability and reservations	In progress
Cookie consent	Scanning and tag blocking	In progress

Questions we get asked

Is this a theme or a starter kit?

Neither, quite. It is a set of NuGet packages a site depends on. The blocks, the views and the stylesheet arrive with the package and are upgraded with it, so a fix written today reaches every client that bumps a version.

Can an editor really change the layout?

Yes, within the choices a block offers. A block's layout is a picker on the block, so switching an icon list from rows to cards is one field. Leaving it unset renders what the block rendered before that choice existed, so nothing already published moves.

How many sites fit in one Umbraco?

As many as the content tree can hold. This instance runs nine template sites plus this one and a couple of client replicas, each with its own domain, brand and language set, on one database and one compiled stylesheet.

What about accessibility?

It is a gate, not a goal. A palette is contrast-checked before it is written, no text is allowed under 16px, and a picture cannot be published without alt text. Pages are scanned with axe-core against WCAG 2 A and AA.

Is the e-commerce optional?

Entirely. It is a second package. A site that does not reference it has no store, no cart and no checkout, and the backoffice shows none of it.

Look at it rather than read about it

Nine of them are running in this same Umbraco, on this same block library, right now.

Open the templates