Newsletter/TemplateId
I moved my thread from Feature-suggestions to questions
https://github.com/wasp-lang/wasp/issues/1553
Hey has this been solved or will this just be closed as not possible? I was trying to use templateId, I guess I could just make a html but would be cooler if I could use templateId from SendGrid.
I solved this by using
Also about creating a newsletter, I still think this would be cleaner if I did this via sendgrid or hubspot or?
Is there any guidelines/best practices about how you all do newsletters?
https://github.com/wasp-lang/wasp/issues/1553
Hey has this been solved or will this just be closed as not possible? I was trying to use templateId, I guess I could just make a html but would be cooler if I could use templateId from SendGrid.
I solved this by using
export const registerTemplate = "my html file" and made my html template through sendgrid.
import { registerTemplate } from './templates/register-template';
export const getVerificationEmailContent: GetVerificationEmailContentFn = ({ verificationLink }) => {
const html = registerTemplate.replace('{{verificationLink}}', verificationLink);
return {
subject: 'Welcome to myappname!',
html,
text: Please verify your email by clicking this link: ${verificationLink}
};
Also about creating a newsletter, I still think this would be cleaner if I did this via sendgrid or hubspot or?
Is there any guidelines/best practices about how you all do newsletters?
GitHub![[Email sender] Allow specifying provider specific options, like tem...](https://images-ext-1.discordapp.net/external/td73yqFHyDnEuQkaLudkXBIWqs6uVGHnApuxZlvqU8s/https/opengraph.githubassets.com/4af86e19005c2f6cdbf6a541223e4e49013140273ed1dfadae3ba6dc6a933c6b/wasp-lang/wasp/issues/1553)
Right now, when defining an email sender, and when sending an email via it, we don't allow any provider-specific options. It would be useful to provide some, because for example, users using Se...
