Language versions / satellites without contexts, with automatic translation of all fields of the resource + seo, and even the translation of lexicons — that I put in the name localizator .

Why did I do this: I was not approached by a babel, I kept one project for migx «localization» for a long time, but too it is not convenient, collected all the minuses that managed to reveal and solved them in its component.

Features
1. Creating pseudo-contexts «localization» (you can work together through site.ru/en/ and ch.site.ru)


2. The resource has a tab, where all standard fields of the resource + seo are filled, then at the push of a button this all can be translated into other languages.




3. For ease of use of lexicons, there are separate tabs on the component page where only the lexicon of the component is visible. There is also a choice of language. There is also automation of translation, one button click.


Localization of pdoTools
Example of pdoMenu (similarly for other snippets):

{'!Localizator' | snippet : [
        'snippet' => 'pdoMenu',
        'parents' => 0,
        'includeTVs'     => 'img',
        'processTVs' => 'img',
        'parents' => 0,
        'level' => 1,
]}

Totally, all the resource fields are replaced with the translated ones.
For TV to be replaced, you need to change the pdoFetch.class setting to pdotools.pdofetchlocalizator

How to use
All fields of the resource are replaced by localized, except content, it is output through {$_modx->resource.localizator_content}.

Settings
To automate the translation, you need api key for the Yandex translator, you can get it here: translate.yandex.ru/developers/keys and specify in the localizator_key_yandex setting, also what would the translator understand from which language to translate you need to specify the localization key in localizator_default_language

Cost
The component is completely free, did for my project, I think many will make life easier.
You can send your thanks here: 410015133943061