Initialize Varbase Internationalization Base Recipe

Problem/Motivation

A unified base recipe is needed to standardize how internationalization, language management, and translation capabilities are installed and configured by default in multilingual Varbase sites.

Proposed resolution

Introduce a new Varbase Internationalization Base recipe that provides a centralized, opinionated setup for multilingual support. This recipe installs core and contributed modules required for internationalization and applies sensible default permissions for common editorial roles.

Included Modules

• language – Core language management
• locale – Interface translation and localization
• config_translation – Configuration translation support
• content_translation – Content entity translation
• eca – Event-Condition-Action framework
• eca_language – Language-specific ECA events and actions

Default Permissions

The recipe grants appropriate translation permissions to common Varbase roles:

• Editor: Create and update content translations, translate any entity
• Content Admin: Create, update, and delete content translations, translate any entity
• Site Admin: Full translation permissions across all entities

Remaining tasks

• ✅ File an issue about this project
• ❌ Addition/Change/Update/Fix to this project
• ❌ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Developer Documentation support on feature change/addition
• ➖ User Guide Documentation support on feature change/addition
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Code review from 1 Varbase core team member
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ❌ Update Release Notes
• ❌ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• N/A