-
-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add subscribe form to meetings and tsc page #1026
feat: add subscribe form to meetings and tsc page #1026
Conversation
✅ Deploy Preview for asyncapi-website ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-1026--asyncapi-website.netlify.app/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😍
So as I understand, when we send email about meetings it is still going to be:
recipients: {
list_id: '6e3e437abe',
segments_opts: {
saved_segment_id: 'meetings-email'
}
}
now, in case of TSC, we should send to:
recipients: {
list_id: '6e3e437abe',
segments_opts: {
saved_segment_id: 'tsc-voting-email'
}
}
so still the same list, just different segment. Right?
There is no GH issue on that. I just figured that we need it when you made changes in lists, as you noticed some people unsubscribed when we started sending "meetings updates". I never created an issue as anyway only you have rights to modify Mailchimp and Zapier that we already have in place.
When I want to update my Mailchimp preferences I see:
Can we change it to AsyncAPI?
Then, when I finally get a link, in update I see only
but I see meetings and tsc too, right?
Just to confirm, you wanna also extend https://github.com/asyncapi/community/blob/master/.github/workflows/notify-tsc-members-mention.yml to send email to Mailchimp, or you leave it to me?
Yes, if I understood Mailchimp API correctly, that's the case.
I'm not quite sure but that's something we can test after it's merged. If it doesn't work, I'd just have to tweak it on Mailchimp so no problem.
I'll leave it up to you. Maybe someone else can help? @KhudaDad414, you're familiar with Github Actions, maybe you can help? All feedback is addressed now @derberg. Please review it again. |
@@ -13,7 +13,7 @@ export default function NewsletterIndexPage() { | |||
</StickyNavbar> | |||
<div className="py-12 mt-12"> | |||
<Container wide> | |||
<NewsletterSubscribe formName="form 1" /> | |||
<NewsletterSubscribe /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fmvilas I am slightly concerned about why we are making the newsletter a separate route on the website. We aren't using this route anywhere in the website, not in the navbar or footer as well. We can simply have NewsletterSubscribe
as a component and can be used in various places as needed. So, can we remove this file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akshatnema this is meant to be referenced externally (emails, slides, etc.). It's a landing page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akshatnema it was there before, it is for tweets and other stuff that @fmvilas mentioned. So you do not send people to asyncapi.com and make them look for newsletter subscription component, but just send them to https://asyncapi.com/newsletter
@fmvilas regarding how it looks like in Mailchimp you can check with https://gmail.us12.list-manage.com/profile/send-email |
@fmvilas can you also check something in Mailchimp. Not sure how you, but I did not receive an email this week (Monday) about the meetings from this week but in CI I can see that campaign was created in mailchimp |
I don't get what you're talking about 🤔 Also, the link doesn't work for me.
I did receive the email 🤔 I wonder what failed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all is clear
I did not get email as I unsubscribed and then subscribed back, but it was when meeting subscription was not yet possible.
Thanks mate!!!
I created followup issue for TSC notifications -> https://github.com/asyncapi/community/issues/503
/rtm |
Oh yeah, I'm editing a Markdown file so I need approval from @alequetzalli :) |
It adds a subscription form to the
/community/meetings
page. I've configured (still on it while opening this PR) Mailchimp to tag users as "meetings-email" so we know exactly which of them should be receiving the weekly meetings email.Not sure there's a related issue. It's been a long-awaited feature by @derberg (along with the TSC members voting email, which will come next).
EDIT:
It also eliminates the need to pass a
formName
param to the NewsletterSubscribe component. We'll always use the same because Zapier/Netlify integration is done by form. This means we need to create a Zap per form and Zapier charges per Zap. Since we're not interested in which form was used, I'm always using the same form name, and the routing will happen based on thetype
field (e.g.,jobs
,meetings-email
, etc.). If notype
is provided, it will just be understood as you're subscribing to the newsletter, as usual.EDIT 2:
I'm also adding the TSC voting form on the
/community/tsc
page, so people can get notified when someone requests the TSC to vote.Check after merge