Consider using Markdown linter / formatter in build process #20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When writing Jinja templates, I find it hard to get the new lines I want without introducing ones that I don't (e.g. blank line before a list, blank line above heading, no consecutive blank lines between content).
I know that this can be improved by people more versed in Jinja than I am. I also know that markdown is essentially an intermediate product intended for use by Hugo, so as long as our markdown output is syntactically correct and reproducible, formatting details should not matter.
However, I still want to output good looking markdown pages. I have been experimenting with rumdl, a markdown linter and formatter written in rust. It can be installed with
uv, and the binary is 13MB (note, there is also markdownlint, available in Debian, but it is a linter without reformatting ability). I tried on a few pages (rumdl check --disable MD013 ...andrumdl fmt --disable MD013 ...) and it works OK.I wanted to ask whether including
rumdlin the page build workflow would be met with approval, considering the non-essential nature of the thing.