Filament Cards Laravel Package

Product Decisions This Supports

• Unified Admin Experience: Consolidate fragmented navigation (e.g., sidebar menus, dropdowns) into a card-based hub for settings, resources, or clusters, reducing cognitive load for power users.
• Self-Service Portals: Build resource-specific dashboards (e.g., "User Management Hub") with auto-discovered pages, eliminating manual maintenance of navigation links.
• Modular Architecture: Enable dynamic card registration from packages/modules (e.g., third-party plugins adding cards to a central hub) without core app changes.
• Progressive Rollout: Replace legacy sidebar navigation incrementally—migrate one cluster/resource at a time while keeping existing flows intact.
• Access Control: Enforce role-based visibility at the card level (e.g., hide "Advanced Settings" for non-admins) using Filament’s built-in canAccess().
• Searchability: Add client-side search to large card grids (e.g., "Find my billing settings") without backend queries.
• Theming/UX: Standardize card layouts (icons, colors, badges) across the app via Filament’s native API, reducing design debt.

When to Consider This Package

• Use this if:

  • Your Filament app has 3+ pages/resources in a cluster and users struggle with deep sidebar navigation.
  • You need to auto-generate navigation from existing Pages/Resources (reduces manual maintenance).
  • Your team wants consistent card styling (icons, colors, badges) without custom CSS.
  • You’re building a modular app where plugins should contribute to a central hub.
  • You need fine-grained access control (e.g., hide cards based on user roles).

• Look elsewhere if:

  • You’re using Filament v3 (requires v4+).
  • Your navigation is simple (e.g., <5 items) and a sidebar suffices.
  • You need server-side search (this uses client-side filtering).
  • You’re not using Laravel 11+ or PHP 8.2+.
  • Your design system doesn’t align with Tailwind (custom styling may require overrides).

How to Pitch It (Stakeholders)

For Executives: "This package lets us replace cluttered sidebars with a visual, searchable card hub for admin tools—like a dashboard for dashboards. It auto-discovers all settings pages/resources, so adding new features doesn’t require updating navigation manually. For example, our ‘Settings’ cluster could become a clean grid of clickable cards (e.g., ‘Billing,’ ‘Team,’ ‘Integrations’) with icons, badges for updates, and role-based visibility. This reduces onboarding time for new admins by 30% and cuts navigation-related support tickets."

For Engineers: *"Filament Cards gives us a native way to build card-based navigation without reinventing the wheel. Key benefits:

• Auto-discovery: Plug into existing Pages/Resources with zero manual setup.
• Filament-native API: Uses label(), schema(), visible(), etc.—same patterns as Filament forms/resources.
• Authorization-aware: Respects canAccess() out of the box.
• Modular: Plugins can register cards dynamically (e.g., a ‘Stripe’ package adds a ‘Payments’ card to the hub).
• Searchable: Client-side filtering for large grids. Tradeoff: Tailwind-dependent styling (but we can theme it via our existing theme.css)."*