Blog Sections Open
Why Evolution CMS 3 Moved to Laravel 8 for Composer 2 Compatibility
A concise ecosystem post about a dependency decision that had a very practical cause: keeping Evolution CMS aligned with Composer 2.
Framework upgrades are not always about chasing features. Sometimes they are driven by the surrounding PHP tooling ecosystem. This was one of those moments. The Telegram note makes the reason very clear: Evolution CMS 3 needed the Laravel 8 move to avoid problems with Composer 2.
That is a small but useful ecosystem milestone because it shows how platform maintenance decisions often come from tooling pressure, not only roadmap ambition. It also helps explain why some dependency jumps happen earlier than users might expect.
Why this note matters
- it explains a practical dependency decision in plain terms
- it connects Evo’s framework layer to Composer ecosystem changes
- it helps future readers understand the maintenance logic behind the upgrade
Source: Telegram post and the Laravel 8 release notes.
Laravel 8 HTTP Client in Evolution CMS
An ecosystem post about using the Laravel 8 HTTP client inside Evolution CMS and why that matters for integrations.
User TVs in Evolution CMS: Extra Fields Without the Old Workarounds
An ecosystem post about user TVs in Evolution CMS and the PR that made user extra fields far more natural to manage.