grunt-sassdoc

grunt-sassdoc

SassDoc Grunt task.

Getting Started

If you haven't used grunt before, be sure to check out the Getting Started guide, as it explains how to create a gruntfile as well as install and use grunt plugins. Once you're familiar with that process, install this plugin with this command:

npm install --save-dev grunt-sassdoc

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-sassdoc');

Tip: the load-grunt-tasks module makes it easier to load multiple grunt tasks.

Documentation

See the Gruntfile in this repo for a full example.

SassDoc task

Run this task with the grunt sassdoc command.

Task targets, files and options may be specified according to the grunt Configuring tasks guide.

Options

Any specified option will be passed through directly to SassDoc, thus you can specify any option that SassDoc supports. See the SassDoc documentation for a list of supported options.

verbose

Type: Boolean
Default: false

Whether to enable SassDoc own logger or not.

config

Type: String
Default: null

Path to a view configuration file.

display.access

Type: Array
Default: ['public', 'private']

Access levels that should be displayed.

display.alias

Type: Boolean
Default: false

Enable/disable display of alias items.

display.watermark

Type: Boolean
Default: true

Enable/disable display of SassDoc watermark in footer.

package

Type: String | Object
Default: './package.json'

Pass your project informations to the generated view. Either a path to your package.json or an object.

Following keys will be looked for: title name version license homepage description

Heads up: If a config file is passed and found, its options will prevail over defauts. Additionnal options passed to the grunt task, will complement it but not override it. You should really manage your options in one place.

Config examples

// Example with external view configuration file.
grunt.initConfig({
  sassdoc: {
    default: {
      src: 'path/to/sass',
      dest: 'path/todocs',
      options: {
        config: 'path/to/view.json'
      }
    }
  },
});

// Example with passed in options.
grunt.initConfig({
  sassdoc: {
    default: {
      src: 'path/to/sass',
      dest: 'path/to/docs',
      options: {
        display: {
          access: ['public', 'private'],
          alias: true,
          watermark: true
        },
        package: './package.json'
      }
    }
  },
});

Events

This task will emit a start event when compilation begins, and a done event on completion. This is useful if you would like simple notifications about the compile process. The start and done events are not intended for replacing the standard Grunt API for configuring and running tasks.
Here is a simple example using the watch event:

// Examples using start and done events.
grunt.event.on('sassdoc.start', function (target, src, dest) {
  grunt.log.writeln(target + ': compiling ' + src + ' to ' + dest);
});

grunt.event.on('sassdoc.done', function (target, src, dest) {
  grunt.log.writeln(target + ': ' + src + ' compiled to ' + dest);
});

Authors

Pascal Duez

Licence

grunt-sassdoc is unlicensed.

Changelog

0.3.0

(2014-07-10)

Features

• Added start and done notification events. (e85cbe86ad)