Does this issue reproduce with the latest release?
N/A? It's observable now.
What operating system and processor architecture are you using (go env)?
N/A? Observed with Safari 15.4 (17618.104.22.168.13) on macOS Monterey 12.3.1 (21E258) on an iMac (Retina 5K, 27-inch, 2017).
What did you do?
I navigated to https://go.dev/ref/.
What did you expect to see?
Some kind of summary of the available reference material, including links to the language spec and memory model.
What did you see instead?
Some weird directory-like listing that has a link to module documentation (good), a link to some default template (bad), no links to the language spec or memory model (bad), and a link to the root page (which it calls "..", which is fine, I guess, but not very web-y) (fine).
The text was updated successfully, but these errors were encountered:
The path to resolution is known, but the work has not been done.
Feedback is required from experts, contributors, and/or the community before a change can be made.
Jun 6, 2022
The reference docs served from /ref/* paths are either in GOROOT/doc (go_mem.html, go_spec.html) or in x/website/_content/ref (mod.md). None of them are from x/website/_content/doc directory. Given that they are somewhat special (spec!) and serving paths are different from other docs, I think it's better to keep ref/mod.md in ref and minimize change.
In cl/413914, I added /ref/index.md and that helped avoid an old issue that prevented setting redirect for /ref/.