Adding email template that'll be used by the periodic catch up organizer script.
Details
I read this article before writing up this template email. Although that's for newsletter, our case is not very different and the suggestions are still useful.
Using HTML in your email can make it look nice, certainly. However, HTML emails are more likely to be flagged as spam by the receiving providers.
^ is the reason for going with plain email. It makes our lives easier as well needless to say.
I've surrounded the parts that we need to dynamically replace within curly braces ({}). No specific reason for choosing curly braces over other symbols. I was just looking for some delimiter and pretty much open to other suggestions there.
I've kept the subject line in the template for now but we can move that elsewhere depending on our implementation. For example, if we end up storing the template in db, email_body column/field can store the actual template and email_subject column/field can store the subject line.
kazi-nayeem
commented
3 years ago
Solves https://github.com/SakibulMowla/catch-up/issues/3.
Context
Adding email template that'll be used by the periodic catch up organizer script.
Details
I read this article before writing up this template email. Although that's for newsletter, our case is not very different and the suggestions are still useful.
^ is the reason for going with plain email. It makes our lives easier as well needless to say.
I've surrounded the parts that we need to dynamically replace within curly braces (
{}). No specific reason for choosing curly braces over other symbols. I was just looking for some delimiter and pretty much open to other suggestions there.I've kept the subject line in the template for now but we can move that elsewhere depending on our implementation. For example, if we end up storing the template in db, email_body column/field can store the actual template and email_subject column/field can store the subject line.