Search Bundle Laravel Package

Product Decisions This Supports

• Informs whether search in a CMS product should be built on Enhavo’s native search bundle versus an external search service.
• Supports roadmap scoping for content search/filtering only when the product is already on Enhavo/Symfony; it does not support a Laravel adoption decision.
• Build vs buy: low evidence for standalone adoption. Treat it as a reusable open-source component only inside the Enhavo ecosystem; otherwise favor a maintained Laravel-native or external search solution.
• Use cases: site search across Enhavo-managed content, admin/content discovery, and filtering if the main Enhavo repo documents index configuration.
• Adoption decision: do not add this as a dependency for a Laravel product. Use it as a reference implementation or fork only if Enhavo is already strategic.

When to Consider This Package

• Consider only if you are building or maintaining an Enhavo CMS or Symfony app already using Enhavo packages and need search aligned with that ecosystem.
• Consider as a reference when evaluating Enhavo’s search architecture or subtree-split packaging.
• Look elsewhere if you are on Laravel, need documented standalone installation, active issue tracking, independent release notes, or strong adoption signals.
• Avoid if you need vendor support, SLAs, transparent versioning, or low integration risk; a read-only subtree split with 2 stars, 0 dependents, and README-level maturity is a high-risk dependency.

How to Pitch It (Stakeholders)

For executives: this is not a standalone search product or Laravel package; it is an internal Enhavo/Symfony component. It does not justify roadmap investment for our Laravel stack. For engineering: treat it as an Enhavo-coupled subtree split with minimal public adoption evidence and documentation in the main repository; evaluate only if Enhavo is already our CMS. Recommendation: do not adopt now; revisit only with a concrete Enhavo use case, or choose a maintained Laravel-native/external search solution.