What's your email stack and your use case for Mailing? #121
Replies: 3 comments 5 replies
-
Hey! If I'm understanding it right, the plan for the first bullet point is to use Storybook. That's what's we use for other projects and it works great. We can view and share components and flag diff in UI tests. |
Beta Was this translation helpful? Give feedback.
-
Currently we "render" mails in our c# backend, with some type of custom templating mechanism implemented. |
Beta Was this translation helpful? Give feedback.
-
I'm building a changelog newsletter powered by a CMS, and I want our emails to match the design: Do you guys have any suggestions on the best mail client? Something like mailchimp with good custom template support, which could possibly integrate well with our CMS? |
Beta Was this translation helpful? Give feedback.
-
Hey y'all. As we sequence the next set of features, it'd be great to know how you're using Mailing, and email in general, in your project. For example, this comment from @mrlubos was super informative. For context, here are a few things we have in mind:
Tagging a few people whose feedback has already been really helpful but whose stacks we haven't heard about – @alan-francis @tobdru @ccarollo @sebasalvarado. Thanks so much!!
Beta Was this translation helpful? Give feedback.
All reactions