My hypothesis is that SmokeSignal core is very close to having everything it needs for an “RSVP” focused product.
That is, no paid tickets, you need email to remind people and share private info.
For my usage, email integration is the final need. I setup a Listmonk instance and Forward Email and am going to do it manually but this is too complicated for simple regular usage.
Scoping this as minimal as possible:
On registration email:
backend field where the organizer can type in what to send on registration, default info is appended with a link to the event
Reminder email 24 hours before, one hour before:
second field with different text
Both are blank by default and just the basic info is sent.
I have thoughts on what people will ask for next but they should ask for it / I’ll write in the thread.
Have an IRL use-case for this soon where I’d love to be able to either collect e-mails for registered users, or at least send an e-mail blast to users subscribed to an event.
I should document the other half of the RSVP from the user perspective:
As part of event setup, the organizer can check a box that says “must include email to RSVP”.
When the user goes to RSVP, if the email is blank, it errors and says something like “The organizer requires an email to RSVP for this event in order to send you information on attending” or something like that.
Yes, people could still RSVP manually via their PDS.
I also also would love to support “don’t have an ATProto account, can I just put my email in” which I think this could support (including messaging about converting into a new ATProto account sign up “later”) … but that is most definitely not minimal scope
