What problem does it solve?
OrchardCore developers often confuse its three indexing concepts—stored queries, full-text index profiles, and YesSql MapIndex tables—and struggle to wire up search correctly. This Skill guides you through defining SQL/Lucene/Elasticsearch queries, building full-text index profiles, and writing content part/field index handlers following project conventions.
Core Features & Use Cases
- Stored Queries: Create and execute named SQL, Lucene, or Elasticsearch queries via recipe steps or
IQueryManager, with Liquid-templated SQL and optional ContentItem hydration.
- Full-Text Indexing: Build index profiles for Lucene, Elasticsearch, or Azure AI Search, and implement
IContentPartIndexHandler/IContentFieldIndexHandler to index custom part and field data.
- Use Case: You need blog posts searchable on your OrchardCore site. Create a
CreateOrUpdateIndexProfile recipe step targeting the BlogPost content type, register a part index handler for custom fields, then query the index through ISearchService.
Quick Start
Ask the AI to create an OrchardCore index profile and a content part index handler so your custom content type becomes searchable in Lucene.