Source record
The creator returned from Laravel to WordPress because WordPress already provides a customizable admin backend for client content management.
Use WordPress for years, but moved to Laravel for backend. So I used that WordPress for years. I've used it for 15 years.
And there was a period where we went through. We were building some quite bespoke projects. And at the time I felt like we needed to move to something else.
And I built probably four projects, I think, in Laravel. And while the front ends were great and they were light and fast and, you know, I was really impressed by the way it worked, what frustrated me was having to build out the CMS. In the background.
So that's why I went back to WordPress and carried on building with WordPress. Because I felt like that was one less thing that we had to build. I didn't have to build a back end for my clients to manage the content.
And that's why I think WordPress is so powerful, because it has this admin that you can use and customise any way that you want. So for me, I sort of build now with the thought process of Laravel. I build a custom front end, but I just utilise WordPress's backend to manage the content for the clients.
And then I customise that. So, yeah.
The creator returned from Laravel to WordPress because WordPress already provides a customizable admin backend for client content management.
Use as a platform-choice card: separate custom front-end needs from the cost of building a CMS/admin backend.
This source is connected to WordPress backend versus custom Laravel backend.
So that's why I went back to WordPress and carried on building with WordPress. Because I felt like that was one less thing that we had to build. I didn't have to build a back end for my clients to manage the content. And that's why I think WordPress is so powerful, because it has this admin that you can use and customise any way that you want.