Morten Piibeleht

Documenter checks if a given docstring is included in the generated manual, but it does not check whether every function/type/module has a docstring. If I understand correctly, you're after the...

For checking exports, it should be relatively straightforward to write a small function that cross-checks what `name(MyPackage)` gives vs what is in `Docs.meta(MyPackage)`. And even though it doesn't really have...

> Assuming you meant `names`, if so this unfortunately doesn't quite work as it includes exported objects that shouldn't be documented or don't need to be, for example exported aliases...

For the time being, I would suggest perhaps turning this into a separate tiny package, since it doesn't require anything from Documenter to work. It could then run either in...

No tooling per se, but you [can set `DOCUMENTER_LATEX_DEBUG`](https://github.com/JuliaDocs/Documenter.jl/blob/6b8f8f917bdfdbb3a095fe1eb380b4c614b489cc/src/Writers/LaTeXWriter.jl#L147-L154) to get the source files and play with them. `\resizebox` seems like a good solution for this, but would it also...

Mermaid looks cool, and it's neat that GitHub supports it. I am not entirely sure we want the maintenance burden of it here in Documenter though, so I would suggest...

This seems like a good test case for the API proposed in #1648 (to get Documenter to load the JS). It would also be possible to create special e.g. `@mermaid`...

I am a little hesitant about this.. this feels like a niche usage, and in those rare cases wouldn't it be okay to just write it as ``[`x -> sin(x)`](@ref...

I am not really able to replicate the non-English locale right now, but could you test if passing `"LC_ALL" => "C"` here to `addenv` fixes it? https://github.com/JuliaDocs/Documenter.jl/blob/18d9cefccd1e114befd932980e01ad6a96720bcc/src/Utilities/Utilities.jl#L819-L828 > For me...

This is basically #505 (we actually go in and modify the docstrings that Julia stores, so they are different after the first run) and should be fixed by #1924.