Evolution CMS 2.0 RC: Myths, Compatibility, and the Laravel-Based Core

The Evolution CMS 2.0 RC release was not only a technical milestone. It was also a moment of clarification, because many teams had questions about what the Laravel-based core would mean for established Evolution workflows.

The most important message

The new branch did not exist to destroy the old way of working. The point was to preserve what teams already valued while opening the door to more modern architecture, cleaner package development, and stronger long-term maintainability.

Main release themes

• modernized internals built on Laravel components
• continued support for familiar Evolution-style development where appropriate
• better foundation for controllers, models, and packages
• a clearer path toward newer PHP practices without abandoning the CMS identity

Historically, this release matters because it answered the fear that “everything old is gone now.” The real message was more balanced: the platform was broadening, not simply resetting.

Source: GitHub release.