Drupal Multilingual Best Practices: Acquia Module 2.8 for Site Builders and Developers

The post clarifies the difference between content translation, configuration translation, and interface translation. It emphasises a configuration-first approach: site builders manage language settings, while developers are expected to write translatable code using $this->t() or Twig’s |t filter. Key UI paths are shared for language setup, detection methods, and translation management, helping readers visualise where each multilingual task is handled.

Best practices include using URL prefixes for SEO-friendly language negotiation, avoiding hardcoded strings or term IDs, and ensuring that Views are configured for language-aware content listings. Common traps flagged for the Acquia exam include creating separate content types for each language, using custom logic where core modules suffice, and neglecting Drupal’s structured translation APIs. The module reinforces the importance of separation between content, configuration, and language context across roles.