Messaging and positioning guide for Drupal AI
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3584790. -->
Reported by: [shruti.desai@acquia.com](https://www.drupal.org/user/3859295)
>>>
<p>[Tracker]<br>
<strong>Update Summary: </strong>[One-line status update for stakeholders]<br>
<strong>Check-in Date: </strong>MM/DD/YYYY<br>
<strong>Additional Collaborators: </strong><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>Limited effort has been invested in Drupal AI messaging and positioning to date due to capacity and skill access. As Drupal AI grows in prominence, content creators, marketers, and event planners need a clear, consistent reference for how to present Drupal AI — one that resonates with our ideal customer profiles, differentiates from the competition, and adapts to regional market motivations (EU, US, public sector).</p>
<p>Without this, Drupal AI risks being presented inconsistently, too narrowly (web CMS only), or without the strategic angles — sovereignty, privacy, freedom to choose — that make it genuinely differentiated.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Produce a messaging and positioning guide covering:<br>
- Core positioning statement and one-liner<br>
- Three message pillars with key phrases and usage guidance<br>
- Persona messaging for marketing leaders, IT leaders, and solutions integrators<br>
- Competitive intelligence (Adobe AEM, Sitecore, Contentful, WordPress)<br>
- Regional messaging adaptation (EU, US, public sector)<br>
- Proof points library with approval tagging<br>
- Use cases: campaigns to market, building a website fast, content at scale<br>
- Glossary of Drupal AI terms<br>
- What we don't say</p>
<h3 id="summary-remaining-tasks">Target date or deadline</h3>
<p>First rough draft: end of April 2026<br>
Final version: end of May 2026</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>
issue