-
Notifications
You must be signed in to change notification settings - Fork 1
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: introduce newsletter opt in to form #13
base: main
Are you sure you want to change the base?
feat: introduce newsletter opt in to form #13
Conversation
There are a few changes wrapped up in here. * Remove CTA from Intro text to form which is on the same page when viewed on homepage. This link is broken when same text is used on About page. * Rename links.html => form-join.html to better communicate purpose * Introduce newsletter checkbox (off by default)
✅ Deploy Preview for twc-site-nl ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I'll have a look see in a day or so about the email checkbox for sign up. Its currently driven by zapier for the newsletter sign up, and I dont believe its validating this field (even if previously used). Part of me wonders what the point is of signing up, but rejecting newsletters though. E.g. just for access to the slack, but then nothing else? |
Yeah I thought that this form change would require some e2e verification with the backend service.
I think wanting access to Slack but opting out of email updates is a reasonable use case, but primarily it ensures folks are explicitly giving consent to receive emails from us. This could also be done be including some text like, "By joining you agree to receiving our low frequency email updates. You can opt out of these at any point in the future." |
Indeed. Personal pref is the latter option. We haven't sent an email yet, and I think we'd not want to bug people (e.g. responsible updates). There is essentially nothing we can do for people without being able to contact them, so I think the default should be opt in with a clear text as you've said. I think its worth posting to the slack to get consensus. Can you do that? |
There are a few changes wrapped up in here.
viewed on homepage. This link is broken when same text is used on
About page.
Screengrab, showing new checkbox component based on existing form pattern of label / newline / input