Skip to content
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.

Using CodeKit (mac) vs Grunt/Bower, etc... #7

Closed
wlanni opened this issue Mar 2, 2014 · 1 comment
Closed

Using CodeKit (mac) vs Grunt/Bower, etc... #7

wlanni opened this issue Mar 2, 2014 · 1 comment

Comments

@wlanni
Copy link
Contributor

wlanni commented Mar 2, 2014

Hey there,

After running into headache after headache getting my mac to install Node.js, etc, I'm back to just wanting to use good 'ol CodeKit to compile my SCSS and js.

However, your documentation encourages using grunt, bower, etc. Considering I can't get the *%(@ stuff to install, I have no idea what it does or what it's for. Do I need this? Or can I just write my own SCSS, JS, and let CodeKit compile them into the CSS and JS I need? Will it hurt anything as far as dev with FoundationPress? Or inhibit upgrades in the future?

@olefredrik
Copy link
Owner

The sass compiler (libsass) and everything you'll need is set up in Gruntfile.js, located in the root folder of the theme. Just make sure you run 'npm install && bower install' (in your FoundationPress theme folder) after cloning the repo, and you should be all set.

Each time you run the 'grunt watch' (or simply just 'grunt') command, the sass compiler will run and watch for changes in your sass folder. Each time you make a change to a sass file, the output will be reflected in a compressed app.css file.

There are several types of sass compilers around. I see no reason why you should not be able to use CodeKit, if that is your preferred tool. Just make sure you include all the neccesary files (scss and js) and specify the correct output destination.

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

No branches or pull requests

2 participants