LIlinhns·Sep 30, 2024
Massively underrated. It's actually used to build the pkg.go.dev website itself.
https://github.com/golang/pkgsite
In Some Go web dev notesgolang
pkgsite
Go2020–2024
golang / pkgsite
pkgsite
[mirror] Home of the pkg.go.dev website
5Distinct people
5Mentions
0Explicit recommenders
1.3KGitHub stars
What to know before exploring
What it is
[mirror] Home of the pkg.go.dev website
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year5 dated mentions
Observed mentions: 2020-08-02 06:06:35 UTC to 2024-09-30 11:26:52 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
2 sourcesWhat 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
In Why is language documentation still so terrible?