Enforce Generator Categorization

[evenstensberg]

Summary

It would be convenient to categorize generators at the search page so that library authors can specify specific grammar for their generator names. This way, it's easier for those authors to create ecosystems for their generator based logic.

Why categorization

Categorizing dependencies isn't only good for finding the right generator, but also for authors. Authors have the possibility to have specific namespaces for their generators and this way creates a viable ecosystem for their libraries. Furthermore, specifying categorizes will allow authors to directly link to the generators related to their projects.

Example

babel-generator-react, first case specifies project, second and third one feature/target ( which is normal convention )

[SBoudrias]

Hey @ev1stensberg! Your suggestion isn't clear to me. Could you maybe try to rephrase and provide more specific example?

[evenstensberg]

In case with webpack-cli, we're trying to categorize generators so that we can show them at our website. If you have something like webpack-addons-<name>, we would add it to our docs page ( if we can query from your page )

Did I phrase myself correctly?

[SBoudrias]

Would it make sense to ask your community to tag their generators with a specific "label" so it makes searching easier?

For example, we only search through packages that are named generator-**** AND are labelled as yeoman-generator.

[evenstensberg]

we're asking them to tag it webpack-addons, but I guess we can query this on our own. It would be nice if yeoman had the same option, cause then people could look up at the official page for the generators