Blog Sections Open
Parsing a Template Through the Evolution CMS API Before Output
Sometimes you need to work with a template as data, not just let Evolution render it at the end of the request.
parseChunk() is convenient when you already know which chunk you want to render. The harder case is when the real target is a template or a template-like document structure that must be assembled before the page finishes rendering.
The key idea
Instead of thinking only in terms of chunk parsing, think in terms of loading the template source first and then passing known data into the parser in a controlled way.
This is especially useful for custom rendering flows, export logic, preview builders, or API responses that reuse template fragments without following the full standard page lifecycle.
Rendering Chunks Reliably from Within Template-Driven Workflows
A practical way to think about chunk rendering when template-level composition starts to outgrow simple parseChunk calls.
Building Multiple Independent Filters on One Page with Ditto
How to design several filters on one page when a single autoFilter instance is not enough for the listing experience you need.