Blog Sections Open
Console-Based Package Installation in Evolution CMS 3.0
A tooling-focused ecosystem post about why console-based package installation mattered once Evolution CMS moved closer to a Composer-friendly workflow.
Console-based package installation is one of those infrastructure changes that quietly improves everything around it. Once add-ons can be installed from the command line with dependency awareness, package management becomes less manual, less fragile, and easier to automate across environments.
That is why this short Telegram note is still worth preserving. It captures a real shift in how Evo packages could be handled in the 3.0 era: less like copied files, more like manageable dependencies.
Why this tooling step mattered
- it reduced friction around package installation
- it made dependency-aware workflows more realistic
- it aligned Evo package handling more closely with modern PHP expectations
Where this fits in Evo 3
This kind of tooling note belongs in the timeline because Evo 3 was not only adding features. It was also changing how teams installed, updated, and automated project dependencies. Command-line package handling is one of those quiet shifts that makes the whole platform feel more modern in daily work.
Source: Telegram post.
Thinking Beyond DocLister: Eloquent Patterns in Evolution CMS 3
An ecosystem article about using Eloquent-style patterns in Evolution CMS 3 and when that approach can be a better fit than older listing helpers.
Why the evocms Package Prefix Matters for Evolution CMS Add-ons
An ecosystem note about the evocms package prefix and why discoverability on Packagist matters for Evolution CMS add-ons.