New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UI] - Make AI Image Block Production-ready #26505
Labels
Comments
This was referenced Nov 16, 2023
john-thomas-dotcms
changed the title
[UI] - Create an AI Image Prompt Extension
[UI] - Make AI Image Prompt Production-ready
Nov 16, 2023
john-thomas-dotcms
changed the title
[UI] - Make AI Image Prompt Production-ready
[UI] - Make AI Image Block Production-ready
Nov 16, 2023
QA notes:
Use the images in the description as reference. |
Needs work. Failing case: When you add multiple consecutive images generated by AI, they are able to render properly (from a page) but when editing the contentlet only one of those images is shown. |
dsilvam
added
Needs Work
QA : Failed Internal
and removed
QA : Needs Internal
Needs Work
labels
Jan 8, 2024
Passed Internal QA: AI Image block working as expected. Case describe in the last comment got fixed. |
erickgonzalez
added a commit
that referenced
this issue
Feb 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Parent Issue
#26495
User Story
As a user of the Block Editor, I want to generate an image using the new AI Image Prompt Extension so that I can seamlessly incorporate AI-generated visuals into my content.
Endpoint:
/api/v1/ai/image/generate
Acceptance Criteria
dotCMS Version
master
Proposed Objective
User Experience
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Command Menu
Modal with the options
Generate it by a prompt
Generate using the content with additional details.
Create a Image Node
Handle error
Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
Tasks
AIImagePromptExtension
prompt extension #26551PUBLISH
endpoint to show correctly theDOTASSET
#26669The text was updated successfully, but these errors were encountered: