dotCMS / dotCMS/core

UX Design for AI Content Generation Flow

Open
#31,333 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dotCMS : AI Team : Falcon Type : Task
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

#31332

Task

Design a user-friendly interaction flow for AI-generated content. This includes UX for both new content creation and updates to existing content types.

Requirements
  • For new content:

    • Design an input field to capture the user's prompt.
    • Include a "Generate Content" button to trigger content generation.
    • Ensure all fields (text, WYSIWYG, categories, tags, block editor) are filled based on AI output.
  • For existing content:

    • Allow users to preview AI-generated suggestions.
    • Preserve non-empty fields unless the user opts to overwrite them.
    • Design a floating input for generating suggestions based on current content context.
  • Provide design mockups for both mobile and desktop views

Proposed Objective

User Experience

Proposed Priority

Priority 2 - Important

Acceptance Criteria
  • Completed design mockups are provided and approved.
  • User interactions are intuitive and minimize manual intervention.
  • Both new and existing content flows are accounted for in the design.
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review parent issue #31332 first, then gather the missing product context and any referenced Figma designs; this issue names no repository files or tests. Done means approved mobile and desktop mockups covering new-content prompts and generation, existing-content suggestions, overwrite behavior, and the listed field types.

Written by the indexing model from the issue text.

Assessment

Domain
content, design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.