find . -name '*.md' -type f -exec sh -c '
for file do
out="docs/${file#./}"
out="${out%.md}.html"
mkdir -p "$(dirname "$out")"
pandoc --quiet --template template.html "$file" -o "$out"
done
' sh {} +11–20 of 55 posts
find . -name '*.md' -type f -exec sh -c '
for file do
out="docs/${file#./}"
out="${out%.md}.html"
mkdir -p "$(dirname "$out")"
pandoc --quiet --template template.html "$file" -o "$out"
done
' sh {} +Pandoc is my go-to tool. Thank you, Sir!
If you compare this with the HTML produced by typst or hevea, this is super useful, as we can then roll out our own styles.
Thanks so much for pandoc! I never heard about djot [0], is anyone using it? [0]: https://djot.net/
I have at times mused that writing the internal state of pandoc to disk (yes 13th standard etc) would be the most interoperable file format
pandoc document.md --to native> by writing N parsers (“readers”) and M renderers (“writers”), one could support N × M conversions. Beautiful writeup for a wonderful project. In an age of vibe-coding hype it's also so nice to see how things can be extended and snowball in usefulness when things are built correctly, by hand, from basic principles. > Perhaps, then, in the future, people will no longer have a need for tools like pandoc. I think we wi…