07:00 <guardian> p/

07:00 <guardian> o/

07:43 <guardian> are you using nanoc + kramdown? the following item doesn't produce a code block here: http://pastebin.com/ED6kyTr5

07:44 <guardian> can you please try to reproduce on your side? For now I'm not sure what to blame: nanoc, kramdown, or my Rules+helpers combo

08:13 <_mw_> I would like to have page specific styles written in scss for every article I publish, any thoughts on how this could be done with nanoc?

08:49 <guardian> ymmv

08:50 <guardian> for item /foo/ you could have an scss item /css/_foo/ (which corresponds to content/css/_foo.scss)

08:50 <guardian> and you would route css partials to /dev/null by returning nil in route '/css/_*/'

08:51 <guardian> and then in your layout, when layouting /foo/ you can look for /css/_foo/ and if it exists inject compiled content as inline css

08:51 <guardian> that's an option

12:08 <guardian> o/

16:32 <jugglinmike> Can nanoc's dependency tracker tell when my build depends on an environmental variable? If not, is there a way I can explicitly tell it about that?

20:06 <bobthecow> jugglinmike: inject them into the site config during preprocessing and it'll recompile when it changes.

20:06 <bobthecow> ddfreyne: confirm that?

20:06 <jugglinmike> ah, interesting

20:06 <jugglinmike> since it probably does a deep compare with the config data structure on recompile

20:07 <bobthecow> in 4.x it'll be better, since your config will be .rb instead of .yaml

21:00 <guardian> o/

21:00 <guardian> ddfreyne: did you think about my question?