Have a checklist of things to consider for each change
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- PR merge metrics
- PR metrics pending
Description
In https://github.com/whatwg/html/issues/1937#issuecomment-257804979 @therealglazou says
first, I think this should NOT have been merged in issue #1945 without some metrics on impacted Wysiwyg editors...
We should do better in the future.
Maybe we can have a checklist of things we need to consider for future changes to HTML, so we remember to consider impact of editors, learnability, accessibility, and so on.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced comment in issue #1937 and the discussion in issue #1945 to understand the change that prompted this request. A completed contribution would define and agree on a reusable checklist covering impacts such as WYSIWYG editors, learnability, and accessibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100