Outreach / messaging / community engagement features tracking issue

[joepio]

I'd like to explore what it would take for Atomic-Server to be usable as a back-end for a community platform.
That would be one possible USP that Atomic-Server might be able to excel at and have an advantage over other headless CMS tools.
At this moment, I don't think it's likely that Atomic-Server will get many community features, as it will probably be a really big investment, so keep that in mind.
This is just a list to keep track of the features that will be required for this type of app.

• Email support E-mail support #276
  • Write and design e-mail, send to some group (i.e. mailchimp, but more basic)
• Groups Refactor grants / rights - don't use a ResourceArray #476
• Table to view / edit users Table feature #538
• Group chat ChatRoom plugin #373
• Commenting. We don't really have commenting, but we have group chats, though. Perhaps that is enough when paired with email + browser notifications for emails.
• Control over commenting per item. Mods should be able to turn on / off comments somewhere.
• Private messaging. Might be the same as group chats, but a group for just two people. Needs UI + UX though.
• Analytics for engagement (views, comments, trends). Quite a big one.
• Reporting items to mods, so some sort of mod queue.
• Basic CMS features (article creation / editing, menu structure)
• Browser notifications Notifications, subscriptions and feeds #77
• Inbox page. Lists all incoming notifications, messages.
• Surveys (custom form with fields, anonymous entry)
• Spam prevention (like captcha, or post-gpt5 impossible captcha)
• Trashing / hiding items without deleting them
• Drafts / publishing Workflow for drafts / publishing / archiving (the Status attribute) #467
• Polls / voting