CI4 CMS

Ivo Miranda, Sounds good but, The problem I see is getting a few people (let alone an entire team) to agree on one way to implement something.

Either way I have mine "system" broken into 6 main parts with everything else installed as a package depending on the project.

Users, Groups, Access
Package Manager
Settings, Menu

Package Manager I think is self explanatory.

Users, Groups, Access library's provide API for packages to add/remove/modify these areas. This also provides basic login/logout
Settings provided a GUI / standardized library to add configure values either by packages or manually.
Menu provides a GUI / standardized library for packages to add menubar entries. Again either from automatically or manually.

Everything else I composer in as a "package" and install it with package manager.

Even the Backend Admin theme is a package which just works with the APIs exposed by those 6 "libraries"

I am sure others have a lot more ideas than mine but, like I said getting even 2 or 3 people in agreement is pretty tough.

DMyers
https://github.com/ProjectOrangeBox

https://github.com/ProjectOrangeBox / https://github.com/dmyers2004