npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

grunt-mkdocs

v1.0.1

Published

Grunt plugin generating documentation web site from Markdown sources using mkdocs

Readme

grunt-mkdocs

NPM version Build Status Coverage Status Dependency Status devDependency Status devDependency Status Code Climate Codacy Badge Built with Grunt

NPM Downloads

Grunt plugin generating documentation web site from Markdown sources using mkdocs

Getting Started

You need node >= 0.8, npm and grunt >= 0.4 installed and your project build managed by a Gruntfile with the necessary modules listed in package.json. 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, you may install this plugin with this command:

$ npm install grunt-mkdocs --save-dev

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

grunt.loadNpmTasks('grunt-mkdocs');

The "mkdocs" tool

This plugin depends on the mkdocs documentation web site generator, which can produce HTML files and other assets suitable for upload to the Read The Docs web site. You must install it before you build the documentation.

You need Python and pip installed, then you install the mkdocs package:

$ sudo pip install mkdocs

Input

Store your written articles in to a folder (docs) and specify a target folder for the generated HTML pages (site); the index.md file will become the title page:

docs/
  index.md
  overview.md
  ...
site/
 overview/
 index.html
 ...
mkdocs.yml
Gruntfile.js

The "mkdocs" task

This module provides a grunt multi-task generating HTML documentation from Markdown sources using mkdocs. In your project's Gruntfile, add a section named mkdocs to the data object passed into grunt.initConfig().

grunt.initConfig({
  mkdocs: {
    dist: {
      src: '.',
      options: {
        clean: true
      }
    }
  }
})

All documentation project options should be maintained in the mkdocs configuration file (mkdocs.yml) in this plugin version.

Options

src

Type: String Default value: '.'

Path to documentation root directory with the mkdocs.yml file.

options.clean

Type: Boolean Default value: false

Removes stale files (from previous builds) from the target folder.

Build

Call the mkdocs task:

$ grunt mkdocs

or integrate it to the default build sequence in the Gruntfile:

grunt.registerTask('default', ['mkdocs', ...]);

Notes

If you want to browse the generated web site from the file system (using the file:// scheme), add the option use_directory_urls: false to the mkdocs.yml configuration files. The generated links will point to .../index.html files instead of just .../ directories relying on the default documents supported by the web servers.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

  • 2018-04-27 v1.0.0 Dropped support of Node.js 4
  • 2016-02-24 v0.2.3 Upgrade dependencies
  • 2016-26-08 v0.2.0 Upgrade to Grunt 1.x
  • 2015-07-30 v0.1.0 Initial release

License

Copyright (c) 2015-2019 Ferdinand Prantl

Licensed under the MIT license.