Create templates for management of AI Initiative Marketing Issues on Gitlab
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3581782. --> Reported by: [jjchinquist](https://www.drupal.org/user/286806) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>Issue Templates will help the AI Marketing initiative (e.g. Blog, Video, Webinar, Case Study).<br> <strong>Check-in Date: </strong>04/22/2026<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>All AI Initiative Issues specific to the <a href="https://www.drupal.org/project/issues/ai_initiative?text=&amp;status=Open&amp;priorities=All&amp;categories=All&amp;version=All&amp;component=Marketing">Marketing sub-group / component</a> have specific requirements. We need formal templates for tasks such as Blog entries, events, documentation, webinars, etc. </p> <p><strong>Changeover schedule: <a href="https://www.drupal.org/project/drupalorg/issues/3409678" target="_blank">Issue #3409678</a></strong>.</p> <h3 id="summary-resources">Resources</h3> <ul> <li><a href="https://www.drupal.org/drupalorg/blog/gitlab-issue-migration-the-new-workflow-for-migrated-projects">GitLab issue migration: the new workflow for migrated projects</a></li> <li><a href="https://www.drupal.org/drupalorg/blog/gitlab-issue-migration-how-to-use-the-new-workflow">GitLab issue migration: how to use the new workflow</a></li> <li><a href="https://www.thedroptimes.com/66057/drupalorg-introduces-new-gitlab-issue-workflow-migrated-projects">Drupal.org Introduces New GitLab Issue Workflow for Migrated Projects</a></li> </ul> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h4>Plan: GitLab Issue Templates for AI Initiative Marketing Component</h4> <h4>Context</h4> <p>The Drupal AI Initiative project (#3528462) is migrating issue management to GitLab (meta: <a href="https://www.drupal.org/project/ai_initiative/issues/3577731">#3577731</a>). The Marketing component needs formal issue templates for specific sub-topics. Issue <a href="https://www.drupal.org/project/ai_initiative/issues/3581782">#3581782</a> tracks this for Marketing specifically.</p> <p>We're creating GitLab issue templates (<i>.gitlab/issue_templates/</i>) to be contributed to the AI Initiative GitLab repo. Starting with <b>Blog</b> and <b>Video</b> templates, with Flyer and Webinar to follow later.</p> <h4>What We're Producing</h4> <p>Two GitLab issue template files:</p> <ol> <li><i>Marketing - Blog Entry.md</i></li> <li><i>Marketing - Video.md</i></li> </ol> <p>These follow GitLab issue template conventions: markdown files in <i>.gitlab/issue_templates/</i> with optional YAML frontmatter for default labels.</p> <h4>Template Structure</h4> <p>Each template will include these sections in order:</p> <h4>1. [Tracker] metadata block</h4> <p>Matching the format from #3581782 / drupalstarforge.ai:</p> <p>[Tracker]<br> <b>Update Summary:</b> [One-line status update for stakeholders]<br> <b>Check-in Date:</b> MM/DD/YYYY<br> <b>Additional Collaborators:</b><br> [/Tracker]</p> <h4>2. Metadata table (sub-topic-specific)</h4> <p>Based on the blog article guidelines, each template gets a metadata table at the top. Fields vary by sub-topic.</p> <p><b>Blog Entry metadata:</b></p> <ul> <li><b>Author:</b> [Name, email]</li> <li><b>Reviewers:</b> [Names]</li> <li><b>Final approvers:</b> [Names]</li> <li><b>Topic:</b> [Main focus of the article]</li> <li><b>Objective:</b> [What the piece should achieve]</li> <li><b>Target audience:</b> [Who it's for]</li> <li><b>Source material:</b> [link]</li> <li><b>Images:</b> [link]</li> <li><b>Summary for LinkedIn:</b> [todo]</li> </ul> <p><b>Video metadata</b> <i>(adapted for video content)</i>:</p> <ul> <li><b>Producer:</b> [Name, email]</li> <li><b>Reviewers:</b> [Names]</li> <li><b>Final approvers:</b> [Names]</li> <li><b>Topic:</b> [Main focus of the video]</li> <li><b>Objective:</b> [What the piece should achieve]</li> <li><b>Target audience:</b> [Who it's for]</li> <li><b>Type:</b> [demo / tutorial / testimonial / promo / explainer]</li> <li><b>Duration target:</b> [e.g. 30s, 1-2 min, 5 min]</li> <li><b>Platform(s):</b> [YouTube / social / drupal.org / conference]</li> <li><b>Source material:</b> [link]</li> <li><b>Assets needed:</b> [footage, graphics, music, b-roll]</li> <li><b>Summary for LinkedIn:</b> [todo]</li> <li><b>Video file metadata:</b> [title, description, copyright, author(s)]</li> </ul> <h4>3. Prerequisite reading (shared)</h4> <p>Reference links that authors should review before starting:</p> <ol> <li>Drupal AI Marketing Strategy 1.0 (+ Core Messaging)</li> <li>Drupal Brand Guidelines</li> <li>Logo and Wordmark Usage Guidelines</li> </ol> <h4>4. Content sections (sub-topic-specific)</h4> <p><b>Blog Entry:</b></p> <ul> <li>Content (Plan &amp; Approach) &mdash; outline/structure of the blog</li> <li>Content (The text) &mdash; the actual draft</li> </ul> <p><b>Video:</b></p> <ul> <li>Script / Storyboard &mdash; outline of the video</li> <li>Production Notes &mdash; recording, editing, assets</li> </ul> <h4>5. Remaining Tasks (checklist)</h4> <p><b>Blog Entry:</b></p> <ul> <li>[ ] Draft written</li> <li>[ ] Reviewed by reviewers</li> <li>[ ] SEO check</li> <li>[ ] Images/assets ready</li> <li>[ ] LinkedIn summary written</li> <li>[ ] Published</li> <li>[ ] Promoted on social channels</li> </ul> <p><b>Video:</b></p> <ul> <li>[ ] Script/storyboard written</li> <li>[ ] Reviewed by reviewers</li> <li>[ ] Assets gathered (footage, graphics, music)</li> <li>[ ] Recorded</li> <li>[ ] Edited</li> <li>[ ] LinkedIn summary written</li> <li>[ ] Published</li> <li>[ ] Promoted on social channels</li> </ul> <h4>6. AI Usage disclosure (shared)</h4> <ul> <li>[ ] AI Assisted Issue</li> <li>[ ] AI Assisted Code</li> <li>[ ] AI Generated Code</li> </ul> <h4>Output Location</h4> <p>Create files locally in <i>/tmp/ai-initiative-templates/.gitlab/issue_templates/</i> ready to be contributed to the AI Initiative GitLab repo.</p> <h4>Verification</h4> <ul> <li>Review templates for completeness and consistency</li> <li>Ensure [Tracker] block matches the format used by drupalstarforge.ai</li> <li>Ensure metadata table fields are appropriate for each sub-topic</li> <li>Confirm templates render correctly as markdown</li> </ul> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <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>[x] 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> > Related issue: [Issue #3571912](https://www.drupal.org/node/3571912) > Related issue: [Issue #3577731](https://www.drupal.org/node/3577731) > Related issue: [Issue #3409678](https://www.drupal.org/node/3409678)
issue