Outputting Raw JSON Without Letting the Evolution Parser Eat It

JSON examples that contain are awkward in Evolution CMS because the parser naturally treats those brackets as CMS tags. If you print the data directly inside a page or chunk, the parser may try to evaluate the content instead of leaving it alone.

This is not really a JSON problem. It is a parser collision problem.

Safer ways to handle it

• move the JSON to an external file,
• generate the JSON in a script or endpoint instead of hardcoding it in the page,
• wrap the example in a code-safe output path when the goal is only documentation.

If the JSON is meant for JavaScript execution, an external asset is usually the cleanest answer. If it is meant only as a visible code example, render it through a code block that prevents the CMS parser from touching it.

Whenever JSON contains parser-like tokens, keep it away from the normal template evaluation path.