Client project
Four UK small-business websites on one WordPress base
A London removals firm, a Birmingham courier, a Slough halal butcher and a Slough building contractor, each a live marketing site built on NinjaNext Canvas: one theme, one update path, four very different businesses.
All four sites are live and publicly reachable. Each is listed below so the work can be checked rather than taken on trust.
- Client
- Confidential client
- Industry
- Laundry & Local Services
- Period
- 2026
- Platforms
- Web
- Key figures
- 4live client sites on one shared theme
- 1update path covering every site
The problem
Small businesses that win work by phone still need a site that explains what they do and makes contact easy, and they need it on hosting that costs a few pounds a month. Building each one as a bespoke theme means every site carries its own bugs, its own update burden and its own security surface, which is how agencies end up maintaining a dozen slightly different codebases for clients paying very little.
What we built
All four run on NinjaNext Canvas, our in-house WordPress block theme. One base carries the templates, patterns and design tokens; each site picks a style variation that sets its palette, typography and spacing. The layout underneath is identical, so a fix made once reaches every site through the normal WordPress Updates screen. There is no page builder, so the sites stay editable in the Site Editor and keep working on modest shared hosting.
Key features
- A service page per offering, so each service can rank and be linked on its own: eight meat categories for the butcher, eight trades for the contractor, and a page per move type for the removals firm
- A multi-step quote form as the primary conversion path, with the fields each trade actually needs
- Click-to-call and email on every page, because most visitors arrive on a phone
- Opening hours, a real trading address and a coverage area, which is what local buyers check first
- A small posts section per site for guides and trade news
- Terms, privacy and cookie pages on every build
- Style variations that make four sites look unrelated while sharing one codebase
Technology stack
The main technologies used in this project.
- WordPress
- NinjaNext Canvas
- PHP
- theme.json
- Block editor
Our role
NinjaNext built and hosts all four sites on its own theme, and maintains the theme they share.
Challenges and how we handled them
One codebase, four trades that look nothing alike
A remover, a courier, a butcher and a builder have different buyers and different proof. The shared base carries structure rather than style: palette, type and spacing come from a style variation, so the sites read as four separate businesses while a template fix still reaches all of them at once.
A fix should reach every site, not one
Per-site themes mean per-site regressions. Canvas ships updates through the normal WordPress Updates screen from our own update server, so a correction made once is applied everywhere rather than being reapplied by hand on each site.
Built for the hosting these clients actually buy
These are shared-hosting sites, not managed platforms. No page builder, self-contained fonts and no third-party request on page load keep them quick on hardware that is not fast.
Let's build it
Planning something similar?
Tell us about your project. If it is close to Canvas client websites, we will explain what we would reuse, what we would do differently and what to decide first.