|author||Russ Cox <email@example.com>||Wed May 26 11:20:23 2021 -0400|
|committer||Russ Cox <firstname.lastname@example.org>||Tue Jun 15 02:35:47 2021 +0000|
internal/backport: add backports of current Go dev template, fs packages This will let us use these APIs on App Engine before Go 1.16 is available. The only thing we can't backport from Go 1.16 is embed, so that has to be build-tagged off still, but we don't really need embed on App Engine. This will let us move golang.org off App Engine Flex onto regular App Engine, which will greatly simplify deployment and make it possible to do automatic deployments. When App Engine adds Go 1.16 support, most of this can go away. (The template packages will need to stay, as go.dev will need some Go 1.17 bug fixes from them.) Change-Id: I16ee64862a43f591a31fae04caf4caa0fdb5af62 Reviewed-on: https://go-review.googlesource.com/c/website/+/323890 Trust: Russ Cox <email@example.com> Run-TryBot: Russ Cox <firstname.lastname@example.org> TryBot-Result: Go Bot <email@example.com> Reviewed-by: Dmitri Shuralyov <firstname.lastname@example.org>
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.
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.
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.