Installing Extras

Choose the Install Path by Package Type

1. Manager Store — easiest path for classic installable extras
2. Composer package — correct path for modern Evo 3 packages
3. Manual asset bundle — fallback for legacy components

Modern Package Install Flow

example-package shows the preferred Evo 3 package flow.

php artisan package:installrequire evolution-cms/example-package "*"
php artisan package:discover
php artisan migrate
php artisan example:install-demo

What Happens in That Flow

• package:installrequire adds the Composer dependency
• package:discover discovers the package provider
• migrate applies package migrations
• example:install-demo publishes assets and seeds templates, TVs, and documents

Publishing Optional Assets

php artisan vendor:publish --provider="EvolutionCMS\Example\ExampleServiceProvider" --tag=example-assets
php artisan vendor:publish --provider="EvolutionCMS\Example\ExampleServiceProvider" --tag=example-config
php artisan vendor:publish --provider="EvolutionCMS\Example\ExampleServiceProvider" --tag=example-views
php artisan vendor:publish --provider="EvolutionCMS\Example\ExampleServiceProvider" --tag=example-migrations

Classic Assets Inside a Modern Package

A package may still ship classic Evolution elements. In example-package these live under:

• assets/chunks
• assets/snippets
• assets/plugins
• assets/tvs
• assets/modules

Install Rule

If the extra has a Composer package, service provider, migrations, config, routes, or commands, treat it as a package first. Do not document it as only a store install.

For package structure, continue with Project Structure and Creating an Extra.