Double Shore builds the Kit, and builds on it
We are a small web studio in Lisbon. The Double Kit is not a product we sell on a marketplace: it is the baseline our own client work runs on, which is why it gets fixed rather than abandoned.
28
Blocks
9
Template sites
16
Self-hosted fonts
1
Stylesheet, for every site
How it got here
-
The problem
Every site started from nothing
A new client meant a new Umbraco, a new set of doc types, a new stylesheet and a new set of bugs. Nothing learned on one project reached the next one.
-
The decision
One baseline, shipped as packages
The blocks, the views and the stylesheet became NuGet packages. A client site depends on a version rather than owning a copy, so a fix written once reaches everyone who upgrades.
-
The hard part
Making one Kit produce different sites
A shared baseline is worth nothing if every site it builds looks the same. So the brand moved onto a Design node, and every block that could reasonably present itself more than one way got a layout picker.
-
The proof
Nine sites in one Umbraco
A hotel, a foundry, a charity, a soft drink, a pizzeria, a surf school, a design studio, a bicycle shop and a comic shop. Same packages, same database, same compiled stylesheet.
-
Now
Beyond the website
AI page generation, analytics without a third party, a CRM, bookings and cookie consent are being built on the same baseline, so a client gets them by upgrading rather than by buying another product.
What this means for a client
You are not buying a one-off build that ages the day it ships. The site you get is on the same version as every other site we run, and it moves forward with them.
If you want something the Kit does not do yet, it gets built into the Kit, and then everyone has it.
Start a conversation
Tell us what the site has to do. We will tell you honestly which parts the Kit already covers and which parts are work.