>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3532169. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>We have to keep the specifics private before the Driesnote to ensure the surprise/wow factor, but we can still do some planning here :)</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Refine the list below and then do full planning/tracking in a private spreadsheet</p> <p>Credit can be given to people on this issue</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Figure out all the things we need to do for the Driesnote and work with the marketing team to create polished results, e.g.</p> <p>First, we need to figure out:</p> <ul> <li>What story/stories do we want to tell (get buy-in from Dries and the CMS/XB teams)</li> <li>What video or videos will help support these stories</li> <li>Who's involved in building these videos, so they are very polished</li> <li>What features/tech/dev needs to be done before we can create these videos</li> <li>What are the estimates and timeline for building everything out</li> </ul> <p>Then, we need to:</p> <ul> <li>Create issues with deadlines and assign owners while still keeping details private</li> <li>Track issue status for needed features</li> <li>Have regular private meetings and/or space for people to report on status and blockers</li> <li>Build the assets as features become available and review with Dries and teams</li> <li>Refine assets as needed</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>