Add support for ignoring blocks of the readme #54

We could add https://github.com/remarkjs/remark-message-control

@issuehunt has funded $40.00 to this issue.

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

Good news is that we have already used remark-lint, which introduced remark-message-control.

Bad news is that our ruleIds, i.e. awesome/badge, contain a slash, which is invalid as parameter. See mdast-comment-marker. So we can't specify ruleIds. Followings do not work.

<!--lint disable awesome/list-item-->
- [foo](https://foo.com) - an invalid description.

@sindresorhus @transitive-bullshit What if we rename ruleIds i.e. awesome-badge? It may affect something.

I would rather fix remark's ability to recognize eslint-style rule names and keep our current rule naming convention than change our naming convention due to an unnecessary constraint within remark.

@wooorm what are your thoughts on allowing this style of lint rule naming within the remark / unified ecosystem?

Message-control and comment-marker conform to HTML, it's like attributes, which I think makes sense for markdown. Note that we also use colons throughout the ecosystem. To differentiate between the 'source' (in this case awesome) and the ruled. That's the reasoning here, but feel free to open an issue!

@wooorm Please check my PR, https://github.com/syntax-tree/mdast-comment-marker/pull/5 and another question https://github.com/unifiedjs/unified-message-control/issues/4.

I'm happy to switch to colons. The rule naming doesn't matter much and following the eslint-style rule naming is not import. @transitive-bullshit ?

Sounds good to me.

@sindresorhus has rewarded $36.00 to @chinesedfan. See it on IssueHunt

• :moneybag: Total deposit: $40.00
• :tada: Repository reward(0%): $0.00
• :wrench: Service fee(10%): $4.00