Adding implementations to the feature list
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 336
- Forks
- 63
- Avg merge
- 12h
- Merged PRs (30d)
- 8
Description
In a future iteration, it would be nice to have an implementations list as part of the feature list. This way people can quickly see where something is implemented. This picks up on the discussion in #11
@chicoxyzzy mentioned the following:
MDN has some data on features support by browsers. IMO it will be good for both MDN and this project if TC39 website will use data from MDN and contribute back to it.
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 discussion in #11 and the referenced MDN browser-support data. Define the scope and data source for an implementations list, then confirm that the feature list can show where each feature is implemented and that the relationship with MDN is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100