Thoughtful multilingual support

In our engine, multilingual support is designed not as an extra add-on, but as part of the website architecture itself. That means the project can be developed step by step in one language first, and other language versions can be added later without rebuilding the whole structure.

During development, one working language can be selected. Closer to launch, it is easy to decide which language will be the main language of the website. This is convenient because at the beginning we can focus on the page structure, logic, and content in the language that is most comfortable for the workflow.

The main language is displayed in the most natural way possible. For example, if Ukrainian is chosen as the primary language, the homepage opens simply at:

your-site.com

And not through an additional language prefix:

your-site.com/uk

So the user does not have to enter the site and immediately be redirected from the homepage to /uk. The main language really remains the main one: it lives on the clean domain without extra parts in the address.

Additional languages are then connected through their own prefixes in the links. For example, if English and Russian are added, their addresses would be:

your-site.com/en your-site.com/ru

This makes the link structure look clearer, cleaner, and better emphasizes the main language of the project.

Many websites handle multilingual support less carefully: a person opens the homepage and is immediately redirected to an address like your-site.com/uk or your-site.com/en.

In our structure, that is not required. If Ukrainian is selected as the main language, it stays on the clean domain without an extra /uk in the URL.

For example:

your-site.com              - homepage in Ukrainian
your-site.com/contacts     - contacts page in Ukrainian

your-site.com/en           - homepage in English
your-site.com/en/contacts  - contacts page in English

your-site.com/ru           - homepage in Russian
your-site.com/ru/contacts  - contacts page in Russian

That means the main language is not hidden behind a technical prefix. It opens naturally: the homepage stays on the clean domain, and inner pages also live without unnecessary language codes.

Additional languages are connected cleanly through their own prefixes. Such a link structure is clearer for the client, more convenient for the user, and better shows which language is the primary one for the project.

This approach makes the site cleaner, easier to understand, and more convenient for further promotion.

Another advantage is translation workflow. There is no need to translate every tiny element separately and then rebuild everything from pieces by hand. A page is stored as complete content, so it can be translated in full: text, blocks, semantic sections, and structure.

Only the key elements for a specific language are changed separately: the page title, the menu label, the SEO description, and the content itself. This is much simpler than working with hundreds of separate phrases and keys.

It is especially convenient to translate such pages with GPT-based tools or other AI models. You can take an already finished page, translate it as a whole, and quickly add a new language version to the site while preserving the structure and style.

As a result, multilingual support does not get in the way of development, does not complicate the structure, and does not become a burden for the content manager or a technical problem for the developer. The website can first be launched in one language and then expanded calmly by adding other languages as the project develops.