Filament Gridstack Dashboard Laravel Package

Product Decisions This Supports

• Shipping a customizable dashboard without building one. This package wraps GridStack.js as a Filament page, so users get drag-and-drop, resizable, persisted widget layouts. That's typically 2–4 sprints of frontend work plus ongoing bug surface — a clear build-vs-buy decision you can close quickly in favor of buy.
• Roadmap: "personalized dashboards" as a fast-follow, not a headline feature. Because layout persistence and grid behavior come for free, you can sequence dashboard work behind core CRUD and treat it as an increment rather than a pillar.
• Role-scoped dashboards become viable in v1.9. The new canAccess and shouldRegisterNavigation options mean the dashboard page can be gated by policy/permission or hidden from nav for users who shouldn't see it. This unlocks segmentation decisions: e.g., a dashboard for managers and a different one for support agents, without forking the plugin.
• Navigation labeling is a product-copy decision, not an engineering one. navigationLabel lets you localize or reposition the entry ("Overview", "My Workspace", "Dashboard") without patching vendor code — useful for multi-tenant or white-labeled deployments.
• Use cases where this fits well: internal admin/back-office consoles, ops tooling, SaaS tenant dashboards where the widgets are Filament widgets you already own. Poor fit for customer-facing analytics products with heavy charting, sharing, or export requirements.

When to Consider This Package

Adopt when most of the following hold:

• You're already on Filament v3+ and your dashboard widgets are (or will be) Filament widgets — the plugin's value collapses if you have to rewrite widgets to fit it.
• Users genuinely need per-user layout persistence (rearranging, resizing, hiding) — if a fixed grid is acceptable, Filament's native dashboard is enough and this is unnecessary dependency surface.
• Your dashboard is internal or admin-facing, where a slightly opinionated UX and a small community plugin are acceptable risk.
• You need access control or nav suppression per role — the v1.9 options make this a reason to adopt now rather than a blocker.

Look elsewhere (or build in-house) when:

• You need widget-level sharing, scheduled reports, exports, or embedded third-party BI — this plugin has no story there.
• You require multi-dashboard-per-user semantics; check current capabilities carefully before promising it.
• You're on Livewire/Filament versions outside the tested matrix or have a strict dependency-review process — this is a single-maintainer package (invaders-xx), so bus factor and upgrade latency are real risks. Pin the version and be prepared to fork.
• You need accessibility guarantees for drag-and-drop interactions — grid libraries in this space are typically weak here, and this package won't fix that for you.

How to Pitch It (Stakeholders)

To executives: We can ship a customizable, drag-and-drop dashboard in days instead of a quarter by adopting a small open-source plugin that plugs into the admin framework we already use. v1.9 adds the controls we needed to safely roll it out by role — we can restrict who sees the dashboard and how it appears in navigation, so we can pilot with one team before general release. Main trade-off: it's maintained by a single developer, so we'll pin the version and treat it as low-risk, replaceable glue rather than a core dependency.

To engineering: This is a thin Filament page wrapping GridStack.js with persisted layouts. v1.9 exposes canAccess, shouldRegisterNavigation, and navigationLabel on the page, which removes the need to subclass or patch the vendor page just to gate or relabel it. Recommendation: adopt, pin to ^1.9, wrap the page registration in our own service provider so we own the access policy, and keep widgets as standard Filament widgets so we can walk away from the package without rewriting UI. Budget a spike to confirm Livewire/Filament version compatibility and to sanity-check layout persistence under our tenancy model.