No, not really; but I think I’m not understanding the question… especially because you were replying to me at the same time I was updating my comment to correct a different misunderstanding of mine.
If I do understand the question, the document generation works as normal. I just run plain old mix docs to get the documentation out. I have done a fair amount with ExDoc configuration in mix.exs, but that’s about it.
bahahaha, I read your response while out walking my dog and now that I’m back it’s crossed out so no need for an off-topic 
Just for clarity, are you talking along the lines of defdelegates and the like here?
I wanted to ask if taking the examples out of the @doc above the method would need remove change their position in the htm.
The question is moot now as you do not do that. (put the docs in a different file)
Also I was trying to figure out how to use the crossout a few days ago so thanks for that as well.
Yeah, a lot of defdelegate, though if the call is to, say a GenServer, then I wrap the GenServer call directly. This is an example of an “API” module using both call styles (and their docs 
):
Ya makes sense, I’m a big fan of defdelegate myself. I see it as one of the keys to not getting stuck in cyclical dependency hell (also of just nicer code in general).
Thanks for the link to that repo! It’s good reading material for someone like me who works alone these days