Add next Drupal Events Block to the Dashboard
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3563854. --> Reported by: [grienauer](https://www.drupal.org/user/80801) Related to !725 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Drupal has a very active global and local community, but this is currently not visible inside Drupal CMS itself. New users and site builders have no built in way to discover upcoming Drupal events or connect with their local community from the dashboard.</p> <p>Other CMSs, most notably WordPress, have included an events widget in the admin dashboard for years. This has proven to be a strong onboarding and community signal.</p> <p>With Drupal CMS we aim to focusing on better first impressions and adoption, surfacing upcoming Drupal events directly in the dashboard would highlight the strength of the ecosystem and encourage community participation.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Install Drupal CMS</li> <li>Log in and open the dashboard.</li> <li>There is no block showing upcoming Drupal community events.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add the <a href="https://www.drupal.org/project/drupical/releases">Event Listing block</a> to the Drupal CMS dashboard.</p> <p>The block would show a small list of upcoming Drupal events with basic information. DrupalCons on the top and Drupal Camps below.<br> <strong>Screenshot</strong><br> <img src="https://www.drupal.org/files/project-images/drupal-events-block.png" width="100%" height="auto" alt="screenshot event listing block"><br> Most content and field decisions have already been discussed in Slack and in the issue queue, and several previously mentioned to-dos have been addressed.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>New block on the Dashboard.<br> Discussion with @hestenet, and his aim would be to show it either side by side with the project Announcements or below of it.<br> The block should be enabled by default and behave like other dashboard components.</p> <h3 id="summary-data-model-changes">Configuration changes</h3> <p>No new data model changes are required. The block consumes and caches the official API from d.o. events listings.</p> <h3>Next steps / open questions</h3> <ul> <li>Review the current state of the module for Drupal CMS readiness.</li> <li>Identify any remaining gaps or requirements for inclusion in Drupal CMS 2.0</li> <li>Clarify the acceptance process for adding it as a default dashboard block.</li> </ul> <p>Feedback on what is still missing and what the next concrete steps are would be very helpful.<br> <a href="https://www.drupal.org/project/issues/drupical">https://www.drupal.org/project/issues/drupical</a> -&gt; Component = Events Listing Block</p>
issue