A copy of this list with number of stars/forks/issues provided

[kaxap]

Hi, I made a script to scrape this awesome list and augment each repository item with its stats, namely number of stars, forks and open issues.

Here is the link to augmented README.md.

I do agree with the comments in the previous discussions that number of stars/forks do not indicate the quality or usefulness of repos very well. Number of open issues on the other hand can tell a lot.

Anyways, it helped me to navigate through the list.

---

IssueHunt Summary

Backers (Total: $20.00)

• rororofff ($20.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[kamilsk]

Nice, @kaxap!

UPD: kaxap/awesome-go-processed#1, kaxap/awesome-go-processed#2

[kaxap]

@kamilsk Thanks!

Added last update as well.

[matrixik]

I would prefer to see this next to main README and no added to it. There could be link to it on top of README.

[avelino]

I would prefer to see this on site (awesome-go.com) not on README, build site on:

• merged on master (as it is today)
• automatic 0am (crontab by example)

On README polluted (visually)

[Ma124]

I created something similar which is already integrated with the old build system: commit diff

But if you start the docker container now you need to provide the -e GH_TOKEN=<ghtoken> where <ghtoken> is generated here.
You need the token because of the GitHub API Ratelimiting.

It looks like this right now but of course we can change the CSS:
A compiled version on my page

[Ma124]

@avelino @kaxap What do you think about this?

[kaxap]

@Ma124 I think it's a great idea! Personally, I had issues with the markdown's layout since I had added too many new columns. In this case I am sure @avelino can check your CSS modifications as well.

[Ma124]

@kaxap I'm planning on making the tables sortable, adding octicons after the numbers in the columns (star, fork etc) and to provide a button to hide individual columns

[Ma124]

@avelino @kaxap

I added sorting and icons

Is this better?

[kaxap]

@Ma124 yeah, definitely. Looks redundant on a short table but long table absolutely needs this, imho.

[IssueHuntBot]

@rororofff has funded $20.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[Ma124]

@rororofff I'm still working on it. I've made Awesome Framework

[Ma124]

#2445

[avelino]

#2445

That way we don't have indexing on Google, read more: #983

[Ma124]

Why that? Isn't the result on awesome-go.com the same?

[avelino]

Why that? Isn't the result on awesome-go.com the same?

People usually search for some library Go on Google, have the content in render (HTML) makes Google find the awesome-go.com

[Ma124]

I'm really sorry but I still don't get it. How could you solve that?

[Ma124]

@avelino
I've read #983 several times now and the only SEO requirement you describe is that the file is put in the gh-pages branch and my pull request does that: https://github.com/Ma124/awesome-go-fork/tree/gh-pages .

Sorry if I'm annoying but I'm still not sure what the problem is so I can't fix it.

[Ma124]

@avelino I wanted to re-ping this issue as the changes still would be useful, and could help with a lot of the other open issues.

Worth mentioning is that my proposal does render everything to a static file on gh-pages and therefore should not impact SEO ratings.
The sorting is done on the client-side instead. The program pulls the statistics, if triggered manually on Travis CI or automatically on every commit, and writes them to the static HTML file. These processes are handled by the Awesome-Framework which has an A+ Go Report Card () and a high unit test coverage ()

You can try it out on my site.

These changes would help with #1446 and #2649 because you could, for example, sort by decreasing time since the last commit and find the projects that aren't maintained anymore more comfortably. It would also be trivial to add links to the GoReportCard and GoDoc.

The extraction of information from the markdown document could aid with #1548, too.

[avelino]

Hey @Ma124, this being in html rendering I find valid (as discussed here #3163 #3154 (comment), but not in the readme/github render), can you assume this implementation along with this issue?

[Ma124]

@avelino yes, I'd be very happy to do so.