- What is goldnead/statamic-insights used for?
- It is a Statamic Control Panel addon that adds a lightweight insights dashboard for editors and administrators. It shows an at-a-glance overview of content and recent activity, configurable widgets, and permission-aware metrics without leaving the CMS. It runs inside a Laravel and Statamic application and is designed to stay out of the way until needed. For teams that do not need a full analytics integration, it is a focused alternative to building custom Control Panel widgets.
- How do I install Statamic Insights in a Laravel application?
- Run composer require goldnead/statamic-insights from your Laravel project root and let Composer resolve the Statamic addon. The package is designed for zero-config setup, so sensible defaults should be available without publishing new configuration. After install, clear Laravel and Statamic caches so the Control Panel navigation and widgets refresh. Check the README for any publish or permission steps specific to your install.
- Does Statamic Insights need configuration?
- It works with sensible defaults, so a zero-config install should surface an overview immediately. Configuration is mainly for tuning which widgets and metrics matter to your team. The v1.6.0 release notes state there is no new config key and no migration, so upgrades should not require config changes. If you need a different widget mix, use the addon's documented widget options rather than forking it.
- Which Laravel and Statamic versions are supported?
- Statamic Insights is a Composer package for Laravel applications running Statamic, so exact support is defined by its composer.json constraints. Check those constraints for the supported PHP, Laravel, and Statamic versions before installing. The addon does not introduce new runtime services, queues, or storage, so it fits normal Laravel deployment pipelines. For navigation behavior in v1.6.0, also check the statamic-brand-context version you have installed.
- Can I customize the insights dashboard widgets?
- The addon is built around configurable widgets for the content and activity metrics you care about. Start with the default overview and adjust the widget configuration to focus editors on the numbers that matter. Keep permission-aware access in mind so different roles see appropriate metrics. Because the implementation is lightweight and cache-friendly, widget changes should not require a separate analytics service.
- Is the dashboard permission-aware for editors and administrators?
- Yes. The dashboard is permission-aware, so access to metrics can align with Statamic Control Panel permissions for editors and administrators. You should still verify role mappings in your project, especially if you customize navigation or share settings pages across addons. Permission behavior matters most when a shared Addon-Suite page aggregates settings from multiple addons. Test with a non-admin editor account before relying on it in production.
- Does Statamic Insights impact performance or caching?
- It is described as a lightweight, cache-friendly implementation rather than a heavy analytics service. The addon does not add queues, storage, or a separate data path; it surfaces metrics inside the Control Panel. The v1.6.0 navigation change lives in the CP navigation layer and does not touch application data. As with any CP addon, clear caches after deployment and watch for expensive custom widget queries if you extend it.
- What does the v1.6.0 settingsNavParent change do in the Control Panel?
- v1.6.0 adds settingsNavParent(), a declarative hook that returns a section and name tuple for the addon's settings navigation. With statamic-brand-context 1.16 or newer, that consumer decides whether settings appear as an Einstellungen sub-item under the addon entry or under a shared Addon-Suite page for addons without their own navigation. With older or absent brand-context, the method is ignored and the previous layout remains. Validate both paths, and check whether the German label is translated in non-German installs.
- How do I deploy a Statamic Insights upgrade safely?
- Treat the upgrade as a Composer update plus cache clear, not a data migration. The release states no migration and no new config key, so bump the package and run php artisan cache:clear and php artisan statamic:stache:clear. Statamic caches navigation and the Stache, so skipping those clears can make the nav change look like a failed upgrade. If statamic-brand-context is present, confirm its version meets the 1.16 threshold before expecting the new settings placement.
- How should I test Statamic Insights navigation with statamic-brand-context absent or older?
- Test a 2x3 matrix: brand-context absent, older than 1.16, and 1.16 or newer, crossed with the addon having its own nav entry or not. Verify that older versions silently keep the previous layout, then verify the new Einstellungen sub-item or shared Addon-Suite placement on 1.16 or newer. Check for duplicate settings entries if the addon also registers navigation independently, and test permissions on the shared page. For maintenance, pin compatible statamic-brand-context versions and review composer constraints and the changelog on each upgrade.