1/10/2024 0 Comments Indented sass codekit![]() Make "plugins" an object with key-value pairs of plugin names matched with an object of options to use when running that plugin: If you need to pass options to plugins, restructure your config file. (It MUST be named exactly that and it MUST be in the root project folder.)Īdd the custom plugin you want to run to the list in the config file, like this:Īs long as the plugin is installed in your project, you don't need to supply a path. You can do that in CodeKit's UI as well.Ĭreate a file named in your project's root folder. This places the plugin and its dependencies in the node_modules folder within your project so that CodeKit can run it.įor projects that already have a package.json file, you might choose to simply install from that file. The most popular ones are built into CodeKit, but you can run any plugin with any configuration you want.įirst, open the Packages area, then search for and install the plugin you want: |-app.css // main.scss outputs all imported sass to this file |-app.js // all js files concatenated together |-/dist // all files compile to this directory |-main.scss // all sass is imported through this file |-main.js // custom js for theme goes here ![]() gitignore file.Ĭheck out this directory structure that I use based on the Roots Sage Starter Theme /your-custom-theme-folder You can also keep dependencies out of the git repo by adding bower_components to your. The advantage of using bower is you can update the packages from the command line and also through CodeKit. CodeKit should then put foundation, jquery, and other scripts and frameworks in a folder called bower_components because it uses bower to fetch the project's dependencies. You should make your CodeKit project only contain the folder for the theme you are developing. How do others setup their projects on CodeKit with WordPress and Foundation? I’m doing this locally so I can’t show you the link, but I guess I just feel like I’m setting this up entirely wrong. I also found that if I place my sass partials in a folder called partials, CodeKit can't compile them, even though I'm importing them with the folder name, example: partials/layout, instead of layout. It says the compiling is complete, but when I look at the code it’s just the import line without the foundation code actually being outputted. I want to include the foundation app.scss file so everything is in one place, but it doesn’t call it up. ![]() I have one master style.sass file where I import all my partials and that works correctly. Where I get hung up is in the compiling of the files. I know in the YouTube video CodeKit mentions not to pull the files out so that any linking isn’t messed up, but I can’t keep those files in the root of my project because they need to be within the theme.Īssets is also where my sass files live for the overall site I then throw in my WordPress files, and throw that ‘Foundation’ folder into the theme I’m working on in WP in my ‘assets’ folder. ![]() ![]() It outputs the files and I throw them into a folder called 'Foundation'. I’m building a WP project so I start by creating a new CodeKit project with Zurb and compass. I’m a new user to CodeKit and sass and I’ve been playing around with it for the past few days trying to figure out how to use it correctly to improve my workflow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |