Just a suggestion... If you are going to have a big list of icons the first thing that comes to mind is "Click on one". Analysis of programming language(s) use

Just a suggestion... If you are going to have a big list of icons the first thing that comes to mind is "Click on one". Analysis of programming language(s) used isn't hard given its built into the GitHub api: https://developer.github.com/v3/repos/#list-languages https://developer.github.com/v3/repos/#list-languages So if you allowed an "import Github Repo option" then linked those icons to the "examples/repositories/snippets" in those languages that would help. You already seem to be able to designate icons-per-project/snippet so you shouldn't need to add much beyond a hyperlink on the icon that scrolls to the first appropriate projects and/or allows the user to designate the project to scroll to. I'd say have a page listing the relevant projects as well by technology [e.g. A "Would you like to know more...?"] but I'm not sure that should be the default behavior. Similarly, I'd encourage/enforce linking to test suite(s) and/or documentation as a requirement to list anything larger than a snippet. That might be a bit too opinionated but I think it encourages "new" developers to get into the right practice of having some sort of documentation [even if it is just a test suite].