Filament Pirsch Laravel Package

Product Decisions This Supports

• Admin UX cohesion: The new navigationGroup(string|Closure) API lets us place the analytics settings page inside an existing panel navigation group (e.g. "Settings", "Insights", "Reporting") instead of a package-controlled translated group. This supports decisions about how much third-party surface area we expose in our admin panel and whether a plugin feels native versus bolted-on.
• Build vs. buy for analytics configuration: Confirms this package is maturing its integration ergonomics rather than its core analytics capability. Good signal that the vendor is investing in host-app fit — a reason to keep buying rather than building an in-house settings screen.
• Panel information architecture: Because grouping is now configurable (string or Closure), we can align the settings entry with our own IA conventions and even conditionally group it per-role — useful when deciding where analytics configuration lives for different audiences (admins vs. analysts).
• Roadmap dependency check: The feature requires filament-analytics-core 3.1. This is a concrete constraint to track in our dependency/upgrade plan — adopting the new navigation behavior means pinning or upgrading the core package in lockstep.

When to Consider This Package

• Adopt when: You already run Filament panels and want a first-party-feeling analytics settings surface, and you care about the settings page matching your panel's navigation structure. The new navigation group option makes it a better fit for panels with a curated/opinionated sidebar.
• Adopt when: You are on (or willing to move to) filament-analytics-core 3.1; otherwise the new grouping capability is unavailable and you fall back to the translated group.
• Look elsewhere when: You need analytics reporting/visualization rather than settings/configuration management — this release is about placement and configuration UX, not data features.
• Look elsewhere when: Your admin navigation is heavily customized or dynamically composed and you'd rather own that layout entirely; a Closure-based group helps but still delegates placement semantics to the package.

How to Pitch It (Stakeholders)

For executives: A small but meaningful quality release for our Filament admin stack. It lets us slot the analytics settings page into our own navigation groups rather than a package-defined one, so the admin experience looks and feels like our product — not a vendor add-on. It's backward compatible (existing behavior preserved by default), so there's no migration risk; the only dependency note is alignment with filament-analytics-core 3.1.

For engineering: Plugin::make()->navigationGroup(string|Closure) is now available, supporting static group labels or dynamic/closure-based resolution (enabling role- or context-aware grouping). Default behavior is unchanged — the translated group is retained if the option isn't set. No breaking changes; adoption is opt-in and gated on the core 3.1 requirement. Low integration effort, improves admin IA consistency.