owzim Posted April 17, 2013 Posted April 17, 2013 I just switched form CodeKit to Guard. I have more control over how things work, it’s cross platform and more team friendly, and it's free. Might be worth a look for you guys as well: "Guard is a command line tool to easily handle events on file system modifications." https://github.com/guard/guard Here's a nice intro by Jeffrey Way on Nettuts+ http://net.tutsplus.com/tutorials/tools-and-tips/guard-is-your-best-friend/ Cheers 3
adamspruijt Posted April 17, 2013 Posted April 17, 2013 Thanks owzim, never heard of this. As a big fan of CodeKit I am certainly curious about this now seeing as you made the switch (Cross platform is a big plus for me).
MatthewSchenker Posted April 17, 2013 Posted April 17, 2013 Hello, I'll take a look at this. For some reason, I have never really been able to get into SASS or LESS, and I tend to keep building CSS as CSS. But I always feel I am missing something, as everyone else seems to be using a pre-processor. Maybe something like Guard will motivate me? I suppose if I wait long enough, at least some of the pre-processor actions will become part of the CSS spec! Thanks, Matthew 1
onjegolders Posted April 17, 2013 Posted April 17, 2013 Same here Matthew and I actually have Codekit!
owzim Posted April 17, 2013 Author Posted April 17, 2013 Keep in mind that Guard is a command line tool, so if you haven't yet tried js/css preprocessors this might be overkill. CodeKit is great for getting started with that the easy way. And for Windows there is at least Scout (http://mhs.github.io/scout-app/) for Sass/Compass.
owzim Posted April 17, 2013 Author Posted April 17, 2013 *grunts* Grunt.js seems too complicated for me, haven't got the hang of it yet. Though, it might be very powerful. I'll for now stick with Guard and might check out Grunt in a month or two =) And Grunt.js is not preprocessing, right? It's a build tool, so how would you use Grunt for compiling Sass, Less and CoffeeScript while developing?
Soma Posted April 17, 2013 Posted April 17, 2013 Grunt.js seems to complicated for me, haven't got the hang of it yet. Though, it might be very powerful. I'll for now stick with Guard and might check out Grunt in a month or two =) And Grunt.js is not preprocessing, right? It's a build tool, so how would you use Grunt for compiling Sass, Less and CoffeeScript while developing? There you go http://gruntjs.com/plugins
yellowled Posted April 17, 2013 Posted April 17, 2013 And Grunt.js is not preprocessing, right? It's a build tool, so how would you use Grunt for compiling Sass, Less and CoffeeScript while developing? You would have Sass (and/or Compass or whatever you prefer) installed and let your Grunt build script's watch task run it for you in the background. For me that's just it: Grunt can do so much more than just run a preprocessor. Yes, it needs some time to get into and get the hang of it, but once you've set up your Grunt tasks, it does practically everything but write code. And I'm sure the Grunt guys are going to figure that out as well one day. 1
owzim Posted April 18, 2013 Author Posted April 18, 2013 Had closer look at grunt yesterday, might even be a better solution for my needs, and the community seems more vivid, development more rapid. Let's see ...
owzim Posted May 8, 2013 Author Posted May 8, 2013 *grunts* Finally grunt-contrib-watch implemented livereload natively so that it can be used without any hassle. Tried previous solutions with the grunt-contrib-livereload in conjunction with regard and connect but could not make it work. Now it works like a charm. http://stackoverflow.com/questions/16371022/how-to-use-grunt-contrib-livereload So yet again, workflow replaced, Guard is yesterday =D 1
bfncs Posted May 12, 2013 Posted May 12, 2013 I think grunt is close to the most interesting thing happening around the organization of frontend projects. While it is certainly great that it can do the dirty and boring work for you, it also really looks like us web developers finally have an open, stable and really flexible way of sharing our process. I have the feeling that with all the projects on Github that use it now, grunt had really come to stay, so it's definitely worth a look for everyone working with the web stack. 1
arjen Posted February 25, 2015 Posted February 25, 2015 I'm looking into Grunt and I was wondering if you guys mind sharing your directory setup. Do you use Grunt in the /site/templates/, in the root or do you have another setup? Thanks!
Adam Kiss Posted February 25, 2015 Posted February 25, 2015 I use Gulp, but the difference is just in syntax; You can see my assets directory here: https://github.com/adamkiss/StarterKit/tree/master/Assets I use it this way (Gulp-ing from /Assets/src) so I can ignore whole source directory when deploying and git/rsync/git-ftp only the distilled directory. 1
arjen Posted February 25, 2015 Posted February 25, 2015 Thanks Adam. Interesting approach. Gonna go with Gulp too after hours of research and fiddling with both. Seems lighter, faster and friendlier than Grunt.
Recommended Posts