Moving the discussion from here...
Aside from using consistent formatting and layouts on all webpack-contrib repositories, we really need to decide on what should be supported in terms of markdown as all the readmes are dynamically pulled into webpack.js.org to be used for a variety of pages. The biggest issue it seems is that while GitHub supports a lot of markdown extensions, they haven't open sourced there parser (as far as I know) which makes it painful for us to support the exact same feature set over at the documentation repo.
Right now we have an extremely long utility that extends the popular, but no longer maintained, marked library. We're still working our way through the backlog of content issues there but I'm really hoping that once that's more under control we can address this markdown issue and potentially switch parsers. So far, there have been a few mentioned that seem promising:
As mentioned above, it would be great if someone knew of a parser that supported most or all of what GitHub's does but, barring that, I think we need to...
This issue is more to discuss the second of those two and potentially add a .markdownlint file to this repo to enforce some restrictions on what features the webpack-contrib repositories can and can't use.
joshwiens and pierreneter
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4