Update language around "Addins"
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Description
Per @CharliePoole in https://github.com/nunit/docs/pull/495#discussion_r464011979:
I wrote the first drafts of this with plans for eventually implementing addins, which had a different meaning in the docs. They were more complex and involved cooperating extensions.
In fact, we never impelmented it. Issue nunit/nunit-console#20 is still there but I don't think it's getting any attention.
Anyway, I think we're stuck with the terminology "addins file" but otherwise we should talk about extensions rather than addins.
This is an issue to track a quick comb-through of the site language in general around this term.
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
Review the site's language around “Addins,” using the discussion in nunit/docs#495 and the linked NUnit console issue for context. Update general terminology to use “extensions” where appropriate, while preserving the established “addins file” wording; the site-wide wording review is complete when no unintended uses remain.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100