pkgsite

Massively underrated. It's actually used to build the pkg.go.dev website itself. https://github.com/golang/pkgsite

What I like the most about go is that it has a unified way to write both unit tests and examples, which get integrated in the autogenerated documentation. Extra quirks and edge cases are just comments in the implementation code. In my opinion that's exactly how it should be. The documentation should be as close to the codebase as possible to avoid redundancies and an out of date documentation. Only the go documentation proxies are a little messed up, see sourcehut blog posts about it. But the huge advantage is that you can selfhost them and create your own automated documentation base for your company, for example. [1] https://github.com/golang/pkgsite

It's also available as a mirror at https://github.com/golang/pkgsite. All the golang.org/x/* packages are thankfully available there, making them pretty easy to find.

A lot of people are saying to read the stdlib, but the stdlib has a lot of objectively bad code in it. Some of it is necessary due to the nature of a standard library - you have extra concerns about dependencies to ensure people don't have to include the entire stdlib in every binary. Some of it is stuff they hacked together when they were still designing the language, and that initial code still works fine so no need to update it. I think the source code for pkg.go.dev is actually a treasure trove of good ideas and design patterns, especially if you are trying to make a small to mdedium sized web app (which, lets be real, is almost all web apps anyone will ever make). https://github.com/golang/pkgsite

There was a proposal to add a new go-source-2 meta tag, but that was abandoned because a lot of code hosting sites would not have been supported yet: https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/40477 That is why they decided to turn it into an internal/source package inside pkgsite first to have test cases for a later go-source-2. If your site does not show source links on pkg.go.dev then add a comment to issue 40477 above and an exception will be added. - internal/source: https://github.com/golang/pkgsite/blob/master/internal/sourc... Note1: Maybe mention this on your website because that took a little to find. It does not fit into the narrative though. Note2: Requiring frontends to offer meta tags is the only way to make code discoverable with the url alone. cgit not offering this is on cgit and not on