Morten Piibeleht

But back to doctests then -- in principle reducing the test down to "was there an exception or not" should be quite possible. However, with doctests we shouldn't inject the...

Do you mean that the self-contained HTML file would be the whole thing that gets sent to the browser, or do you imagine that Documenter would still try to generate...

To support the `title` links, we'd need to support a different Markdown parser, like [CommonMark](https://github.com/MichaelHatherly/CommonMark.jl). For the HTML inclusion, at-raw blocks (or at-eval blocks with `text/html` `show` methods) would be...

I believe we first sort according to category (type, module, function, const, etc.)? So I am not sure if what you're seeing is really due to case.

> But if people prefer the current way, perhaps "section headings" could be inserted to make this clearer This actually sounds like could be a good idea for long indices....

The default is based on the CSS media feature https://github.com/JuliaDocs/Documenter.jl/blob/d2ed9b8b171e487835f456524e52799aa9da1d15/assets/html/themeswap.js#L14-L17 but this can be overridden by a user-defined value in `localStorage`, hence why the whole check is done in JS.

It also looks like a parsing issue (so a problem in the Markdown stdlib), rather than a Documenter problem. What does `Markdown.parse_file` output when parsing these files?

I am not familiar with Podman, but the interface emulates Docker? Happy to take a PR if there is interest in this. It should be easy enough to support it....

It actually looks like it might be preinstalled on the Ubuntu images. By the way, can Podman reuse [the Docker image we have](https://hub.docker.com/r/juliadocs/documenter-latex)?

Thanks for the PR! One think I wanted to double check with this change: what exact version of Julia was the `softscope!` -> `softscope` made exactly (i.e. which is the...