Weave Code
Translations Laravel Package
backstage/translations
Backstage Translations is a Laravel/PHP package for managing and organizing application translations. It helps developers maintain localization files, streamline multilingual content workflows, and keep language strings consistent across projects.
Backstage Translations for Filament
Frequently asked questions about Translations
- What is backstage/translations and what does it do?
- Backstage Translations is a Filament panel plugin for browsing and editing Laravel translation strings from an admin UI. It is a content-operations surface for maintaining localization files, not a translation runtime; it does not change how __() resolves unless it writes to a database-backed loader. Treat the package description as the only signal until you verify the code in a scratch environment.
- How do I install backstage/translations in a Laravel application?
- Install it with composer require backstage/translations, then register the plugin on a Filament panel. If persistence is database-backed, publish and run the package migrations and config. Confirm the exact service provider and panel registration syntax in the README or plugin class, because the available metadata is sparse.
- Does backstage/translations support Filament v3 or v4?
- The package's composer.json is the source of truth here, because Filament v3 and v4 are a breaking boundary. Check the filament/filament constraint before installing and do not assume support for both majors. If your panel runs a major the package does not declare, expect plugin registration or rendering failures.
- Which PHP and Laravel versions does backstage/translations support?
- Check composer.json for php, illuminate/support, and filament/filament constraints before committing. The available package metadata does not confirm version breadth. A narrow constraint set is fine for a greenfield app but can block adoption in an older Laravel codebase.
- Does it write translations to lang files or to a database table?
- It is not confirmed whether saves write directly to lang/ files, a dedicated database table, or an external translation driver. Verify this in a throwaway environment before adopting. File-backed editing is the classic source of deploy drift and concurrent-edit races, while a database-backed loader avoids those failure modes.
- Does backstage/translations handle JSON files, nested keys, pluralization, and interpolation?
- Verify support for JSON versus PHP array files, nested keys, pluralization, and interpolation before relying on it for real locale files. Direct writes to nested or pluralized structures can corrupt them if the parser is naive. Test against a copy of your actual translation files, not a demo set.
- Can I restrict who is allowed to edit translations?
- Editing is typically gated by Filament panel access, but confirm whether the package exposes a policy or gate hook. If editing must be restricted beyond panel login, add an authorization layer around the resource or plugin. Do not assume role-based restrictions are built in.
- Is there an audit trail or draft, review, and publish workflow?
- No audit trail or draft/review/publish workflow is documented in the available metadata. Assume every save is immediate and irreversible until proven otherwise. If review workflow matters to your team, a commercial TMS or a custom Filament resource is a better fit.
- Will backstage/translations work in a containerized or immutable deployment?
- In containerized environments lang/ is usually baked into an immutable image, so file-backed edits will either fail on permissions or silently disappear on the next rollout. Use a database-backed translation loader or treat the plugin as read-only in production. Validate the full save path against your deploy pipeline before trusting it.
- Is backstage/translations actively maintained, and what alternatives should I consider?
- The package shows zero stars, zero dependents, and score 0, so there is no production track record or community pressure to fix defects. It belongs to a small-org suite where a single maintainer's attention is the availability guarantee, so check release cadence and support channels first. Alternatives include a hand-rolled Filament resource over spatie/laravel-translation-loader, or a commercial TMS such as Lokalise or Phrase if review workflow matters.
Weaver
How can I help you explore Laravel packages today?