Create Individual Pages For Each Official AI Demo
> Migrated to [ai_initiative_marketing#10](https://git.drupalcode.org/project/ai_initiative_marketing/-/work_items/10). Use that ticket. >>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3584244. --> Reported by: [dan2k3k4](https://www.drupal.org/user/2437398) >>> <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>The Drupal AI Initiative has successfully launched several interactive demos, allowing users to spin up temporary environments provided by amazee.io to test AI capabilities. However, these demos currently lack dedicated landing pages.</p> <p>Users arriving at these environments often find it difficult to understand the specific AI capabilities being showcased, the intended workflow, or the underlying configuration.</p> <p>To maximize the impact of these demos, we need informative content pages on Drupal.org that provide context, video demonstrations, and technical summaries for each individual demo.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Create six new content pages under the drupal.org/ai/demos path.<br> Each page will serve as the "front door" for a specific demo, featuring:</p> <ul> <li>An embedded video showing the demo in action.</li> <li>Clear text describing the use case and the specific AI capabilities (e.g., RAG, LLM-based summarization, etc.).</li> <li>A prominent "Launch Demo" form that triggers the environment spin-up.</li> <li>Technical metadata regarding the modules and providers used.</li> </ul> <p><strong>Individual Demo Requirements (to be broken into sub-issues):</strong></p> <ol> <li><strong>Simplified Text (<a href="https://www.drupal.org/project/ai_initiative/issues/3549160" target="_blank">#3549160</a>):</strong> <ul> <li>Showcase: Reducing complex language to specific reading levels.</li> <li>AC: Explain the accessibility benefits and the use of AI for readability improvements.</li> </ul> </li> <li><strong>Advanced Drupal Skills (<a href="https://www.drupal.org/project/ai_initiative/issues/3549161" target="_blank">#3549161</a>):</strong> <ul> <li>Showcase: AI-assisted development (code generation, debugging, documentation lookup).</li> <li>AC: Highlight how this accelerates the developer experience (DX) and reduces syntax errors.</li> </ul> </li> <li><strong>AI Search (<a href="https://www.drupal.org/project/ai_initiative/issues/3549162" target="_blank">#3549162</a>):</strong> <ul> <li>Showcase: Natural language and contextual search results.</li> <li>AC: Compare the experience to traditional keyword search; explain the relevance of RAG/embeddings.</li> </ul> </li> <li><strong>Compliance (<a href="https://www.drupal.org/project/ai_initiative/issues/3549163" target="_blank">#3549163</a>):</strong> <ul> <li>Showcase: Automatic scanning for brand guidelines and accessibility standards.</li> <li>AC: Demonstrate the "flagging" workflow for non-compliant content and risk mitigation.</li> </ul> </li> <li><strong>Content Categorization (<a href="https://www.drupal.org/project/ai_initiative/issues/3549158" target="_blank">#3549158</a>):</strong> <ul> <li>Showcase: Automatic tagging and taxonomy suggestions based on body text.</li> <li>AC: Focus on editor efficiency and taxonomy consistency across large sites.</li> </ul> </li> <li><strong>CKEditor Integration (<a href="https://www.drupal.org/project/ai_initiative/issues/3549159" target="_blank">#3549159</a>):</strong> <ul> <li>Showcase: In-editor AI tools for summarization and tone adjustment.</li> <li>AC: Highlight the "stay in the flow" benefit for content creators without switching tabs.</li> </ul> </li> </ol> <h3 id="summary-target-date">Target date or deadline</h3> <p>As soon as possible.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Draft technical copy for each individual demo page.</li> <li>Record or collect short (1-2 min) "teaser" videos for each capability.</li> <li>Create sub-issues for each page to track content production and review.</li> <li>Update the main "Try Drupal AI" demos landing page to link to these new detailed pages.</li> </ul> <h3 id="summary-ai-usage">AI usage (if applicable)</h3> <p>[ ] 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> This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision.</p> <p>[ ] AI Generated Code<br> This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human.</p> <p>[ ] Vibe Coded<br> This code was generated by an AI and has only been functionally tested.</p> > Related issue: [Issue #3549161](https://www.drupal.org/node/3549161) > Related issue: [Issue #3549162](https://www.drupal.org/node/3549162) > Related issue: [Issue #3549163](https://www.drupal.org/node/3549163) > Related issue: [Issue #3549158](https://www.drupal.org/node/3549158) > Related issue: [Issue #3549159](https://www.drupal.org/node/3549159) > Related issue: [Issue #3549160](https://www.drupal.org/node/3549160)
issue