PhpStorm

This page is for developers working with Blade views and package code in Evo 3.

PhpStorm Setup

1. Open the project root so PhpStorm indexes composer.json, core/src, views, and core/custom/packages.
2. Run Composer install before expecting autoload navigation and completion to work.
3. If you use Laravel Idea, keep it enabled. It already handles most Laravel and Blade features.

Custom Blade Directives

Evolution CMS adds a few project-specific directives that older PhpStorm setups may not know automatically.

• @makeUrl($id) — render a resource URL
• @evoRole($role), @evoElseRole($role), @evoEndRole — role-based output
• @evoConfig($name, $default) — read Evolution configuration

What to Register Manually

If Laravel Idea does not discover them, add these Blade directives in PhpStorm under PHP → Blade → Directives.

• makeUrl — parameter required
• evoRole — parameter optional or role key
• evoElseRole — parameter optional or role key
• evoEndRole — no parameter
• evoConfig — one required config name, one optional default value

Workspace Advice

Keep package folders, site views, and core code in one workspace. That gives you usable navigation between Blade templates, service providers, controllers, migrations, and package config files.