Nova Blog Laravel Package

Product Decisions This Supports

• Admin/editor experience investment. Release 9.7.0 adds nova-sortable so the Category resource supports drag-and-drop ordering. This is a direct productivity feature for the people who operate the product (content editors, merchandisers, ops), not an end-user feature — useful when deciding whether to spend roadmap capacity on internal tooling versus customer-facing work in a given cycle.
• Taxonomy and content-organization roadmap. Category ordering is a prerequisite for anything where sequence is meaningful: navigation menus, category landing-page ordering, featured collections, editorial curation. If ordered categories are on the roadmap, this release removes a build item.
• Build vs buy for internal admin tooling. A maintained package that already ships a Nova Category resource with sorting is a credible substitute for a custom Nova resource + custom sortable field. The decision reduces to: accept a dependency and its conventions, or own ~days of Nova/Livewire work plus ongoing maintenance.
• Vendor trust and upgrade cadence. The jump to a mature 9.x line with a small, additive minor release is a signal of active maintenance and semver discipline — relevant when scoring the package in a dependency review or deciding whether to standardize on it across projects.
• Scoping the next admin sprint. This is a low-effort, high-visibility increment to bundle into an existing admin iteration rather than a standalone initiative.

When to Consider This Package

Consider it when:

• The product runs on Laravel Nova and needs a Category/taxonomy resource that editors manage directly.
• Ordering is frequently changed by non-engineers — merchandising, nav sequence, category prominence — so a drag-and-drop UI removes recurring ad-hoc requests to engineering.
• You want buy over build for a well-bounded admin concern and are comfortable adding a third-party dependency plus its conventions (an ordering column, Nova resource configuration).
• You need a quick validation: the feature is additive, so it can be trialed behind a single resource without committing the whole admin surface.

Look elsewhere when:

• You are not on Nova (Filament, custom Livewire/Inertia admin, headless CMS) — the value proposition collapses entirely.
• You need hierarchical/nested taxonomies, multi-locale ordering, or per-tenant ordering; a flat nova-sortable ordering may not model that, and you would be fighting the package's assumptions.
• You need an API-first or audited taxonomy (versioned category trees, approval workflows) rather than an admin-screen convenience.
• Your org has strict dependency-minimization or security-review policies that make a transitive third-party sortable field a net cost.
• Category ordering is rarely or never changed — then it is unused surface area.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a small, additive release in a mature 9.x package that lets content editors reorder categories by dragging rather than filing engineering tickets. It converts a recurring operational friction — "please move X above Y" — into self-service, at the cost of a minor version bump and one well-established dependency. No breaking changes, no migration of customer-facing behavior; the main decision is whether we adopt the package's conventions for ordering in our admin, which we can validate in a short spike before committing.

For engineering: Minor, non-breaking addition (nova-sortable wired into the Category resource). Confirm three things before rollout: (1) the installed Nova version satisfies nova-sortable's constraint and the package's own Nova constraint, (2) a persisted ordering column exists and is included in migrations for all environments (staging/production drift is the likely failure mode), and (3) ordering is deterministic and scoped correctly if categories are ever filtered or segmented. Pin the transitive dependency and note it in the dependency inventory.

The ask: A short timeboxed spike (half a day) to validate Nova compatibility and ordering persistence in staging, then fold the result into the next admin-tooling iteration. Success looks like: editors reorder categories without engineering involvement, and the "reorder categories" ticket class stops appearing.