Jo Sprague

Seems that this project isn't actively maintained anymore. @Hacker0x01 is it up for adoption?

@martijnrusschen I'm willing to open a PR. I was waiting for some feedback from the maintainers about which type of PR they would merge for this. I can do one...

Once I get a response from the package maintainers about which type of PR they would prefer I'll open one. Until then, I'm closing this issue.

Hi @RichardLitt is there a linter already in progress? I started working on one that uses `remark` and `remark-lint` before discovering this conversation. Here's what I've built so far: https://github.com/SparkartGroupInc/quality-docs...

I've updated quality-docs to use remark's defaults and to accept a configuration file to override the default rules. The configuration file wouldn't have to be used in the case of...

The default I was referring to was remark's default. Seems reasonable to me to try to make remark-lint's defaults match the standard-readme spec. I'm assuming it's already pretty close, and...

Ok, in that case I can add a set of rules to `quality-docs` that modifies the `remark-lint` defaults to check the `standard-readme` spec in a lenient way that helps people...

I'll have to put this on the back burner for now, but now that I've gotten more familiar with the project, I'm thinking that `quality-docs` could be used as a...

If someone wants to tackle this before I get back to it, feel free to open issues or PRs in `quality-docs` for any features that need to be added.

From my side, I'm working on a different team now, and don't have time to work on this. But feel free to fork what's there and continue working on it....