Drupal AI UX meeting 13 April 2026
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3565732. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h2 id="meeting-overview">Meeting Overview</h2> <p><strong>Date:</strong> Monday, April 13, 2026<br> <strong>Attendees:</strong> Aidan Foster, Bruno, Marcus, Sahil, Arian Raeesi, Darren, Emma </p> <h3 id="delete-icon-change-x-to-garbage-can-3579423-https-www-drupal-org-node-3579423-">Delete Icon Change (X to Garbage Can) &mdash; <a href="https://www.drupal.org/node/3579423">#3579423</a></h3> <ul> <li>Approved swap to the shared-library garbage can icon; moved to RTBC for the 1.4 release.</li> </ul> <h3 id="model-recommendation-and-deprecation-notifications-3575689-https-www-drupal-org-node-3575689-">Model Recommendation and Deprecation Notifications &mdash; <a href="https://www.drupal.org/node/3575689">#3575689</a></h3> <ul> <li>Direction set on surface, label, and scope; Bruno to iterate designs. Details tracked in the ticket.</li> </ul> <h3 id="chat-ui-width-and-draggable-resize-3544476-https-www-drupal-org-node-3544476-">Chat UI Width and Draggable Resize &mdash; <a href="https://www.drupal.org/node/3544476">#3544476</a></h3> <ul> <li>User testing shows people try to drag the chatbot panel wider; chatbot and Canvas AI will share one draggable pattern.</li> </ul> <h3 id="ai-review-module-prototype-status">AI Review Module Prototype Status</h3> <ul> <li>Artem's backend build expected this week against a small sample page; extraction and response time are the current bottleneck.</li> <li>AI Content Advisor and AI Content Suggestions to be deprecated once AI Content Review lands, with a migration path; Yoshua joining on SEO agents.</li> </ul> <h3 id="ai-review-use-case-scenarios">AI Review Use Case Scenarios</h3> <ul> <li>Three scenarios drafted: university editorial style guide, FinDrop/Drupalcon prototype, and a minimal Nielsen Norman tone-and-voice worksheet.</li> <li>FinDrop dry run produced ~15 items per review, surfacing the need for three outcomes per item: accept, dismiss as not applicable, or flag as bad feedback.</li> <li>MVP UI direction: page-order feedback table with source content in a separate tab; in-place fixes deferred.</li> </ul> <h3 id="drupal-forge-qa-patch-testing">Drupal Forge QA Patch Testing</h3> <ul> <li>No update; Marcus to follow up with Tawny at Wednesday's QA meeting.</li> </ul> <h2 id="decisions">Decisions</h2> <ul> <li>AI Review MVP is a page-order feedback table with source in a second tab; in-place fixes deferred.</li> <li>AI Content Advisor and AI Content Suggestions will be deprecated in favor of AI Content Review.</li> </ul> <h2 id="questions">Questions</h2> <ul> <li>How should "apply this feedback" work in AI Review beyond the side-by-side MVP?</li> <li>Status of the Drupal Forge patch-apply QA workflow (waiting on Tawny).</li> </ul> <h2 id="next-steps">Next Steps</h2> <ul> <li><strong>Bruno/Angela:</strong> Iterate model notification designs per #3575689.</li> <li><strong>Emma:</strong> Tighten #3544476 and open a linked Canvas AI child issue; comment on the AI Review use cases doc.</li> <li><strong>Aidan:</strong>keep developing the three AI Review scenarios, support Deprecated model flagging</li> <li><strong>Artem:</strong> Deliver first testable AI Review backend build this week.</li> </ul> > Related issue: [Issue #3565731](https://www.drupal.org/node/3565731)
issue