Blog Sections Open
Why the evocms Package Prefix Matters for Evolution CMS Add-ons
A small but useful ecosystem post about naming conventions and why package discoverability matters once an addon ecosystem starts growing.
Package ecosystems become much easier to navigate once naming starts following a visible pattern. That was the practical point behind the Telegram note about using the evocms- prefix: it makes Evolution CMS add-ons easier to discover on Packagist instead of scattering them under unrelated package names.
This may sound minor, but conventions like this improve adoption, searchability, and long-term ecosystem legibility. They help developers find packages faster and help package authors position their work in a way the community can actually browse.
Why this is worth keeping
- it documents an early ecosystem naming convention
- it improves discoverability for third-party packages
- it shows the community thinking about ecosystem structure, not only code
Source: Telegram post and Packagist search for evocms packages.
Console-Based Package Installation in Evolution CMS 3.0
An ecosystem post about installing Evolution CMS add-ons through the console with dependency awareness in the Evo 3 era.
evoCacheManager: A Quick Cache-Building Utility for Evolution CMS
An ecosystem note about evoCacheManager, a small utility for warming or building cache pages in Evolution CMS projects.