- How do I install tapp/filament-footer in a Laravel Filament application?
- Install it with Composer using composer require tapp/filament-footer, then register the plugin in your Filament panel provider. The exact plugin class and registration method should be confirmed in the package README or source because documentation may be sparse. Test the installation in staging and pin the package version before deploying.
- Which Filament versions does tapp/filament-footer support?
- The package is intended for projects using Filament v3 or later, but you should verify the exact Filament and PHP constraints in its composer.json before installing. Because it is a very new package, test it against your precise Filament version in a staging environment. If you use Filament v4 or another major version, confirm compatibility first.
- How do I customize footer text and links per Filament panel?
- Use the package's fluent API in each panel provider to configure footer text and links for that panel. This per-panel approach lets you tailor branding and footer content across multiple Filament admin panels. Check the README or source for the exact method names and link syntax.
- Can I use a custom Blade view for the Filament footer?
- Yes, the package supports rendering a custom Blade view per panel according to its overview. You configure the plugin to point at your Blade view and can tailor the markup for your branding needs. Review how the view is rendered and ensure any dynamic content is escaped appropriately.
- Does tapp/filament-footer work with multiple Filament panels?
- Yes, it is designed for per-panel configuration through Filament's plugin registration in each panel provider. That makes it possible to show different footer text, links, or views across panels. Test every panel after installation to confirm the render hooks behave as expected.
- Is tapp/filament-footer production-ready and actively maintained?
- Treat it as unproven: it has very low adoption, including 5 stars and 0 dependents at the time of assessment, and it was released very recently. The technical and security risk is low because it only renders static footer content, but abandonment and compatibility risk are elevated. Review the source, pin the version, and monitor the repository before relying on it in production.
- Are there automated tests for tapp/filament-footer?
- The available context does not confirm whether the package includes automated tests. Because it is new and lightly adopted, inspect the repository for a test suite and CI configuration. If tests are missing, add smoke tests that verify the footer renders in your target Filament version.
- How does tapp/filament-footer compare with adding a footer manually in Filament?
- A manual footer can be implemented in-house with a few lines of Blade or panel configuration, which lowers dependency risk for a single simple footer. The package adds value by centralizing per-panel footer configuration through a fluent API, especially across multiple panels. Evaluate the source size and documentation before deciding whether that convenience is worth the extra dependency.
- Will tapp/filament-footer affect performance or security?
- Performance impact should be negligible because the footer is static and adds no measurable runtime overhead. Security risk is also low as long as footer text and links are escaped and any custom Blade view is reviewed. Do not render unsanitized user input or untrusted URLs through the footer.
- What should I do if tapp/filament-footer is abandoned or breaks after a Filament update?
- Pin the package version and test Filament upgrades in staging so breakage is caught before deployment. Keep a simple Blade component fallback ready, because the footer feature is trivial to replace or fork. If the package is abandoned, swapping in an in-house footer should require only limited effort.