Skip to content

Introduce rule documentation #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Dec 28, 2022
Merged

Introduce rule documentation #26

merged 8 commits into from
Dec 28, 2022

Conversation

khiga8
Copy link
Contributor

@khiga8 khiga8 commented Dec 23, 2022

#25 must be reviewed first! This PR should be rebased after #25 is merged.

Fixes: #12

We don't currently have documentation to the rules. This PR introduces a documentation folder, documentation for each rule, and updates the linter error message to link to the rule doc so that consumers have more context to fix the rules.

@khiga8 khiga8 requested a review from a team as a code owner December 23, 2022 16:33
@accessibility-bot
Copy link
Collaborator

👋 Hello and thanks for pinging us! An accessibility first responder will review this soon.

  • 💻 On PRs for our review: please provide a review environment with steps to validate, screenshots (with alt text), or videos (with description following) demonstrating functionality we should be checking. This will help speed up our review and feedback cycle.
  • ⚠️ If this is urgent, please visit us in #accessibility on Slack and tag the first responder(s) listed in the channel topic.

```

```md
<!-- Mark decorative images with an empty string -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was this comment supposed to go above the first "correct" example?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, thanks for catching. Fixed!

"scripts": {
"publish": "npm publish --access public --@github:registry=https://registry.npmjs.org",
"test": "npm run lint && jest",
"lint": "markdownlint-cli2 \"**/*.{md,mdx}\" \"!node_modules\" \"!test/example.md\" && eslint .",
"lint": "markdownlint-cli2 \"**/*.{md,mdx}\" \"!node_modules\" \"!docs/rules\" \"!test/example.md\" && eslint .",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am excluding our docs because I don't want it to flag our "incorrect' usecase rules. 😅

Copy link
Contributor

@ericwbailey ericwbailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One suggestion, but it's not blocking merge!

Comment on lines +15 to +21
```md
![Screen Shot 2022-06-26 at 7 41 30 PM](https://user-images.githubusercontent.com/abcdef.png)
```

```md
<img alt="Screen Shot 2022-06-26 at 7 41 30 PM" src="https://user-images.githubusercontent.com/abcdef.png">
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like how you provided examples of both Markdown and HTML techniques!

Co-authored-by: Eric Bailey <ericwbailey@users.noreply.github.com>
@khiga8 khiga8 merged commit 23e2eb6 into main Dec 28, 2022
@khiga8 khiga8 deleted the kh-introduce-docs-folder branch December 28, 2022 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add docs for each rule
4 participants