top | item 7765279 Show HN: A Grunt workflow for designing and testing HTML emails 66 points| fonziguy | 12 years ago |github.com | reply 11 comments order hn newest [+] [-] funkiee|12 years ago|reply I really like the simplicity of the 'How it works' section and I will probably steal the concept for explaining parts of our build to new employees. [+] [-] jaegerpicker|12 years ago|reply Are you open to pull requests? I forked this and added a couple of things that I'd be happy to contribute back to: -- Less support -- added a Gemfile to bundle install the ruby requirements -- added an npm preinstall task to run bundle install I tested and it's working locally [+] [-] mrmch|12 years ago|reply This is pretty cool; we've put a lot of work into sendwithus to solve many of these same problems (inline css at send time, staging versions of templates, and multiple types of api keys).Kudos for having a README that actually makes sense. [+] [-] illicium|12 years ago|reply See also: grunt-email-boilerplate [1][1] https://github.com/dwightjack/grunt-email-boilerplate [+] [-] consta|12 years ago|reply +1 for the simplicity of the workflow. I got it running within a few minutes. [+] [-] SimeVidas|12 years ago|reply Hm, wanted to try this out but the Ruby dependency is discouraging -.- [+] [-] fonziguy|12 years ago|reply Using the premailer gem for inlining CSS. Agreed would be nice not to have that dependency. Played with other solutions but couldn't find one as good. [+] [-] brbcoding|12 years ago|reply Isn't Ruby a dependency for Sass in general? Don't think that's a function of this grunt task. load replies (1)
[+] [-] funkiee|12 years ago|reply I really like the simplicity of the 'How it works' section and I will probably steal the concept for explaining parts of our build to new employees.
[+] [-] jaegerpicker|12 years ago|reply Are you open to pull requests? I forked this and added a couple of things that I'd be happy to contribute back to: -- Less support -- added a Gemfile to bundle install the ruby requirements -- added an npm preinstall task to run bundle install I tested and it's working locally
[+] [-] mrmch|12 years ago|reply This is pretty cool; we've put a lot of work into sendwithus to solve many of these same problems (inline css at send time, staging versions of templates, and multiple types of api keys).Kudos for having a README that actually makes sense.
[+] [-] illicium|12 years ago|reply See also: grunt-email-boilerplate [1][1] https://github.com/dwightjack/grunt-email-boilerplate
[+] [-] consta|12 years ago|reply +1 for the simplicity of the workflow. I got it running within a few minutes.
[+] [-] SimeVidas|12 years ago|reply Hm, wanted to try this out but the Ruby dependency is discouraging -.- [+] [-] fonziguy|12 years ago|reply Using the premailer gem for inlining CSS. Agreed would be nice not to have that dependency. Played with other solutions but couldn't find one as good. [+] [-] brbcoding|12 years ago|reply Isn't Ruby a dependency for Sass in general? Don't think that's a function of this grunt task. load replies (1)
[+] [-] fonziguy|12 years ago|reply Using the premailer gem for inlining CSS. Agreed would be nice not to have that dependency. Played with other solutions but couldn't find one as good.
[+] [-] brbcoding|12 years ago|reply Isn't Ruby a dependency for Sass in general? Don't think that's a function of this grunt task. load replies (1)
[+] [-] funkiee|12 years ago|reply
[+] [-] jaegerpicker|12 years ago|reply
[+] [-] mrmch|12 years ago|reply
Kudos for having a README that actually makes sense.
[+] [-] illicium|12 years ago|reply
[1] https://github.com/dwightjack/grunt-email-boilerplate
[+] [-] consta|12 years ago|reply
[+] [-] SimeVidas|12 years ago|reply
[+] [-] fonziguy|12 years ago|reply
[+] [-] brbcoding|12 years ago|reply