Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

msd-it's avatar

Laravel as CMS (backend/frontend)

Hello Laravel Experts,

I would like to develop a universal backend (CMS-like) app in Laravel that will be used for the administration of future web sites.

Everything is fine when I talk about one web site, but my plan is to develop a separate Laravel application that will be my universal backend and attach that code to different front ends.

The technical question is, I have sites 1, 2, and 3; I would like to have the same backend but a different frontend. I can deploy 2 laravel apps as final product on same db and every site will have same backend app + unique forntend and additional db tables.

It is possible to deploy that backend and have some sort of git or composer-like process that will update all backends (something like the composer requirements for Livewire) on all of my websites.

Thank you a lot for your ideas in advance...

0 likes
4 replies
Snapey's avatar

develop your backend as a package and then require it in each of the projects.

You would still need to visit each project and update its dependencies, but this could be scripted.

msd-it's avatar

Hello, @Snapey,

First of all, thanks for the ideas and tips! If I understand you correctly, I can develop a Laravel app or a part of a Laravel app and deploy it as a module. I know that I need to update all my sites, and this is OK, but my main idea was to develop the backend in one place and deploy it everywhere. If you have some useful links and documents about how to develop a Laravel app and deploy it as a package, please add them here to give me an idea of where to learn more about that.

Thanks, once again, for all...

Snapey's avatar

Each project would be its own laravel installation, but your backend admin would come from the package.

The package gets installed into the project.

But, these things very rarely pay off since each project will need a unique set of models to manage and things get messy when you have a standard admin area but now you need to manage a new entity that you have not done before and you need just for the one project.

Have you considered Laravel Nova ? No point re-inventing the wheel?

msd-it's avatar

@Snapey

Thanks for advice, Laravel Nova look fine and I'm going to give my attention and time to that idea.

Thanks again for all...

Please or to participate in this conversation.