Development of InLexIA, the AI translation solution

What is InLexIA? Presentation of the module

A module 100% integrated with Ibexa DXP

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

The InLexIA solution works with API connectors to recognised translation engines, such as DeepL, which is already integrated into the module. This open architecture also means that other translation engines can be added in the future, depending on the language or use case.

As the environment is entirely centralised, 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.

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.

Editors can :

• Choose the languages into which they wish to translate (or not) content
• View the status of translations (in progress, completed, to be validated)
• Reprocess translated content manually if required

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

Developers

Technical teams can :

• Define the types of content to be translated
• Exclude fields by content type (e.g. an event or a location for which translation is not required)
• Define front page block attributes
• Define attributes for Form Builders
• Integrate InLexIA into customised workflows
• Connect other translation engines via API
• Associate translation rights with certain user roles (e.g. contributors, editors, translators, administrators),
• Thanks to the bundle's architecture 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 with the rich text editor
• Page Builder blocks
• Forms created with Form Builder
• Custom fields (metadata, extracts, quotes, 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.

How does InLexIA work?

As soon as content is published in a source language, the module automatically triggers the translation process without any manual intervention. InLexIA detects that content has been validated and put online, then identifies the elements to be translated based on the parameters configured.

How does it work?

• The module recognises the fields to be translated
• It retrieves the source language defined for the content
• It cross-references this information with the list of target languages activated in the settings
• It triggers the generation of translated versions using the configured translation engine
• The content is transmitted via API, then automatically retrieved, reformatted and saved in the Ibexa DXP locations provided for each language.

This workflow means that content can be translated and published in several languages within seconds of validation.

The system also supports mass translation, enabling an entire site to be translated at the click of a button.

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, with the addition of the following dependency:

composer require inforca/auto-translation-bundle

No external gateway or manual synchronisation is required: everything is executed and stored in the existing Ibexa architecture, enabling seamless deployment of workflows.

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. It is possible to select either DeepL or OpenAI. This choice is simply made in the configuration file, using the following directive:

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?

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

By automating translations via APIs, editorial teams save time when 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)

Contextual translation of entire pages

One of the next major developments will concern the processing mode: instead of translating field by field, InLexIA will be able to send an entire page in context to the translation engine, which will improve the fluidity and consistency of the result.

Management of linguistic variants

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

Configurable level of formality

Finally, 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.

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