>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3555612. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h2 id="meeting-overview-topics">Meeting Overview / Topics</h2> <ul> <li><strong>AI Core &gt; Default Providers - New Vibe Coded UI:</strong> Aidan shared a demo of a "vibe-coded" improvement for the AI default settings page, which was rebuilt into a cleaner table layout. This process highlighted significant gaps in the Gin admin theme, such as a lack of proper tooltips, external link icons, and consistent typography classes.</li> <li><strong>FlowDrop UI Prioritization:</strong> The team reaffirmed that focusing on improving the new FlowDrop UI is a better long-term strategy than trying to fix the complex and confusing legacy Drupal forms for agent configuration. <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ai_initiative/-/work_items/3562010" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai_initiative/-/work_items/3562010</a></span></li> <li><strong>UX Triage &amp; Workflow:</strong> The team reviewed the "Needs UX review" board on Drupal Starforge, acknowledging the influx of complex issues. They discussed the current workflow, where smaller teams or pairs work on difficult issues offline before presenting a summary or proposed solution to the larger group.</li> </ul> <h2 id="decisions">Decisions</h2> <ul> <li><strong>AI Dashboard 1.0 is Released:</strong> The first stable version of the <a href="https://www.drupal.org/project/ai_dashboard">AI Dashboard </a>is complete and released.</li> <li><strong>Shared AI UI Library:</strong> To address the gaps in the Gin theme, the team decided to create a small, shared library of custom CSS and JavaScript within the AI module. This will provide consistent UI elements like tooltips and icons. Custom CSS classes will be prefixed with ai- to avoid conflicts. Icons will be sourced from the Drupal CMS design system first, and the Phosphor icon library second.Tippy.js will be considered for implementing tooltips.</li> <li><strong>Icon in UI Library</strong> - When possible used the Drupal CMS library (<a href="https://www.figma.com/design/IQNqQnxkUiFjp5GSp9E3nV/Design-System---Drupal-CMS?node-id=2349-2606&amp;t=PUrVmEHZ567a5ZBu-0">https://www.figma.com/design/IQNqQnxkUiFjp5GSp9E3nV/Design-System---Drupal-CMS?node-id=2349-2606&amp;t=PUrVmEHZ567a5ZBu-0</a>) If nothing is useful there then source from <a href="https://phosphoricons.com/">https://phosphoricons.com/</a></li> </ul> <h2 id="questions">Questions</h2> <ul> <li>How can the team effectively prioritize the large and growing backlog of complex UX issues, given the limited time in the weekly sync meeting?</li> </ul> <h2 id="next-steps">Next Steps</h2> <ul> <li><strong>Sahil:</strong> Connect with Harivansh to get onboarded and start contributing to the FlowDrop UI project.</li> <li><strong>Aidan:</strong> Follow up with Drupal CMS team to advocate for including the new AI Dashboard in the official AI recipe.</li> <li><strong>Aidan:</strong> Create a new issue to propose the creation of a shared UI asset library (CSS/JS) within the AI module to provide consistent tooltips, icons, and typography classes.</li> <li><strong>Aidan:</strong> Sync with Jamie and Marcus to review the proposed AI Provider Registry YAML file format. <ul> <li><strong>Goal:</strong> Get feedback and confirm the architectural approach for managing provider metadata (e.g., info links, model details).</li> <li><strong>Key Question:</strong> Should this be a central registry in the AI Core module? (What other options do we have?)</li> </ul> </li> <li><strong>UX Teams (1x, Aidan &amp; Emma, OpenSense Labs):</strong> Continue to triage and work through the "Needs UX review" board, using smaller offline sessions to tackle complex issues before bringing summaries to the main Monday meeting.</li> </ul> > Related issue: [Issue #3555611](https://www.drupal.org/node/3555611)