Add new features and improvements to event management in the map view

Author: SableRaf

TODO.md

@@ -1,4 +1,14 @@
-- [ ] Add "create event" button to Map view (link to forum thread?)
-- [ ] Fix hover color for links in dark mode (currently very hard to see)
+- [x] Add a maintainer for each event who is responsible for keeping the map data up to date
+- [x] Fix hover color for links in dark mode (currently very hard to see)
+- [x] Side panel should be closeable also when scrolled. Currently the close button is only visible when the user is scrolled all the way to the top of the panel, which is not ideal. Use a side tab on the edge of the panel with a chevron icon that is always visible to open/close the panel. Only show it after the user has selected an event and the panel is open, and hide it again when the panel is closed. Use a close button when in mobile view (full width panel) though, since the side tab could not be seen. Then the close button should be a "Back to map" button instead of just an "X", to make it more clear what it does.
+- [x] Add a floating "Want to host a PCD?" hero button to Map view top-middle (link to forum thread: https://discourse.processing.org/t/pcd-worldwide-2026/48081)
+- [ ] Add github issue template to submit a new event, to make it easier for maintainers to add new events to the map. The template should include all the necessary fields and instructions on how to fill them out, and also ask for the name and contact information of the maintainer who will be responsible for keeping the event data up to date. Link to this template in the "Want to host a PCD?" hero button. Add a workflow to automatically create a new branch and pull request when a new issue is created with the "New Event" template. It should also automatically add the "Needs Review" label to the issue and assign it to the PCD team. In the pull request description, include a checklist for the maintainers to review the event data and merge the PR if everything looks good. The workflow should add the new event to the nodes.json file and also create a new markdown file for the event details page with the provided information (we should migrate from long_description to getting the data from the markdown file). It should also automatically close the issue once the PR is merged (`closes #issue_number` in the PR description). Also handle malformed data (e.g. missing fields, invalid date format, etc.) by adding a validation step in the workflow and commenting on the issue with friendly human readable errors if the data is not valid.
+- [ ] Support for TBD location (e.g. for events that are confirmed but the location is not yet known). Add a "Location TBD" to the event details instead of the address. For TBD location, replace the minimap with a placeholder (a map to the center of the city if provided or a fun location) a note that the location is not yet confirmed and will be added once it's known.
+- [ ] Support for TBD date (e.g. for events that are confirmed but the date is not yet known). Add a "Date TBD" to the event details instead of the date.
+- [ ] Support for TBD time (e.g. for events that are confirmed but the time is not yet known). Add a "Time TBD" to the event details instead of the time.
+- [ ] Support online events. For online events, do not show the minimap. Show a link to the event online platform (zoom webinar, or similar, provided by the event organizer) instead of the address. Add an "Online Event" label to the event details. Have a different icon for online events on the map (e.g. a wifi signal icon instead of the location pin).
+- [ ] Add link to discussion for events that have a forum thread and are not confirmed yet
+- [ ] Support linking to specific events on the map (e.g. via URL query parameter) and use this for the share button in the event details
 - [ ] Fix popup color background in dark mode (currently too close to the sea color, making it hard to visually separate from the map)
-- [ ] Add link to discussion for events that have a forum thread and are not confirmed yet
+- [ ] Support for draft events. Shown on the map but with a different color and a "Draft" label. Change "confirmed" to "status" with values "confirmed", "draft", "cancelled", etc. and add a field for whether the event is visible on the map or not (for cancelled events we might want to keep them in the database but hide them from the map, while for drafts we want to show them but with a different color and a "Draft" label).
+- [ ] Fractional zoom levels cause gaps in the map tiles on Chromium. (this is a known issue with Leaflet, see: https://github.com/Leaflet/Leaflet/issues/3575)