Evolution CMS 3.5.0

Evolution CMS 3.5.0 is a milestone release because it combines a modern framework baseline with a deliberately conservative product strategy. The release note is not just a changelog. It is a positioning document: Evolution CMS is presented as a mature platform with more than two decades of continuity, modern internals, and a commitment to backward compatibility rather than disruptive rewrites.

The central technical point is the move to Laravel 12 as the backend baseline for the 3.5 generation. That matters because it gives the project a stronger long-term application core while preserving the familiar Evolution editing model and project delivery style.

Main release themes

• 21 years of continuous development: the release explicitly frames Evolution CMS as a stable platform with a long lineage from MODX Evolution 0.7 in 2004 to the modern Evolution CMS branch.
• Laravel as strategic foundation: since Evolution CMS 2.0 the backend has been built on Laravel, reducing maintenance risk, broadening architectural options, and aligning Evo with a well-supported PHP ecosystem.
• Evolution, not revolution: the team stresses updates and continuity instead of breaking rewrites, with backward compatibility still treated as a core principle.
• Scalable ecosystem: the release highlights real surrounding modules for commerce, SEO, multilingual content, multisite, async tasks, and media management.

What 3.5 adds to the timeline

This release is important not only because of a framework upgrade, but because it clearly explains the project’s philosophy. Evolution CMS is positioned as a platform that wants modern internals without abandoning long-lived production sites. That is why 3.5.0 belongs in the release archive as both a technical and strategic milestone.

Ecosystem directions highlighted in the release

• sCommerce for ecommerce
• sSeo for SEO work
• sLang for multilingual sites
• sMultisite for multisite architectures
• sTask for asynchronous task processing
• sGallery for structured content and media handling

Source: View full release notes on GitHub.