[FEATURE] AI-Powered Search & Content Discovery
Open
Nobody has claimed this yet.
stale
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem
Developers need semantic search capabilities to help users find relevant content using natural language queries instead of exact keyword matching.
Goal
Integrate dotCMS's AI search functionality into the SDK, enabling semantic content discovery with relevance scoring.
Target Personas
- Developer teams
- Content teams
Demo Expectations
// What can be demonstrated in bi-weekly demo
const searchResults = await client.ai.search('articles about renewable energy');
const relatedContent = await client.ai.search.related('sustainability trends');
// Show: semantic matching, content scores, extracted text
console.log(searchResults.map(item => ({
title: item.title,
score: item.score,
extractedText: item.aiContent
})));
User Stories
- As a developer, I want to implement intelligent search in applications, so that users can find content using natural language instead of exact keywords
- As a content team member, I want better content discoverability in headless applications, so that users can more easily find relevant content
- As a developer, I want relevance scoring and semantic matching, so that search results are ranked by actual relevance rather than just keyword matching
Acceptance Criteria
- Semantic search endpoints implemented with full TypeScript support
- Related content search functionality
- Relevance scoring included in search results
- Support for content type filtering and field-specific search
- Integration with existing dotCMS content structures
- Pagination and result limiting capabilities
- Extracted text and AI content summaries in results
Links
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked dotAI Search API and locate the existing SDK content structures; the issue names no files or tests. Done means the demonstrated AI search and related-content calls support the listed filtering, scoring, pagination, extracted-content, and TypeScript requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100