Content Modeling

Content modeling in Evolution CMS starts with the resource tree, templates, and TVs. The goal is simple: each content type should have its own structure, editing fields, and output rules.

Core Building Blocks

• Resource — one page, product, article, landing page, or record in the tree.
• Template — page structure and output logic.
• TV — structured field attached to selected templates.
• Chunk — reusable HTML fragment.
• Snippet — dynamic logic used for output or processing.

Typical Modeling Pattern

A product template may use TVs such as price, old_price, gallery, sku, and vendor. A news template may use published_at, lead, and cover_image. Do not force different content types into one generic template.

Useful Extras

• multifields and multiTV — repeated structured rows inside one resource.
• cfgTv — configuration-style field editing in older projects.
• sGallery — media attached to resources from the manager.
• DocLister — listing structured content once the model is stable.

Output Example

[[DocLister?
  &parents=`12`
  &tpl=`product_card`
  &tvPrefix=``
  &orderBy=`menuindex ASC`
]]

This works well only when the product resources already share one template and one predictable TV set.

Practical Rule

Model first, list later. If editors do not know where to enter a value, developers will not be able to query or render it consistently either.

See also Templates, TVs, and Snippets, Lists, Forms, and Search, and the TVs & Field Types extras section.