bdkjones
commented
8 years ago The solution to this is coming. Hang in there.
On 4 Apr 2016, at 09:02, aaronstezycki notifications@github.com wrote:
If any of you have used Hammer for Mac, you'll know that a project has a /build folder for all files compiled by Hammer, and they keep folder structure consistent.
Whats the simplest way to achieve this (and keep folder structure consistent with source folders) within Codekit?
Currently (which doesn't seem to work), I have Set Output Folder to /build/ and this is relative to project root folder.
Project -->Web Folder ----> index.jade -->Styleguide Folder ---->index.jade
As is, all index files just go to /build/index.html. This is not the desired outcome. I want it to maintain folder structure and compile to /build/context-folder/index.html.
Seems pointless to set an output folder and all files just go to /build/.
Forgive me if I'm wrong, or I've set the settings incorrectly, but this isn't an obvious part of code kit to figure out.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/608
aaronstezycki
If any of you have used Hammer for Mac, you'll know that a project has a /build folder for all files compiled by Hammer, and they keep folder structure consistent.
Whats the simplest way to achieve this (and keep folder structure consistent with source folders) within Codekit?
Currently (which doesn't seem to work), I have Set Output Folder to /build/ and this is relative to project root folder.
Project -->Web Folder ----> index.jade -->Styleguide Folder ---->index.jade
As is, all index files just go to /build/index.html. This is not the desired outcome. I want it to maintain folder structure and compile to /build/context-folder/index.html.
Seems pointless to set an output folder and all files just go to /build/.
Forgive me if I'm wrong, or I've set the settings incorrectly, but this isn't an obvious part of code kit to figure out.
Edit: If I want to maintain folder structure, I have to manually edit every file and set an output path. ... Nope, just nope. I don't want to have to do this every time I create a new jade file.