Drupal AI UX meeting 27 April 2026
<h2 id="meeting-overview">Meeting Overview</h2>
<p><strong>Date:</strong> Monday, April 27, 2026
<strong>Attendees:</strong> Aidan, Bruno, Ángela, Emma, Darren</p>
<h3 id="drienote-chicago-demo-on-drupal-forge">Drienote Chicago Demo on Drupal Forge</h3>
<ul>
<li>Install is live; Emma to test and report on instructions and API key flow.</li>
<li>Database key entry persists per demo instance; the .env path was local-only and didn't survive between instances.</li>
<li>Darren investigating form-driven key injection at container startup; Aidan to talk to Amazi about pre-installing their provider with a trial key as an alternative one-click path.</li>
</ul>
<h3 id="ccc-ux-review-comps-3573715-https-www-drupal-org-node-3573715-">CCC UX Review Comps — <a href="https://www.drupal.org/node/3573715">#3573715</a></h3>
<ul>
<li>Aidan walked through three CCC comps generated with Claude Design from GIN theme code, AI module code, CCC code, and ~50 screenshots; renders mockups from prose change requests.</li>
<li>"Connector" agreed as the label for external context sources (Google Analytics etc.); "manual" left unresolved as the label for file-style context items.</li>
<li>"Use Case" adopted as the umbrella concept (over "activity type"); generic defaults "working with text", "working with media", "working with people" extendable by modules.</li>
<li>Token usage promoted to its own column with a warning icon and green/yellow/red color coding when context risks overwhelming the model; contrast fixes in next pass.</li>
<li>Publishing status and last-updated combined into one column on the context list (overlaps with <a href="https://www.drupal.org/node/3586127">#3586127</a>).</li>
</ul>
<h3 id="ai-content-review">AI Content Review</h3>
<ul>
<li>Aidan to mock up feedback rendered in the node edit form (and possibly node view) for group review at the new Friday standing meeting.</li>
</ul>
<h3 id="gitlab-migration-contributor-workflow">GitLab Migration — Contributor Workflow</h3>
<ul>
<li>Non-maintainer contributors cannot assign issues on migrated projects; need Reporter membership per project. AI Initiative is the pilot.</li>
<li>Improves maintainer ergonomics but raises an open-source contribution friction question; team to follow up with maintainers to be added where needed.</li>
</ul>
<h2 id="decisions">Decisions</h2>
<ul>
<li>"Connector" is the label for external context sources; "Use Case" is the umbrella label with generic "working with ..." defaults extendable by modules.</li>
<li>Token usage gets its own column with warning icon and color coding; standing Friday meetings added for AI Review and design work.</li>
</ul>
<h2 id="questions">Questions</h2>
<ul>
<li>What is the right label for manual/file context items?</li>
<li>How should AI Review feedback render on the node edit form vs. node view?</li>
</ul>
<h2 id="next-steps">Next Steps</h2>
<ul>
<li><strong>Emma:</strong> Test the published Chicago demo and report on instructions and API-key UX.</li>
<li><strong>Darren:</strong> Prototype a form-based API key injection at container startup.</li>
<li><strong>Aidan:</strong> Talk to Amazi about provider integration with trial keys; update CCC comps with token-weight column and contrast fixes; mock AI Review feedback in node edit form for the Friday session.</li>
<li><strong>Bruno:</strong> Post mid-week Slack updates instead of waiting for Monday.</li>
<li><strong>All:</strong> Get added as Reporter members on the migrated GitLab projects; suggest alternatives for "manual".</li>
</ul>
> Related issue: [Issue #3565733](https://www.drupal.org/node/3565733)
issue