Weave Code
Admin Translations Laravel Package
savannabits/admin-translations
Laravel package for managing app translations from an admin interface instead of editing language files by hand. Browse, add, and edit translation keys and values across multiple locales, keeping strings organized and editable at runtime.
savannabits/admin-translations adds a ready-made admin interface for managing your Laravel translation files without editing PHP arrays by hand. It scans your lang directories, lists every key and locale, and lets authorised users create, edit, or delete translation strings directly from the browser.
- Browse and search all translation keys across locales
- Inline editing of values with instant save
- Create new keys and language files on the fly
- Missing-translation detection per locale
- Configurable routes, middleware, and authorisation hooks
Frequently asked questions about Admin Translations
- What is savannabits/admin-translations used for?
- It is a Laravel package that adds an admin interface for managing your application's translation strings. Instead of opening PHP language files in an editor, you browse and edit keys from a web UI. It is built as a translation manager for savannabits/admin-ui, so it fits into that admin panel ecosystem.
- How do I install savannabits/admin-translations?
- Install it with Composer, typically via composer require savannabits/admin-translations. Because it is an add-on to savannabits/admin-ui, expect to install and configure that admin panel package as well. Check the repository README for any publish or install steps specific to the current release.
- Does this package require savannabits/admin-ui?
- Yes. The package is described as a translation manager for savannabits/admin-ui, so it is designed to plug into that admin panel rather than run standalone. Plan on having admin-ui installed and set up before wiring in the translation screens. Confirm the exact version constraints in the package composer.json.
- Which Laravel versions are supported by savannabits/admin-translations?
- Support depends on the release. The authoritative answer is the illuminate/support constraint in the package's composer.json on Packagist and the version notes in the repository. Check those before upgrading Laravel or installing on an older application, and pin a compatible tag if needed.
- Does it edit PHP language files directly or use a database?
- The package is positioned as a way to edit language strings and organize locale files without manually touching PHP translation files, so it works with your existing file-based translations. The exact read and write behaviour depends on the version, so review the README and source before pointing it at production language files. Backing up your lang directory before bulk edits is a sensible precaution.
- Can I manage multiple locales and translation groups in one place?
- Yes, the admin interface is built for browsing and editing language strings across locales. You can organize locale files and streamline multilingual content updates from a single screen. The precise grouping and filtering options are shown in the UI and described in the README.
- Is it safe to use savannabits/admin-translations in production?
- It is an admin-side tool, so the main production concerns are access control and file permissions. Restrict the translation routes to trusted administrators and ensure the web server user can write to your lang directory if file edits are enabled. Test on staging first and keep your translation files under version control so changes can be reviewed and reverted.
- How do I restrict who can access the translation manager?
- Access is normally governed by the authentication and authorization setup of savannabits/admin-ui, so gate the admin routes behind your existing admin middleware or policy. Do not expose the translation screens on public routes. Verify the middleware configuration in your admin-ui installation before deploying.
- Do I need to publish config or assets, or run migrations?
- Many Laravel admin packages ship publishable config and assets, and some store data in tables. Check the README install section for vendor:publish tags and any migration commands for your version. If no migrations are listed, the package likely operates on your existing translation files.
- How does it compare with other Laravel translation management packages?
- The main differentiator is tight integration with savannabits/admin-ui, so it is the natural choice if you already use that admin panel. Standalone alternatives such as Laravel translation managers or vendor packages like spatie/laravel-translation-loader may suit projects without admin-ui or those preferring database-backed translations. Compare storage approach, Laravel version support, and maintenance activity before deciding.
Weaver
How can I help you explore Laravel packages today?