You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'll be redesigning pkg.go.dev based on feedback received over the last year. This is the third in a series of issues about plans for the pkgsite/design-2020 milestone. Comment below with any feedback or suggestions related to this issue!
Overview
There are multiple ways in which “latest” can be defined for a path. In order to better express various relationships, we will use the following terms:
Series: 1 or more modules that are major versions of each other
Latest minor version: the latest minor version of a module containing a path, according to the cmd/go definition. This is also referred to as the “latest” or “@latest” version.
Latest major version: the latest major version in a module series.
If the latest major version does not have any tagged versions, but an earlier version does, pkg.go.dev will default to the earlier version as the “latest” major version.
Design
Pkg.go.dev will continue to use the following:
A “Latest” badge to indicate whether a user is viewing the latest minor version
A banner to indicate when a user is not viewing the latest major version
Note: This image is a mock, so the data may not accurately represent the exact contents of this package.
We plan to also use the banner style to indicate other information related to surfacing the “latest” version, such as when a path is not present in the latest version of the module.
If a path exists in the latest version of a module, pkg.go.dev/<path> will always show the contents for the latest version of the containing module.
I guess this is fine as a fallback, if v3/syntax doesn't exist as a package. But if the same sub-package exists in the new major version of the module, I think we should directly link there. Otherwise I have to go into "directories" and find it again.
These changes are live on pkg.go.dev, and all related issues have been addressed except flag packages that are no longer present in the latest version of the containing module, which is tracked at #37631.
We'll be redesigning pkg.go.dev based on feedback received over the last year. This is the third in a series of issues about plans for the pkgsite/design-2020 milestone. Comment below with any feedback or suggestions related to this issue!
Overview
There are multiple ways in which “latest” can be defined for a path. In order to better express various relationships, we will use the following terms:
Design
Pkg.go.dev will continue to use the following:
Note: This image is a mock, so the data may not accurately represent the exact contents of this package.
We plan to also use the banner style to indicate other information related to surfacing the “latest” version, such as when a path is not present in the latest version of the module.
If a path exists in the latest version of a module, pkg.go.dev/<path> will always show the contents for the latest version of the containing module.
Related Issues
The text was updated successfully, but these errors were encountered: