SilverStripe.
This is the thinnest page on this site, and it should be. One SilverStripe project: a trade consultancy site, frontend and backend, built and delivered. That is the whole of it. I am not a SilverStripe specialist and I would not start a new project on it in 2026. But almost nobody lists SilverStripe at all, and if you are sitting on one wondering who can touch it, one shipped project beats the alternative you are currently facing.
A CMS editors actually like
The admin is the point of SilverStripe, and it is good: content teams get a clean, comprehensible interface without a developer standing behind them.
Content modelling that holds
Page types and structured fields keep a content site coherent as it grows, instead of degrading into a pile of freeform blocks.
Templates stay separate
A clear split between templates and logic, which keeps the frontend workable and means design changes do not become code archaeology.
Quiet and low-maintenance
A SilverStripe site runs for years without drama. That is a large part of why so many of them are still out there, unattended.
This is the entire reason to call me about SilverStripe. The agency that built it has moved on, and the search for anyone who has used it is going badly. I have shipped one, front and back.
Page types, templates, and admin work on an existing site — the ordinary changes that keep a site current, done without a framework tour first.
If the site has outgrown being a site — accounts, integrations, real application logic — that is a Laravel job, and the content can come with it.
I would not start here in 2026, and one project does not make me the person to lean on for an ambitious new SilverStripe build. New work belongs on Laravel, where I can point at thirty projects instead of one.
SilverStripe is a single project on a long list, kept on this site for one reason: it is nearly unlistable elsewhere. If you are on it, the market for help is thin, and one engineer who has genuinely delivered a SilverStripe site front and back is a better starting point than a stranger reading the docs at your expense.
One project — a trade consultancy site, frontend and backend. That is it, and I would rather you know now than find out later. For maintenance and extension of an existing site, it is enough.
Yes. It is a small ecosystem with a loyal base and very little new adoption, so the people who know it are mostly the ones who built these sites years ago. That is the problem this page exists to solve.
If it is a content site doing content-site things, no — SilverStripe is doing that job fine and a rebuild buys you nothing. If you are pushing accounts, integrations, or business logic into it, that is the signal to move.
In my work
One SilverStripe project: a trade consultancy site, frontend and backend. One is one — but it is one more than most people advertise, and it is the reason this page is here.