>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3567570. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <strong>Blocked by: </strong>[#XXXXXX] (New issues on new lines)<br> <strong>Additional Collaborators: </strong> @username1, @username2<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>This came out of a call with Kristen+Aidan+Emma.</p> <p>We need to create a demo to provide a concrete target for the MVP.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>We've discussed using FinDrop for this and need to clean up the context:</p> <ul> <li>Company and product info</li> <li>Brand guidelines</li> <li>Mercury Byte design system component usage</li> </ul> <p>We are looking to make these into templates that could be adopted.</p> <p>Once this is working as expected with CCC, we can tag 1.0 (MVP).</p> <p>Resources from Vienna:</p> <ul> <li><a href="https://github.com/FreelyGive/v2025demo/blob/main/Prompts_v4-(3%20Different%20Landing%20Pages).md">Prompts</a></li> <li><a href="https://github.com/FreelyGive/v2025demo/tree/main/custom_recipes/canvas_ai_setup/config">Context config</a></li> <li><a href="https://docs.google.com/document/d/1Ex24im9_xCTgd_1TZwjZCN97zHOG7fHWCR5JKI--Yrs/edit?tab=t.0#heading=h.vad2mug03smu">Context doc</a></li> </ul> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <p>March 2026</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Add child issues as needed</p> <h3 id="summary-ai-usage">AI usage</h3> <p>The code associated with this issue was developed using AI tools.</p> <p>A human worked with the AI tool to:</p> <ul> <li>Clarify the requirements</li> <li>Spec out the plan and architecture</li> <li>Create the code</li> </ul> <p>The human:</p> <ul> <li>Reviewed the code</li> <li>Manually tested the functionality</li> <li>Requested adjustments from AI</li> <li>Adjust the code themselves when necessary</li> </ul> <p>Issue credit is still relevant for humans working with AI as they are using AI as a tool and not to do everything for them. It requires human expertise and oversight to utilize AI effectively and efficiently in addressing these issues.</p>