dc95675888
Updated the test reader to generate outfile paths prior to test runs so that it is easier to read/write to a cache of images in a future CL. Change-Id: I3f27194c3fb7d215d5d258fe24da0b2b8ff53a5f Reviewed-on: https://go-review.googlesource.com/c/website/+/373476 Run-TryBot: Jamal Carvalho <jamal@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jonathan Amsterdam <jba@google.com> Trust: Jamal Carvalho <jamalcarvalho@google.com> |
||
---|---|---|
_content | ||
_later/security | ||
cmd | ||
internal | ||
tour | ||
.eslintrc.json | ||
.gitattributes | ||
.prettierrc | ||
.prettierrc.yaml | ||
.stylelintrc.json | ||
AUTHORS | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
LICENSE | ||
PATENTS | ||
README.md | ||
codereview.cfg | ||
content.go | ||
go-app-deploy.sh | ||
go.mod | ||
go.sum |
README.md
Go website
This repo holds content and serving programs for the go.dev and golang.org web sites.
Content is in _content/ (go.dev) and tour/ (go.dev/tour). Server code is in cmd/ and internal/.
To run the combined go.dev+golang.org 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/ directories.)
Each command directory has its own README.md explaining deployment.
JS/CSS Formatting
This repository uses prettier to format JS and CSS files.
See also:
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.
Deploying
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
Report Issues / Send Patches
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
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.