Add deprecated and new-feature "badges"
Open
Nobody has claimed this yet.
documentation
- Dominant language
- JavaScript
- Stars
- 2.9k
- Forks
- 461
- PR merge metrics
- No merged PRs in 30d
Description
Some sort of small HTML (web component? probably not) that we can apply to documentation.
```
Dust allows Promises to be passed as part of your context. When a Promise is found...
2.6.2
Dust allows Promises to be passed as part of your context. When a Promise is found...
```
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating how Dust documentation is authored and rendered, then determine how a deprecated or new-feature badge with a version should be applied; done means both badge types can be used consistently in documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100