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

markmd

v0.5.0-rc5

Published

Node.js CLI that compile markdown to beautiful HTML API document

Downloads

68

Readme

MarkMD

npm version NPM

Node.JS Structured document with markdown to HTML translator

  • Mobile Device Responsive
  • Directory-Oriented
  • Real-time compiler

What's new in MarkMD

  • Improve stylesheet to readable layout
  • Syntax hilighter in code block

Table of Contents

Usage

Install markmd tools to your project

npm install markmd --save

Start

To make API document, just call markmd (put it in your package scripts)

npm run markmd

Folder Structure

README.md will be your home page. For sub-category, all markdown file should be stored in docs folder. All image file should be stored in docs-img folder.

Example

├─ README.md
├─ /docs
|   ├─ Alpha.md
|   ├─ Bravo.md
|   └─ Charlie.md
└─ /docs-img
    ├─ foo.jpg
    └─ bar.jpg

This will be compiled to static HTML structure like this

├─ index.html
└─ /docs
    ├─ Alpha.html
    ├─ Bravo.thml
    ├─ Charlie.html
    └─ /docs-img
        ├─ foo.jpg
        └─ bar.jpg

Customize configuration

Make configuration by create markmd.json

{
  "source": "custom-docs",
  "destination": "exported-docs",
  "image": "custom-img",
  "version": true
}

Options

| option | description | default | |--------|-------------|---------| | source | Different document folder name | "docs" | | destination | Different exported folder name, by default | "apidoc/des" | | image | Different image folder name | "docs-img" | | version | Use version structuring | false | | fakeApidocConfig | Generate fake apidoc.json | false |

Versioning

For multi-version API document, just put "version": true into configuration file (described above). Versioning folder should be like this

Example

├─ README.md
└─ /docs
   ├─ /v1
   |  └─ fetch.md
   ├─ /v1.1
   |  ├─ fetch.md
   |  └─ delete.md
   └─ /v2
      └─ migration.md

Watching Changes

For real-time compiling, just add --watch or -w option to the command

markmd --watch