Building a Simple Multilingual Switcher Snippet in Evolution CMS

Multilingual sites were always possible in Evolution CMS, but many projects did not need a heavy architecture just to switch between two or three language trees. the article showed a lightweight snippet approach for building a language switcher from known root documents.

The basic idea

Pass a list of language prefixes and corresponding root resource IDs, then let the snippet determine which top-level language branch the current document belongs to.

[!lngChange? &langs=`ru,4;en,5`!]

Why teams liked this pattern

• simple setup for small multilingual sites
• no need for a large switch/case block for each language
• the approach scales to more than two languages with the same basic structure

Where it fits best

This pattern works best when each language has a clear root branch and the content tree is kept consistent across languages. It is a good historical example of how Evolution CMS sites solved multilingual switching before more structured packages became common.