Closed DerekNonGeneric closed 4 years ago
Yes, please fix this! 😀
@Trott, it is my impression that this would be an excellent opportunity to switch to highlight.js for a few reasons:
I think there was a reason why @zeke mentioned it in passing — it's the route to go nowadays. If GitHub's syntax highlighting library (Prettylights) were OSS, we'd ideally use that, but that doesn't seem to be one of our options. I can give it a day or two before proceeding in case others want to shop around and propose a superior frontend syntax highlighting library, but this seems like the best bet as far as I can tell.
/cc @nodejs/documentation
I think there was a reason why @zeke mentioned it in passing — it's the route to go nowadays
☝️ Yep that is why I mentioned it.
Hi folks! As this discussion mentions ideally using PrettyLights by GH, I wanted to drop a suggestion for a project which I made that does exactly that: https://github.com/wooorm/starry-night. HLJS is much lighter, but if y’all are noticing problems, starry-night
might be a good choice!
📗 API Reference Docs Problem
Location
Section of the site where the content exists
Affected URL(s):
Problem description
Concise explanation of what you found to be problematic
While looking into #32938, I discovered that currently, every single <pre> tag gets highlighted as JavaScript regardless of the info string specified (and even if left unspecified). The following line executes the code that does this.
https://github.com/nodejs/node/blob/94e5b5c77dade0d8f7358c66144b75c369679cab/doc/template.html#L56
This behavior can be observed in the C++ code blocks in the published API reference documents. The following line is the reason for this — the language has been hard-coded.
https://github.com/nodejs/node/blob/94e5b5c77dade0d8f7358c66144b75c369679cab/doc/api_assets/sh_main.js#L542
^ I'm currently on summer vacation, so I would have the time to work on this.
/cc @Trott