Context document
Open
Nobody has claimed this yet.
report
- Dominant language
- HTML
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We should probably have a context document for the new terms, so people can start experimenting with them.
I think using semantically-version-stamped contexts can be really helpful; see the miscellany context for an example.
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 reviewing the linked miscellany context, especially its version-stamped URL pattern, and identify the new terms that the context must cover. Done means a context document exists for those terms and follows a clearly versioned approach; the issue does not name a target file or test.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100