Weave Code
Filament Kanban Laravel Package
packstub/filament-kanban
Filament Kanban adds drag-and-drop Kanban boards to Filament admin panels. Organize records into columns, move cards between stages, and manage workflows without leaving the panel. Simple setup for Laravel and Filament apps.
A fast, simple Kanban board for Filament: optimistic drag and drop, per-user columns and drop rules, a focus mode without the sidebar, and cards shaped in one closure.
Frequently asked questions about Filament Kanban
- What is packstub/filament-kanban and what does it add to Laravel?
- Filament Kanban is a Filament panel plugin that renders a drag-and-drop Kanban board as a Livewire component. It maps one Eloquent model per card and a column set per board, and adds card and create actions, per-user columns, drop rules, WIP limits, column summaries, polling, and focus mode. It is aimed at Laravel teams already using Filament resources rather than standalone apps.
- How do I install packstub/filament-kanban in a Laravel Filament app?
- Install it with Composer using packstub/filament-kanban, then register and configure the board component in a Filament page or panel resource. You will also need a card model, a status or column attribute, and an ordering field. Follow the package README for the exact board class names and registration steps for your panel.
- Does packstub/filament-kanban support Filament v3 and Laravel 11 or 12?
- The current release targets Filament v4: its CreateAction::make()->schema usage and HasActions contract place it in the Filament v4 action API. Filament v3 teams will need a v3-compatible branch or a version bump, so v3 is the largest adoption gate. The assessment does not state a Laravel version matrix, so check composer.json for the exact Laravel and PHP constraints before adopting.
- How do I define Kanban columns and map them to an Eloquent model?
- Use one Eloquent model per card and a status or column attribute on that table, plus an ordering field for card position. Columns can be enum-defined or closure-defined; if you use an enum, add HasLabel and HasColor so columns render with names and colors. The card component should be a Filament resource or implement HasActions so card and create actions are available.
- Can I configure per-user columns and drop rules?
- Yes. Per-user columns and drop rules are core features, so different users can see different column sets and the board can restrict which transitions are allowed. Configure the column set and rules in the board definition and rely on server-side enforcement rather than client-side checks. Remove any older client-side limit logic at cutover to avoid two sources of truth disagreeing.
- How are WIP limits enforced, and what happens when a move is refused?
- WIP limits and column creatability are enforced server-side, and card and create actions run through Filament's action system. That means the server can refuse a move or create that would violate a column limit. The exact failure UX, such as a toast, revert, or silent snap-back, is not specified, so test the rejection path before relying on it in production.
- Are card actions subject to the underlying model's policies?
- Card actions resolve through the board's own query, so they inherit whatever scoping the board is configured with rather than requiring a separate authorization path. That is useful for reducing integration surface, but board scoping and model policy authorization are not the same control. Model policy enforcement is not explicitly documented, so add policy checks in your action definitions or resource policies if you need them.
- Does packstub/filament-kanban dispatch events like CardMoved for automation?
- The package exposes a CardMoved event according to the technical assessment, but its transaction boundaries and delivery guarantees are not documented. If you use it for notifications, SLA clocks, or other downstream automation, verify that dispatch happens after commit and that listeners are safe to retry. Prefer queued listeners and idempotent handlers for production automation.
- How should I test drag-and-drop, polling, and concurrency behavior?
- Test the server-side rules directly with feature tests for WIP limits, drop rules, and create permissions, then use Livewire tests for the board component's move and action flows. There is no documented conflict policy for two users moving the same card or for a poll landing mid-drag, so simulate those cases explicitly. Check the refusal UX and optimistic updates on a staging board before production rollout.
- What are the main production risks, and when should I choose an alternative?
- The biggest risks are Filament v4 coupling, silent degradation when the card component lacks HasActions, and unspecified concurrency or refusal UX. Column summaries are also computed per column after moves and are uncached by default, so wide boards may need caching or fewer summaries. If you are on Filament v3 or need policy-level authorization out of the box, choose a v3-compatible package or a hand-rolled Livewire board; for a Filament v4 greenfield board, this package is a strong fit.
Weaver
How can I help you explore Laravel packages today?