Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different template engines #25

Closed
yuri-karadzhov opened this issue Feb 4, 2013 · 3 comments
Closed

Different template engines #25

yuri-karadzhov opened this issue Feb 4, 2013 · 3 comments

Comments

@yuri-karadzhov
Copy link

It will be useful to add ability to use different template engines (jade, ect and so on).

@capynet
Copy link

capynet commented Mar 21, 2013

+1, I'm using handlebars :D

@niftylettuce
Copy link
Collaborator

@yuri-karadzhov @capy you can change how you use EJS, e.g. the opening/closing tags:

emailTemplates(templatesDir, { open: '{{', close: '}}' }, function(err, template) {

The reason we don't use jade or something else (other than EJS) is because (e.g. jade for example) gives us a hard time when writing plaintext email templates.

Another contributor was working on adding swig. If any of you would like to contribute some sort of template modularization that'd be great :) Closing for now.

@yuri-karadzhov
Copy link
Author

We use ect - it's fast light and use coffe-script syntaxis. It is really convinient as we write coffe-script code. We will probably write an ect realization if we have some time, but it is better to have ability to add any render engine (and then if they do not work like jade - try to make workaround)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants