Filament Umami Laravel Package

Product Decisions This Supports

• Admin information architecture: Decide where the analytics/settings page lives in a Filament panel by assigning it to an existing navigation group with Plugin::make()->navigationGroup(string|Closure).
• Multi-panel and multi-tenant UX: Use a string or Closure to place the page in context-specific groups per panel, brand, or tenant without forking the package.
• Localization governance: Choose between the package’s translated default group and an intentional product-defined group name.
• Build vs. buy: Avoid custom Filament page/navigation wiring for a common admin-panel need; configure the package instead.
• Upgrade planning: Treat this as an additive minor release with a dependency consideration: filament-analytics-core 3.1+ is required for the new navigation-group behavior.

When to Consider This Package

• Consider it when you are building or maintaining Laravel/Filament admin panels and want a packaged analytics/settings surface rather than a custom page.
• Adopt when your product needs the settings page to sit inside an existing panel navigation group, especially across multiple panels or localized admin experiences.
• Ensure your application can satisfy the filament-analytics-core 3.1+ requirement before relying on the new navigationGroup() API.
• Look elsewhere if you are not using Filament, need a standalone analytics/BI product rather than an admin settings integration, or cannot upgrade the core dependency.
• This release is additive and opt-in; without navigationGroup(), existing translated-group behavior is preserved, so migration risk is low for current users.

How to Pitch It (Stakeholders)

For executives: This is a low-risk minor release that improves admin usability by letting teams place analytics settings in the right navigation group. It reduces custom build work and keeps the admin experience consistent across panels.

For engineering: Version 3.5.0 adds an opt-in Plugin::make()->navigationGroup(string|Closure) API. It is backward compatible—default translated grouping remains unless configured—and requires filament-analytics-core 3.1. No breaking changes are indicated.

For product: Use this as a configuration decision, not a migration project: decide per panel whether the analytics page should use the default localized group or align with an existing product navigation group.