Uh oh!
There was an error while loading. Please reload this page.
Convert a few posts to Markdown - #2437
Conversation
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
I think a bunch of the link checking is done through regex. Can't hurt to file an issue with the library though. Not sure if there is a rule that covers links or not
XhmikosR
commented
Aug 23, 2019
Alright, I went ahead and put back the old IDs for backward compatibility. |
XhmikosR
commented
Aug 23, 2019
Alright, I believe this is ready for review. We could tweak these further later. |
XhmikosR
commented
Aug 25, 2019
If it helps, to review you can check the rich diff for each file on GitHub. |
Fixes a few HTML validation errors along the way. Also remove the 404 images from /multi-server-continuous-deployment-with-fleet.md. For npm's posts, I kept the old IDs for backward compatibility.
XhmikosR
commented
Sep 2, 2019
Can we get this merged? The plan is to convert most inline HTML to Markdown when possible so that we are consistent. This also fixes 2 404 errors. There are a few mixed content errors I noticed too, and I'll fix them in another PR. |
Trott
commented
Sep 3, 2019
@nodejs/website This needs reviews. |
Fixes a few HTML validation errors along the way.
Also remove the 404 images from /multi-server-continuous-deployment-with-fleet.md.
For npm's posts, I kept the old IDs for backward compatibility.