Filament Polder Theme Laravel Package

Product Decisions This Supports

• Build vs. buy for admin chrome: If your product’s roadmap includes a branded Filament admin panel—custom breadcrumb bar, user menu, header styling—this package offers a ready-made, narrow replacement layer instead of you maintaining overridden Blade views. The trade-off is a dependency on Filament’s internal view structure, not a first-party extension point.
• Multi-panel architecture decisions: v0.2.1 fixes a real scoping bug: the header/user menu replacements were bleeding into panels that did not register the plugin, rendering Polder markup without Polder CSS. If you run multiple Filament panels in one Laravel app (e.g. admin + customer portal), this release makes per-panel opt-in viable. Before this, adoption in multi-panel apps was a visible regression risk.
• UI polish vs. core roadmap: The release is cosmetic and corrective—removing a CSS rule for .fi-select-wrp, a class Filament does not define. This tells you the package is still tightening its surface area. Budget for it as presentation-layer plumbing, not as a feature investment.
• Deferring custom admin theming work: If your team is weighing whether to spend engineering time on admin panel branding, this package is a plausible shortcut for breadcrumbs and user menus—provided you accept pre-1.0 churn and a dependency that tracks Filament releases.

When to Consider This Package

Consider it when:

• You are on Filament and want a consistent breadcrumb bar and user menu across one or more panels without forking Filament views.
• You run multiple panels and need opt-in behavior per panel—v0.2.1 specifically addresses this, so multi-panel apps are now the intended supported case rather than a leaky one.
• You are comfortable pinning a 0.x dependency and reviewing diffs on each Filament upgrade, because the package overrides Filament’s own header and user-menu views.
• The scope matches your need: header and user menu only. This is not a full theme, navigation overhaul, or design system.

Look elsewhere when:

• You need guaranteed compatibility across Filament major versions, or you cannot tolerate a package that shadows Filament’s internal views.
• You require a single-panel app with minimal customization—Filament’s stock header may be sufficient, and the dependency adds little.
• You need a broader admin UI kit, theming framework, or component library; this is a focused replacement layer, not a platform.
• Your compliance or support requirements demand a supported, versioned contract. At v0.2.x with two releases’ worth of notes, treat it as early-stage.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost Laravel/Filament add-on that gives our admin panels a consistent custom header and user menu without us building and maintaining that UI ourselves. The latest release (v0.2.1) is a maintenance fix: it stops the custom chrome from appearing in panels that did not opt in, and it removes a stray CSS rule. That means it is safer for multi-panel setups than the prior version. It is pre-1.0, so we should treat it as a pinned dependency with upgrade review—not a set-and-forget platform bet.

For engineering: v0.2.1 scopes the replaced page header and user menu to panels that register the plugin; other panels now render Filament’s own views instead of Polder markup without Polder CSS. It also drops a rule for .fi-select-wrp, which Filament does not define. No breaking API changes in this release, but the package overrides Filament’s header and user-menu views, so pin the version and re-check after Filament upgrades. Adoption is reasonable for breadcrumb bar and user menu consistency; avoid it if you need a supported 1.x contract or broader theming.