- How do I install mokhosh/filament-kanban in a Laravel application?
- Install it with Composer using composer require mokhosh/filament-kanban, then register the package's plugin provider on the Filament panel where the board should appear. Publish any config or asset files the package ships if you need to customize styling. Because it is a Filament plugin, it assumes Laravel, Filament, and Livewire are already in place.
- Which Filament versions does filament-kanban support?
- The package tracks a specific Filament major, and each Filament major bump will likely require a matching kanban release. Pin Filament and filament-kanban together in composer.json and treat them as a coupled pair. Before adopting a new tag such as v2.11.0, load a board page in staging against your exact Filament and PHP versions to confirm there are no signature or class-load errors.
- How do I turn an Eloquent model into a Kanban board?
- Your model needs to satisfy the package's ordering and status contract, which typically means an ordering column for card position and a status or enum field for the column a card belongs to. You then point the board at that model and define the columns that map to status values. Most of the integration effort lives in getting this data contract right rather than in the package itself.
- Does filament-kanban require database migrations?
- The package is a presentation layer and does not own your data, so it adds no tables of its own. If your model already has an ordering column and a status field, adding a board is purely additive with no schema change. If those are missing, budget a migration plus a backfill so existing records get sensible ordering and status values.
- How do drag-and-drop moves and status transitions get persisted?
- The board is a Livewire component, so when a card is dragged between columns the package updates your model through the ordering and status fields you defined. A safe rollout is to render a read-only board against a non-critical model first, verify column mapping and sorting, and only then enable drag and status mutation for real users.
- Is filament-kanban safe to use in production?
- Technical risk is low to moderate: the package has no infrastructure footprint, no background jobs, and no data ownership, so exit cost is low. The main concerns are the version lock to a specific Filament major and a thin contributor base around a single maintainer, meaning you should not assume fire-and-forget upgrades. Validate each release on a staging board page before merging.
- Can I customize the Kanban board's columns, cards, and styling?
- Yes. The package is designed as a presentation component with a clean, customizable UI, and you control which statuses become columns and how cards are rendered. Publish and override the package views or config where offered to match your admin panel's design system. Styling work is expected as part of onboarding, alongside the data contract work.
- What changed in v2.11.0 and should I upgrade?
- v2.11.0 is a maintenance release: two Dependabot bumps limited to CI workflows, a fix for issue #81, and a method-signature correction from a first-time contributor. No new features, deprecations, or public API surface were added. The signature fix is a correctness change rather than a breaking change for consumers, but verify it against your Filament version since mismatched override signatures cause fatal errors on class load.
- Can I use filament-kanban without Filament, or should I extract its board logic?
- No, the package is built specifically for Filament and Livewire and is not usable outside that stack. Extracting the board logic into a bespoke UI is not recommended, since the value is the ready-made Filament integration. If you are not on Filament, evaluate other options rather than adapting this one.
- How much ongoing maintenance does filament-kanban require?
- Day-to-day maintenance is near zero because there is no database, no queue work, and no config drift to manage. The recurring cost is upgrade coordination: each Filament major release will probably need a corresponding kanban bump, so budget a small recurring line item for that coupling. Support burden also shifts to the UI team rather than platform engineering.