Thanks for posting, @julieqiu, my 2 cents:

Based on feedback that we've received, we understand that users find viewing the full package API useful, so the documentation index will be added back.

Great!! 🎉

At the same time, we’ve heard that having a sidenav is useful for navigating the documentation, especially when the documentation is very long. We plan to keep this feature as well. In the new design, the function and type sections will be closed by default, since having everything expanded can be overwhelming. When a user clicks on a function or type from the index, that section will auto-expand.

This sounds good and the mock GIF looks good as well. Initial reaction is that it's cool that the README is in the sidebar as well, and I feel like the header (with package version, refresh date, license, etc.) seems improved.

We want to create a consistent structure across different packages in the documentation section. Therefore, when a section in the documentation is empty, we will still display the section header (for example, "Variables"), along with a message indicating it is empty ("There are no variables in this pacakge.")

I think this is a great idea.

Next to each code block, we will be adding a copy button, so that users can easily copy and paste the code in that block.

Sounds neat; not major, but neat.

We also want to make jumping to the source identifier a more discoverable feature. To do so, if a block of code corresponds to a function, type or method, we will also include a source code widget. Clicking on that link will take users to the source code.

Sounds good; it would be cool to have an example as well. Linking into appropriate source locations is a very useful aspect of the docs, so expanding this is capability sounds like a move in the right direction, although it could perhaps be overdone with links in every nook and cranny.

Thanks again!

Thanks @tooolbox! That's great to hear :)

Sounds good; it would be cool to have an example as well. Linking into appropriate source locations is a very useful aspect of the docs, so expanding this is capability sounds like a move in the right direction, although it could perhaps be overdone with links in every nook and cranny.

Clicking on <> in screenshot under New Features would take you to the source code. On hover, both <> and copy icon will display a tooltip that provides context on what that icon does.

The redesign looks amazing! Can we also show how many downloads or go gets were there for the module as NPM, PIP etc also show it? I most of the time have to see git clones.

PS: I didn't want to open a separate issue for this.

@Delta456, glad to hear! If you don't mind, could you please raise a separate issue for this? While the feature you suggest sounds interesting, it doesn't fit under the umbrella of this design issue.

A preview of the redesign is now available on beta.pkg.go.dev! Give it a try, and please file an issue for any bugs.

See #41585 (comment) also for instructions on how to run the beta site locally.

This is now live on pkg.go.dev! See #41585 (comment) for details.