content/static: add readme headings to the sidenav

This change adds the readme headings to the outline
in the sidenav and unifies the navigation tree into
a single accessible structure.

Styles within the tree are based on the accessiblity
tree structure. This will make it easier to see when
updates to the tree are inserted incorrectly because
they'll be matched by visual breakages on the page.

Sidenav and readme click handlers are updated to
ensure that when an outline item is clicked the
corresponding content is visible.

Change-Id: Ie6062c24f37bec9fffe242aa1398ec815606c613
Trust: Jamal Carvalho <>
Run-TryBot: Jamal Carvalho <>
TryBot-Result: kokoro <>
Reviewed-by: Julie Qiu <>
11 files changed
tree: 70441c6ad1c41420aa07b925932fa45aba2e34f2
  1. .dockerignore
  2. .gitignore
  3. .prettierignore
  4. .prettierrc.yaml
  9. all.bash
  10. cloudbuild.yaml
  11. cmd/
  12. content/
  13. devtools/
  14. doc/
  15. go.mod
  16. go.sum
  17. internal/
  18. migrations/
  19. third_party/

A site for discovering Go packages is a website for discovering and evaluating Go packages and modules.

You can check it out at

Roadmap launched in November 2019, and is currently under active development by the Go team.

Here's what we are currently working on:

  • Design updates: We have some design changes planned for, to address UX feedback that we have received. You can expect a more cohesive search and navigation experience coming soon. We plan to share these designs for feedback once they are ready.

  • redirect: Longer term, we are working towards redirecting traffic to We know that there are features available on that users want to see on, and we want to ensure that we address these. We’ve been keeping track of issues related to redirecting traffic on Go issue #39144. These issues will be prioritized in the next few months. We also plan to continue improving our license detection algorithm.

  • Search improvements: We’ll be improving our search experience based on feedback in Go issue #37810, to make it easier for users to find the dependencies they are looking for and make better decisions around which ones to import.

We encourage everyone to begin using today for all of their needs and to file feedback! You can redirect all of your requests from to, by clicking Always use at the top of any page on


If you want to report a bug or have a feature suggestion, please first check the known issues to see if your issue is already being discussed. If an issue does not already exist, feel free to file an issue.

For answers to frequently asked questions, see

You can also chat with us on the #tools slack channel on the Gophers slack.


We would love your help!

Our canonical Git repository is located at There is a mirror of the repository at

To contribute, please read our contributing guide.


Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.