README.md

mdox

mdox (spelled as md docs) is a CLI for maintaining automated, high quality project documentation and website leveraging Github Flavored Markdown and git.

Goals

Allow projects to have self-updating up-to-date documentation available in both markdown (e.g readable from GitHub) and static HTML. Hosted in the same repository as code and integrated with Pull Requests CI, hosting CD and code generation.

Features

• Enhanced amd consistent formatting for markdown files, focused on .md code readability.
• Auto generation of code block content based on mdoc-exec directives (see #code-generation).
• Robust and fast relative and remote link checking.
• "Localizing" links to relative docs if specified (useful for multi-domain websites or multi-version doc).

Usage

Just run mdox fmt and pass markdown files (or glob matching those).

For example this README is formatted by the CI on every PR using mdox fmt -l *.md command.

usage: mdox fmt [<flags>] <files>...

Formats in-place given markdown files uniformly following GFM (Github Flavored
Markdown: https://github.github.com/gfm/). Example: mdox fmt *.md

Flags:
  -h, --help                     Show context-sensitive help (also try
                                 --help-long and --help-man).
      --version                  Show application version.
      --log.level=info           Log filtering level.
      --log.format=logfmt        Log format to use. Possible options: logfmt or
                                 json.
      --check                    If true, fmt will not modify the given files,
                                 instead it will fail if files needs formatting
      --code.disable-directives  If false, fmt will parse custom fenced code
                                 directives prefixed with 'mdox-gen' to
                                 autogenerate code snippets. For example:
                                 
                                   ```<lang> mdox-gen-exec="<executable + arguments>"
                                 
                                 This directive runs executable with arguments
                                 and put its stderr and stdout output inside
                                 code block content, replacing existing one.
      --links.anchor-dir=LINKS.ANCHOR-DIR  
                                 Anchor directory for link transformers. PWD
                                 flag is not specified.
      --links.localise.address-regex=LINKS.LOCALISE.ADDRESS-REGEX  
                                 If specified, all HTTP(s) links that target a
                                 domain and path matching given regexp will be
                                 transformed to relative to anchor dir path (if
                                 exists).Absolute path links will be converted
                                 to relative links to anchor dri as well.
  -l, --links.validate           If true, all links will be validated
      --links.validate.address-regex=^$  
                                 If specified, all links will be validated,
                                 except those matching the given target address.

Args:
  <files>  Markdown file(s) to process.

Code Generation

It's not uncommon that documentation is explaining code or configuration snippets. One of the challenges of such documentation is keeping it up to date. This is where mdox code block directives comes handy! To ensure mdox will auto update code snippet add mdox-gen-exec="<whatever command you want take output from>" after language directive on code block.

For example this Readme contains mdox --help which is has to be auto generated on every PR:

``` bash mdox-gen-exec="mdox fmt --help"
...

You can disable this feature by specifying --code.disable-directives

Installing

Requirements to build this tool:

• Go 1.15+
• Linux or MacOS

go get github.com/bwplotka/mdox && go mod tidy

or via bingo if want to pin it:

bingo get -u github.com/bwplotka/mdox

Production Usage

• Thanos (TBD)

Contributing

Any contributions are welcome! Just use GitHub Issues and Pull Requests as usual. We follow Thanos Go coding style guide.

Initial Author

@bwplotka