>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3555804. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>As part of the UX meeting today, we were going over the new dashboard design <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/ai_initiative/issues/3554163" title="Status: Active">#3554163: [Meta] UX concept for AI Dashboard / Status Page / Kickstarter</a></span>.</p> <p>Certain AI modules and thus recipes work better if you are using specific models.</p> <p>If you try it with a different model that "technically" could work, it may not actually work or just not work that well.</p> <p>This is bad UX if a person thinks a model will support their feature, but it doesn't really.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Provide a mechanism (e.g. a yml or json file) for AI modules and recipes to have a list of tested/preferred/compatible models.</p> <p>The dashboard code would be able to inspect this information to provide the user with sensible guidance to set up the right providers with these models.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Discuss</li> <li>Agree on approach</li> <li>Create issues in the right places</li> <li>Add documentation for module and recipe developers</li> </ul> > Related issue: [Issue #3554163](https://www.drupal.org/node/3554163)