Morten Piibeleht

> all of the native elements have all their fields declared mutable That's fair actually. But yea, the intent there is two fold: (1) you should be able to change...

Can you explain the use case here a bit? You have an at-eval block that tries to interpolate a `Documenter.RawNode`? In general, I'd like the at-eval blocks to be a...

Should we maybe use the standard `Docs.HTML` for that? I.e. if the block returns that, we'll just convert it to an `@raw html` node?

We don't know what's internal and what is not though, so I am not sure it's actionable on this level. This should maybe be addressed by not including those docstrings...

Note: it looks like this is a regression in 0.10 -> 0.11.

Yea, I agree. I think should be handled like normal errors.

I don't think this would necessarily have to be breaking. We can have an option to return `doc` (not sure if we use `debug` for anything other than returning `doc`),...

> * construct a document without rendering it, and then render it where you choose A very hacky option could be add an option to return `doc` without calling the...

Technically, you can probably just call `render`, no? It does pick the renderer from the `doc` object. https://github.com/JuliaDocs/Documenter.jl/blob/25f9027d1dd7adfb4fbdc47d12b2a26b7570beff/src/writers.jl#L41-L48 It's what gets called in the last build step: https://github.com/JuliaDocs/Documenter.jl/blob/25f9027d1dd7adfb4fbdc47d12b2a26b7570beff/src/builder_pipeline.jl#L266

> Or are you saying some kwarg will just halt rendering entirely? You mean to get the `doc` out before rendering? Yea, that's what I imagine. It's not pretty, but...