You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we use Mailchimp for our marketing emails (transactional emails like workshop invites are sent via Sendgrid). This has become very expensive and we have found an alternative - Flodesk.
This task is to update the embedded newsletter sign up form as well as the API integration when people sign up for marketing emails to use Flodesk.
Screenshots 📷
Steps to fix 🛠
People can sign up to or manage marketing emails three ways on the websites:
Sign up form at the bottom of the homepage and chapter pages (Fig. 1)
During the account creation process they are prompted to sign up to the newsletter (Fig. 2)
They can manage their subscription on the /subscriptions page (Fig. 3)
We use the gibbon gem to integrate with the Mailchimp API. AFAIK Flodesk doesn't have a Ruby wrapper for their API so we'll have to write our own. We'll only really need to support two features:
Sign up to a general list via the account creation flow and on the /subscriptions page
Opt-out of the newsletter (unsubscribe from the general list) on the /subscriptions page
Flodesk does support embedded forms so the current Mailchimp for will be easy to replace on the bottom of the homepage and chapter pages.
Migration plan
TBD, we'll have to come up with a migration plan to ensure no outage while we switch over from Mailchimp to Flodesk. AKA go live plan.
To do 📋
Claim this issue (comment below, or assign yourself if you are part of the codebar org)
Fork and clone the repository
Update the relevant files. Follow the steps to fix section in this issue.
Commit your changes as one commit. Use the title of this issue as your commit message
Submit a pull request
Mention this issue in the PR description by including it's number
Have your pull request reviewed & merged by a codebar team member
The text was updated successfully, but these errors were encountered:
I’d be interested in looking into this. Comparing both, the concept of list doesn’t seem to exist on Flodesk, looks like the closest to that is segment. Wanna guide me a bit through MailChimp, @KimberleyCook?
@gnclmorais this is a high priority ticket for us so it would be awesome if you could look into it. I'd be happy to support you in any way you need as we really want to get this done as soon as possible. Flodesk does use the concept of segments instead of lists (I think Lists are now called Audiences in Mailchimp) but AFAIK functionally these are the same. Here's a high level guide from Flodesk on hoe to migrate from other providers: https://help.flodesk.com/en/articles/3305401-how-do-i-move-my-subscriber-list-from-my-old-provider-to-flodesk. In short we would have to export the codebar Newsletter audience, both the signup form on the homepage and the API endpoints subscribe members to this audience/list, and then update the signup form and the endpoints on our site to subscribe members to the appropriate segment in Flodesk. I'm also happy to jump on a call to explain to you what's what in Mailchimp, but perhaps @KimberleyCook is better placed to do that as she uses Mailchimp more.
Description of the issue 📄
Currently we use Mailchimp for our marketing emails (transactional emails like workshop invites are sent via Sendgrid). This has become very expensive and we have found an alternative - Flodesk.
This task is to update the embedded newsletter sign up form as well as the API integration when people sign up for marketing emails to use Flodesk.
Screenshots 📷
Steps to fix 🛠
People can sign up to or manage marketing emails three ways on the websites:
We use the gibbon gem to integrate with the Mailchimp API. AFAIK Flodesk doesn't have a Ruby wrapper for their API so we'll have to write our own. We'll only really need to support two features:
Flodesk does support embedded forms so the current Mailchimp for will be easy to replace on the bottom of the homepage and chapter pages.
Migration plan
TBD, we'll have to come up with a migration plan to ensure no outage while we switch over from Mailchimp to Flodesk. AKA go live plan.
To do 📋
The text was updated successfully, but these errors were encountered: