Native multilingual support across all sites

A turning point in 2010

After launching Clarion (2010), we hit a wall: building separate Russian, English, and Ukrainian sites was too costly, too messy, and impossible to scale.

The solution: we refactored the Core to support native multilingual content, not as an add-on, but as a foundation.

Features and highlights

• 🌍 Every site multilingual by design, not duplication.

• 🧩 Phrase-based translation system: every string in the interface and every piece of content could be edited in the admin panel, phrase by phrase.

• 🔄 Single admin panel for all languages — update once, publish everywhere.

• 🗂️ Per-language structure control: sections, menus, and content could differ if needed, or stay unified.

• ⚡ Instant rollout: TchernovAudio was first to benefit, enabling full Russian, English, and Ukrainian versions across its ecosystem.

Why it mattered

• ✅ Clients could expand into new markets without rebuilding sites.

• ✅ Updates became seamless — no more parallel management of “different” versions.

• ✅ For us, multilingual stopped being a “feature request” and became a native property of the Core.

👉 Since 2010, every project on our Core has carried multilingual inside — from small corporate sites to massive ecosystems.