Skip to main content
DeployStack uses Vue I18n with a modular file structure. Translations are organized by feature for easy maintenance.

Architecture

  • Location: src/i18n/
  • Current language: English only (en)
  • Structure: Feature-based translation files
  • Framework: Vue I18n with Composition API (non-legacy mode)

Basic Usage

Using in Components

Adding New Translations

1. Add to Translation File

Find the appropriate file in src/i18n/locales/en/ and add your translation:

2. Use in Component

Creating a New Feature Translation File

When adding a new feature, create a dedicated translation file:

1. Create the Translation File

2. Register in Index

Key Naming Convention

Structure

Examples:
  • globalSettings.errors.configNotSet
  • mcpCatalog.filters.byCategory
  • common.buttons.save
  • validation.required

Rules

  1. Use camelCase for keys
  2. Group by feature (globalSettings, mcpCatalog, teams)
  3. Use descriptive names (avoid generic keys like ‘msg1’, ‘error1’)
  4. Common translations go in common.ts
  5. Validation messages can be shared or feature-specific

Parameters and Pluralization

Parameters

Pluralization

Quick Reference

Common Translation Keys

CategoryKey ExampleLocation
Buttonsbuttons.save, buttons.cancelcommon.ts
Validationvalidation.required, validation.emailcommon.ts
Statuscommon.status.runningcommon.ts
Errors{feature}.errors.{errorType}Feature file
Success{feature}.messages.successFeature file
Forms{feature}.form.{field}.labelFeature file