support for events

[nicki182]

Contributor checklist

• [] This pull request is on a separate branch and not the main branch
• [] I have run the tests for the backend and frontend depending on what's needed for my changes as described in the testing section of the contributing guide

---

Description

Description of the proposed change...

Related issue

• Add support functionality and organizations/events to home page #849

[github-actions]

Thank you for the pull request! ❤️

The activist team will do our best to address your contribution as soon as we can. The following are some important points:

• Those interested in developing their skills and expanding their role in the community should read the mentorship and growth section of the contribution guide
• If you're not already a member of our public Matrix community, please consider joining!
  • We'd suggest that you use the Element client as well as Element X for a mobile app
  • Join the General and Development rooms once you're in
• Also consider attending our bi-weekly Saturday developer syncs!
  • Details are shared in the Development room on Matrix each Wednesday before the sync
  • It would be great to meet you 😊

Note

activist uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[netlify]

✅ Deploy Preview for activist-org ready!

Name	Link
🔨 Latest commit	6b08d36
🔍 Latest deploy log	https://app.netlify.com/projects/activist-org/deploys/6aa83082748c35000700127a
😎 Deploy Preview	https://deploy-preview-2400--activist-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• Tests for changes have been written and the TypeScript, pytest and formatting workflows within the PR checks do not indicate new errors in the files changed

• The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

• The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)