3 years ago

Category: Laravel, PHP, MySQL, api, javascript

I maintain a custom PHP legacy CMS for a client, and have also been building a micro-CMS as a learning project, so I’ve spent quite a lot of time in the last few years thinking about how content should be managed, and how applications to manage it should work. I’ve also at least tinkered with a few different content management systems down the years, and I’ve found it depressing how many times Wordpress has been the default choice, despite it being probably the worst CMS I’ve ever had the gross misfortune to use.

Creating a new site using a CMS should be as simple as running something like the following command: And updating it should be as simple as running the following: Installing a plugin should be a case of running this: It should then be possible to activate the plugin simply by listing it in a config file.

A good CMS should feel familiar if you’ve got some experience working in MVC frameworks, and it should embrace PSR standards. Adding a route should largely be a matter of writing a controller, mapping it to a route, and adding a view file, just as it would be in a framework