Weave Code
Filament Localizable Resources Laravel Package
apility/filament-localizable-resources
A Filament plugin that makes resources localizable: translate resource labels, navigation, form and table fields per locale, and switch languages without duplicating resources. Integrates with spatie/laravel-translatable-style workflows to keep multilingual admin panels clean.
Filament Localizable Resources adds first-class support for translatable resource content to Filament admin panels. It lets you manage localized fields side by side—typically as locale tabs or stacked forms—so editors can switch between languages without leaving the resource page, while your Eloquent models keep storing translations in your preferred structure.
- Locale-aware form fields with per-language tabs and switching
- Works with common translation setups such as spatie/laravel-translatable
- Seamless integration with Filament resources, forms, and tables
- Configurable locales and fallback handling for missing translations
- Clean, predictable APIs that fit standard Filament conventions
Frequently asked questions about Filament Localizable Resources
- What does apility/filament-localizable-resources do?
- It is a Filament plugin for Laravel admin panels that makes resources locale-aware. It lets you translate resource labels, navigation, and content per language so multilingual teams can manage localized admin experiences. The goal is to avoid duplicating the same Filament resource for each locale.
- How do I install apility/filament-localizable-resources in a Laravel app?
- Install it with Composer using the package name apility/filament-localizable-resources. Then follow the repository README for any Filament panel registration, configuration publishing, or resource-level setup steps. Because Filament plugins can require panel wiring, check the README before assuming the package is active.
- Which Laravel and Filament versions are supported?
- The supported Laravel and Filament versions are defined by the package's Composer constraints, so check its composer.json and release notes before installing. Confirm compatibility with your application's Laravel and Filament versions, especially before upgrading either framework. If your project uses an older Filament major version, verify support in the repository rather than assuming compatibility.
- How do I translate Filament resource labels and navigation items per locale?
- The package makes Filament resources locale-aware so labels and navigation can resolve according to the active locale. Configure the localized values for each resource as described in the package documentation, then switch the application locale through Laravel's normal locale handling. Test the navigation and resource labels under each supported locale to confirm they resolve as expected.
- Does it translate resource content or only admin labels?
- The package overview describes translating resource labels, navigation, and content per language. That means it is intended for localized admin experiences rather than only static UI strings. How localized content is stored and resolved depends on your resource configuration and the package documentation, so review those details for your data model.
- Can I use it with multiple locales and switch languages in the admin panel?
- Yes, the package is designed around locale-aware Filament resources, so multilingual admin usage is the main use case. Locale switching should be handled through your Laravel and Filament locale configuration, middleware, or session behavior. Confirm the exact switching approach in the README and test it with each locale your team uses.
- How do I test localized Filament resources in Laravel?
- Set the application locale in your Laravel test before rendering or interacting with the Filament resource, then assert that labels, navigation, and content match the expected locale. Use your existing Filament and Laravel testing setup, and repeat assertions for each supported locale. Also test locale switching behavior if your admin panel lets users change languages at runtime.
- Is apility/filament-localizable-resources suitable for production?
- Treat it like any third-party Composer package: review the repository's release history, open issues, and Composer constraints before using it in production. Pin a tested version and run your own localization and admin-panel tests. The package description indicates a focused Filament plugin, but production readiness depends on your Laravel and Filament versions and maintenance expectations.
- What are alternatives to using this package for localized Filament resources?
- You can manually translate Filament labels and navigation using Laravel localization helpers, or build custom resource traits and base classes to handle locale-aware behavior. Another option is maintaining separate resources per locale, but that increases duplication and maintenance. This package is intended to reduce that duplication by making resources themselves locale-aware.
- Does it work with existing Filament resources without duplicating them?
- The package is specifically aimed at making Filament resources locale-aware so you do not have to duplicate resources for each language. You will still need to adapt existing resources according to the package documentation and define their localized labels, navigation, and content. Start with one resource in a test environment, verify locale behavior, then apply the pattern to the rest.
Weaver
How can I help you explore Laravel packages today?