What Are Extras
Extras include snippets, plugins, modules, TVs, and package-based add-ons that extend Evolution CMS.
Docs Navigation Open
Extras and Packages
Extras are a major part of how Evolution CMS projects grow over time.
This section is about Evolution CMS extras and component documentation. In the older docs, this area was organized mostly by component name: DocLister, FormLister, Commerce, eFilter, YAMS, Wayfinder, eForm, PHx, ManagerManager, and many others.
That old structure is still important because many live projects were built with those components. Evo 3 also adds a newer package-based layer with actively maintained extras such as sApi, sTask, eAi, eMCP, ePasskeys, sCommerce, sOffers, sLang, and related tools.
Use this section to understand what an extra is, how to install it, when to prefer a current package over a legacy component, and how the old component docs relate to the current extras catalog.
Installing Extras
Install extras through the manager store, Composer packages, Artisan commands, or classic asset bundles, depending on how the extra is distributed.
Current Extras
Current extras are the preferred starting point for new Evo 3 projects and refreshed project stacks.
Legacy Extras
Legacy extras remain important for maintenance and migration because many Evolution projects still depend on them.
Creating an Extra
Create an Evolution CMS extra as a real package with composer metadata, a service provider, config, migrations, views, assets, and optional classic elements.
Maintaining Extras
Maintain extras as real packages with documented install flow, compatibility notes, config, commands, assets, and upgrade guidance.