- How do I install aymanalhattami/filament-page-with-sidebar?
- Install it with Composer using composer require aymanalhattami/filament-page-with-sidebar, then register the plugin in your Filament PanelProvider. There are no migrations, models, or config files to publish for basic use. Pin an explicit version in composer.json and commit the lock file so panel behaviour stays predictable across deployments.
- Does this plugin support Filament v3 and Filament v4?
- The package is built for Filament v3 panels, and later releases target Filament v4 as well. Because Filament ships breaking changes between majors, confirm the exact supported versions in the repository README and changelog before installing. Pin both the plugin and your Filament minor version, and treat every Filament major upgrade as a re-validation checkpoint for this plugin.
- What are the requirements for this package (PHP, Laravel, Livewire)?
- Expect Laravel 10 through 12 with PHP 8.1 or newer, plus Livewire, Tailwind, and a Filament v3 or v4 admin panel. It is a Filament panel plugin, so it does not apply to Nova, Backpack, or hand-rolled Blade admin areas. If your admin layer is not Filament, do not attempt to port it.
- How do I add a sidebar to a specific Filament resource page?
- The sidebar is opt-in per page class rather than a global rewrite of your panel, so you enable it on the pages where it earns its place. Register the plugin once in the PanelProvider, then adopt it resource by resource, starting with a page that has several child pages such as view, edit, and relation managers. Documenting the opt-in pattern for your team keeps navigation consistent as more resources are added.
- Can I add grouped links, icons, badges, and nested sidebar items?
- Yes. Grouped navigation links, icons, badges, and nested items are the core feature set, defined alongside your page content using simple page classes. This makes the package a good fit for settings screens, documentation-style panels, and any resource with many related sub-pages. Keep the item list shallow at first, since deep nesting can hurt discoverability more than it helps.
- Can I publish and customize the sidebar Blade views?
- The visual layer is implemented in Blade views, which are typically publishable so you can override markup without forking the package. Check the README for the exact vendor:publish tag and confirm whether customization is officially supported or effectively requires a fork. If you maintain a custom panel theme, verify the sidebar inherits your Tailwind tokens instead of shipping its own styling.
- Does it work with multi-tenancy, Filament Shield, or policy-based visibility?
- This is a presentation-layer plugin, so link visibility ultimately depends on how Filament resolves navigation for the current tenant and user. Test explicitly against tenancy-scoped navigation and Shield or policy-driven hiding, because the plugin swaps out parts of Filament's default page chrome. Validate on a tenant-scoped resource before rolling it out to every panel.
- Is the sidebar responsive and accessible, with RTL and localization support?
- Treat the sidebar as desktop-oriented chrome until you have verified otherwise in your own panel. Check keyboard navigation, responsive collapse on smaller screens, translation coverage for navigation labels, and right-to-left behaviour for locales such as Arabic. If your admin users work primarily on tablets or phones, benchmark the sidebar against Filament's default page navigation first.
- Is this package production-ready, and how actively is it maintained?
- It is a small MIT-licensed package with a single maintainer, no vendor SLA, and limited visible production feedback, so plan for a bus factor of one. The blast radius is contained to the admin UI, which means a break is an inconvenience rather than an outage. Budget time for re-testing on Filament upgrades and keep the plugin on your upgrade checklist.
- How do I remove the plugin later, and what are the alternatives?
- Rollback is simply unregistering the plugin from your PanelProvider, since the package adds no tables, data, or service bindings. That makes adoption a low-ceremony trial rather than a commitment. If the sidebar does not pay off, the alternatives are Filament's built-in resource pages, relation manager tabs, and panel-level navigation or clusters.