Github markdown preprocessor.
npm install gitdown
Gitdown adds additional functionality (generating table of contents, including documents, using variables, etc.) to GitHub Flavored Markdown.
``js
// Generate table of contents
{"gitdown": "contents"}
{"gitdown": "contents", "maxLevel": 4}
{"gitdown": "contents", "rootId": "features"}
// Use a custom defined variable
{"gitdown": "variable", "name": "nameOfTheVariable"}
// Include file
{"gitdown": "include", "file": "./LICENSE.md"}
// Get file size
{"gitdown": "filesize", "file": "./src/gitdown.js"}
{"gitdown": "filesize", "file": "./src/gitdown.js", "gzip": true}
// Generate badges
{"gitdown": "badge", "name": "npm-version"}
{"gitdown": "badge", "name": "bower-version"}
{"gitdown": "badge", "name": "travis"}
{"gitdown": "badge", "name": "david"}
{"gitdown": "badge", "name": "david-dev"}
{"gitdown": "badge", "name": "waffle"}
// Print date
{"gitdown": "date", "format": "YYYY"}
`
* Cheat Sheet
* Contents
* Command Line Usage
* API Usage
* Logging
* Syntax
* Ignoring Sections of the Document
* Register a Custom Helper
* Features
* Generate Table of Contents
* Heading Nesting
* Find Dead URLs and Fragment Identifiers
* Reference an Anchor in the Repository
* Variables
* Include File
* Get File Size
* Generate Badges
* Print Date
* Gitinfo
* Recipes
* Automating Gitdown
`sh
npm install gitdown -g
gitdown ./.README/README.md --output-file ./README.md
`
`js
import Gitdown from 'gitdown';
// Read the markdown file written using the Gitdown extended markdown.
// File name is not important.
// Having all of the Gitdown markdown files under ./.README/ path is the recommended convention.
const gitdown = await Gitdown.readFile('./.README/README.md');
// If you have the subject in a string, call the constructor itself:
// gitdown = await Gitdown.read('literal string');
// Get config.
gitdown.getConfig()
// Set config.
gitdown.setConfig({
gitinfo: {
gitPath: __dirname
}
})
// Output the markdown file.
// All of the file system operations are relative to the root of the repository.
gitdown.writeFile('README.md');
`
Gitdown is using console object to log messages. You can set your own logger:
`js
gitdown.setLogger({
info: () => {},
warn: () => {}
});
`
The logger is used to inform about Dead URLs and Fragment Identifiers.
Gitdown extends markdown syntax using JSON:
`json
{"gitdown": "helper name", "parameter name": "parameter value"}
`
The JSON object must have a gitdown property that identifies the helper you intend to execute. The rest is a regular JSON string, where each property is a named configuration property of the helper that you are referring to.
JSON that does not start with a "gitdown" property will remain untouched.
Use HTML comment tags to ignore sections of the document:
`html
Gitdown JSON will be interpolated.
<!-- gitdown: off -->
Gitdown JSON will not be interpolated.
<!-- gitdown: on -->
Gitdown JSON will be interpolated.
`
`js`
gitdown.registerHelper('my-helper-name', {
/**
* @var {Number} Weight determines the processing order of the helper function. Default: 10.
*/
weight: 10,
/**
* @param {Object} config JSON configuration.
* @return {mixed|Promise}
*/
compile: (config) => {
return 'foo: ' + config.foo;
}
});
`json
{"gitdown": "my-helper-name", "foo": "bar"}
`
Produces:
`markdown
foo: bar
`
a
`json
{"gitdown": "contents"}
`
Generates table of contents.
The table of contents is generated using markdown-contents.
`json
{"gitdown": "contents", "maxLevel": 4, "rootId": "features"}
`
`markdown
* Generate Table of Contents
* Example
* JSON Configuration
* Heading Nesting
* Parser Configuration
* Find Dead URLs and Fragment Identifiers
* Parser Configuration
* Reference an Anchor in the Repository
* JSON Configuration
* Parser Configuration
* Variables
* Example
* JSON Configuration
* Parser Configuration
* Include File
* Example
* JSON Configuration
* Get File Size
* Example
* JSON Configuration
* Generate Badges
* Supported Services
* Example
* JSON Configuration
* Print Date
* Example
* JSON Configuration
* Gitinfo
* Example
* Supported Properties
* JSON Configuration
* Parser Configuration
`
| Name | Description | Default |
| --- | --- | --- |
| maxLevel | The maximum heading level after which headings are excluded. | 3 |rootId
| | ID of the root heading. Provide it when you need table of contents for a specific section of the document. Throws an error if element with the said ID does not exist in the document. | N/A |
Github markdown processor generates heading ID based on the text of the heading.
The conflicting IDs are solved with a numerical suffix, e.g.
`markdownFoo
Something
Bar
Something
`
`htmlFoo
Something
Bar
Something
`
The problem with this approach is that it makes the order of the content important.
Gitdown will nest the headings using parent heading names to ensure uniqueness, e.g.
`markdownFoo
Something
Bar
Something
`
`htmlFoo
Something
Bar
Something
`
| Name | Description | Default |
| --- | --- | --- |
| headingNesting.enabled | Boolean flag indicating whether to nest headings. | true |
Uses Deadlink to iterate through all of the URLs in the resulting document. Throws an error if either of the URLs is resolved with an HTTP status other than 200 or fragment identifier (anchor) is not found.
| Name | Description | Default |
| --- | --- | --- |
| deadlink.findDeadURLs | Find dead URLs. | false |deadlink.findDeadFragmentIdentifiers
| | Find dead fragment identifiers. | false |
> This feature is under development.
> Please suggest ideas https://github.com/gajus/gitdown/issues
`json
{"gitdown": "anchor"}
`
Generates a Github URL to the line in the source code with the anchor documentation tag of the same name.
Place a documentation tag @gitdownanchor anywhere in the code base, e.g.
`js
/**
* @gitdownanchor my-anchor-name
*/
`
Then reference the tag in the Gitdown document:
`
Refer to foo.
`
The anchor name must match /^[a-z]+[a-z0-9\-_:\.]*$/i.
Gitdown will throw an error if the anchor is not found.
| Name | Description | Default |
| --- | --- | --- |
| name | Anchor name. | N/A |
| Name | Description | Default |
| --- | --- | --- |
| anchor.exclude | Array of paths to exclude. | ['./dist/*'] |
`json
{"gitdown": "variable"}
`
Prints the value of a property defined under a parser variable.scope configuration property. Throws an error if property is not set.
`js
const gitdown = Gitdown(
'{"gitdown": "variable", "name": "name.first"}' +
'{"gitdown": "variable", "name": "name.last"}'
);
gitdown.setConfig({
variable: {
scope: {
name: {
first: "Gajus",
last: "Kuizinas"
}
}
}
});
`
| Name | Description | Default |
| --- | --- | --- |
| name | Name of the property defined under a parser variable.scope configuration property. | N/A |
| Name | Description | Default |
| --- | --- | --- |
| variable.scope | Variable scope object. | {} |
`json
{"gitdown": "include"}
`
Includes the contents of the file to the document.
The included file can have Gitdown JSON hooks.
See source code of ./.README/README.md.
| Name | Description | Default |
| --- | --- | --- |
| file | Path to the file. The path is relative to the root of the repository. | N/A |
`json
{"gitdown": "filesize"}
`
Returns file size formatted in human friendly format.
`json
{"gitdown": "filesize", "file": "src/gitdown.js"}
{"gitdown": "filesize", "file": "src/gitdown.js", "gzip": true}
`
Generates:
`markdown
9.3 kB
2.8 kB
`
| Name | Description | Default |
| --- | --- | --- |
| file | Path to the file. The path is relative to the root of the repository. | N/A |gzip
| | A boolean value indicating whether to gzip the file first. | false |
`json
{"gitdown": "badge"}
`
Gitdown generates markdown for badges using the environment variables, e.g. if it is an NPM badge, Gitdown will lookup the package name from package.json.
Badges are generated using http://shields.io/.
| Name | Description |
| --- | --- |
| npm-version | NPM package version. |bower-version
| | Bower package version. |travis
| | State of the Travis build. |david
| | David state of the dependencies. |david-dev
| | David state of the development dependencies. |waffle
| | Issues ready on Waffle board. |gitter
| | Join Gitter chat. |coveralls
| | Coveralls. |codeclimate-gpa
| | Code Climate GPA. |codeclimate-coverage
| | Code Climate test coverage. |appveyor
| | AppVeyor status. |
What service are you missing? Raise an issue.
`json
{"gitdown": "badge", "name": "npm-version"}
{"gitdown": "badge", "name": "travis"}
{"gitdown": "badge", "name": "david"}
`
Generates:
`markdown
`
| Name | Description | Default |
| --- | --- | --- |
| name | Name of the service. | N/A |
`json
{"gitdown": "date"}
`
Prints a string formatted according to the given moment format string using the current time.
`json
{"gitdown": "date"}
{"gitdown": "date", "format": "YYYY"}
`
Generates:
`markdown
1563038327
2019
`
| Name | Description | Default |
| --- | --- | --- |
| format | Moment format. | X (UNIX timestamp) |
`json
{"gitdown": "gitinfo"}
`
Gitinfo gets info about the local GitHub repository.
`json
{"gitdown": "gitinfo", "name": "username"}
{"gitdown": "gitinfo", "name": "name"}
{"gitdown": "gitinfo", "name": "url"}
{"gitdown": "gitinfo", "name": "branch"}
`
`
brettz9
gitdown
https://github.com/brettz9/gitdown
update-readme
`
|Name|Description|
|---|---|
|username|Username of the repository author.|name
||Repository name.|url
||Repository URL.|branch
||Current branch name.|
|Name|Description|Default|
|---|---|---|
|name|Name of the property.|N/A|
|Name|Description|Default|
|---|---|---|
|gitinfo.defaultBranchName|Default branch to use when the current branch name cannot be resolved.|N/A|gitinfo.gitPath
||Path to the .git/ directory or a descendant. | __dirname of the script constructing an instance of Gitdown.|
Use Husky to check if user generated README.md before committing his changes.
`json
"husky": {
"hooks": {
"pre-commit": "npm run lint && npm run test && npm run build",
"pre-push": "gitdown ./.README/README.md --output-file ./README.md --check",
}
}
`
--check` attributes makes Gitdown check if the target file differes from the source template. If the file differs then the program exits with an error code and message:
> Gitdown destination file does not represent the current state of the template.
Do not automate generating and committing documentation: automating commits will result in a noisy commit log.