Docs Navigation Open
Current Extras
Prefer current ecosystem extras when starting new work or refreshing an existing project stack.
For new Evo 3 projects, start with maintained packages first. They fit current PHP versions, Composer workflows, migrations, package discovery, and service-provider-based extension.
Platform, API, and Automation
- sApi — API layer
- sTask — scheduled and operational task flows
- eAi, eMCP, ePasskeys — current package-level capabilities
Content and Editing
- DocLister — still practical for listings
- FormLister — still practical for form-heavy projects
- multifields — structured repeatable TV input
- sGallery, eTinyMCE, eCodemirror, eFilemanager
Business Packages
- sCommerce, sOffers, multiCurrency
- sMailer for package-level mail delivery
Localization
- sLang, sMultisite, bLang
How to Pick
Prefer packages that are still maintained, match Evo 3 runtime expectations, and solve the exact project problem without pulling in a whole legacy stack unnecessarily.
Previous
Installing Extras
Install extras through the manager store, Composer packages, Artisan commands, or classic asset bundles, depending on how the extra is distributed.
Next
Legacy Extras
Legacy extras remain important for maintenance and migration because many Evolution projects still depend on them.