Drupal is a registered trademark of Dries Buytaert

The WissKI DDM Translations module provides ready‑made translations
for the configuration that comes with the WissKI Default Data Model. It solves a
current limitation in Drupal recipes: recipes can install configuration, but they
cannot import language overrides. By installing this module, new and experienced
Drupal users alike get properly translated labels, descriptions, and UI texts for
WissKI Default Data Model bundles and fields without having to manage translation
YAML files manually.

Supported WissKI Default Data Model Version corresponse with the version number of WissKI DDM Translations.
Currently supported translations:

  • german (de)

Features

  • Configuration translations for WissKI DDM – Ships language overrides for the
    configuration included in the WissKI Default Data Model (bundles, fields, displays, etc.).
  • Recipe‑friendly solution – Works around the current inability of Drupal recipes to
    import language overrides, so multilingual WissKI sites can still be built via recipes.
  • No UI changes or extra complexity – The module quietly provides better labels and
    descriptions in the existing WissKI user interface.
  • Consistent editor experience – Content editors see clean, translated field labels and
    help texts tailored to the WissKI data model.

Use this module whenever you install the WissKI Default Data Model and need translated
configuration (for example, a German UI) as part of a multilingual WissKI setup.

Post-Installation

After enabling WissKI DDM Translations, you need to run the provided Drush
command to import and apply the translation configuration.

  • 1. Enable the module – Use the Extend page or run
    drush en wisski_ddm_translations -y.
  • 2. Run the Drush command – Execute the translation import command, for example:
    drush wisski-ddm:translations-import (adjust to the exact command name used by the module).
  • 3. Clear caches – Optionally run drush cr so that all translated labels
    and descriptions are visible immediately in the UI.

There is no dedicated configuration form for this module; all work is done via the
Drush command, which imports the shipped translation configuration into your site.

There is no dedicated configuration form for this module; it simply ships
translation config that becomes active when the corresponding languages are
available on the site.

Additional Requirements

  • Drupal – A supported Drupal 11 (or compatible) installation.
  • WissKI – The core WissKI modules, including the WissKI Default Data Model
    (usually installed via a recipe) or an equivalent WissKI data model configuration.
  • Language module(s) – Drupal’s language and configuration translation components
    enabled for your target language(s).
  • WissKI ecosystem modules – Other WissKI contrib or custom modules that provide
    additional bundles, views, and workflows for your project.
  • Interface Translation / Configuration Translation – Core translation tools to
    adjust or extend the shipped translations as needed.

Supporting this Module

If your institution or project relies on WissKI DDM Translations, please consider
contributing back by:

  • Reporting issues and edge cases in the issue queue.
  • Submitting merge requests for additional languages or improved translations.
  • Sponsoring development time through your organization or funding programs.

Activity

Total releases
2
First release
Dec 2025
Latest release
3 months ago
Release cadence
0 days
Stability
50% stable

Releases

Version Type Release date
1.2.4 Stable Dec 3, 2025
1.x-dev Dev Dec 3, 2025