Foundation-emails: [question] How to handle all email templates in a big company in different languages and different email management services?

Created on 25 Feb 2016 · 6Comments · Source: foundation/foundation-emails

We have approximately 100 templates.
Of course many of them are not really necessary if we would use partials, but this is the step we want to go now. And foundation-emails, especially the new version looks awesome for this use case!

There are some other parts which I want to ask for best practice:
Imagine your company have at least 3 departments: marketing, customer support, sales.
Each of the department uses another email management service, for instance: MailChimp, Zendesk, etc.
And each of the services provides its own email template managing mechanism.
Does it make sense to handle all the email templates at a central place?

Another question: the content of the emails can be splitted into 2 groups:

recipient related content (customer for instance)
langauge related content

The recipient related content (name, email, interests) is stored at the email management service in most cases, that's okay.
But the language stuff is not and there is also no support to provide multi language templates at all at the services. So they need to be stored somewhere else, maybe the same central place as I asked above?

question

Source

timaschew

Most helpful comment

Thanks for reply.
I didn't want to modify the library itself and came with a simpler solution for my case (not as elegant as yours !): https://gist.github.com/lbineau/823c40e85e0ec2604895df8cc81bbd1f
I added a setlang and i18n helper for mustache.
Then you can launch npm run start --lang=cn, it will create a dist/cn folder with you email translated

lbineau on 19 Aug 2016

👍2

All 6 comments

That's a lot of templates!

You may be best off managing the templates in a single project on GitHub. Each department can have it's headers and footers that they'd re-use in HTML partials.

How are you language templates generated. If they are static translated version, then you can make each language a separate partial as well then just include the language you need.

Does that make sense/help?

rafibomb on 1 Mar 2016

Yes that sounds good, I already started with an own GitHub repo and panini and add i18n into it. It works very well! I'm now working on a preview feature. I will show you when it's done.

timaschew on 2 Mar 2016

Awesome!

rafibomb on 3 Mar 2016

@timaschew Do you have a sample of i18n implementation ? I have also emailing for multiple languages to produce.

lbineau on 16 Aug 2016

I hope this helps
https://gist.github.com/timaschew/a8f4c6bcf5af3f53bd65cd22e9aaa931

timaschew on 19 Aug 2016