We are excited to launch a new search experience on pkg.go.dev. pkg.go.dev These changes were motivated by feedback we’ve received about the search page, and we hope you enjoy them. This blog post provides an overview of what you can expect to see on the site. feedback we’ve received Grouping related package search results Search results for packages in the same module are now grouped together. The most relevant package for the search request is highlighted. This change was made to reduce noise when several packages in the same module may be relevant to a search. For example, searching for “markdown” shows a row listing “Other packages in module” for several of the results. Results for different major versions of the same module are also now grouped together. The highest major version containing a tagged release is highlighted. For example, searching for “github” shows the v39 module, with older versions listed as “Other major versions”. Lastly, we have reorganized information related to imports, versions, and licenses. We also added links to these tabs directly from the search results page. Introducing symbol search Over the past year, we have introduced more information about symbols on pkg.go.dev and worked on improving the way that information is presented. We launched the ability to view the API history of any package. We also label symbols that are deprecated in the documentation index and hide them by default in the package documentation. With this search update, pkg.go.dev now also supports searching for symbols in Go packages. When a user types a symbol into the search bar, they will be brought to a new search tab for symbol search results. There are a few different ways in which pkg.go.dev identifies that users are searching for a symbol. We’ve added examples to the pkg.go.dev homepage, and detailed instructions to the search help page. search help page Feedback We’re excited to share this new search experience with you, and we would love to hear your feedback! As always, please use the “Report an Issue” button at the bottom of every page on the site to share your input. If you’re interested in contributing to this project, pkg.go.dev is open source! Check out the contribution guidelines to find out more. contribution guidelines Julie Qiu Julie Qiu This article is available on The Go Blog under a CC BY 4.0 DEED license. This article is available on The Go Blog under a CC BY 4.0 DEED license. The Go Blog The Go Blog Photo by Agence Olloweb on Unsplash Photo by Agence Olloweb on Unsplash Agence Olloweb Unsplash

Unsplash

The Search Experience on pkg.go.dev: How It Works

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

A Beginner's Guide to Code Coverage for Go Integration Tests

104 Stories To Learn About Go

The Noonification: How to Use React to Replace useEffect (12/31/2022)

3 Golang Pitfalls Every Developer Needs to Know

207 Stories To Learn About Golang

2 Error-Free Options for Decimal handling in Golang

A Beginner's Guide to Code Coverage for Go Integration Tests

104 Stories To Learn About Go

The Noonification: How to Use React to Replace useEffect (12/31/2022)

3 Golang Pitfalls Every Developer Needs to Know

207 Stories To Learn About Golang

2 Error-Free Options for Decimal handling in Golang

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps