2.0.1 • Published 5 years ago

gitbook-comment v2.0.1

Weekly downloads
23
License
ISC
Repository
github
Last release
5 years ago

Markdown Generator based on comment (Ideal for Gitbook)

js-standard-style

What does it do?

It generate markdown for any comment line starting with /// (there is a space at the end of it).

/// ### Method Name
/// This is my awesome method.
function Sum(a, b) {
  /// This will convert to markdown
  // This is a normal comment
  return a + b
}
/* Another normal comment */

Above code will become this:

Method Name

This is my awesome method.

function Sum(a, b) {

This will convert to markdown

  // This is a normal comment
  return a + b
}
/* Another normal comment */

Instruction

  1. Install the npm using npm install --save gitbook-comment
  2. Use gitbook-comment --help to read the command line instructions
  3. Edit your package.json with
  "scripts": {
    "doc-generate": "gitbook-comment generate -p ./",
    "doc-clean-up": "gitbook-comment clean-up -p ./",
    "doc-publish": "gitbook-comment publish -p ./"
  }
  1. Make suer you have docs branch created locally on your machine by git branch docs
  2. Make sure you have your code committed on your working branch
  3. Run npm run doc-generate on your working branch:
    • This will switch branch automatically to docs
    • Create documents next to source files
    • Push them to github
    • Switch back to working branch

Note If you do not commit your work in working branch, it may get lost in switching the branches.

note: This generator is creating the .md files in same folder next to the original files.

Alternatively you can generate or clean up docs in any branch

# Generate doc in current branch
npm run doc-generate

# Check help for a command
npm run doc-generate -- -h

# Get full documentation
./node_modules/gitbook-comment/bin/gitbook-comment -h

# Use more more options on a command
npm run doc-generate -- -p ./src -i bin -e js,css,scss

# Clean up generated docs
npm run doc-comment clean-up

If you generate doc manually, make sure they are uploaded to docs or any other none development branch and use gitbook.com integration to view them.

2.0.1

5 years ago

2.0.0

5 years ago

1.0.6

5 years ago

1.0.5

5 years ago

1.0.4

5 years ago

1.0.3

5 years ago

1.0.2

5 years ago

1.0.1

5 years ago

1.0.0

5 years ago