Category Laravel Package

Product Decisions This Supports

• Admin/back-office UX standardization. The release moves CategoryTypeForm off a Flex-based flat layout to a unified status component and aligns status enums to a single color palette (with CategoryTypesTable normalized). For a PM, this supports a decision to standardize admin UI patterns centrally rather than let each module invent its own status styling — fewer design reviews, less visual drift, faster delivery of new category/admin screens.
• Search as a platform capability, not a per-feature build. keywordSearchFields added to models for polymorphic search is the most product-relevant change. It supports roadmap decisions like "global admin search across polymorphic entities" and "model-driven searchability," letting teams make an entity searchable via configuration rather than bespoke query code. Fits a phased rollout: opt in model by model.
• Build vs buy for internal CRUD/admin tooling. The package is accumulating the plumbing most internal admin builds need — category type management, polymorphic categoryable handling, table/form conventions, status/color system, and now search fields. If you're weighing a custom internal admin framework, the search-field addition is a concrete capability to score against the build option.
• Upload/storage direction. Renaming localUpload to plainUpload signals a simplification toward the common local-disk case (and away from abstraction). Relevant if your roadmap needs multi-disk/S3 uploads: assume that is not the package's optimization target and plan accordingly.
• API stability and upgrade budget. Two changes in this release are consumer-visible: getSnSubjectHrefUrl is removed from HasSnSubject, and localUpload is renamed. Within a 1.0.x line, that is a signal to treat the package as not strictly semver-stable for downstream customizations — a reason to pin versions and reserve upgrade time, or to avoid deep coupling to internal helpers.
• Developer experience / tooling alignment. The laravel-boost core.blade.php update and enum standardization support decisions about onboarding and consistent codegen/scaffolding across teams.

When to Consider This Package

Consider it when:

• You're building Laravel admin/CRUD surfaces with category classification and polymorphic associations (categoryable) and want established table/form conventions rather than re-inventing them.
• You want model-configured search (keywordSearchFields) so searchable entities are added without touching core code.
• Your team standardizes on a Blade/component-based admin stack (per the *Form / *Table / .blade.php references) plus laravel-boost.
• Design-system consistency for statuses/tables matters to your product (multi-module admin, consistent client-facing back office).
• You value a small, opinionated, internally evolvable codebase over a large public package.

Look elsewhere / proceed with caution when:

• You need strict semver guarantees within 1.x — this release contains breaking removals and renames.
• You depend on SN-subject hyperlink generation (getSnSubjectHrefUrl) — it was removed; you'd need to reimplement at call sites.
• You need pluggable or multi-disk uploads out of the box; the plainUpload direction suggests the simple local path is the intended one.
• You need vendor SLAs, extensive public docs, or a large community — this reads as an internal/opinionated package.
• Your customizations are deeply wired into internals like the SN trait; the churn cost may outweigh reuse.

How to Pitch It (Stakeholders)

Executives: This is a low-cost consolidation release, not a new product line. It tightens consistency in the admin UI (one status color system, normalized category tables) and adds a small but reusable search foundation (keywordSearchFields for polymorphic search). The commercial value is reduced bespoke UI/search work on future internal tools and a more coherent back office. There are two small breaking changes (getSnSubjectHrefUrl removed, localUpload renamed to plainUpload) — a short upgrade task, no new infrastructure or licensing cost. Recommend adopting v1.0.12 with a pinned version and a one-time upgrade verification.

Engineering: Treat this as a hardening plus small-feature release. Action items: (1) grep for getSnSubjectHrefUrl and localUpload across app code, Blade views, and tests; replace with local implementations / plainUpload; (2) add a smoke test covering uploads and SN-subject rendering; (3) adopt keywordSearchFields on models where polymorphic search is desired — it is opt-in and low risk. Also note the categoryable guard-check optimization, enum standardization, and the laravel-boost core.blade.php update; re-run codegen/scaffolding checks after upgrade. Pin v1.0.12, verify in staging, then roll forward.