3
5 Comments

Should I build the Github Insights tool?

Description of the tool:

  1. Put your repo link or repo name
  2. The tool will spit out stars, contributors, commits.
  3. You can also add another repo for comparison.

Why?

  • This is a part of the content strategy that I am working on. By building this tool, I am hoping to gain backlinks, improve SEO etc.

I know GitHub already has insights section in the repo but it doesn't go into low-level information like this.

What do you guys think?

on November 29, 2020
  1. 1

    Developer analytics is an extremely competitive field with robust free offerings, particularly https://go.codeclimate.com/velocity-free-for-teams

  2. 1

    I can see this being an SEO play. Where you generate all of the comparisons a head of time and make ti SEO friendly, so people come to you via search.
    But really I don't see tons of added value except maybe if you build a rich tool to compare code quality, activity, issues trends etc...

    1. 2

      To be honest the main reason I am doing this is SEO. But to help on the SEO there should be at least some proper value-add so that I can generate backlinks to bump my rank.

  3. 1

    I noticed there are two types of authors on GitHub. Bored enthusiasts with pet projects that nobody cares about. And serious developers with serious projects. First category might use something like that. Second category most likely won't unless it provides unique and actionable insight.

    1. 1

      Sure. But how about professional developers? They might use this tool to compare two open source projects to make a decision on which one should they use. Let's say if they are confused between choosing a datepicker for their project. They can hop into this tool and then find insights about which library is more maintained, which has more issues etc, and then make a decision? What do you think?