Unfortunately packages.json is not categorized and the tags are not based on structured classifiers, see https://github.com/nim-lang/packages/pull/339
I'd be happy to add browsing pages if we had categories or if the Curated-Packages had a machine-parsable format
lists each tag
Unfortunately not all packages have an optimal set of tags. For tagging, once my nimble publish was rejected due to too many tags, then I may had a nimble publish fail maybe because I typed the tags too slowly, then I tried gain with only one fast typed tag and nimble publish was successfull. So rtree package has only library tag I guess.
It would be fine if we could select from available tags when we publish a package, and maybe add a new one. And it would be nice if we could improve tags for our package. Maybe we can add tags to the .nimble file which each package has, so we have update tags with a git push?
And while we are talking about nimble -- the website entry seems not to work too nice. My rtree first got no website, while there is http://ssalewski.de/tmp/rtree.html. Many packages have website entry identical to url as your
$ nimble search aporia
aporia:
url: https://github.com/nim-lang/Aporia (git)
tags: app, binary, ide, gtk
description: A Nim IDE.
license: GPLv2
website: https://github.com/nim-lang/Aporia
which is useless noise.
Does at least nimble search description takes content from .nimble file? Seems not really to work for me.
And for nimble search, would be nice if we get latest version number available and date of last update.
That's one of the many reasons why I listed all the packages available in Nimble this summer, and documented them in a Google Sheet where you can use the Categories columns to regroup them.
I had suggested adding this information to Nimble and even proposed a pull request. Maintaining this information in a file, JSON or Google Sheet is not ideal though. A central repository like https://nimble.directory with a database would be the best to implement browsing by categories or displaying tag clouds.
Meanwhile I created the Curated Packages page to provide hierarchical categories. As a wiki page, it is more user oriented than tool oriented, and it does not show other information like descriptions or licenses...
The current tags are far from descriptive, while categories organize packages only along one arbitrary dimension.
A much better taxonomy in used in Debian by Debtags: https://salsa.debian.org/debtags-team/debtags-vocabulary/blob/master/debian-packages because it implements https://en.wikipedia.org/wiki/Faceted_classification
For example, nmap is tagged: admin::monitoring, implemented-in::c, interface::commandline, network::scanner, role::program, scope::utility, use::scanning