Initialize Varbase Search Base Recipe

Problem/Motivation

A standardized base recipe is needed to provide a consistent, ready-to-use search foundation aligned with Varbase best practices and suitable for projects that do not rely on external search engines such as Solr or Elasticsearch.

Proposed resolution

Introduce a new Varbase Search Base recipe that centralizes search-related modules, default configurations, and permissions using Drupal core Search and Search API with a database backend.

Included Features

• Core Search: Drupal core search functionality enabled
• Search API: Flexible framework for building advanced search solutions
• Search API DB: Database-based search backend suitable for most Varbase sites
• Database Server: Pre-configured search server with partial matching and autocomplete support
• Cron Management: Automated indexing via Ultimate Cron

Installed Modules

• search
• search_api
• search_api_db

Default Configuration

• Pre-configured Search API database server
• Minimum search keyword length set to 3 characters
• Partial matching enabled for improved result relevance
• Autocomplete support with suffix and word suggestions
• Search API cron job configured via Ultimate Cron

Permissions

The recipe defines basic search access for end users:

• Anonymous: Search site content
• Authenticated: Search site content

Remaining tasks

• ✅ File an issue about this project
• ❌ Addition/Change/Update/Fix to this project
• ❌ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Developer Documentation support on feature change/addition
• ➖ User Guide Documentation support on feature change/addition
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Code review from 1 Varbase core team member
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ❌ Update Release Notes
• ❌ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• N/A