#Find coda 2 temporary files code

I've not started using grunt yet but looking to get it set up pretty soon.

grunt-screenshot-element - use for screenshotting.

grunt-htmlhint - detects syntax errors in html.

grunt-text-replace - use regex's to replace text content.

grunt-prompt - prompt for user input on command line.grunt-litmus - sends tests to Litmus, built by yours truly.grunt-contrib-clean - used to clean temporary files/folders.grunt-contrib-copy - copy files and directories.grunt-contrib-watch - watch files for changes.grunt-email-builder - use to inline css.Then, whenever I make changes to one of them and save, Grunt/Gulp kicks in and creates an 'email.html' file that has the production ready code. Specifically they watch for changes to a template.html file that I work out of as my development code. I work multiple emails a day so I needed a way to handle all of the monotonous tasks like validating, minifying, inlining, testing, and screenshotting and do all of them fast.Īll of the emails I work on are contained within one directory which Grunt/Gulp watches for changes. I have found Gulp to be a lot faster than Grunt for what I do. I'm moving away from Grunt and onto Gulp. Then every time I save it, Grunt creates a separate production ready file. That doesn't mean I won't look into it again in the future, but for now, I just work out of one document keeping the styles embedded in the. I was only using it to see if it would improve my workflow and concluded that it didn't for the type of emails I was building. I have used the LESS Grunt plugin, which is pretty similar to Sass, and it worked fine. I'm going to try to test it out in the next month or so, see if it has anything to offer. I downloaded the beta of Github's new Atom editor, too.

#Find coda 2 temporary files code

If I need to just trouble shoot a module of code or something, I sometimes use Codepen. I can get the same results using a number of tools in tandem with Sublime Text. It's cool, but still a bit buggy to actually use all of the time. I've been messing around with Brackets, which has a great live preview feature, allowing me to see changes to my email in Chrome as I code them. It's typically my go-to editor, but that could change in the future. When it comes to coding, I love Sublime Text. I know a lot of people start in Photoshop before moving into code, but I generally like working with the code first and using either Photoshop or, increasingly, Sketch for building out assets for a design. I actually wrote about this a while back on my personal site, so that gives a good overview of my thoughts on the subject.