Taxonomy Terms Order Laravel Package

Product Decisions This Supports

• Adopt/hold on editorial tooling: v1.0.2 is a low-risk patch that improves the Control Panel experience for editors managing taxonomy terms. It supports a decision to keep or adopt the addon for content-ordering workflows rather than building custom CP screens.
• Build vs. buy: The release strengthens the "buy" case for teams on Statamic/Laravel who need term ordering in the Control Panel: it now handles empty states and surfaces real permission/validation errors, reducing the support burden that often justifies an in-house build.
• Upgrade/roadmap hygiene: The distributed package is now ~60 KB instead of ~160 KB, with tests, CI and build tooling excluded from the Composer download. This supports a "safe to upgrade" call and lowers dependency-review friction for platform/roadmap planning.
• Editorial UX roadmap: Improved empty-state copy ("no terms yet" instead of a blank box) and clearer failure messages map directly to reduced editor confusion and fewer "it's broken" tickets—useful evidence when prioritizing admin UX work.
• Integration risk flag: The documented reservation of order as a field name is a concrete product constraint to carry into data-model and content-type planning, avoiding field-name collisions in future taxonomy designs.
• Use cases supported: ordering taxonomy terms for navigation, curated category/tag sequences, editorial collections where term order is meaningful to the front end.

When to Consider This Package

Consider it when:

• You are running a Statamic/Laravel application and need editors to control the order of taxonomy terms from the Control Panel.
• Your team wants a small, low-maintenance dependency—the v1.0.2 distribution is slim and no longer ships tests/CI/build tooling.
• You value clear failure feedback in admin workflows (denied permissions, failed saves/resets) over generic error messages.
• You are on (or can move to) a compatible 1.x release line; v1.0.2 is a patch with no indicated breaking changes.
• You can avoid or rename an order field in the affected content types, per the new documentation.

Look elsewhere when:

• You are not on Statamic or do not use its Control Panel/taxonomy model—the value proposition is largely CP-specific.
• You need complex ordering semantics beyond term ordering (e.g., multi-context orderings, workflow/publishing rules, localization-specific order) that this addon does not claim to cover.
• You require a long-term supported, enterprise-grade dependency with a formal SLA; a v1.0.x addon is still early-stage.
• Your data model cannot accommodate the reserved order field name and renaming is impractical.
• You need guaranteed API stability across minor versions; 1.x patch releases are a good sign, but the project's maturity should be validated against your risk tolerance.

How to Pitch It (Stakeholders)

For executives: This is a small, focused addon for our Statamic/Laravel stack that lets editors order taxonomy terms directly in the Control Panel. The new v1.0.2 release is a quality and hygiene update, not a feature overhaul: editors get clearer empty states and meaningful error messages (e.g., permission denials) instead of blank boxes and generic failures, and the package download shrinks from ~160 KB to ~60 KB by excluding tests and build tooling. Risk is low—no breaking changes indicated—and it reduces day-to-day editorial friction and support noise.

For engineering: Treat this as a routine patch upgrade. Verify the documented constraint that order is a reserved field name in this addon's scope and audit existing blueprints/taxonomies for collisions before rollout. The slimmer Composer artifact means less vendor bloat and a cleaner dependency footprint. The improved error surfacing comes from the Control Panel's returned messages, so permission failures should now be diagnosable without guesswork. Recommend pinning to ^1.0 and validating in staging, particularly any save/reset flows for term ordering.