How could we approach an integration with Translated Config

Problem/Motivation

Hi,

We'd like to use Features to build a common set of configuration (content types, medias, taxonomy, etc.) shared across multiple websites.
Our current concern is with multilingual websites. Usually our sites are all in English by default, but some of them aren't. Those are usually not available in English at all.

For now, Features can't handle a scenario where a feature would be imported in a website with a different base language, then updated in the future. Which is 100% normal as this is how the current core configuration management workflow works. Base config are in one language, and translation are in a different folder.

Proposed resolution

We came across this module https://www.drupal.org/project/translated_config → that could help in this case. We could potentially use this so the base configuration set Features uses to import on different websites are first translated. This would requires us to have all translations required in our feature, which isn't an issue for us.

Our current idea would be to hook up in the import process of Features to add Translated Config in the mix. I'm opening the issue to start the discussion and see if we're missing something important, or if we could solve this in an easier way.