Clarification (simplification) of tool categories
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 87
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
User Story
As a user, I need to orient in tool categories quickly. Currently, some categories are synonymous. Some categories are fine-grained (such as data validators), while others are coarse (Server, Security, Testing).
As a tool provider, I want to know which category to pick or which to check if my product is already listed.
Detailed Requirement
I would suggest setting categories according to API lifecycle phases plus Security and Learning, which relates to all of them:
- Design
- Mocking / Virtualization
- Implementation
- Testing
- Documentation
- Deployment / Runtime
- Security
- Learning
Maybe the "Use Case Area" (or an apter word) would describe the categories best.
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 identify files, tests, or entry points to inspect. Start by locating where tool categories are defined and displayed, then confirm the category model and its use cases with maintainers before changing it.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100