A note on usability to the authors of the sites for open-source projects like this: my personal "user story" case study flows something like this: 1. I read th

A note on usability to the authors of the sites for open-source projects like this: my personal "user story" case study flows something like this: 1. I read the front page, skim the comment thread, and determine that this is roughly relevant to my interests. 2. I check that it's open source, because if it's not something I can install inside my firewall, my interest is terminated. (I expect this to be a quicker and easier check than almost any other validator, so I do it first.) 3. I search for the word "source" and "github" on the front page. No links? Hrm. 4. I search for the word "source" and "github" on the "get panamax" page. STILL no links? 5. ...? I guess next step is to copy the project name into google and look for the repo from there. But danger, project maintainers, danger: this is a step in the conversion funnel where I simply might get distracted and you might lose me before I make it farther. In all honesty, I am still going to try things from a binary release before I try building it from source -- I'm no huge exception to the basic truths about onboarding flow needing as much ease as possible. But I'm still going to look to see if the source actually exists first. In this case, the github can be found by searching for the project name, and also by following some of the documentation links, which jump to a wiki on github. But I want that flow. The "Panamax is an open-source product from CenturyLink" footer line would be a great place for a direct link to the source repo.