Store markdown documentation in the same folder as code, run this script, get html documentation in a dedicated folder

Suppose you have some project that looks like this:

foo
├── bar.md
├── baz
│   ├── image.png
│   ├── qux.md
│   └── some.other.file
├── grault
│   └── file
├── README.md
└── some.file

where foo is a git repo containing markdown files with hyperlinks to each other

If you add this repo as a submodule and run md_htmldoc.sh

1. ./foo/foo_htmldoc will be deleted, if it exists
2. All of the .md files under foo will be found and deemed "documentation-relevant"
3. Any files that they reference will be found and deemd "documentation-relevant"
4. All documentation-relevant files will be copied into ./foo/foo_htmldoc
5. All .md files will be converted to .html files
6. Hyperlinks will be fixed so that the .html files link to each other

Then you'll have a directory tree like this

foo
├── bar.md
├── baz
│   ├── image.png
│   ├── qux.md
│   └── some.other.file
├── foo_htmldoc
│   ├── bar.html
│   ├── baz
│   │   ├── image.png
│   │   └── qux.html
│   └── README.html
├── grault
│   └── file
├── md_htmldoc
│   └── ...
├── README.md
└── some.file
test.txt

• foo_htmldoc has been added
• it contains just the documentation, and the markdown has been converted to html

As soon as you tested the script, you can set it to automatically execute in background after changes - e.g. hooks post-commit, post-checkout and post-merge, so HTML version will always be up to date.

Example hook script:

#!/bin/sh
echo "Converting Markdown to HTML in background"
./md_htmldoc/md_htmldoc.sh >/dev/null 2>&1 &

Copy that script to .git/hooks of your foo repository with corresponding hook name and make sure it is executable.

• Have python installed
• Install Pandoc: apt install pandoc
• Install panflute: pip install panflute

Maybe you want to share documentation with somebody that doesn't have access to your source repository, but you don't want to separate your documentation from your code. You can use this script to create documentation builds and then serve them to the wider world, without also providing access to your code.

This makes me sad, but it appeases certain people that I work with

• If you get cp: cannot create regular file errors, make sure that all of the documentation-relevant files in the parent repo are checked in. md_htmldoc uses git ls-tree to discover the directory tree of the parent repo, and it will fail to mimic the directory structure if there are pending changes
• If you get Exception: unknown tag: Caption in log for some files: Downgrade to Pandoc 2.9.2.1 as Pandoc 2.10 is not yet supported by panflute