Multilingual and Multisite

Multilingual and multisite projects should be planned at the URL and tree level. The core question is not only translation, but how all language variants stay structurally consistent.

Current Packages

• sLang — modern language management for Evo 3 projects.
• sMultisite — shared codebase and manager workflows for multisite setups.
• bLang — lightweight multilingual package still seen in some projects.

Legacy Package: YAMS

YAMS is one of the most feature-rich multilingual addons in older Evolution projects. Its main idea is that all language variants can stay in one document tree while templates and placeholders generate language-aware content and URLs.

• one tree for all languages
• language-aware placeholders in templates
• multiple URL strategies: aliases, root-name prefixes, hostnames, mixed modes
• extensions for Ditto, Wayfinder, Jot, and eForm
• custom multilingual TVs

Questions to Decide Early

• Will each language use its own branch, hostname, or root prefix?
• Do editors translate per resource or maintain parallel trees?
• Does one manager serve one site or several sites?

Practical Recommendation

Use sLang and sMultisite for new Evo 3 work. Keep YAMS, evoBabel, or bLang where a legacy project already depends on them and the migration cost is higher than the maintenance cost.

See the Localization & Multisite extras section.