On the Cloudways blog there's a new post from author Saquib Rizwan that compares two of the most popular Laravel-based content management systems: OctoberCMS VS AsgardCMS.

Web developers and development agencies around the world love rapid application development. To keep up with the fast pace of development and fulfill client requirements within the deadline, developers often use a CMS. Popular CMS options available today include WordPress, Drupal, Joomla, and Magento. There are times when these established players are not up to the task. In such scenarios, developers often need a flexible and customizable CMS that are often created using the Laravel framework.

In this article, I will compare OctoberCMS and AsgardCMS, the top two Laravel powered CMS.

The article starts with a brief overview of each, describing some background and how their architected. It then lists some of the requirements for each, installation methods, GitHub "profile" and the basic features offered. It then gets into the comparison, sharing some of the pros and cons for each CMS. There's no "winner" in the article as it's just designed to compare.

In a new post to his site Nicolas Widart introduces you to the idea of building Laravel applications a bit differently than you may normally: in a more modular structure. This structure makes use of this package to make it happen.

Let me start by saying Laravel is an amazing framework. However when it comes to writing more complex and bigger applications, I find the default structure laravel comes with cumbersome and not ideal.

The way the default laravel installation comes with is basically all the application logic inside an app/ folder. This works, but I would not suggest going this route. [...] This is what being modular is trying to resolve. You split of the business logic into different parts, which belongs together. If you're into Domain Driven Design, you can consider a module an aggregate.

Each module has its own resources (routes, models, views, etc) combined into a single "drop-in" structure. He provides an example of this structure and compares it to the more traditional Laravel "all-app" structure. The package he links to makes this modular structure simpler and points out that this system is what the AsgardCMS already uses behind the scenes.