>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3585119. --> Reported by: [cadence96](https://www.drupal.org/user/3520894) Related to !1500 >>> <p>[Tracker]<br> <strong>Update Summary: </strong>Standardize AI Automator naming across UI.<br> <strong>Short Description: </strong>Fix inconsistent lowercase usage of "ai automator" in UI labels.<br> <strong>Check-in Date: </strong>04/16/2026<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> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The term <strong>"AI Automator"</strong> is used inconsistently across the UI. In several places it appears as <em>"ai automator"</em> (lowercase), which creates a UI/UX inconsistency and looks unpolished. Additionally, acronyms such as <strong>"AI"</strong> should be written in uppercase, so using lowercase is incorrect.</p> <p>Examples:<br> <img width="400" height="auto" src="https://www.drupal.org/files/issues/2026-04-16/error-example-1.png"><br> Expected: Add an <strong>AI A</strong>utomator</p> <p><img width="400" height="auto" src="https://www.drupal.org/files/issues/2026-04-16/error-example-2.png"><br> Expected: Edit <strong>A</strong>utomator {title}</p> <p><img width="400" height="auto" src="https://www.drupal.org/files/issues/2026-04-16/error-example-3.png"><br> Expected: Are you sure you want to delete the <strong>AI A</strong>utomator {title}</p> <p><img width="400" height="auto" src="https://www.drupal.org/files/issues/2026-04-16/error-example-4.png"><br> Expected: AI Automator <strong>Field C</strong>onfiguration</p> <p><img width="400" height="auto" src="https://www.drupal.org/files/issues/2026-04-16/error-example-5.png"><br> Expected: + Add <strong>A</strong>utomators <strong>T</strong>ool</p> <h4 id="summary-steps-reproduce">Steps to reproduce (required for bugs, but not feature requests)</h4> <p>1. Switch to 2.0.x-dev<br> 2. Go to <code>/admin/config/ai/ai-automators</code><br> 3. Click on "Field Automators"<br> 4. Observe the title: "Add an ai automator"<br> 5. Create, edit or delete an automator<br> 6. Observe inconsistent casing in titles and confirmation dialogs</p> <p>Environment:<br> - AI module: <code>2.0.x-dev</code><br> - Component: <code>AI Automators</code></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Standardize all UI strings to consistently use:</p> <p><strong>"AI Automator"</strong></p> <p>Examples:<br> - "Add an AI Automator"<br> - "Edit AI Automator"<br> - "Delete AI Automator ..."</p> <p>Ensure consistency across:<br> - Page titles<br> - Form labels<br> - Confirmation dialogs<br> - Messages</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>- [ ] Identify all occurrences of "ai automator" in the codebase. Currently identified in:</p> <ul> <li>ai_automators.routing.yml</li> <li>ai_automators.permissions.yml</li> <li>src/Entity/AiAutomator.php</li> <li>src/Form/AiAutomatorEditForm.php</li> </ul> <p>- [ ] Update strings to "AI Automator"<br> - [ ] Verify UI consistency across all related pages<br> - [ ] Check for translation impact (string changes)</p> <h3>Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)</h3> <p>This is a UI-only change. No API or data model changes expected.</p> <h3 id="summary-ai-usage">AI usage (if applicable)</h3> <p>[x] AI Assisted Issue<br> This issue was generated with AI assistance, but was reviewed and refined by the creator.</p> <p>[ ] AI Assisted Code<br> [ ] AI Generated Code<br> [ ] Vibe Coded</p>