Open hornta opened 6 years ago
A stepping stone would be to add some star badges. That would help us keep the sort order up to date, and would also help developers find things in the meantime.
We can run some sort of cron job (daily on CI?) to create the list with stars. Basically a script to generate markdown on CI and commit to the project
I'd actually prefer to sort by last update, and simply display the star count. I think all of those lists should be sorted like this, but I never see it so I guess it's just me
all of that is fairly complicated, since it's just a markdown file, but if you have the inclination to do so, I feel like it would probably be best to transform the list to a json or something, and the markdown to be generated e.g. daily from that data, with the PRs only going to the data.
PR definitely welcome if you want to work on this
This would be cool...also would be cool if there were deeper categories..like components is huge...and some things can be grouped...like material-ui components, table components, etc....
if you make a PR to split them up in categories, I'd definitely approve @patrickcurl, however sorting by stars is not practical, since the list is static, and stars aren't
I mean by 'this would be cool' ... sorting by last update, and display star count, from a json version... could even have a website where people can simply submit a new item, that will add to the json array, and repopulate the list's markup automatically... that way you wouldn't even have to worry about PR requests... I might tinker w/ that after I finish up a few projects I'm working on.
I had an idea a looong while ago to use a badge to combine some key stats for each project. It would really help with a list like this which is long and often out of date.
I ended up joining Shields and I'm excited that I have a little time to revisit the idea.
We could pick two or three key metics and render them like this:
That's one I designed a while ago, which shows stars, forks, and issue count.
Implementing this on the markdown side will require a link next to each item. That seems a little unwieldy so I'm not completely sure this is feasible. Seems high enough impact, though that it might be worth pushing forward with this and seeing if we find something that works well enough.
Some metrics we might want to show:
What seems the most valuable?
Looks like a nice idea to me! Easy to have a wrong metric for the peer dependency though, so maybe we can only show that if it's "positive". Otherwise the exact design for the badge seems a bit odd with sizing, maybe that can be done differently?
Easy to have a wrong metric for the peer dependency though, so maybe we can only show that if it's "positive".
👍
Otherwise the exact design for the badge seems a bit odd with sizing, maybe that can be done differently?
Could you elaborate? I think it can be improved, just trying to think about what to focus on.
Any thought on whether downloads or stars is a better popularity metric? Or what makes a good activity metric?
the sizes of the icons don't seem consistent is what I meant.
Activity -> downloads Popularity -> stars
I'm not fully sure though, on Yarn I decided to show both
Downloads are a measure of popularity, too. They show how many people are using the project.
For activity, I'm trying to get at what's happening in the project. Does it have outside contributors, recently merged PRs, a recent release?
Possible to make all react components sorted by stars or is that hard? It is so frustrating trying to find a decent library and sorting by stars makes it easier.
Maybe even sort by number of issues or the last commit.