On https://golang.org/pkg/, only the packages from the standard library are included, so it is viable to list every single package in an exhaustive list on the front page. On https://pkg.go.dev, there are many more packages that can be discovered, so exhaustively listing them all on the front page is not viable.

Do you think something else can be done? Or is your suggestion to make it easier to understand how to find a list of packages that are only in the standard library?

One more question. Are you already aware of the https://pkg.go.dev/std page, which has a "Packages" tab that lists all packages? I'm asking because if you weren't aware of it, it's possible that making that page more discoverable can be a way to improve the situation.

/cc @julieqiu @jba @jamalc per owners.

Do you think something else can be done? Or is your suggestion to make it easier to understand how to find a list of packages that are only in the standard library?

Yes I was suggesting making it easier to discover standard library packages without needing to know about their existence in the first place.

https://godoc.org lists the top 25 packages by popularity and has links to the standard library, golang.org/x packages, and various search filters on Github. This level of discoverability is nice, in my humble opinion.

Given that a flash message on https://godoc.org is currently offering to "Always use pkg.go.dev" instead of godoc.org, it would be great to keep this level of discoverability in the new offering.

One more question. Are you already aware of the https://pkg.go.dev/std page, which has a "Packages" tab that lists all packages? I'm asking because if you weren't aware of it, it's possible that making that page more discoverable can be a way to improve the situation.

I wasn't aware of this page. Thank you for pointing it out.

For the purposes of making this issue actionable, I second your suggestion of linking to https://pkg.go.dev/std from the "Discover Packages" page.

I'd like to give a strong +1 for this issue. I would really like to see the standard library documentation explicitly linked somewhere instead of hidden behind the search functionality.

Right now, my solution to this problem is having a bookmark that takes me to https://pkg.go.dev/std -- but I'm an experienced Go user, and I knew that that was what I was looking for, and that it's the standard library documentation. From the perspective of a new user of any language, I like to know what packages are available in the standard library, and right now that information is not intuitive to find on pkg.go.dev at all.

In addition to the proposed option of adding some kind of link to the main "Discover" page, I would also recommend adding a "Standard Library" link under "Packages" in the page footer (where the red box is in this screenshot):

While putting the link in the footer isn't ideal, it would be a lot better than not having it anywhere, and I'm honestly surprised every time I go to pkg.go.dev without using my standard library bookmark that it's not there already.

/cc @jinhongy @fflewddur for UX input

Thanks for the feedback. We are in the process of unifying the experience for golang.org and go.dev, with the new design, we will include the standard library link on the secondary navigation on top, which I think will solve this issue.

The new unified experience was launched today, but there still doesn't seem to be a link to the standard library overview https://pkg.go.dev/std in the navigation.

Change https://golang.org/cl/366577 mentions this issue: _content: adjust footer

The updated footer seems to only affect go.dev but not pkg.go.dev?

Change https://golang.org/cl/370994 mentions this issue: static/shared: adjust footer

Closing as done