There are a lot of ways we can improve docs tooling to make the docs team more efficient and make our docs better.
We need a new docs manifest parser/generator! Here's what I'd like to see:
toc.json as the source of truth, with manifest.json being built as a totally separate/machine-generated artefact.~manifest.json should pull page titles from the markdown, rather than needing to set it in multiple places~root-manifest.json anymore~toc.json should be extended to provide a wildcard option, so auto-generated docs don't need to be explicitly listed inside the file, and can be included in the correct place inside the handbook outlineI'd also like to propose the addition of a markdown linter. This is partly to aid the parser, for example to ensure that all docs have an h1 title, but also to improve the consistency of our markdown formatting (consistent heading syntax, line breaks, wrapping, etc.). Right now it varies pretty wildly and having a consistent format would be super valuable.
markdownlint and remark-link seem like the leading candidates. Does anyone have an opinion or experience on either of these?
To be clear I don't want to lint grammar/spelling, just the markdown _syntax_.
A lot of this has been done. Right now the two missing pieces are wildcard placeholders inside toc.json, and markdown linting.
Pending any strong opinions I think markdownlint and remark-lint. Both seem powerful and reasonably well-maintained. Anyone see anything in either package that makes it the better choice?
remark-lint looks good to me with all the plugins to generate toc, process links
Remark definitely seems a little more pluggable and customisable. I might work on a POC over the weekend 馃憤
Nice, that would be awesome to have it included in the workflow. Lint all the things :)
Most helpful comment
Remark definitely seems a little more pluggable and customisable. I might work on a POC over the weekend 馃憤