How Humanfrog Started Speaking Croatian, Italian, German, and Hungarian

For now, English only 

»For now, we will launch the website in English and add translations later.« That decision was made at one of our meetings as the website launch deadline was fast approaching, and there were too many language versions to prepare in time. The temporary solution seemed sensible, as we were confident we would handle the translations soon after launch. 

The problem was not just the translation itself. Each language version had to be prepared, reviewed, and entered, and then properly updated with every content change. Even a minor edit on the source page could mean a new round of coordination across the language versions. 

The content was ready, as were the expertise and technical capabilities. What was missing was an efficient way to manage multilingual content without extra manual work and constant coordination. As a result, the temporary solution stayed in place much longer than we originally planned. 

The solution was within reach all along 

Although we work every day on development, content, and digital solutions for clients, our own improvements often wait for a more suitable moment. Our own website is often the one that comes last. The shoemaker often goes barefoot. 

In our case, the situation was even a little more unusual. Our team also includes Josh Rocchio, an American who has lived in Slovenia for twenty years and could have helped adapt the English content to other languages quickly and at minimal cost. So the solution was within reach, yet the task still did not make it to implementation for a year and a half. 

This clearly showed that the issue was not access to expertise or translators. What was missing was a system that would integrate translation into regular website management and reduce the amount of manual work. 

Since last week, things are different 

Our website is now available in multiple languages, and translation of new content is automated. We prepare the content in the source language, and the system generates the corresponding language versions. Translations are no longer a separate task waiting for a better moment; they are produced together with the new content. 

How it works 

Behind the scenes, AI agents are directly connected to our CMS systems. Their task is not only to translate the text, but to prepare complete language versions that take into account content structure, terminology, context, and the characteristics of each market. 

When an editor prepares new content, the system: 

• identifies all elements that need to be translated, 

• creates versions in all supported languages, 

• retains the page structure and content layout, 

• applies the agreed specialist terminology, 

• adapts specific parts of the text to the language, market, and target audience, 

• places the content into the appropriate language fields in the CMS. 

This is not just literal translation. The system can adjust individual terms, sentences, or emphases so the content works naturally in each language while preserving the same meaning, intent, and tone of communication. 

The final decision still remains with the editor. Each language version can be reviewed, corrected, approved, or rejected before publication. Automation does not replace human oversight; it shortens the time needed to prepare, check, and maintain multilingual content. 

Which CMS systems we support 

The solution is designed in a modular way, so it is not tied to a single environment. During integration we take into account the structure of each system, the data model, language versions, and editorial roles. This allows us to incorporate it into the existing way of managing content without having to completely change how the editorial team works. 

We currently support: 

• Laravel with the Twill platform, 

• Umbraco CMS, 

• WordPress. 

On the same principle, we can also integrate the solution into other CMS systems if they allow appropriate integration and management of multilingual content. The key is for the solution to adapt to the company’s technical environment and its actual needs, not the other way around. 

When such a solution makes sense 

This kind of solution is especially suitable for companies that manage websites in multiple languages, publish new content regularly, or operate in different markets. The more language versions there are and the more frequent the changes, the more time translation, verification, and coordination of content require. 

It brings the most benefit to teams that want to: 

• shorten the time from content preparation to publication, 

• reduce the amount of repetitive manual work, 

• ensure greater consistency across language versions, 

• maintain control over quality and the final publication, 

• simplify the long-term maintenance of multilingual content. 

However, the solution is not limited only to large websites. It makes sense wherever multilingual content is a regular part of the work and where the current process requires too much time, coordination, or manual intervention. 

What we learned 

Our experience has shown that the problem is often not a lack of knowledge or technical capability, but processes that require too much time, coordination, and manual work. As long as translation remains a separate task, it is often easiest to postpone it. 

When we integrated translation directly into content management, the entire way of working changed. A task that had remained on the list for a year and a half became a manageable and repeatable part of the everyday process. 

The real value of automation is therefore not just in a faster translation of individual texts. More importantly, it reduces the number of manual steps, simplifies content maintenance, and ensures that language versions are ready when we actually need them.