|author||Russ Cox <email@example.com>||Wed Jun 02 20:43:09 2021 -0400|
|committer||Russ Cox <firstname.lastname@example.org>||Thu Jun 03 14:59:40 2021 +0000|
blog, go.dev, tour: add cloudbuild deployment configs These deployment configs are meant to be run from Cloud Build. They deploy a new version of the site on each commit, using the commit date and hash to derive the app version. If a commit is submitted with a Website-Publish+1 vote, then the new version is promoted to be the live version of the site. Otherwise the new version is left unpromoted, where it can be manually inspected and potentially manually promoted, or simply ignored and eventually automatically deleted. golang.org will work this way too, after we move it off of Flex. Change-Id: Iaddb3596276d5cfbf18aa67f210fcd33f323d9d5 Reviewed-on: https://go-review.googlesource.com/c/website/+/324511 Trust: Russ Cox <email@example.com> Run-TryBot: Russ Cox <firstname.lastname@example.org> Reviewed-by: Dmitri Shuralyov <email@example.com> TryBot-Result: Go Bot <firstname.lastname@example.org> Website-Publish: Russ Cox <email@example.com>
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.