Curated list of top generators

[SBoudrias]

We often get comments about the fact there's too much choices of Yeoman generators. I think that is true, with >1500 generators, there's a lot of choices!

I was wondering if it would make sense for us to curate a list of top quality generators we know are maintained. Like on npm, we could curate a list of our top ~9 generators or something like that on yeoman.io frontpage.

Couples related questions:

• What would be our criteria?
• How often should we review the list?

[ruyadorno]

👍 awesome idea

we should leave this here: http://en.wikipedia.org/wiki/The_Paradox_of_Choice

[ragingwind]

NPM download count could be one of the option

[arthurvr]

NPM download count could be one of the option

We can take a look at the download count, but popularity shouldn't be our main consideration. IMHO we should focus on listing good generators, not popular ones. In the original comment in this issue: "top quality".

[stefanbuck]

we should focus on listing good generators, not popular ones.

Good point @arthurvr 👍

• Is the generator up to date (which generator version is used).
• The average response time for issues / PR's

[sindresorhus]

We can take a look at the download count, but popularity shouldn't be our main consideration. IMHO we should focus on listing good generators, not popular ones. In the original comment in this issue: "top quality".

👍

[ragingwind]

In my point of view, "Top quality" is related to popularity. I agree that popularity is not major option to criteria for selection. however, I think that we don't need to disregard popularity decisively. If there are good many generators in competition , we have to choose from one of them, popularity could be one of the option.

[addyosmani]

I'm 👍 on this idea, but we'll need come up with an agreed upon list of criteria. If we were looking at what we know to be up-to-date, well maintained etc. we could easily fall in the trap of just recommending generators we officially maintain. I imagine the goal of this is not that :)

[SBoudrias]

I think there's a couple factors we need to consider:

1. Generator quality (is it using last versions, is it using good practices). How: review code
2. Generator community (is there an active community offering support and is there a contributors team tackling issues raising up). How: review # of stars, # of downloads and the github pulse tab
3. Diversity (it is important for us not to list 9 JS frontend framework. We want to showcase the diversity of the Yeoman generators ecosystem). How: Manually filtering if we have too many angular generators. Or maybe we could present platforms with Yeoman generators and bundle multiple generators under each platform/framework?

[arthurvr]

Those criteria seem like a really good start @SBoudrias. 👍

[zckrs]

👍 @SBoudrias
work in progress ?
Or I can try to contribute.

[SBoudrias]

I don't think anyone started to work on this. Any help is welcomed.

[mischah]

Possible addition to the good criterias of @SBoudrias

1. Generator quality (is it using last versions, is it using good practices). How: review code

• Does it have tests with a good coverage (> 95%?) running on an CI (and does it build)
• Does it follow semver (Plus does it have any kind of changelog)

Just in case this issue is still a thing 😘

[mischah]

Plus npms offers kinda neat quality metrics https://npms.io/search?q=generator-chrome