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 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-mdoc

v1.0.3

Published

Grunt task generating HTML documentation from Markdown sources using mdoc

Downloads

83

Readme

grunt-mdoc

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

NPM Downloads

This module provides a grunt multi-task generating HTML documentation from Markdown sources using mdoc.

Installation

You need node >= 0.10, 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-mdoc --save-dev

Input

Store your written articles in to a folder (input), specify a target folder for the generated HTML pages and optionally a title page (index.md):

input/
  overview.md
  ...
output/
 assets_/
 index.html
 overview.html
 ...
index.md
Gruntfile.js

Configuration

Add the mdoc entry with the mdoc task configuration to the options of the grunt.initConfig method:

grunt.initConfig({
  mdoc: {
    dist: {
      src: 'input',
      dest: 'output',
      options: {
        indexContentPath: 'index.md',
        baseTitle: 'My Project Documentation'
      }
    }
  }
});

The supported options are:

  • src : (required) the source folder with files in the Markdown format; sub-folders will be searched recursively
  • dest : (required) the target folder for the HTML files
  • indexContent: (optional) HTML markup to put to the top of the index page; it takes precedence over indexContentPath
  • indexContentPath : (optional) Markdown source file for the index page
  • baseTitle : (optional) the title text for the HTML page head
  • ... refer to the mdoc documentation for all the available options

Then, load the plugin:

grunt.loadNpmTasks('grunt-mdoc');

Build

Call the mdoc task:

$ grunt mdoc

or integrate it to your build sequence in Gruntfile.js:

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

Notes

The generated index.html file should be opened from a HTTP server. The sidebar that shows the documentation index is loaded by AJAX, which does not work when the HTML page is opened from the file:// scheme.

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
  • 2017-02-24 v0.3.1 Update dependencies
  • 2016-26-08 v0.3.0 Upgrade to Grunt 1.x
  • 2016-03-05 v0.2.2 Update dependencies, improve build testing
  • 2015-01-31 v0.1.1 Initial release

License

Copyright (c) 2015-2019 Ferdinand Prantl

Licensed under the MIT license.