We've recently pushed an update to our readme file and the markdown for readme.md is being processed differently on flows.nodered.org compared to npmjs or github. On flows.nodered it is processed as a full-page 2 column document. We would expect it to look more like it does on npmjs and github.
Is this a thing we should fix in our readme.md file or is it a thing which should be looked at in the inner workings of the nodered website?
@knolleary if you or your team could point us to the instructions how to resolve that it would be great.
Also, if you could link repo which is handling flows.nodered at the moment then I could look myself as well.
Please keep it in mind that GitHub markdown engine is very limited, so we cannot play with CSS too much in there.
It depends how urgent it is to get resolved. The quickest fix under your control is to modify your readme.
If you identify the specific difference in the generated markdown, that would certainly help.
Last time I checked (which was a while ago) neither github nor npm have published their markdown renderer - nor do we want to maintain our own. So we use the marked markdown engine as it's one of the more "standards" compliant.
If you're referring to how the image is not letting text wrap around it, seems that removing the vspace="500" attribute from the image does the trick. I tested it out using marked and it seems to work Marked markdown demo
Looks like both GH and NPM remove this attribute in the actual HTML.
@knolleary it's not especially urgent, we will probably take away the vspace=500 attribute in this case for a quick/easy fix. But I thought it would be good to raise the question here because while all 3 sites use the same source file, only one of them is not like the others. Since so much development happens on GH and NPM for nodered plugins, it is probably ideal for all 3 to render the markdown very similar to each other.
I'll leave it to @Shaquu to continue the conversation on rendering engines, since that's over my head.