Filament Polder Theme Laravel Package

Getting Started

• Confirm the package is registered on each Filament panel that should use Polder’s UI. In v0.2.1, the replaced page header and user menu apply only to panels that register the plugin; other panels render Filament’s own views.
• Look first at your panel providers, typically app/Providers/Filament/*PanelProvider.php, plus the package’s published config/assets/views. Register the package plugin on the panel that should show Polder’s breadcrumb bar and user menu:

public function panel(Panel $panel): Panel
{
    return $panel
        ->id('admin')
        ->plugin(PolderPlugin::make()); // use the package’s actual plugin class
}

• First use case: enable Polder chrome on the admin panel only, then verify the page header, breadcrumb bar, and user menu. Leave customer/operations panels on Filament defaults by not registering the plugin there.

Implementation Patterns

• Use per-panel registration as the default. Multi-panel apps can show Polder’s header/user menu in admin while other panels keep stock Filament views.
• If several panels share a provider or config, register conditionally by panel ID/env so Polder UI is intentional rather than global.
• After upgrading to v0.2.1, audit every panel provider. Add the plugin to panels that should show Polder chrome; remove expectations that non-registered panels will inherit it.
• Keep published views and CSS scoped to registered panels. Avoid global view overrides or global CSS that reintroduces Polder styling without the plugin being active.
• When customizing the user menu or breadcrumb area, prefer package config/published views and panel-scoped registration over editing vendor files.
• Add a small regression test or manual checklist for each panel: registered panels show Polder breadcrumb/user menu; non-registered panels show Filament’s own header/user menu.

Gotchas and Tips

• v0.2.1 is a behavior change: Polder’s replaced header and user menu no longer leak into panels that do not register the plugin. This is usually a fix, but it will surprise apps that relied on partial Polder chrome in other panels.
• If a panel suddenly shows Filament’s default header/user menu, check plugin registration for that panel first. It may not be a CSS issue.
• Clear caches after changing panel providers, e.g. php artisan optimize:clear and any Filament-specific optimization clear command. Rebuild published assets if you use them.
• The removed .fi-select-wrp style targeted a class Filament does not use. No migration is normally needed, but remove or rename any custom CSS that referenced it.
• Debug multi-panel behavior by confirming which panel is active and whether the plugin is registered for that panel, then inspect rendered markup for Polder’s breadcrumb/user menu versus Filament’s defaults.
• Prefer the package’s plugin/config extension points and panel-scoped registration over global view or CSS overrides; global overrides can recreate the exact cross-panel leakage v0.2.1 fixes.