|author||Ian Lance Taylor <email@example.com>||Mon Mar 21 09:56:03 2022 -0700|
|committer||Ian Lance Taylor <firstname.lastname@example.org>||Tue Mar 22 03:16:40 2022 +0000|
_content/doc/go1.18: change some 1.19 references to "a future release" Realistically many of these changes are not going to happen in 1.19, since the freeze is only five weeks away. If they get in, great. But let's not suggest that that is likely. Change-Id: Icd8478d10bc8657838fd196fb1157204c7a9b629 Reviewed-on: https://go-review.googlesource.com/c/website/+/394254 Reviewed-by: Robert Griesemer <email@example.com> Reviewed-by: Daniel Martí <firstname.lastname@example.org> Trust: Ian Lance Taylor <email@example.com>
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.
It is encouraged that all JS, TS, and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
<script type="module" src="/ts/filename.ts">
Write unit tests for TypeScript code using the jest testing framework.
./npx jest [TestPathPattern]
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
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.