Nova Sortable Laravel Package

Product Decisions This Supports

• Content ordering & curation features: Enables drag-and-drop reordering of records directly in Nova's index view, unblocking product needs around manually curated lists — navigation menus, homepage sections, category ordering, FAQ ordering, featured/pinned items, media galleries, and any "priority" or "position" field on a model.
• Build vs. buy: The underlying capability (a position/order column, a sortable index, persistence on drop) is a small-but-recurring piece of admin tooling. This package lets you skip custom Nova field/controller work and redirect engineering effort toward higher-leverage product work. v3.9.0 reinforces the "buy" side: it now supports spatie/eloquent-sortable ^5.0, meaning the ordering logic underneath is a mature, widely used library rather than bespoke glue — less of the surface area is the vendor's own untested code.
• Admin UX roadmap: Signals demand for a better editor experience — PMs can treat drag-and-drop as a baseline expectation for editorial workflows and evaluate whether the broader admin surface meets it.
• Roadmap scoping: Useful for validating whether "manual ordering" is a genuine user need (e.g., merchandisers, content editors) before committing to a bigger CMS or custom editorial tool; results can inform whether ordering belongs in MVP or a later iteration.
• Platform/lifecycle planning: The v3.9.0 release adds Laravel 13 compatibility (via the spatie ^5.0 constraint). This matters if your Nova admin is on — or plans to move to — a newer Laravel major. Ordering tooling that hard-blocks a framework upgrade becomes a roadmap tax; this one currently doesn't.
• Use cases: Best-fit when the product is already on Laravel Nova and non-technical editors need to control display order without engineering involvement.

When to Consider This Package

• Adopt when: You already run a Laravel Nova admin panel; models have (or can have) an explicit ordering column; editorial/merchandising users need to control sequence; and the ordering requirement is straightforward (single list, no complex nesting or multi-tenant variations).
• Do due diligence first: Community signal remains thin (0 stars, 0 dependents, very low score), so treat it as an unproven dependency despite the recent activity. The upside from v3.9.0 is evidence of maintenance, not of adoption: the release is almost entirely Dependabot bumps to front-end build/dev dependencies (webpack, lodash, minimatch, svgo, node-forge, follow-redirects, and similar), which is a positive security-hygiene signal but tells you nothing about production usage. Still verify maintenance cadence, review the source, confirm Nova version compatibility against your installed Nova major, and plan to vendor/fork or wrap it behind an internal abstraction if the capability is business-critical.
• Look elsewhere when: You are not on Nova (e.g., Filament, custom admin, headless CMS); you need nested/hierarchical or multi-dimensional ordering; ordering must be transactional/auditable at scale; or your org has strict dependency-vetting rules that a zero-adoption package won't pass — a Dependabot-driven patch release doesn't change that calculation. In those cases, implement a small position field plus a sortable index directly, or choose a mature alternative.

How to Pitch It (Stakeholders)

• For executives: A lightweight, MIT-licensed add-on for our existing Laravel Nova admin that lets editors reorder records with drag-and-drop. It removes a recurring "can we just move this item?" engineering request, improves content-editor productivity, and costs essentially nothing to trial. The latest release is a maintenance/security-dependency update with no breaking changes and no new product surface, and it adds forward compatibility with the next Laravel major — a small positive signal on longevity. Risk is still low-but-unproven; we'd pilot it and keep an internal fallback.
• For engineering: It plugs into Nova's index view to provide drag-and-drop sorting backed by an ordering column, avoiding custom field/controller code. v3.9.0 is a safe, non-breaking minor: dependency bumps across the front-end build chain, plus loosening the spatie/eloquent-sortable constraint to ^5.0 for Laravel 13 support — nothing to migrate, but do confirm your spatie/eloquent-sortable and Nova versions resolve cleanly before bumping, since that's the only runtime-relevant change. Zero dependents and minimal community signal still mean we should review the source, pin the version, and isolate it behind our own abstraction so we can swap or fork without disruption. Effort to pilot: hours, not days.
• Recommendation: Proceed with the previously planned time-boxed pilot on one low-risk resource, and pin to v3.9.0 (or later) so we start on the Laravel 13-compatible line. No re-scoping needed — this release doesn't change the product case, only marginally improves the maintenance-risk picture. If the pilot holds up, adopt for editorial ordering; otherwise, spend the small incremental effort to build the equivalent in-house.