webdiscus
webdiscus
@davidmurdoch Thanks for clarifying. You are right, I will add the checking for this use case.
@davidmurdoch the issue is fixed in the v3.17.2
Hello @vralle, Thank you for your efforts to improve the documentation. Over 3 years, the documentation has truly grown to incredible sizes. At the same time, I tried to describe...
> removed id attributes from named anchors many years ago I already made links without `id`, but I encountered problems either on NPM or on Github itself: without `id` attribute,...
As recommended on [stackoverflow/Cross-reference (named anchor) in markdown](https://stackoverflow.com/questions/5319754/cross-reference-named-anchor-in-markdown): > Markdown doesn't seem to mind where you put the anchor point. A useful place to put it is in a header....
80 chars per line was OK for the 198x era, but not in the 4K monitor era ;-) 80 chars for markdown containing many links is too little. I know,...
In any case I will merge your PR with markdown linting as is. Then we can improve and optimise it.
> The recommendation to keep line lengths in Markdown files (and other text files) under 80 characters is rooted in both historical and practical reasons Even - _historical reasons_ but...
> > We can write anchor in a headline > I'm not sure. ok, at least for me locally, `markdown-it` renders anchor in a headline into html correctly and it...
Yes, that's a good idea. Here is the [html-bundler-docs](https://github.com/webdiscus/html-bundler-docs) repo for the documentation.