Hire
Docs Navigation Open

Frontend and Layouts

Keep frontend implementation clean by separating content structure, reusable presentation, and runtime logic.

Evolution CMS supports both the classic parser model and modern Blade-backed themes. The correct choice depends on the age of the project, the team, and how much package-level frontend logic is involved.

Classic Layer

  • Template — page skeleton.
  • Chunk — reusable fragment.
  • Snippet — dynamic logic.
  • TV — structured content field.
<!doctype html>
<html>
<head>
  {{head_tags}}
</head>
<body>
  [*content*]
</body>
</html>

Blade-Backed Layer

Evo 3 projects may also use Blade views, package-provided view namespaces, and directives such as @makeUrl(), @evoRole(), and @evoConfig().

<a href="@makeUrl(12)">Catalog</a>
@evoRole('admin')
  <x-manager-links />
@evoEndRole

Practical Structure

  • keep layout concerns in templates or Blade views
  • keep repeatable fragments in chunks or partials
  • keep data queries in snippets, controllers, or package services
  • keep TVs focused on editor data, not on full presentation logic

See Templates, TVs, and Snippets, PhpStorm, and Extending Evolution.

Previous

Commerce Sites

Use Evolution CMS as a content-first foundation for catalogs, stores, and business-facing project flows.
Next

Content Modeling

Model content types deliberately so editors enter structured data and templates stay clean.