Search Widget Laravel Package

Product Decisions This Supports

• Search UX inside Victoire DCMS — this is not a general-purpose search package; it is a widget for the Victoire DCMS widget system. The only decision it directly supports is "how do we give editors a droppable search component in a Victoire page" without building one.
• Build vs. buy (heavily weighted toward build) — with 0 stars, 0 dependents, and no community signal, treat this as a reference implementation, not a dependency. The realistic PM decision it informs is: "do we vendor/fork ~a few hundred lines of Symfony widget glue, or write our own widget against Victoire's widget API?"
• Roadmap scoping for content search — useful for estimating the size of the "search box on marketing pages" story. It shows the minimum surface area: widget definition, form/config, template, and wiring to whatever index you already have (this bundle does not ship a search engine).
• Not a Laravel decision at all — if the current stack is Laravel, this package is out of scope. It is a Symfony bundle (WidgetSearchBundle) for a Symfony CMS. Any roadmap item it "supports" presumes a Victoire/Symfony front end.

When to Consider This Package

Consider it only when all of the following are true:

• You are running Victoire DCMS and need a search widget that plugs into its widget registry.
• You are comfortable pinning to the exact Victoire/Symfony version the bundle was written against — there is no release cadence to rely on.
• You have in-house Symfony capability to read, patch, and own the code, because you will likely be the maintainer.
• Your search backend already exists (Elasticsearch, Solr, DB LIKE, whatever) and you only need the editor-facing widget and rendering layer.

Look elsewhere — or build in-house — when:

• You are on Laravel, WordPress, or a headless JS front end; the package is architecturally irrelevant.
• You need maintained code: security patches, Symfony major-version support, or a support channel. Zero dependents means zero downstream pressure to keep it current.
• You need real search features (facets, relevance tuning, indexing, analytics). This bundle is a UI adapter, not a search product.
• You are making a buy vs. build call at the platform level: a 0-star bundle is not a vendor relationship, it is a code sample.

How to Pitch It (Stakeholders)

To executives: This is a small, unmaintained open-source component for a niche Symfony CMS. It is not a strategic dependency and carries no vendor cost — but it also carries no vendor support. Recommend it only as a starting reference if we are already committed to Victoire; otherwise it should not appear on a roadmap slide.

To engineering: Treat friendsofvictoire/search-widget as a fork candidate, not a dependency. It is Symfony/Victoire-specific (not Laravel), has effectively no adoption, and should be pinned or vendored if used at all. Budget a short spike to read the widget registration and template code, then decide whether to adopt-and-own or reimplement against Victoire's widget API. Do not assume it provides search — it provides the box and the wiring, and we bring the index.