Skip to content
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

Implement e-mail subscription #45

Open
1 of 7 tasks
andrerpena opened this issue Jun 13, 2019 · 2 comments
Open
1 of 7 tasks

Implement e-mail subscription #45

andrerpena opened this issue Jun 13, 2019 · 2 comments
Labels
🌈 New feature New feature or request

Comments

@andrerpena
Copy link
Owner

andrerpena commented Jun 13, 2019

The goal is to have an e-mail subscription in such a way that whatever filter is applied to https://remoted.io can be transformed into an e-mail subscription. For example: It will be able to subscribe to only react jobs with salary, excluding US-only jobs.

  • Create the newsletter_subscription table and associated TypeScript type
  • Implement the email HTML generation
  • Implement the NewsletterSubscriptionService with functions to add and remove a subscription
  • Implement GraphQL mutations to add and remove subscription
  • Implement the HTTP endpoint to unsubscribe, including the UI
  • Add a form to remoted.io to subscribe
  • Implement the logic to actually send the e-mails through Amazon SES
@andrerpena andrerpena added the 🌈 New feature New feature or request label Jun 13, 2019
@andrerpena
Copy link
Owner Author

I'm currently trying to simply render the React component used for displaying jobs on remoted.io using Juice to inline all styles and images so that I don't have to maintain two codes. The e-mail would be exactly like the website:

image

@andrerpena
Copy link
Owner Author

That is not exactly easy. There are complications like: What CSS should I include? Should I include fonts? Is it possible to inline fonts? How to I embed company logo images?

Using https://github.com/niftylettuce/email-templates has the disadvantage that I have to implement the e-mail manually, as opposed to just "juice" the current job list but it has the advantage that I don't have to make everything that exists already to also work inside the e-mail context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌈 New feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant