Morten Piibeleht

I would suggest trying to implement a proof-of-concept version externally as a plugin. It should be [a separate `ExpanderPipeline`](https://github.com/JuliaDocs/Documenter.jl/blob/68dbd53d4ff6b339e795a4a3328955ad5c689e0e/src/Expanders.jl#L212-L221) step.

Nope, not currently possible, but would be something that could be done if someone needs it. Sounds like a new ` ```@ `-block (`@include`?). But I would leave the implementation...

> Does it enable syntax color highlighting for Julia ? You can always add the language to the code block, e.g.: ````` ````@eval Markdown.parse(""" ```julia $(readstring("PATH_TO_FILE")) ``` """) ```` `````...

LGTM @tpapp! I would stick to CamelCase with the keys though, to be consistent with the other at-blocks. `parseblock` just `parse()`s into AST and does not `eval`, as far as...

I agree with the sentiment and I think it would be awesome to have something like this, but it's a little non-trivial. Here are some of my unorganized thoughts: *...

I didn't know about utterances. It looks really neat and solves most, if not all, the difficult parts. For the backend, I was imagining you'd have to authenticate anyway, probably...

I presume it's because the index would usually apply to the whole page or manual. However, I don't see any harm in allowing optional custom filtering here.

Rather than implementing this as a new, special block in Documenter, I am thinking it would be better to make it easier for the user to implement their own custom...

Duplicate of #1020?

Ah, yes, I believe you're right that this is not a duplicate of that issue, but an escaping issue. That said the double-backtick version ``` ``echo `$(nothing)` `` ``` is...