Clarify "classifiers"/"filters" wording

[brainwane]

Per conversation on python-list (1, 2), the "Filter projects" section on the left-hand side of the page is not clearly related to the "list of classifiers", and

"Classifiers" is what the relevant package metadata is called, but it's not exactly what the average user would refer to that data as.

What can we do to both serve people who don't know what classifiers are and people who know that term and are specifically thinking in terms of classifiers?

[brainwane]

#3410 adds an FAQ entry about adding a new classifier. As we get more consistent about talking about filters and classifiers, I'd like us to update this wording or add another FAQ to clarify where the "Trove"/"classifier" wording and master list originated.

[drunkwcodes]

Maybe introducing https://github.com/nepsilon/search-query-parser and letting users to type search queries like "Framework:Django" in the search bar will help.

Because we are familiar with Google search and Github search.

[nlhkabu]

We could do something like this:

Filter by classifier ℹ️

Hovering your mouse over the icon could then launch a tooltip that describes what a classifier is.
@brainwane could you provide some appropriate text for this?

[brainwane]

Gregory Ewing brought up "Categories" which seems, to me, a very sensible name for what we're talking about.

Here's text for the tooltip:

Each project's maintainers give PyPI a list of "trove classifiers" to use to categorize each release, describing who it's for, what systems it can run on, and how mature it is.

[brainwane]

(Background, in case anyone wants to add an FAQ item: the original list of trove classifiers was drawn from Freshmeat and SourceForge lists. The relevant standard is the Core Metadata Specification and the best documentation to point new maintainers to is this part of PyPUG.)

@drunkwcodes that's an interesting idea! I'm going to mention that in #727. Thanks for bringing it up.