Support Laravel Package

Product Decisions This Supports

• Build vs. buy for back-office surfaces. This is a Laravel package that ships a prebuilt admin UI layer (CSS component/utility split in v1.1.0) plus a configurable global search. The decision it informs is whether to assemble internal tooling from a package or invest engineering weeks in a custom admin front end and search stack.
• Roadmap: unified cross-module search. v1.1.0's "global search enhancement" (module config covering channels, terms_operator term-splitting/combinations, a single integrated search button, results page with placeholder and explicit search) is effectively a shipped version of a common roadmap item: "one search box across all entities." That can pull a planned epic forward or kill it.
• Search UX and scoping decisions. Configurable channel coverage and term operators mean PMs can decide which modules are searchable and how queries are tokenized without new code. The results-page placeholder and explicit-search behavior are small but real UX levers for empty states and query intent.
• Design-system and theming strategy. The CSS layering refactor (shared sn-* utilities moved to utilities.css, index.css reduced to entry point and component-local styles) is a product decision about white-labeling and brand theming: do we own the design system, or adopt the package's class contract?
• Not a fit for: domain logic, data modeling, analytics/reporting, or search relevance ranking. Those remain in-house; this package is presentation + search configuration, and the roadmap should not assume it delivers relevance tuning.

When to Consider This Package

Consider adoption when:

• The product is a Laravel application and the surface in question is an internal/admin/back-office UI where CRUD screens plus a cross-entity search box cover most user needs.
• You want configurable multi-module search (channel coverage, term operators) more than you want relevance tuning, fuzzy matching, or ML ranking.
• Your team is small or backend-heavy, and the cost of maintaining Blade templates, CSS, and a search UI is a real constraint.
• You are comfortable owning the upgrade path: v1.1.0 is a minor release but touches CSS architecture and search behavior, so treat it as a change requiring visual regression QA, not a silent bump.

Look elsewhere when:

• You need headless/API-only delivery, a non-Laravel stack, or a decoupled SPA where the shipped CSS/Blade markup provides no leverage.
• Search must scale to large corpora or require relevance ranking, faceting, or typo tolerance — that is an Elasticsearch/Meilisearch/Algolia decision, not this package's.
• You have strict design-system ownership or accessibility/i18n requirements that are not documented as guarantees for this package.
• You have heavily overridden index.css or depended on where sn-* utility classes were defined — the v1.1.0 refactor relocates those classes, so customized installs should audit overrides and expect visual regressions before upgrading.

How to Pitch It (Stakeholders)

Executives (one line): A low-cost, Laravel-native package that gives us an admin UI and a configurable cross-module search out of the box; v1.1.0 improves search coverage and cleans up the CSS layer, and the upgrade is a small, contained engineering task.

Engineering: v1.1.0 is a minor bump but CSS-touching — shared sn-* utilities moved into utilities.css and index.css is now entry point plus component-local styles. Audit any local overrides, check Blade/markup overrides survive, and run visual regression on key screens. Search now reads module config for channels and terms_operator, and the results page supports placeholder and explicit search — verify index/query assumptions and permission scoping on newly searchable modules.

Product/PM: Do not staff a "unified search" build; configure modules against the new search options and spend the saved time on a short relevance/quality spike. Sequence the upgrade with a QA pass for UI regressions, and keep the roadmap's analytics, ranking, and data-model work in-house — this package does not cover those.