Fill out the API documentation
Open
documentation
- Dominant language
- JavaScript
- Stars
- 441
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
Including browsers, so we can talk about where the API is weak.
Contributor guide
Research direction
The issue names no files or tests. Start by locating the existing API documentation and browser-facing entry points in this JavaScript repository; document the API sufficiently to discuss where it is weak, including browser coverage. Done means the API documentation is filled out enough to support that review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100