>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3584827. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Discussing AI UX work and upcoming Drupal CMS UI/UX changes, including XB AI UX, AI navigation and workflows, chatbot UX, etc.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Meetings every two weeks on Mondays 7am Pacific / 3pm UK / 730pm IST</p> <p>Contact Kristen Pol via Slack if you would like to be added to the meeting invitation.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Meet and discuss</li> <li>Recording made available in the Slack channel</li> </ul> ## Meeting notes ### Meeting summary **Quick recap** The UX team met to discuss several AI-related projects and updates. The main topics covered included improvements to the AI API Explorer UI, updates to the Context Control Center design, and progress on the AI content review features. Marcus presented requirements for modernizing the API Explorer to better align with industry standards, including features like chat history, export/import functionality, and improved formatting options. Bruno shared updates to the tool configuration interface, removing unnecessary fields and adding parameter selection dropdowns. The team reviewed the Context Control Center design, discussing token display approaches and label naming conventions. Aidan presented exploratory designs for the AI content review interface, focusing on how to display multiple review categories and thresholds effectively. The conversation ended with a discussion about making the DreesNote demo more accessible by potentially securing additional API credits from Amazi, with plans to follow up with Matthew about this possibility. **Next steps** - Aidan: Reach out to Matthew (and possibly Dan) at Amazi to discuss the possibility of providing a $5 API token for the DreesNote demo and explore the technical/business requirements for unique demo tokens. - Aidan: Set up a follow-up meeting with Darren, Salim, and Michael (from Amazi) to demo the DreesNote instance and discuss provisioning of demo tokens with increased budget. - Aidan: Review the revised Context Control Center list UI with Kristen to get her feedback, especially regarding the use of tokens as a column and the new label conventions. - Aidan: Work with the team to refine the tooltip and warning messages for token usage in the Context Control Center UI, ensuring clarity and appropriate accessibility. - Aidan: Continue UI work on the AI review interface, focusing on how to best display multiple review categories/scores, and bring findings to the next relevant meeting. - Bruno: Proceed with submitting the updated tool configuration UI for review, as no further changes are needed based on current feedback. - Aidan (and relevant team): Schedule and attend the Friday project-specific AI review meeting to continue UI work and progress on AI review features. - Aidan: Coordinate with Salim and Darren to ensure they are included in relevant meetings as they get enrolled in all project meetings. **Summary** **UX Team Meeting Updates** Aidan welcomed Salim to the UX meeting and clarified that this was a smaller UX-focused meeting rather than the main meeting. The team discussed several agenda items including updates on UX-tagged issues, improving the one-click installer for Drupal AI, and addressing questions about a new partner with front-end skills. Aidan also mentioned revisions to the context control center list and work on AI content review, noting that time constraints would likely prevent them from covering all items on the agenda. **AI API Explorer UX Design** Marcus presented a new UX design for the AI API Explorer, explaining that it would address functionality gaps in the current tool by aligning with modern playgrounds like OpenAI's platform. He outlined plans to implement export/import capabilities for requests and logs, allowing users to recreate failed requests or share test cases. The discussion ended mid-presentation as Marcus was about to show the current UI, with Aidan expressing interest in seeing a demonstration of the local interface. **UI Moderation and Chat Features** Marcus demonstrated the UI for moderation and chat features in their system, showing how users can test against moderation layers and perform complex chat functions. He identified several UX issues, including poor design, non-compatibility with dark mode, and missing features like chat history functionality. Aidan asked about the purpose of certain UI elements and inquired about using chat history, to which Marcus confirmed this feature would allow users to see previous conversations and export them. **AI Module Features Discussion** The team discussed features for an AI module, focusing on debugging capabilities and user testing functionality. They explored options for exporting and importing chat histories and media, with Marcus explaining the technical challenges of file formats and storage. The discussion included plans for adding features like image embeddings, formatted responses (particularly for Markdown and JSON), and adaptive UI elements based on selected models. Aidan noted the need to learn more about image LLMs, and Marcus demonstrated the current JSON formatting capabilities using PHP's JSON beautification. **AI Project Interface Design Updates** The team discussed several key topics related to their AI projects. Bruno presented UI updates for a tool interface, removing the key field and adding parameter selection options with descriptions. The team reviewed the Context Control Center design, deciding to keep tokens as a separate column and use "text" as the label for static content types. Aidan shared exploratory designs for AI review interfaces, focusing on how to display multiple review categories effectively, with the team agreeing that showing pass/fail counts rather than just averages would be more useful. The team also addressed challenges with the DriesNote demo, discussing the need for additional API credits and potential collaboration with Amazi to provide demo tokens.