Update TODO

Author: SableRaf

TODO.md

@@ -12,6 +12,7 @@
 - [x] Move the light/dark mode toggle to an easily accessible place in the UI, such as the top right corner of the map, instead of being hidden in the side panel.
 - [ ] Show activities in the event details (e.g. workshops, talks, etc.) if that information is provided by the event organizers.
 - [ ] Have the action add a comment on the issue when the data is not valid, with friendly human readable error messages to help the user fix the issue. For example, if the date format is invalid, it should say "The date format is invalid (found: `Wed 15th`). Please use `YYYY-MM-DD` format." or something similar. Make a list of all the possible validation errors and the corresponding error messages to show to the user. The comment should format the feedback in a clear and easy to understand way, and also include instructions on how to fix the errors. If multiple errors are found, list them all in the same comment in a clear and organized way (e.g. using bullet points or a table).
+- [ ] Add form submission using Decap CMS or similar, to allow organizers to submit their events without needing a Github account or going through the issue/PR process.
 - [ ] Fix the Review checklist to account for the new TBD date/time/location and online event features.
 - [ ] Add a "Submitted by" field to the event details, showing the github account url of the user who submitted the event. This can be automatically added in the workflow when a new PR is created for the event, by getting the github username from the issue that triggered the workflow and adding it to the event data.
 - [ ] 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 "Submit your event" 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.