Using Different Domains for Each Language in bLang

bLang becomes much more interesting when it moves beyond simple path prefixes and starts driving real language-specific domains. The donor topic showed a compact but useful pattern: map domains to language codes, set the active language from the current host, and generate alternate URLs from the same configuration.

Core idea

sitename.com=en
sitename.ru=ru

With that mapping, plugin logic can build language-specific URLs, set the right lang parameter from HTTP_HOST, and even keep separate cache behavior for not-found responses when needed.

Why this is useful

• Language domains become explicit instead of implied.
• Cross-domain language switching stays predictable.
• It fits projects where each locale is a real market presence, not just a translated section.

For multilingual Evolution CMS builds, this is a much cleaner direction than bolting domain switching on after the routing layer is already complicated.