InLexIA, the AI translation solution for Ibexa DXP

How web portal translation is going so far

How large organisations will still be working in 2025

Companies that do not have the benefit of modern tools to manage the different languages of their sites rely on processes that are often manual and inefficient:

• The editor prepares French content in a Word document
• This document is sent to various translators, each specialising in a different language
• Each translator, at their own pace and according to their knowledge of the context, prepares the requested translation in a Word file
• The files received are then manually integrated into the CMS using copy/paste.

Limitations of this operating mode

• Translations by a translator
  • Reactivity and translation time
  • Cost
  • Reliability
  • Availability
• Complexity of the translation process

The coverage/completion rate of translations is limited due to these business constraints.

High constraints = limited translations

What is InLexIA? Module overview

Strategic objectives for your translation process

• Simplify the translation process
• Reduce processing times
• Guarantee reliability and availability
• Reduce translation costs
• To achieve 100% translation coverage
• To add more languages to your portal to reach new speakers AND localised languages to target more countries

A module 100% integrated with Ibexa DXP

InLexIA is a translation module designed specifically for Ibexa DXP. Developed by our teams, it is natively integrated into the Ibexa administration interface. Contributors retain their working habits while benefiting from automatic translation options accessible from the content publication screens.

• Users publish content in their preferred language
• On publication
  • InLexIA detects new or updated content
  • InLexIA checks whether this content is one of those to be translated
  • If the content needs to be translated, InLexIA retrieves the translation parameters
  • InLexIA lists the translation tasks to be performed
  • For each target language, InLexIA translates all the fields concerned, and saves the content in Ibexa

The InLexIA solution works with API connectors to recognised AI translation engines, such as DeepL, which is natively integrated into the module. We created InLexIA with an agnostic and open architecture, which means we can also envisage adding other translation engines in the future, depending on the languages available, different use cases or even the customer's specific suppliers.

With Ibexa DXP, it is possible to manage several multilingual sites from a single interface. This is a major advantage for multi-site organisations, such as institutions, international groups or large-scale content publishers. With InLexIA, you can automate the updating of your sites in the different target languages.

A solution designed for publishers and developers

InLexIA has been designed to meet the needs of both business and technical teams, without compromising between ease of use and functional complexity.

For editors

There's no need for a separate interface: translation options can be accessed directly from the content management screens on the home page of each site.

Publishers can :

• Choose the languages into which they wish to translate (or not) the site
• Add a Glossary to ensure consistent terminology in translations
  • For business keywords
  • For brand, entity and group names
• View the actions of the translation robot
• Reprocess manually translated content if required

Thanks to its ease of use, no technical skills are required to trigger a translation.

From an editor's point of view, InLexIA is an AI agent editor that is automatically triggered and generates the translations required in the content in the administration site.

Developers

Technical teams have access to a configuration file for :

• Define the elements to be translated
  • For content types
    • Exclude fields by content type (for example, to avoid translating the "organiser name" field for an event)
  • For front page block attributes
  • For Form Builder attributes
• Configure translation validation workflows
  • Enable / Disable
  • Validator groups
• Connect other translation engines or AI via API
• Associate translation rights with certain user roles (e.g. contributors, editors, translators, administrators),
• Thanks to the architecture of the bundle and the interfaces provided, the bundle is flexible: you can develop your own services to adapt it to your needs.

InLexIA complies with the best development practices recommended by Ibexa. To facilitate its deployment, adaptation and evolution, our teams have carefully documented the module.

Content supported

One of InLexIA's great strengths is its ability to manage all types of content available on a site developed using Ibexa DXP. The module covers all the editorial components of a site, including those created dynamically.

Content supported includes

• Classic pages created using text fields and the rich text editor
• Page Builder blocks
• Forms created with the Form Builder
• Custom fields (metadata, extracts, citations, tags, SEO titles, etc.)

Depending on the configuration, InLexIA automatically identifies the fields to be translated according to the type of content. This granularity of parameterisation optimises the solution's performance and reduces translation costs, by processing only what is really useful.

Thanks to its structural analysis logic, the module is able to preserve the block hierarchy and RichText content formatting. In this way, translated content remains perfectly consistent with the source version, both in terms of content and form.

Key features of InLexIA

• Configuration of automatic translations per site from the administration site
  • Activation / deactivation
  • Destination languages (tick box for each available language)
  • For security reasons, these functions are reserved for a profile whose role has been specially configured to have access to these settings.
• Advanced configuration (technical side)
• Automatic triggering of content translation on publication in the Ibexa DXP administration site
  • When content is published, all expected translations are carried out almost in real time
  • All types of Ibexa content can be managed: Home page/Rubrics with dynamic blocks, Page content, Forms
• Glossary support
  • The glossary lists the words whose translation you want to check
  • For each target language, the expected translation or words are given
  • The glossary is updated by uploading an XLS document
• Mass translation
  • Triggered from the "Translation" tab on the site home page (or from the command line)
    • Translates all the content on a site
    • Respects site configuration
    • Does not overwrite manual translations by default
  • Ideal for
    • Adding a new language to your portal
    • Improving existing translation coverage when you start using InLexIA
