Product Decisions This Supports
- Admin-panel build vs. buy for hierarchical data. If the roadmap includes any content model with parent/child structure — categories, menus, org units, folder taxonomies, comment threads, CMS pages — this package replaces hand-rolled tree-sorting UI with a drop-in Filament component. The decision it unblocks is "do we spend 1–3 sprints building and maintaining drag-and-drop tree editing, or adopt this and spend that time on the differentiating feature?"
- Laravel 12 upgrade timing. v1.2's only substantive change is Laravel 12 compatibility. That converts an "unknown" into a green light for the platform-upgrade workstream: teams planning a Laravel 11 → 12 migration can now keep nested-list admin functionality without forking or pinning.
- Scope control for internal-tooling work. For back-office and ops tooling, this is a category where buying (even via OSS) is almost always correct — the UI is fiddly, the value is low-differentiation, and internal users tolerate a plugin's opinions far better than paying customers do.
- Filament-version standardization. Choosing Filament as the admin stack already implies a plugin-ecosystem bet. Tracking whether this package keeps pace with Laravel/Filament majors is a concrete input into that bet, not a footnote.
When to Consider This Package
Consider it when:
- You're on Filament 3.x and need editable tree/hierarchy ordering in a form or table — categories, navigation menus, nested pages, org charts.
- You're on Laravel 12 (or migrating to it) and want a maintained option rather than a fork. This release exists specifically to make that path viable.
- The hierarchy is shallow-to-moderate depth and edits are admin-side, not high-concurrency end-user traffic.
- You want the capability in hours, not a sprint, and you're comfortable with a small-team OSS dependency.
Look elsewhere when:
- You need guaranteed long-term support, SLAs, or a vendor to escalate to. This is a community package with a thin maintainer roster (v1.2 includes a first-time contributor) — treat it as "adopt with an exit plan," not "adopt and forget."
- Your hierarchy semantics are exotic — closure tables, multi-parent graphs, versioned trees, per-tenant reordering with complex permission rules. Nested-list components typically encode adjacency-list assumptions; fighting those is worse than building.
- Ordering writes are hot-path or need transactional guarantees under concurrent reordering. Validate this against your actual write patterns before committing.
- You're mid-migration on the Filament major and the package hasn't caught up — check that its Filament constraint matches your version, not just Laravel's.
Specific to v1.2: it's a compatibility release, not a feature release. No new API, no deprecations, no breaking changes. The adoption risk it removes is the Laravel 12 barrier; the risk it doesn't address is maintenance depth and test coverage. Pin to ^1.2 and re-evaluate on the next Filament major.
How to Pitch It (Stakeholders)
For executives (one line): A free, open-source component that gives our admin panel tree-style drag-and-drop editing out of the box, now compatible with our Laravel 12 upgrade path — saving the team roughly a sprint of UI work with no licence cost and no lock-in.
For engineering leads: v1.2 is a maintenance release adding Laravel 12 support. It's a minor bump with no API changes, so integration surface and migration risk are both low. It's a Filament plugin, so it inherits Filament's constraints — verify the Filament version alignment before wiring it in. The trade-off is explicit: we take a small-team OSS dependency in exchange for not owning a niche, low-differentiation UI. Mitigate by isolating it behind our own form component so the package is replaceable without touching feature code, and by writing one integration test that pins the reorder behaviour we depend on. If the package stalls on a future major, that wrapper is a day's work to swap out — which is the whole reason we're comfortable starting.
Recommendation: Adopt for internal/admin tooling on Laravel 12. Do not adopt for customer-facing or high-concurrency ordering without a spike on write contention and permissions. Re-review at the next Filament major release.