go: go.dev: 404 error should include a link to instructions on how to add a missing module

Just a note… these instructions aren’t actually actionable:

To add a package or module, simply fetch it from proxy.golang.org. 

I don’t know what “fetch it from proxy.golang.org” means or how to go about doing that. I’m sure I’m not the only one.

Also, avoid putting “simply” or “just” in directions, because they trivialize a step which may actually not be trivial for the person attempting it. Like, me, trying to figure out how to fetch something from a go proxy. Remove the word and it reads exactly the same, except if I don’t know how to do it, I don’t feel like I’ve been talked down to.

This change is now live.

Thanks Julie! I believe it would improve the user experience by providing a possible next step for someone who has dead-ended in a search.

On Fri, Feb 7, 2020 at 11:16 AM Julie Qiu notifications@github.com wrote:

At the moment it only appear on the 404 page: http://pkg.go.dev/github.com/doesnot/exist

We can add the link on the search results page too when there are no matches if you think it would be helpful.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/golang/go/issues/36986?email_source=notifications&email_token=AACY7VLQ2XTAZICYZJKVP23RBWCMTA5CNFSM4KO3JAF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELDSQQI#issuecomment-583477313, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACY7VJXYZ6JWXQXHTSN2VTRBWCMTANCNFSM4KO3JAFQ .

–

• from mobile

Eight years of people using godoc.org and it working exactly that way is why I think it should work that way. Also you assume that every package is widely used, many are hyper specific and may only be used by people that have a corporate proxy… Until someone tries to view the docs here.

I just honestly don’t know why you wouldn’t just try to fetch it.