• Security: effective control over the operations of the translation robot
  • Dedicated robot user per translation API
    • With a dedicated role for the translation robot
    • Track the publications of each robot
  • Creation of an activity log
    • Records every event, action, API consumption and robot involved
    • Can be consulted directly in the content information
  • Validation workflow: InLexIA can be configured to prevent automatic translation of translated content
    • Content is not published immediately
    • A workflow action is initiated
    • A notification is sent to the validation group
    • Webmasters can edit the prepared translation and then modify/validate/reject it
• Translation dashboard
  • List of content to view the translation status of all content
  • Aims: To help your "human" translators check for missing languages
    • Filters by type of content, missing language, or search by title
      

What sets InLexIA apart from other translation solutions

Native integration with Ibexa DXP

InLexIA has been developed as a bundle designed to integrate with the Ibexa ecosystem. The module is installed via Composer, and the dependency is added in the classic way:

composer require inforca/auto-translation-bundle

No external gateway or manual synchronisation is required: everything is executed and stored in the existing Ibexa architecture, making deployment easy.

Please note: a specific configuration in your project with an access token linked to your licence is required for installation.

A customisable glossary

InLexIA supports the use of customised glossaries to ensure terminological consistency in translations. This feature involves importing an .xlsx file into the Ibexa back office.

Here's how it works:

• The administrator creates a folder entitled "Glossaries" in the "Media" section of the back office.
• An Excel file is then uploaded to this folder. It must follow a precise structure with :
  • a column for the source language
  • one or more columns for the target languages
  • rows containing the terms to be translated and their correspondences in each language
• When published, glossaries are taken into account for the translation engine used.

The system is compatible with suppliers that support this function, such as DeepL, provided that the correct language codes are used in accordance with the API documentation.

This configuration enables companies to impose specific translations for certain words or expressions, thus avoiding frequent errors or inconsistencies in brand names or sensitive formulations.

A solution adaptable to several translation engines

By default, InLexIA uses DeepL as its translation engine. This choice is based on the recognised quality of the translations provided by DeepL in European languages.

The module has been designed to allow the administrator to choose the translation provider via the configuration.

Today, DeepL is the API that Inforca recommends: it is economical, capable (more than 70 target languages), intelligent (adapts to the context) and has numerous customisation options (tone, translation quality).

We have also prepared other translation engines:

• Open AI: for more specific translations
  • for example, to create a Spanish translation with specific Colombian expressions
• [Coming soon] Modern MT
• [Coming soon] Systran

It is possible to define the translation engine in the configuration file that your project teams create for you.

auto_translate.default.config: default_api: 'deepl' # ou 'openai'

This flexibility allows each organisation to adapt the solution to its preferences or budgetary constraints, and to switch easily from one engine to another.

What are the benefits of InLexIA for companies?

• 🕒 Reduced translation time
  • Close to real time with automation
• 🌟 Ensures availability and quality
  • APIs always available
• 💸 Reduces translation costs
  • from €20 per 1 million characters
• 🌍 Complete translations
  • Translate everything, in as many languages as your users/customers speak, without spending a fortune

InLexIA has one objective: to simplify the multilingual management of websites while optimising resources.

By automating translations via APIs, editorial teams save time publishing content in several languages. No more manual copy-pasting and laborious duplication. The translated version is generated automatically within seconds of the content being published.

This also significantly reduces costs. By limiting the use of professional translators for current or recurring content, InLexIA reduces budgets without sacrificing consistency, thanks to the use of a customised glossary and the integration of advanced translation engines such as DeepL.

Finally, InLexIA facilitates access to new language markets. Thanks to mass translation and coverage of multiple languages via the available connectors, companies can rapidly expand their international presence, without making major changes to their internal organisation or complicating their content production chain.

Future development of InLexIA

The development of InLexIA is continuing apace, with a number of changes planned to enhance the accuracy and intelligence of the module over the coming months.

Diversification of translation engines

With DeepL and OpenAI already integrated into InLexIA, the module will soon be able to use other providers such as ModernMT and Systran. This openness will enable you to choose the engine that best suits your content, languages and business requirements.

Advanced configuration by target language

It will soon be possible to define a different configuration for each target language:

• The types of content to be translated
• The translation engine to be used
• The level of intervention (translation on creation, on modification, or both)

Management of language variants

The module will take into account regional language variants such as Mexican or Ecuadorian Spanish, so that the register and vocabulary can be adjusted to suit the target audience.

Configurable formality level

The addition of a formality level parameter (standard, professional, colloquial) will enable the tone of translations to be adjusted according to the publication context, where the translation engine supports this.

AI translation agents

After setting up validation workflows for webmasters to check translations, we asked ourselves: How can we help companies check the quality of translations without costing them more time?

The solution? Create AI agents to do the job:

• An agent to optimise the translations produced
• Agent to validate the consistency of translations
  

These enhancements, which are currently under development, are designed to make InLexIA an increasingly intelligent, accurate and customisable solution, tailored to the translation requirements of companies of all sizes.