Content Edit dotAI Integration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
Currently, content creation and refinement in dotCMS requires significant manual effort. Content editors lack AI-powered tools to enhance, generate, and refine content at various levels (field, content type, and block editor). This results in inconsistent content quality, increased time-to-publish, and limited content optimization capabilities.
Objectives
- Implement a progressive, phased approach to AI-powered content enhancement in dotCMS
- Deliver immediate customer value through vertical slices of functionality
- Seamlessly integrate AI capabilities with existing dotCMS interfaces
- Enable customization of AI behavior through field variables and global settings
- Support multiple content refinement and generation scenarios
User Story
As a content editor, I want access to AI-powered content enhancement tools at various levels (field, content type, block editor), so I can efficiently create, refine, and optimize content while maintaining consistency and quality.
Acceptance Criteria
- The system provides AI assistance for Text Field, WYSIWYG, and Textarea field types
- Users can apply predefined and custom content refinements through an intuitive interface
- Content generation capabilities support both new and existing content
- The solution preserves existing content when requested
- All components follow dotCMS design system guidelines
- Integration with dotAI provides appropriate loading states and error handling
- The system supports customization through field variables and global settings
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
Implementation Approach
The implementation will follow a phased approach, delivering vertical slices of functionality that provide immediate value:
- Basic Field Refinements - Field-level AI assistance with predefined options
- Customizable Refinements - Customer-specific AI behavior configuration
- Full Content Generation - Complete content entries with structured output
- Advanced Content Generation - Content-type level AI customization
- Context-Aware Generation - Intelligent field-aware content generation
- Block Editor Enhancement - AI integration with block editor
- Taxonomy Enhancement - AI-powered content organization
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
- dotAI API is available and can support the required functionality
- UI/UX designs for each phase are finalized before development begins
- Adequate performance and error handling have been considered
Implementation Notes
- Ensure seamless integration with dotAI structured data endpoints.
- Optimize performance to prevent delays when generating or updating content.
- Implement user-friendly options to preview, accept, or reject AI-generated content.
Impact Analysis
- Affected features: Content editing, dotAI integration, structured data handling.
- Data migration needs: None
- Backwards compatibility: Ensure compatibility with existing content types and dotCMS APIs.
Task Complexity
- Technical complexity: High - requires integration with dotAI API, structured data handling, and multiple field types
- Testing complexity: High - involves testing various content types, user scenarios, and edge cases
- Integration complexity: High - requires coordination across multiple dotCMS components
Video 1 Hackathon - Content Generation
https://github.com/user-attachments/assets/ff2e1beb-2f8d-4f6e-a610-a19c193c173f
Video 2 Hackathon - Inputs refinement
https://github.com/user-attachments/assets/a8340def-e2c8-4a1c-bf5e-dda48030062f
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
No source files, tests, or entry points are identified. Start by reviewing the dotAI structured data endpoints and the existing Text Field, WYSIWYG, and Textarea editing flows; done requires a phased implementation covering the listed field assistance, generation, refinement, loading, error, and configuration requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ai, api, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100