Docs Navigation Open
What Are Extras
Understand how extras extend Evolution CMS and why they have always been part of the ecosystem.
An extra is any installable extension that adds behavior to Evolution CMS. Some extras are only one snippet. Others are full packages with migrations, config, views, routes, modules, assets, and service providers.
Classic Extra Types
- Listing and data — DocLister, Ditto
- Forms — FormLister, eForm
- Navigation — Wayfinder, Breadcrumbs
- Output helpers — PHx
- Manager customization — ManagerManager
- Multilingual — YAMS, evoBabel
- Commerce — Commerce, Shopkeeper, eFilter
Current Evo 3 Package Types
- API and automation — sApi, sTask, eMCP, eAi
- Security and auth — ePasskeys
- Commerce — sCommerce, sOffers
- Localization — sLang, sMultisite
- Media and editing — sGallery, eTinyMCE, eFilemanager, eCodemirror
What Extras Usually Solve
Most real Evolution sites depend on extras for lists, menus, forms, multilingual behavior, manager UX, media handling, or commerce. Choosing the right extra is often more important than writing everything from scratch.
Maintaining Extras
Maintain extras as real packages with documented install flow, compatibility notes, config, commands, assets, and upgrade guidance.
Installing Extras
Install extras through the manager store, Composer packages, Artisan commands, or classic asset bundles, depending on how the extra is distributed.