Group related plugins
Metadata
Current evaluation
No evaluation has been recorded for this issue yet.
Issue body
### What needs to get done
This should at least be done for documentation, but could also be reflected in the organization of the source code.
Proposed organization:
1. Built-in
1. dump
1. nil
1. Multi-language
1. ant
1. autotools
1. bazel
1. cmake
1. colcon
1. jlink
1. make
1. meson
1. qmake
1. scons
1. .NET
1. dotnet
1. dotnet_v2
1. Go
1. go
1. go_use
1. Java
1. gradle
1. java
1. maven
1. maven_use
1. JavaScript
1. npm
1. npm_use
1. Python
1. poetry
1. python
1. python_v2
1. uv
1. Ruby
1. ruby
1. Rust
1. cargo_use
1. rust
```
### Why it needs to get done
The number of plugins exceeds what's reasonable for a flat list. As they are sorted alphabetically, users can miss relevant plugins because they stop scrolling, e.g. choosing to use the Python plugin without realizing a uv plugin exists.
Evaluation history
No evaluation history available.