LaTeXML

Tell us what you would need described in a tutorial to be productive, as well as your background with the technologies involved (TeX/LaTeX, perl, XML, XSLT, HTML). Probably best as a new issue: https://github.com/brucemiller/LaTeXML/issues It's a pretty deep rabbit hole, but I wholeheartedly agree most standard package support incantations should be easy and few to use.

Stacks project is available on github, so in theory (if you're bored enough) it should be possible to reverse engineer their design from their make-project file https://github.com/stacks/stacks-project/blob/master/documen... At a high level they use plastex https://github.com/plastex/plastex to convert latex to html (you seem to be using pandoc?) and so can control the rendering to any fine accuracy they want. I liked this general style as well, so I tried using plastex but couldn't get my head around it and so started using LateXML https://github.com/brucemiller/LaTeXML My usecase: I wanted to have a "dependency graph" of lemmas to make it easier to see proofs without having to jump back and forth through a pdf, and this was sort of similar to lean formalization blueprint graphs https://teorth.github.io/pfr/blueprint/dep_graph_document.h

LaTeML [1] is presumably the latex to html tool that arXiv is testing right now. What are peoples thoughts about it compared to other such tools? [1] https://github.com/brucemiller/LaTeXML

They aren't using the rendered PDFs. They are convering from the LaTeX sources, that you upload to arxiv with https://github.com/brucemiller/LaTeXML

I'm using KaTeX as well, but there's also https://dlmf.nist.gov/LaTeXML/ (GitHub: https://github.com/brucemiller/LaTeXML) I want to switch to LaTeXML eventual over KaTeX (via embedded JavaScript), but my blog workflow is based on Emacs Org-mode and it was much easier to replace Org's native MathJax with KaTeX.