Blog Sections Open
evoBabel: A Different Multilingual Direction for Evolution CMS
YAMS was the default reference point for multilingual Evolution CMS projects for a long time, but it was not the only possible direction. evoBabel explored a different model inspired by the ideas behind MODX Revo Babel.
YAMS was the default reference point for multilingual Evolution CMS projects for a long time, but it was not the only possible direction. evoBabel explored a different model inspired by the ideas behind MODX Revo Babel.
Why It Stood Out
- closer alignment with structured multilingual content relationships
- support around DocLister, Wayfinder, and Breadcrumbs integrations
- more explicit handling of translated fields and TV data
The value of evoBabel was not just “another language addon.” It represented a different architectural answer to multilingual content in Evolution CMS.
That makes it a good Ecosystem article: it documents a real shift in how the community thought about multilingual implementations.
Source: original evoBabel article.
Integrating LiqPay Payments into an Evolution CMS Order Flow
A practical note on where LiqPay should connect into an Evolution CMS checkout flow and why order identifiers matter early.
Sending SMS from Evolution CMS with ByteHand
A short ecosystem overview of the ByteHand integration for sending SMS notifications from Evolution CMS or MODX Revolution workflows.