Comments on: Automate the generation of your style guides with KSS-node

By: shoogledesigns

shoogledesigns — Thu, 05 Mar 2015 20:49:43 +0000

Hi Raul,
got to say I haven’t used kss nodes in ages…

By: Raúl Aguilar

Raúl Aguilar — Wed, 04 Mar 2015 05:32:13 +0000

Hi, very interesting, but, do you have any idea why when I use {$modifiers} doesn’t works?, when I compile with kss-node, it doesn’t replace the modifier for a class.

Thanks

By: Mark

Mark — Fri, 17 Oct 2014 13:44:04 +0000

This was really useful, thanks for such a simple walk-through!

One part I was having an issue with was the first step within ‘Customization’. kss-node –init resulted in a ‘TypeError’ … Turns out I just needed to pass in the destination directory of styleguide-template after –init and it worked a treat.

By: sribas

sribas — Thu, 07 Aug 2014 20:50:30 +0000

Hi,

Thanks for this tutorial
Followed it step by step. However, it doesn’t generate the navigation structure. The public/style.css is empty and I have nothing but the Overview.
Any suggestion?

Thanks very much.

By: Ogb

Ogb — Mon, 02 Jun 2014 11:32:52 +0000

Hello, I found this article very helpful. Surprised though that there are so few resources and most from almost a year ago.

I use Sass and found that mixin parameters are outputted on a single line as a paragraph.

Also, when adding Markup, how does one indicate what format it’s in, HTML, CSS, SCSS etc?

Thanks a lot. Again, this article was a great help. Now i’m off to battle with using kss-node with Grunt.

Cheers.

By: Hanna Kutcher

Hanna Kutcher — Sat, 12 Apr 2014 02:53:20 +0000

Hmmm. I’m only seeing curly braces in the index.html file even though “Generation completed successfully!” in the Terminal. I’m tried kss-node both .css and .scss files. Followed your example to the letter. I’m on Mavericks 10.9.2, Terminal, CodeKit, opening index.html in Safari and Firefox both locally and on a remote server. Would you mind pointing me in the right direction? What am I doing wrong?

By: shoogledesigns

shoogledesigns — Thu, 20 Mar 2014 12:54:12 +0000

Hi Iain,

Not tried with pictures defined by relative paths.
You could mimic the folder structure of the styleguide, but that’s not exactly what we’re looking for here.

Anybody’s got something on this?

By: Iain

Iain — Thu, 20 Mar 2014 12:16:50 +0000

Have you managed to get it working with CSS images defined by a relative path? By default, the paths to any CSS images come out wrong as the generated css file is nested one layer deep inside a public’ directory. Eg my less files are in the root, when I run kss-node, it creates a public folder in this root, and creates a styles.css file inside this. The relative paths in styles.css are therefore wrong. I’d love to hear if you solved this problem.

By: Birger Fühne

Birger Fühne — Thu, 13 Feb 2014 15:33:23 +0000

Thanks so much for your article, quite useful for my dev workflow.

I just stumbled upon a little problem following your instructions:

The comments in the css need to be done by line comments (//), or otherwise the processing of the sass files fails:

Not working:

/* Top level description of the feature
A description.*/

Working
//Top level description of the feature
//A description