MkDocs and markdown-link-validator
The documentation of DSP-TOOLS is built with MkDocs (see README). Please consider the following caveats:
Styling constraints in the documentation
In our GitHub actions, we check PRs for dead links in the documentation.
Our tool markdown-link-validator is only able to check internal links
if they start with ./. For example:
[prefixes](./dsp-tools-create.md#prefixes-object)instead of
[prefixes](dsp-tools-create.md#prefixes-object)instead of
It is okay, however, to make an internal link to a title of the current document:
[prefixes](#prefixes-object)
Please follow this constraint, so that markdown-link-validator can check the internal links.
Handling false positives of markdown-link-validator
What can be done if your links are correct, but markdown-link-validator doesn't recognize them?
One solution is to add an ignore pattern
to the call to markdown-link-validator in .github/workflows/tests-on-push.yml.
If your link is in a code block, and isn't intended to be used as link, you can also add an invisible Unicode character, like in the examples above.
No duplicate headings, no special characters in headings
When linking to a heading, the name heading is slugified. Unfortunately, there are different flavors of Markdown, and different slug algorithms. As long as the heading is unique in the document, and doesn't contain special characters, there is no problem.
But consider a document like this:
# Heading / Title
First heading with this name
# Heading / Title
Second heading with this name
# Further down in the document
[link to second heading](#heading-title_1) <!--mkdocs supports only this syntax-->
[link to second heading](#heading--title-1) <!--npm markdown-link-validator supports only this syntax-->
To make things worse, different IDEs use different slug algorithms, too, which might lead to misleading hints from the IDE.
The real danger lies within MkDocs: while it doesn't support the heading--title-1 syntax,
it doesn't complain if you use it, not even when using the --strict flag.
This can lead to broken links on https://docs.dasch.swiss/,
without anyone noticing.
The best solution how to deal with this
- give a unique name to every heading within the same document
- don't use special characters in headings
A short overview of Markdown tools and slug algorithms
- MkDocs uses Python Markdown to translate Markdown files into HTML (see here).
- Python Markdown's default slugify used to strip out all Unicode chars (see here).
- markdown-link-validator uses uslug to create the slugs (see here).
- VS Code targets the CommonMark Markdown specification using the markdown-it library (see here).
Another useful reading is here.