1. Translations

Refreshed against dev-next. New user-facing strings require English and German.

1.1. Rules

Do not hard-code UI text in controllers, Blade views, or Livewire components
Provide at least en and de for every new user-facing string
Prefer existing global language files before inventing parallel structures

1.2. Where translations live

Location	Use for

Location	Use for
`lang/en/` and `lang/de/`	Global UI strings
`modules/<Module>/lang/en/` and `.../de/`	Module-specific strings

1.3. Important global files

File	Purpose

File	Purpose
`dt_header.php`	Index/table headers and form field titles
`helper.php`	Help text and common helper messages
`view.php`	Labels, buttons, placeholders, and many view strings
`messages.php`	Flash/log/error-style messages

1.4. Common patterns

Index headers often resolve through model index_header values via trans('dt_header.'.$field)
Menu labels configured as plain strings are commonly resolved through view.Menu_{string}
Module namespaces may still appear as billingbase::...-style keys depending on the module’s language registration

1.5. Community translations

Broader locale contributions are coordinated through Crowdin. Keep the repository language layout authoritative when Crowdin mapping and docs disagree.