The sidebar really doesn't work for complex nodes since it is too limited as is the formatting. I'm not complaining of course, the formatting is fine for a help panel and totally useful for that. It is the right tool for the majority of nodes for sure.
Rightly or wrongly, I decided that it would be helpful to anyone who wanted to be offline to have the main documentation available locally and it was in the repo anyway so comes through with the installation. As we have a web-server to hand anyway, why not use it for fuller documentation about the node if the node warrants it.
I'd be totally happy for there to be a standard URL that could be optionally included in a node. I'd also be happy if it had some standards - though I think that is possibly a much harder ask and potentially quite a lot of work to come up with a standard. For my docs, you'll see that I chose to use Docsify because it lets you stick to simple Markdown with a single HTML page to do all the work. It also lets you expand into quite comprehensive markdown extensions such as incorporating various diagrams and some nice-to-haves such as note/warning/information panels. It also uses VueJS under the skin and so lets you add niceties such as using frontmatter data in the page display. (As a sidenote, I use the same code on our IT Standards document at work, just with a different style on it).
So I understand the concern about consistent style - though I might argue that for full docs, I'm not sure it matters so much? Again, though, I wouldn't mind as long as there was some flexibility to accommodate more complex documentation.
I was wondering if one could get away with just an object like;
"description": "Some useful help text to introduce the node.",
"detail": "Accepts a string, object or array"
"details": "Some more information about the node."