>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3560206. --> Reported by: [afoster](https://www.drupal.org/user/594458) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>UI Settings proposal ready for review<br> <strong>Short Description: </strong>Reorganize AI Settings from vertical form list to capability-focused tables for easier navigation and comparison<br> <strong>Check-in Date: </strong>11/26/2025<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h2 id="problem-motivation">Problem/Motivation</h2> <p>The current AI Settings page (<code>/admin/config/ai/settings</code>) presents configuration options as a long vertical list of nested form elements. As more AI providers are installed, this page becomes increasingly difficult to navigate and compare settings across providers.</p> <p><strong>Current pain points:</strong></p> <ul> <li>Vertical scrolling through 15+ capability sections</li> <li>No easy way to compare which providers support which capabilities</li> <li>Provider/model selection is repetitive across each capability</li> <li>Vector database configuration is mixed in with inference capabilities despite being architecturally distinct</li> </ul> <h2 id="proposed-resolution">Proposed Resolution</h2> <p>Restructure the page using a table-based layout organized around <strong>AI Capabilities</strong> as the primary concept:</p> <p><strong>1. Capability-focused tables</strong> &mdash; Group configurations into scannable tables where rows represent capabilities (Chat, Image Vision, Embeddings, etc.) and columns show the configured provider, model, and relevant info.</p> <p><strong>2. Separate installed vs. available capabilities</strong> &mdash; Clearly distinguish between capabilities that are ready to use versus those requiring additional provider installation.</p> <p><strong>3. Surface pricing/documentation links</strong> &mdash; Each capability row should include an "Info" column linking to provider pricing or documentation, helping administrators make informed decisions.</p> <p><strong>4. Distinct Vector Data section</strong> &mdash; Separate vector database configuration (embeddings + VDB providers) from inference capabilities, reflecting their different architectural roles.</p> <h2 id="proposed-information-architecture">Proposed Information Architecture</h2> <ul> <li><strong>AI Capabilities from Installed Providers</strong> &mdash; Table of currently configurable capabilities</li> <li><strong>Additional AI Capabilities</strong> &mdash; Capabilities available if additional providers are installed</li> <li><strong>Vector Data Capabilities</strong> &mdash; Embeddings and vector database provider configuration</li> </ul> <h2 id="before">Before</h2> <p> <img src="https://www.drupal.org/files/issues/2025-11-26/AI%20Settings%20%28Before%29.png" alt="Current UI"><br> <br><em>[Current AI Settings page with vertical nested form elements]</em></p> <h2 id="wireframe">Wireframe</h2> <p> <img src="https://www.drupal.org/files/issues/2025-11-26/AI%20Model%20Capabilities-Operations%20%280.5x%29.png" alt="Wireframe of table UI"><br> <em>[Proposed table-based layout &mdash; this is a rough wireframe to frame discussion, not a final design] </em></p> <h2 id="discussion-topics">Discussion Topics</h2> <ul> <li>Can we require documentation for each model's cost for each provider?</li> <li>Can we include EOL info for models that are deprecated?</li> <li>Can we at least link to the pricing page?</li> </ul> > Related issue: [Issue #3567389](https://www.drupal.org/node/3567389) > Related issue: [Issue #3558401](https://www.drupal.org/node/3558401)