Laravel for Content Management: October CMS and PyroCMS 3

Laravel is an open source PHP web framework. It is intended for development of all kinds of web applications using the MVC (Model View Controller) methodology that separates concerns of storing data, managing the layout and taking actions on the two.

The framework is now considered to be one of the most popular PHP frameworks together with Symfony2, Yii and Zend Framework 3. While Laravel sometimes receives criticism, it certainly makes up for this in marketshare that is gained through to ease of use.

As a general purpose framework it is no surprise that there are a number of Content Management Systems built on it. Two prominent ones are October CMS and PyroCMS. Both are individual projects that share a common framework. In turn Laravel uses several Symfony Components to power core functionalities such as HTTP messaging abstraction and console.

October and Pyro are both quite similar in concepts and share an ethos of simplicity. Both are easy to use and have and attractive user interface. As an older project (on Laravel) October is a bit better established and it has a thriving market place. PyroCMS only moved to Laravel in a recent rewrite.

The danger of coupling tightly to a framework like Laravel is that they have limited control on how the underlying system moves forward. This gives certain instability, especially since the Laravel API has only stabilised lately. From the first iterations until the current Laravel 5.x series the API has undergone many changes.

This has enabled Laravel to evolve quickly, but for a system that is possibly live for a decade it might be preferred to use a more backwards compatible friendly frameworks, one of which is the Symfony2 framework.

In addition neither October CMS or Pyro3 offer comprehensive REST API or GraphQL interfaces for decoupling from the backend of the CMS. This might be a limiting fact for many looking forward to using these tools as a backend for front end apps built with Angular 2 or React.js.