- How do I add collapsible sub-navigation to my Filament v3/v4/v5 resource pages with minimal effort?
- Install via Composer (`composer require emuniq/filament-collapsible-subnav`) and it auto-registers to all panels. No manual setup is needed—just works with Filament’s sub-navigation sidebars (secondary nav).
- Does this plugin work with both top navigation and sidebar layouts in Filament?
- Yes, the plugin specifically targets sub-navigation sidebars (secondary nav) and works seamlessly with both top navigation and sidebar layouts in Filament v3–v5.
- Will this break my existing Filament theme or CSS?
- No, the plugin injects minimal inline CSS by default to prevent FOUC. For better performance, run `php artisan collapsible-subnav:install` and `npm run build` to bundle the CSS with your theme.
- Does this support Livewire SPA mode in Filament?
- Yes, the plugin includes a `livewire:navigated` listener to ensure real-time state sync for Livewire SPA mode, making it ideal for collaborative admin panels.
- How does state persistence work (e.g., remembering collapsed state)?
- The plugin uses server-side cookies (not localStorage) for collapsed state, ensuring compatibility with SSR, SPAs, and hybrid rendering modes. No client-side storage dependencies.
- Can I manually register this plugin for specific panels instead of auto-registering everywhere?
- Yes, you can manually register the plugin for specific panels using `->plugin(CollapsibleSubnavPlugin::make())` in your panel configuration, useful for A/B testing or gradual rollouts.
- Is this plugin compatible with Laravel 10–13 and PHP 8.1+?
- Yes, the package supports Laravel 10–13 and PHP 8.1+, aligning with Laravel’s LTS support window. It’s tested against Filament v3–v5 without version-specific forks.
- What if Filament v5 introduces breaking changes to its DOM structure?
- The plugin is designed to auto-detect Filament versions and minimize breaking changes. Monitor Filament’s release notes and test against v5’s beta/RC channels for early compatibility updates.
- Does this plugin work with multi-tenant SaaS apps where navigation varies by user role?
- Yes, the plugin targets secondary navigation (resource pages) and avoids conflicts with primary panel layouts, making it ideal for multi-tenant SaaS or role-based admin panels.
- How can I test if the plugin works with my custom Filament theme or CSS?
- Start with the default inline CSS injection. If conflicts arise, use the optional theme integration (`php artisan collapsible-subnav:install`) to bundle the CSS with your app’s assets and reduce specificity issues.