Morten Piibeleht

> I'm mostly interested in this because I want to maintain support for both 1.0 and 1.1, and I run doctests as part of CI. I would version guard that,...

I agree that an option to `deploydocs` would be the way to go. Another possibility would be to allow the user to pass a full regex, requiring it to have...

You shouldn't be getting errors if you are not referring to them in an `@docs` block. For an `@autodocs` block you can, you can specify the `Private` option to ignore...

@lelogrott: Apologies for not replying before. The underlying assumption is that all docstrings are meant to be public (whether that is reasonable is up for debate). As you're not including...

I am not entirely sure this is the right way to go -- the footnote bodies can have different content. So really this is a situation where the user should...

I didn't go through this yet, but one small request which can help expedite this: could you add a page to the [example HTML build](https://github.com/JuliaDocs/Documenter.jl/tree/master/test/examples) which would showcase all the...

I think it should be possible to check in the browser if the URL in the other version 404-s or not, and decide based on that.

So, just to clarify: ``[`foo(x)`](@ref)`` should be transformed into `foo(x)` if there is only the _function_ `foo` has a docstring. But if there is a docstring for the method `foo(::Any)`,...

Don't `@example` blocks work in docstrings?

Ah, no, you're right, apparently they don't work. I assumed that they might. I don't see any other objection to enabling them other than that `@example` etc. blocks are not...