Morten Piibeleht

On the topic of "font subsetting": are you suggesting we should split the JuliaMono into separate font files, for each class of symbols and serve them separately? And then the...

> Don't block for various other "info" scripts (`siteinfo.js`, `versions.js`) I'm not against this necessarily, but these are really tiny files, so I am not sure it's worth the effort....

The crux of the problem is that in the hosted builds the HTML files technically live one directory down. (e.g. the `dev/usage/` page is `dev/usage/index.html`, instead of just `dev/usage.html`, as...

You would still have to update the value of `prependpath` when changing the build mode, no? It would also open up a whole can of worms where we'd have to...

Where is this actually used in practice? This is not a standard admonition supported by the Markdown stdlib, right? My view generally has been that we only style admonitions that...

I think my inclination here is not to deviate from the Markdown stdlib and the Julia REPL 🙁 I only wish it was easier to customize the themes and admonitions...

> I guess I just have to patch Markdown and REPL first then :) That's definitely one way to go about it :rofl:

The conversion to HTML is handled by https://github.com/JuliaDocs/ANSIColoredPrinters.jl I believe. cc @kimikage

> DocumenterVitepress 0.1.6 DocumenterMermaid works only with the standard Documenter HTML output. I assume DocumenterVitepress just has a fallback render for unfamiliar blocks. Maybe @asinghvi17 has some thoughts? Or if...

Is there a stacktrace or an MWE you could put together? Not really sure _which_ regex is blowing up, though minimally it looks like we should add some error handling...