Default Content Locale

Default Content Locale bridges the gap between Drupal's default content system and its locale translation infrastructure. Recipes and site templates distributed on Drupal.org tyipcally ship their default content in English, even though the sites installing them may be configured in another language or multiple languages. This module helps bridge that gap by connecting the default content importer to the locale string storage that Drupal's translation system already uses — so any community-contributed or custom string translations are automatically applied to imported content without any extra work when the default content is imported.

Note that those strings are not yet pushed to localize.drupal.org, so without that part done in other projects, this is just a backend infrastructure waiting to be used.

Features

The module works by listening to the PreEntityImportEvent fired by Drupal core's content importer. For each entity being imported, the module inspects all translatable text and string fields, looks up their values in the locale string storage, and — if translations exist for an installed language not already covered by the content export — injects them as entity translations. On a monolingual non-English site the translated strings become the entity's own default field values; on a multilingual site they are added as a proper translation alongside whatever languages the export already carries.

Post-Installation

There is no configuration. The module "just works". The locale sources are only considered when importing the default content, updates should not be expected after.

LLM disclosure

The development of the module and its copious tests were accelerated with LLM.