Blog Sections Open
Using Inline SVG and JavaScript Gradients in an Evolution CMS Theme
Before modern browser support was taken for granted, SVG in templates often needed JavaScript help and careful fallback planning.
This scenario came from a project that used inline SVG for a stylized headline effect and relied on JavaScript to build the gradient and text nodes. The idea may feel dated now, but it reflects a real frontend pattern from the period: use Evolution CMS for content, then let JavaScript finish advanced visual rendering.
Example SVG shell
<svg class="svg" height="25px" width="590px">
<text id="myCircle" class="important" fill="url(#myGradient)" y="17" x="0">
<tspan></tspan>
</text>
</svg>
Why JavaScript was involved
At the time, browser support for SVG behavior was inconsistent enough that some teams preferred to construct parts of the SVG node tree with script, including gradients and text nodes. That made the effect more portable, but also made the frontend more fragile.
Modern takeaway
The Evo-specific lesson still stands: keep the content values in the CMS, but isolate experimental rendering behavior in the theme layer. Do not let presentation hacks leak back into the content model unless they are truly reusable.
Source: Evolution CMS on GitHub.
Programmatically Creating Users with the MODX Revo API
A practical overview of creating users programmatically in MODX Revolution and why that workflow mattered to developers moving beyond purely manager-driven setups.
MODX EVO Console: A Small Desktop Tool for Working with Data Imports
A look at the old MODX EVO Console utility, what problem it tried to solve, and why import-focused tooling mattered for Evolution CMS teams.