Statamic Insights Laravel Package

Product Decisions This Supports

• Control Panel UX and information architecture: v1.6.0 lets the package declare where its settings belong in the Statamic CP. If statamic-brand-context 1.16+ is present, the package’s settings appear as “Einstellungen” under its own navigation entry; otherwise, addons share an “Addon-Suite” settings page.
• Ecosystem and bundling decisions: This is most useful when evaluating the package as part of a broader Statamic addon suite, especially where consistent settings navigation across multiple addons matters.
• Upgrade risk assessment: The release is explicitly non-breaking: no migration and no new config key. PMs can treat it as a low-risk minor upgrade and schedule it with normal maintenance.
• Roadmap signal: The package is investing in admin usability and compatibility with statamic-brand-context, not in new end-user features. This supports a “polish and integration” roadmap theme rather than a major feature launch.

When to Consider This Package

• Consider it when the product uses Statamic Control Panel addons and you want settings navigation to feel native, grouped, and consistent for editors/admins.
• Consider it if you already use, or plan to use, statamic-brand-context 1.16 or newer; the new navigation behavior depends on that integration.
• Consider it if you manage an addon suite and want individual addons to surface their settings under their own CP navigation entry instead of a shared settings page.
• Look elsewhere or defer if the product does not use Statamic, does not rely on Control Panel settings pages, or is pinned to an older statamic-brand-context version and cannot upgrade. In that case v1.6.0 is backward compatible, but the primary benefit will not appear.

How to Pitch It (Stakeholders)

v1.6.0 is a low-risk usability release for the package’s Statamic Control Panel settings. It adds an optional declaration that lets the addon place its settings under its own navigation entry when used with statamic-brand-context 1.16+, while older versions simply keep the existing layout. There is no migration, no new configuration, and no breaking change. For executives, this is a minor maintenance upgrade that improves admin experience and ecosystem alignment; for engineering, it is safe to adopt in a routine release cycle if the product uses the relevant Statamic/brand-context stack.