Open liquidvisual opened 10 years ago
Actually forget the above, it seems that Takana doesn't work at all in situations where you have a 'build' folder separate from the source directory.
In my situation, I'm running Jekyll 2.0.2 (not using Grunt) and editing my css files inside the ./css directory. Jekyll then compiles this and places it in:
./_site/css/example.css
When I fire up Takana, I point it at the project folder - but it doesn't work. I had limited success feeding it the '_site' (build) folder - but it only refreshed occasionally when I saved.
Are there any tricks to get this working? I'd really love to use Takana.
My workaround is to comment out the front matter, then move main.scss
form /css
to /_sass
and execute takana .
inside _sass
. When finished developing, move the file back and uncomment the front matter. Alternately, you can import the partials' full path like @import "../_sass/base"
.
With Jekyll's 2.0 release now supporting Sass, I'd love to get Takana running with it. At present, scss files in Jekyll need to have font matter at the top to get compiled, eg:
Normally the front matter is blank, so it's just the two sets of "---". Working with a file like this gets an "invalid top-level expression" error in Takana. Is there anyway this could simply be ignored, to work in Jekyll?