- How do I install Filament Cards in a Laravel project with Filament v4 or v5?
- Run `composer require harvirsidhu/filament-cards` and update your Tailwind theme configuration to include the package’s CSS. No additional PHP dependencies are required beyond Filament’s core. The package integrates seamlessly with existing Filament setups.
- Can I use Filament Cards to replace the default Filament sidebar navigation?
- Yes, it’s a common use case (Use Case A in the docs). Replace your cluster’s front page with a `CardsPage` to transform the sidebar into a card grid. Auto-discovery ensures all pages/resources appear dynamically, while manual overrides let you customize specific cards.
- Does Filament Cards support multi-tenant applications with dynamic card visibility?
- Absolutely. Cards respect Filament’s `canAccess()` checks, so they’ll automatically hide based on user permissions or tenant-specific logic. Use `visible()` closures or `showInFilamentCards()` hooks to fine-tune visibility per tenant or role.
- How does auto-discovery work, and can I exclude certain pages/resources?
- Auto-discovery scans your cluster or resource for pages/resources and generates cards for them. Exclude items by adding them to the `$excludedClusterComponents` or `$excludedResourceComponents` arrays in your `CardsPage` configuration. Hidden pages (via `hidden()`) are also skipped.
- Will Filament Cards slow down my application if I have hundreds of pages/resources?
- Auto-discovery runs on page load, so performance depends on your cluster/resource size. For large applications, test with a high-volume setup or use custom discovery filters to limit what gets scanned. Manual cards avoid this issue entirely.
- Can I mix auto-discovered cards with custom cards (e.g., external links or custom UI)?
- Yes, the package supports hybrid setups. Use `CardItem::make()` to manually add cards alongside auto-discovered ones. This is useful for external links, custom buttons, or non-Filament components that don’t fit the auto-discovery model.
- What Laravel and Filament versions does this package support?
- Filament Cards requires **Laravel 10+** and **Filament v4 or v5**. It’s actively maintained (last update: May 2026), so check the [GitHub repo](https://github.com/harvirsidhu/filament-cards) for version-specific compatibility notes before upgrading Filament.
- How do I style cards differently from Filament’s defaults (e.g., custom colors, layouts)?
- Use Tailwind classes directly on the `CardItem` or wrap it in a custom Blade view. The package provides utility classes like `filament-cards-*` for common styles, but you can override anything via Tailwind’s `@layer` directives or custom CSS.
- Is the client-side search feature enabled by default, and does it require extra setup?
- Search is optional and disabled by default. Enable it via the `searchable()` method on your `CardsPage`. Ensure Filament’s JavaScript bundle is properly configured (it uses Alpine.js under the hood), and no additional setup is needed for basic functionality.
- Are there alternatives to Filament Cards for card-based navigation in Laravel?
- For Filament-specific solutions, consider **spatie/laravel-filament-resource-card** (simpler, resource-focused) or **filament/filament**’s built-in widgets for basic cards. For non-Filament Laravel apps, packages like **livewire/ui** or custom Blade components with Tailwind can achieve similar results, but none match Filament Cards’ deep integration with Filament’s ecosystem.