Laravel Translation Manager

Laravel Translation Manager is a package for editing and organizing your application’s translations. It imports the PHP language files (and optionally JSON translations) stored in your Laravel project into a database, then exposes a web-based interface where translators and developers can search, edit, add, and delete translation strings across every locale in one place.

When you are done editing, it can export the database strings back into the standard Laravel language files, so your version-controlled files stay the source of truth. A set of artisan commands (import, export, find, clean, reset) automate the workflow, and a find command scans your codebase for translation keys that are used but not yet defined.

What You Get

• Import/export commands that sync language files with a translations database table
• A web interface to search, edit, add, and delete strings across all locales
• A find command that scans source code for used-but-missing translation keys
• Clean and reset commands to prune empty entries or start over
• Optional Google Translate integration for auto-filling suggestions

Common Use Cases

• Letting non-developer translators edit strings through a UI instead of raw PHP files
• Auditing which translation keys are used in code but missing from language files
• Managing many locales side by side and spotting untranslated gaps
• Round-tripping translations between version-controlled files and a database

Under The Hood

Architecture - The heart of the package is src/Manager.php, which orchestrates importing translation groups from files into Eloquent Translation models (under src/Models), detecting changes, and exporting back to language files. Controller.php and routes.php serve the web UI (Blade views under resources/), while src/Console holds the artisan commands (Import, Export, Find, Clean, Reset). Two service providers wire everything: ManagerServiceProvider registers the manager/UI and TranslationServiceProvider optionally swaps Laravel’s translator to record missing keys. Domain events under src/Events fire on translation changes.

Tech Stack - PHP 8.1+ on top of illuminate/support, illuminate/translation, and symfony/finder (Laravel 9-13). A database migration under database/ creates the translations table, and configuration lives in config/. Tests use Orchestra Testbench.

Code Quality - A tests/ suite runs against a Testbench Laravel app to exercise import/export and manager behavior. The code is cleanly separated by concern (manager, controller, commands, models, events) and has evolved through many contributors over a decade, though release cadence is now modest.

API Design - Day-to-day use is command- and UI-driven rather than programmatic: php artisan translations:import, :find, :export cover the workflow, and the web interface handles editing. Configuration options control which groups are managed and whether missing keys are recorded, keeping the setup approachable for typical Laravel projects.