![]() ![]() 2 would be the ideal solution for my use case.This solution is the closest to my existing process. It would essentially abstract 1 which would be great. If I am using a library, I am looking to reduce the code I have to maintain myself and this feels like an essential feature that should be abstracted. 3 is an overkill for my use case so I didn’t analyse it further.4 would allow me to accomplish my task, but it would be a step back in all senses.I’ve had instances in the past when a template was breaking and I had to inspect the rendered HTML and go through iterations to figure out what’s wrong. This would shorten that feedback loop, and ideally allow me to modify the rendered HTML in browser so I can play with the output. Please let me know how likely you’re to add 2 to mailing, otherwise I may go with 1. You’re right, static props will work for me. Due to the integration with SendGrid, I use the handlebars templating language to inject variables into templates. None of the features you list would break this workflow. It started as a single template, copy-paste one more, and one more, you know how it goes. At this point I would definitely benefit from some automation but it’s not clear what benefits this would give me. I rarely need to update multiple templates and making one-off changes is fast and straightforward with the current approach. I am currently considering moving templates into the server code, curious if you have any thoughts on that. The challenge is that our server is written in Python, so the communication with templates would have to happen through HTML files. This is fine, but it means I will definitely need the ability to output HTML. In addition to that, I need an automated way to update templates inside the server code. One of my ideas at the moment is outputting the HTML files into the server project and update handlers with new variables as needed. Ideally, my templates would be consumed as a package so I always know which version I’m running, but I am not sure how to achieve that. I also want to avoid creating a complex setup just to gain this single benefit, so it would have to be reasonably simple to Sure. I have an existing project where I created my own “ mailing” package and used it to develop email templates. Our email infrastructure definitely needs some love, but it is what it is, so… we have a client written in TypeScript (CRA boilerplate), server written in Python (FastAPI), and emails hosted in SendGrid. ![]()
0 Comments
Leave a Reply. |