Make the spec clear about it being an extension mechanism
Open
Nobody has claimed this yet.
class 3
pr exists
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 14d 42m
- Merged PRs (30d)
- 2
Description
The spec isn't currently clear about it being an extension mechanism and defining a couple of extensions. The spec should be updated to make it clear.
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
The issue does not name a file, test, or spec section; start by locating the repository's specification source and reviewing its current extension-related text. Done means the specification clearly describes itself as an extension mechanism and defines two extensions.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100