Thanks for the detailed answer 
Definitely.
On the other hand doing something like we did with the groupflow plugin, i.e. having a plugin demonstrate the feature which then can be used in the meantime is probably the golden middle road.
I'm pretty sure that something like the groupflow will - eventually - make it into core. Having a plugin to test the feature and add suggestions before then is really useful.
Can I ask does FlowFuse parse the url and to determine what functionality is to be called? I.e. could I add something like [Name](#search/search%20term) so that I can trigger the RED.search.open("search term") functionality?
I know that extending the markdown rendered isn't rocket science, just whether that is possible via a plugin remains a mystery to me.
I think this isn't a good idea for portability 
- hardcoding both the IP and node id means that importing the flow somewhere else will probably break the documentation ....
onclick is definitely no solution. I totally forgot to use markdown notation (because I started with onclick), so having [..](#<function>/<arg>) convention for markdown links would be the way to go...
Cheers!
