Ask HN: What are the benefits of having a project webpage vs. GitHub README?
Aside from Google Analytics are there any other benefits to having a project webpage for an open source project?
Are there any guides or statistics on the impact of having a webpage vs just a github repo?
I'm artistically challenged, so I prefer to just have a README.md, but wondering if I'm missing out by not doing so? I'm currently at ~450 stars with just readme and an asciicast gif: https://github.com/aelsabbahy/goss
However, I noticed other open source projects in this same category have webpages.
10 comments
[ 3.1 ms ] story [ 35.0 ms ] threadWhat I mean with linear:
With the repo you linked, I have to scroll past the file list, then the readme-header, then your twitter links, then the gif to even get to the introduction which tells me what I'm looking at. Next is installation, which has to be in the readme, but I don't care right now because I still want to see more details. With e.g. a navigation bar on the side I could have simply clicked on "Introduction" and then "quickstart" to get what I want.
And all GitHub repos look the same, so I won't recognize the site by it's design if I find it again a while later. Nothing memorable there.
That doesn't mean that a site should be a high priority for you, but these are some reasons why you might want one.