|author||Jamal Carvalho <firstname.lastname@example.org>||Thu Apr 07 20:39:35 2022 +0000|
|committer||Gopher Robot <email@example.com>||Thu Apr 07 21:12:41 2022 +0000|
_content/css: use color variables in download table For the text in the download table to be visible for all themes the row background color must switch with the page theme. For golang/go#34601 Change-Id: I369445f25efc3b3771f324f1c0555f9049cf3390 Reviewed-on: https://go-review.googlesource.com/c/website/+/398974 Trust: Jamal Carvalho <firstname.lastname@example.org> Run-TryBot: Jamal Carvalho <email@example.com> Reviewed-by: Jonathan Amsterdam <firstname.lastname@example.org> TryBot-Result: Gopher Robot <email@example.com> Auto-Submit: Jamal Carvalho <firstname.lastname@example.org> Reviewed-by: Russ Cox <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.