Local Development Setup
Set up a local Evo 3 project so package development, migrations, Blade views, assets, and Artisan commands work predictably.
Docs Navigation Open
Development
Development is for implementers who want full control over markup, structure, and custom behavior.
Development in Evolution CMS still starts from familiar elements such as templates, snippets, plugins, and modules. In Evo 3, those classic pieces now live next to a modern runtime with Composer, Artisan, Blade views, service providers, and package-based extensions.
This section explains how to work safely in that mixed model: local setup, project structure, extension points, data access, IDE support, and problem isolation.
Project Structure
Understand the Evo 3 project layout and the package structure used by real custom packages such as example-package.
Extending Evolution
Use service providers, controllers, views, migrations, classic assets, and manager modules to extend Evolution CMS in a package-friendly way.
Events and Modifiers
Use system events and built-in modifiers for targeted customization without rewriting larger parts of the project.
Data Model
Review the main Eloquent models used by Evolution CMS and how resources, TVs, users, permissions, and code elements relate to each other.
Troubleshooting
Troubleshoot Evolution projects in a stable order: structure, data, tags, cache, extras, and environment.