go.dev/cmd/frontend: fix learn.go.dev by redirecting to go.dev/learn

The old Hugo setup was strange in that Hugo thought it was generating
pages for go.dev/learn, and then we put in a redirect from go.dev/learn
to learn.go.dev, and then we had a whole separate app just for serving
files in that subtree. All the actual file serving was done in app.yaml using
static file directives, not anything in Go.

In the migration to a Go web server, I did not make learn.go.dev/ work,
so it was showing the main go.dev page instead, which is clearly bad.
I spent a little while trying to make the Go server behave like the old
setup, but in the end I gave up and removed all the subterfuge.
Now the pages are served from go.dev/learn, same as in the _content tree,
and there is a redirect from learn.go.dev/anything to go.dev/learn/anything.
Given how much trouble I had getting the server to work the other way,
it seemed like we'd keep tripping over this special case as we make more changes.
And given that the long-term plan is to move everything onto go.dev,
it seemed better all around to just start telling the truth now.

This fix is already deployed, to fix the broken learn.go.dev.

Change-Id: I774850ade327623eefffc785f923f5002f3abff8
Reviewed-on: https://go-review.googlesource.com/c/website/+/322970
Trust: Russ Cox <rsc@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
1 file changed
tree: 6d6fee4eba68729d7813c1c593003091b72ddf8c
  1. .gitattributes
  2. .prettierrc
  8. README.md
  9. _content/
  10. blog/
  11. cmd/
  12. codereview.cfg
  13. content.go
  14. go.dev/
  15. go.mod
  16. go.sum
  17. internal/
  18. tour/

Go website

Go Reference

This repo holds content and serving programs for the golang.org web site.

Content is in _content/. Server code is in cmd/ and internal/.

To run the server to preview local content changes, use:

go run ./cmd/golangorg

The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for admin.golang.org and google.golang.org. (They do not use the _content/ directory.)

Each command directory has its own README.md explaining deployment.

JS/CSS Formatting

This repository uses prettier to format JS and CSS files.

The version of prettier used is 1.18.2.

It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the website repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.