>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3365466. --> Reported by: [froboy](https://www.drupal.org/user/271282) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>As it has grown, <a href="https://www.drupal.org/community/events">https://www.drupal.org/community/events</a> has gone from a clean listing to a Frankenstein's monster of a page.</p> <p>As a visitor to /community/events<br> I want to be able to find certain types of events in area of my choosing (state/province, country, continent)<br> So that I can go to an event, learn, and be happy!</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>- Visit <a href="https://www.drupal.org/community/events">https://www.drupal.org/community/events</a><br> - Be confused</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Map changes:<br> - Map should use per-type icons and colors, similar to <a href="https://www.drupical.com/">https://www.drupical.com/</a><br> - Map should show all events that have locations set<br> - Map should use geo-data if available to center on the user's location, with a zoom at approximately the continent-level</p> <p>Listing changes:<br> - Remove existing type-based listing blocks (Upcoming Events, Upcoming Trainings, DrupalCons, Local Meetups, Contrib Events, Calls for Content, Proposed Events)<br> - Add a unified list view of all event types using a similar display to the existing lists with exposed filters for Event Type, Location (if possible with hierarchy (continent and country, or country and state/province)<br> - Listing should allow events (like DrupalCon) to be made sticky or called out otherwise<br> - Listing should have a way of flagging certain events with a pill or tag or other inline style:<br> - Cancelled items should show, but be greyed out<br> - Events with open Calls for Content should be flagged<br> - Events with "Proposed" status should have a "Tentative" flag</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>- Mock up changes<br> - Discuss<br> - Split out work into child tickets</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>Many</p> <h3 id="summary-api-changes">API changes</h3> <p>None</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None</p>