When you receive a proposal or an audit report and one of the technologies listed is Laravel, it is reasonable to pause. You know Craft CMS. You may not know Laravel. If your site depends on something you have never heard of, that can feel like a risk.
It is not. If your Craft CMS site was built with a Laravel front-end, that is a considered architectural choice, and right now it is one that puts you ahead of the curve.
Craft CMS manages your content. It is where your editors work, where entries are created, where fields and sections are structured. But content management is only half of what a website does. Something also needs to take that content and turn it into what visitors see, the pages, the navigation, the layouts.
On a traditional Craft site, Craft handles both sides. On a headless setup, those responsibilities are separated. Craft handles content, and a dedicated front-end application handles what visitors see. In this case, that application is built on Laravel.
Laravel is a well-established PHP framework with a large developer community and active maintenance. It is not an obscure or experimental technology. It is the kind of foundation that developers reach for when they want something reliable and well-supported for the long term.
Not every Craft site uses this architecture. A developer choosing a headless setup with a separate Laravel front-end is making a deliberate call. It gives them more control over performance, more flexibility in how content is delivered, and a cleaner separation between content management and front-end code. It tends to suit more complex sites where those trade-offs are worth making.
If your site was built this way, it was not accidental.
Craft CMS is moving its own foundations to Laravel. As we covered in a recent post, Craft 6 will switch its internal framework from Yii 2 to Laravel, the same framework your front-end may already be running on. The authoring experience and content structure carry over, but what sits underneath is changing.
If your site was already built with a Laravel front-end, your development team is already working with the architecture Craft itself is now moving toward. The technology your developer chose is not incidental. It is where the platform is heading.
When Craft 6 arrives, every Craft site will eventually need migrating. For sites on Craft 5, the timeline is comfortable, with Long-Term Support through at least 2031.
But the complexity of that migration depends significantly on how your site is built today. For sites with a Laravel front-end already in place, the upgrade path is considerably simpler. The front-end layer is architecturally aligned with Craft 6. A developer who built your site this way, and understands both Craft and Laravel, is well placed to carry it forward without rebuilding from scratch.
For sites on a more conventional setup, the same migration is achievable, but there is more ground to cover.
Seeing Laravel in a proposal is a signal that your developer understood where the platform was heading and built accordingly. That is the kind of decision that makes a site easier to maintain and upgrade as the platform evolves.
The more useful question is whether you still have the right developer in place. Understanding how your site is built, and having someone who can navigate what is coming, matters more than the technology name itself.
If you are not sure how your site is structured, or whether you have the right technical relationship in place for the road ahead, that is exactly where we can help. We carry out Craft CMS site reviews covering architecture, version status, plugin health, and forward planning. Get in touch to discuss your site.
Craft CMS has announced it is rebuilding its foundations on Laravel, one of the most widely used PHP frameworks in the world. If you run a business on a Craft-powered site, this is the kind of change that can sound alarming but, handled correctly, is entirely manageable. Here is what you need to understand, and what the right response looks like depending on which version your site is running.
If you have been told that a project will be built using Laravel, or if you are evaluating options for a custom web application, you have probably encountered the name without a clear explanation of what it actually is. This is that explanation, written for business owners rather than developers.
Most business websites are built on content management systems. That makes sense for most situations. But there are cases where a CMS is the wrong tool, and the gap between what a CMS can do and what a business needs it to do creates ongoing friction, cost, and limitation. Knowing when a bespoke solution makes more sense is a useful thing to understand.
Most clients come to us when their site has started to feel like a risk rather than an asset. Whether the agency relationship has ended, an upgrade has been delayed, or the site has simply grown beyond what it can handle, a conversation costs nothing.
Get in touch with KarlTrusted by established businesses and growing brands across the UK
Expression 37 works with a small number of clients at any one time. These are some of them.
Karl founded Expression 37 in 2007 and has worked exclusively with ExpressionEngine and Craft CMS ever since. He does not take on work in other platforms and does not hand work to other developers. Expression 37 is deliberately small, because the kind of support that matters to clients with business-critical sites is specific to their site, not something that scales in the conventional sense. If you work with Expression 37, you work with Karl.
Find out how we workKarl has been instrumental in delivering the ExpressionEngine development requirements for our client. Karl very quickly became part of our extended team as he is reliable, dependable and thorough in everything he does. Karl has a genuine desire to see his clients succeed and he will go out of his way to help them achieve that. Karl worked hard on our projects and was so helpful all along the way. He is driven, talented and an absolute pleasure to work with! Any organisation would be lucky to have Karl on their team.
Wayne Smallman
Octane Ltd.