- How do I install filament-kanban in a Laravel app?
- The package is not yet registered on Packagist, so a plain composer require will not resolve v1.0.0 today. Add a VCS repository entry pointing at the GitHub repo in your composer.json and require eduardoribeirodev/filament-kanban with an explicit v1.0.0 constraint. Once Packagist registration lands, switch to the standard coordinate so future updates resolve normally.
- Which Laravel, Filament, and Livewire versions does filament-kanban support?
- The release states Filament 5 and Livewire 4.1 or higher are required. A full PHP and Laravel compatibility matrix is not documented in the release notes, so confirm your app matches before adopting. Both are recent majors, which means the plugin is only viable on applications already on, or ready to move to, that stack.
- How do I add a Kanban board to a Filament resource?
- You register the board inside a Filament panel and point it at the Eloquent model you want to organize. It renders through Livewire and follows your panel's layout, validation, and authorization conventions instead of introducing a parallel abstraction layer. Because it is a native Filament plugin, you configure columns, cards, and actions the same way you configure other Filament components.
- Can I customize the Kanban card layout and column content?
- Yes. Cards are rendered with Blade views, so custom card content stays within standard Laravel templating and needs no Vue, React, or Svelte build step. Columns are configurable, so you can map them to a status field, an enum, or any grouping on your model. Card and column actions reuse Filament's shared action forms.
- How does filament-kanban persist card ordering after a drag and drop?
- The package writes an ordering column on your records to persist position and support move-to-top behavior. That delegates a schema and concurrency commitment to third-party code, so review the migration it publishes carefully. The exact strategy, whether an integer sort column, fractional indexing, or adjacency, and the conflict handling for simultaneous drags should be confirmed with the maintainer.
- Does filament-kanban support Filament filters and actions?
- Yes. The board consumes Filament's native filters plus card and column actions, along with shared action forms and infolist schemas, rather than reimplementing them. For teams already standardized on Filament, the conceptual surface area is small. Filter state applies to board queries, and complete filtered totals are reported alongside paginated columns.
- How does progressive loading behave on large Kanban boards?
- The board supports progressive loading or independent per-column pagination while still reporting complete filtered totals. That implies the package issues aggregate queries against your tables, so performance on very large boards becomes your problem rather than the package's. Ask the maintainer about any hard limits on cards per column before pagination degrades.
- Does filament-kanban respect Filament policies and multi-tenancy?
- Because it is a native Filament plugin running through Livewire, it inherits your panel's authorization and layout conventions. Whether policies and tenant scopes are applied to board queries automatically, or must be wired manually, is not spelled out in the release notes. Verify tenant scoping on a staging panel before relying on it in a multi-tenant admin.
- Is filament-kanban tested, and can I run its test suite in CI?
- The release ships 85 tests with 861 assertions, plus Composer validation, dependency security audits, and a reproducible CSS build. Missing from the stated coverage are a published PHP and Laravel version matrix, static analysis, multi-database runs, and browser-level tests for the drag-and-drop path. Confirm whether the suite and audits run in a public CI workflow or are only asserted in the release notes.
- Is filament-kanban production ready, and what are the alternatives?
- It is a greenfield v1.0.0 with no public issue history, no observed upgrade behavior across Filament minor releases, and no Packagist listing yet. The main risks are dual upstream exposure to Filament and Livewire, plus ownership of an ordering column and aggregate board queries. Adopt it on a net-new resource first so rollback means deleting one page class, and treat replacing an in-house kanban page as the realistic migration path.