- How do I install digital-creative/nova-dashboard in Laravel Nova?
- Install it with Composer, register the package provider or Nova tool as documented, publish config and assets, then define a dashboard and attach your existing Nova cards and metrics. Because this is a presentation-layer Nova add-on, the main setup work is wiring dashboards and layouts rather than creating data models. Verify the package's Composer constraints against your production Nova, Laravel, and PHP versions before adopting it.
- Does digital-creative/nova-dashboard support Laravel Nova 5 and Laravel 12?
- The package is a Laravel Nova add-on, and its last release date is March 2024, so Nova 5 and Laravel 12 support should not be assumed from that date alone. Check the declared Composer constraints for Nova, Laravel, and PHP against your production runtime. Then test provider registration, asset publishing, and any Blade overrides against the exact Nova major you run.
- What is the difference between digital-creative/nova-dashboard and native Nova dashboards?
- Nova 4 and later ship native dashboards and cards, while digital-creative/nova-dashboard focuses on multiple named dashboards, routing, per-dashboard assignment, and layout control for existing Nova cards and metrics. The package is not a dashboarding platform and owns no domain logic or persistence model. Establish the specific gap it closes for your team before adding it, because overlap with native Nova makes it pure cost if the native features already fit.
- Can I create multiple dashboards and assign different cards and metrics to each one?
- Yes, the package is intended for multiple named dashboards and lets you organize existing Nova cards and metrics into tailored layouts. Per-dashboard assignment and routing are part of its value proposition, so you can give different dashboards different widget sets. Confirm the exact configuration syntax in your installed version and test the assignment behavior against your Nova version.
- Can nova-dashboard target dashboards to roles, teams, or tenants?
- The package's fit for role-, team-, or tenant-targeted dashboards depends on how you map Nova authorization and routing around each dashboard. Multiple named dashboards and per-dashboard assignment help, but dashboard visibility alone is not authorization. Verify that every card and metric respects Nova policies, lenses, and tenant scoping for non-admin users.
- Does nova-dashboard persist dashboard layouts or user preferences, and where is that data stored?
- The overview does not establish whether digital-creative/nova-dashboard persists layouts or user preferences, so confirm that during your spike before launch. If it does persist data, define ownership, backup, export, and decommissioning for that data. Treat the package as an additive UI dependency and document where any persisted preferences live.
- Are cards and metrics on nova-dashboard dashboards protected by Nova policies and tenant scoping?
- Dashboard widgets must respect Nova policies, lenses, and tenant scoping, and the evaluation flags authorization as a medium risk for this package. Do not rely on hiding a dashboard link as your access control. Test each card and metric with non-admin users and tenant-scoped accounts to confirm it inherits the same Nova authorization boundaries as your other Nova screens.
- Is digital-creative/nova-dashboard actively maintained and safe for production?
- Maintenance risk is high: the package has a single-vendor origin, a March 2024 last release, 72 stars, and zero dependents in the evaluation. That does not make it unusable, but it means you should pin the exact version, record the supported Nova/Laravel/PHP matrix, and name an internal owner for the fork-or-fallback decision. Run a time-boxed spike and keep a native Nova fallback documented.
- What performance impact do metric cards have on a Nova dashboard built with this package?
- Aggregate cards and metrics can create heavy read load on a Nova dashboard unless you add caching or query budgets. The package orchestrates existing Nova cards and metrics, so performance depends on the widgets you attach and how often they run. Test with production-like data and monitor dashboard queries before rolling it out broadly.
- How do I test or migrate away from nova-dashboard to native Nova?
- Use a strangler pattern: run the package dashboard alongside native Nova behind a feature flag, compare parity, then consolidate. Document the native-Nova equivalent of every widget before launch so exit is a configuration change, not a rewrite. If native Nova already covers your use case, skip the dependency and avoid the maintenance and compatibility risk.