>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3555613. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <p>Aidan Foster, Marcus Johansson, Emma Horrell, Bruno Bruno, Sahil Sharma, Abhisek (DropSolid - new), Rakhi Mandhania</p> <hr> <h2 id="meeting-overview-topics">Meeting Overview / Topics</h2> <h3 id="ai-experience-wizard-demo">AI Experience Wizard Demo</h3> <p>Abhisek from DropSolid demoed a new "AI Experience Wizard" module that simplifies provider installation through a click-through interface. The module uses Drupal's Package Manager to install providers and apply recipes automatically. The team discussed how this relates to the AI Dashboard (which will be included in Drupal CMS 2.0) and identified the different use cases:</p> <ul> <li><strong>Drupal CMS:</strong> Pre-configured with default providers (OpenAI, Anthropic, Amazi); Amazee will be the zero-config default</li> <li><strong>AI Experience Wizard:</strong> For users who already know which provider they want and need guided installation</li> </ul> <h3 id="default-provider-settings-redesign-3560206-https-www-drupal-org-node-3560206-">Default Provider Settings Redesign (<a href="https://www.drupal.org/node/3560206">#3560206</a>)</h3> <p>Aidan showed the updated table-based layout for the AI Settings page, now with provider/model icons (plug for provider, cube for model). Eric Homanchuk is converting the prototype to production-ready code. The team discussed:</p> <ul> <li>Whether UX changes should go in patch versions (1.2) vs minor versions (1.3)</li> <li>The provider registry YAML will include a comment marking it as a "moving target" until 1.3</li> </ul> <h3 id="provider-registry-schema">Provider Registry Schema</h3> <p>Discussion about the YAML structure for storing provider metadata (capabilities, pricing links, model info). Key points:</p> <ul> <li>Dynamic model discovery means the registry may be out of date (e.g., GPT-5 appeared automatically)</li> <li>Simple installers should focus on API-key-based providers (not complex setups like AWS/Azure)</li> <li>Future consideration: hooks allowing providers to override their own entries</li> </ul> <h3 id="shared-ui-library-3567389-https-www-drupal-org-node-3567389-">Shared UI Library (<a href="https://www.drupal.org/node/3567389">#3567389</a>)</h3> <p>Aidan presented the CSS utility library documentation with <code>ai-</code> prefixed classes. The library:</p> <ul> <li>Uses Drupal core CSS variables (Claro) with Gin fallbacks</li> <li>Includes typography utilities, icon buttons, and form element widths</li> <li>Icons stored locally as CSS background images</li> <li>Bruno emphasized the importance of making developers aware the library exists</li> </ul> <h3 id="flowdrop-ui-update">FlowDrop UI Update</h3> <p>Sahil has connected with Harivansh and will share design updates by the next call. Focus is on improving the side panel form that opens when clicking agent nodes in the visual editor.</p> <h3 id="standardized-provider-selector-form-element-3556181-https-www-drupal-org-node-3556181-">Standardized Provider Selector Form Element (<a href="https://www.drupal.org/node/3556181">#3556181</a>)</h3> <p>Marcus explained the new form element Abhisek is building:</p> <ul> <li>Single dropdown combining provider + model (no AJAX cascade)</li> <li>AJAX only loads when model-specific config options are needed</li> <li>Simplifies the current situation where each module implements this differently</li> <li>Abhisek completed documentation fixes; NEEDS UX REVIEW</li> </ul> <hr> <h2 id="decisions">Decisions</h2> <ol> <li><strong>Shared UI library approach approved</strong> - Proceed with <code>ai-</code> prefixed classes using Drupal core CSS variables</li> <li><strong>Icons centralized in AI Core</strong> - Duplicate icons in submodules (Dashboard, CCC) should be refactored to use shared library</li> </ol> <hr> <h2 id="questions">Questions</h2> <ul> <li>How can the team effectively prioritize the large and growing backlog of complex UX issues?</li> <li>Should there be a stable identifier/key for provider registry entries to support overrides?</li> <li>How do we ensure new contributors discover and use the shared UI library?</li> </ul> <hr> <h2 id="next-steps">Next Steps</h2> <ul> <li><strong>Sahil:</strong> Share FlowDrop UI design update by next call</li> <li><del><strong>Abhisek:</strong> Complete 2 remaining doc fixes on provider selector issue (<a href="https://www.drupal.org/node/3556181">#3556181</a>)</del> &#9989; Done</li> <li><strong>Abhisek:</strong> Check if config names are standardized across providers</li> <li><strong>Marcus:</strong> Link research issues for markdown editor, JSON schema builder, and token autocomplete</li> <li><strong>Aidan:</strong> Add "moving target" comment to provider registry YAML; meet with Rakhi on sprint issues</li> <li><del><strong>Aidan + Emma:</strong> Review Needs UX Review board for lighter issues to close before Friday sprint deadline</del> &#9989; All done by Kristen!</li> <li><strong>Eric Homanchuk:</strong> Continue making table layout code production-ready for 1.2 release</li> <li><strong>Team:</strong> Continue async discussion in #ai-ux Slack channel on AI Experience Wizard integration with existing tools</li> </ul> > Related issue: [Issue #3555612](https://www.drupal.org/node/3555612)