This is a NodeJS implementation of Knyle Style Sheets (KSS), "a documentation syntax for CSS". Beyond that, it's intended to have syntax readable by humans and machines - hence, this module can be used to create a "living styleguide". The methodology and ideas behind Knyle Style Sheets are contained in the specification.
There's an example project in the demo directory of this repo.
Just one line: npm install kss. If you want to use the command line interface, make sure the installation is global: npm install -g kss
To get you up and running quickly, a styleguide generator is included that can be used from the command line. It parses a directory of stylesheets and spits out a set of static HTML files like the ones used on this site.
Usage: kss-node <sourcedir> <destdir> [options]
<destdir> defaults to "styleguide" if not specified.
Options:
-i, --init Create a new styleguide template to work from
-t, --template Use a custom template to build your styleguide
-m, --mask Use a custom mask for detecting stylesheets in the source directory, e.g. "*.css"
-c, --css Include a CSS stylesheet
-s, --style Compile and include a stylesheet - the precompiler is chosen based on file extension
-l, --less Compile and include a LESS stylesheet
-S, --sass Compile and include a SASS stylesheet
-y, --stylus Compile and include a Stylus stylesheet
-L, --load-path Include a load path for precompiler imports
You'll need to specify a directory containing all of your stylesheet files to be parsed for documentation as the first argument. Optionally, the second argument can be used to specify a target directory. Your CSS won't be included by default, hence you should use the --less, --css, etc. flags to point to a stylesheet to compile and include. You can generate a copy of the demo styleguide like so:
$ kss-node demo styleguide --less demo/styles.less
You can create your own templates too. Use the node-kss --init command to initialize a copy of the default template so you can edit it and use it when generating your styleguide with the --template flag. This option is best when you need to compile your stylesheets with a preprocessor workflow not supported by kss-node; simply link the generated CSS from inside the custom template's index.html.
$ kss-node --init custom-template
$ kss-node ../path/to/sass styleguide --template custom-template
The default template should look something like this:
Check out the Module API a full explanation. Here's an example:
var kss = require('kss'),
options = {
markdown: false
};
kss.traverse('public/stylesheets/', options, function(err, styleguide) {
if (err) throw err;
styleguide.section('2.1.1') // <KssSection>
styleguide.section('2.1.1').description() // A button suitable for giving stars to someone
styleguide.section('2.1.1').modifiers(0) // <KssModifier>
styleguide.section('2.1.1').modifiers(0).name // ':hover'
styleguide.section('2.1.1').modifiers(0).description // 'Subtle hover highlight'
styleguide.section('2.1.1').modifiers(':hover').description() // 'Subtle hover highlight'
styleguide.section('2.1.1').modifiers(0).className() // 'pseudo-class-hover'
styleguide.section('2.x.x') // [<KssSection>, ...]
styleguide.section('2.1.1').modifiers() // [<KssModifier>, ...]
});Included are a few additional (optional) features to allow for completely automated styleguide generation.
Take a look at the demo project for some examples.
Overview Document*. This "overview" page is generated from a Markdown file, which you should place in the directory you're generating from, just name it styleguide.md and it will be included in the final styleguide automatically.
HTML Markup. In kss-node you can include sample markup in your styleguide entries. This is not only helpful for newcomers to a project, but is also used by the generator to include samples in your styleguide - just start a paragraph in your description section with Markup: like so:
// Buttons
//
// Buttons can and should be clicked.
//
// Markup: <button class="button {$modifiers}">
//
// :hover - Highlight the button when hovered.
//
// Styleguide 1.1Multi-line descriptions. You can run your descriptions over multiple lines and paragraphs, and if you don't want to include the "modifiers" section you don't have to.
Forking, hacking, tearing apart of this module welcome - it still needs some cleaning up.
If you've got mocha installed, you can run the module's tests with npm test or make test.
To generate a new version of the demo styleguide, use make gh-pages. After committing your changes to master you can use the gh-pages.sh script to move this over to the gh-pages branch real quick.