Docs Navigation Open

Terminology

Learn the core Evolution CMS terms, parser tags, and the way templates, TVs, chunks, snippets, and plugins work together.

Core Elements

Resource (older docs often say document) is the main content object in the site tree. A resource stores fields such as pagetitle, alias, introtext, content, template, parent, and publication flags.
Template defines the page structure. In classic Evolution it is mostly HTML with Evolution tags. In Evo 3 it may also be backed by Blade views.
TV (Template Variable) is an extra field attached to a template. TVs are used for structured content such as prices, subtitles, images, links, flags, dates, or repeatable editor inputs.
Chunk is a reusable presentation fragment. It usually holds markup, but it may also hold plain text, e-mail layout, JSON fragments, or placeholder-based partials.
Snippet is executable PHP logic used to build dynamic output, process input, or prepare data for templates and chunks.
Plugin is code that runs on a named event such as saving a resource, rendering a page, or authenticating a user.
Module is a manager-side tool or application screen. Modules are used for larger back-office workflows.
Placeholder is a named runtime value that snippets and parser logic can inject into output and later render in templates or chunks.

Common Tag Syntax

[*pagetitle*], [*longtitle*], [*content*] render resource fields.
[*price*] renders a TV value when the TV name is price.
{{Header}} renders a chunk.
[[DocLister? &parents=`2`]] calls a cached snippet.
[!FormLister!] calls an uncached snippet.
[+title+] renders a placeholder.
[(site_name)] renders a system setting.
[~44~] renders a URL for a resource id.
[^t^], [^q^], [^m^] render debug-style parser values.

Cached and Uncached Snippets

Evolution supports both cached and uncached snippet calls. Use cached calls when the result may safely be reused. Use uncached calls when output depends on the current request, session, user, cart, or form state.

[[Wayfinder? &startId=`0`]]
[!FormLister!]

How the Parts Work Together

A template usually calls chunks, snippets, TVs, and resource fields together. The old documentation explained this point well and it still matters in Evo 3.

<!doctype html>
<html lang="[(lang_code)]">
{{head_tags}}
<body>
    {{site_header}}
    [*content*]
    [[Wayfinder? &startId=`0`]]
</body>
</html>

If you want the practical side of tree-based content, continue with Resources. For model classes and Eloquent relations, see Data Model.

Cheat Sheet

Keep the most common tag patterns, fields, and quick syntax reminders in one place.

Resources

Understand how resources are stored, how the tree works, and how SiteContent can be queried in code.