UNPKG

doks

Version:

A configurable, bring-your-own-template documentation generator aimed for user and developer documentation based on source code.

72 lines (58 loc) 1.99 kB
doks ==== A configurable, bring-your-own-template documentation generator aimed for user and developer documentation based on source code. Basic Use ========= You can either use `doks` as a command line tool (`npm install -g doks`) or programmatically, with `var Parser = require('doks').Parser`. If you choose to run it from the command line, the best option is to create a `doks.json` file in the root of your repository, with a structure like this (taken from [our doks.json](https://github.com/kellyirc/doks/blob/master/doks.json)): ```json { "language": "coffee", "glob": "lib/parser.coffee", "arrayTags": [ "supports", "param" ] } ``` Then just run `doks` and it will generate your documentation, based on your source code comments. Whether you use the command line tool or run it yourself, the supported options are [available here](http://kellyirc.github.io/doks/#!/TagParser/Option). Themes ====== Themes are very flexible by design. You could build one from scratch, or work based off of the existing efforts put forth. Themes should generally have a similar structure, like so: ``` core vendor views config.json // this is required favicon.ico // this should be the default doks favicon.ico index.html // this is required ``` A config.json should be structured like so: ```json { "keys": { "category": "package", "mainType": "category", "subType": "name" }, "options": { "page": { "pageName": "Doks", "favicon": "favicon.ico", "showGitHubBadges": true }, "nav": { "categorySeparate": false, "mainTypeRight": false, "useSearchBar": true }, "content": { "showFileLabels": true, "sourceLink": "https://github.com/kellyirc/doks/tree/master/%filePath#L%lineNumber-L%endLineNumber" } } } ``` However, the only required key here is `options` - doks uses that to merge user configuration into the theme configuration. Everything else is determined by the theme.