|author||Zvonimir Pavlinovic <firstname.lastname@example.org>||Thu May 19 09:12:22 2022 -0700|
|committer||Zvonimir Pavlinovic <email@example.com>||Tue May 24 20:01:07 2022 +0000|
_content/security: add vulncheck page Images showing the initial state of the page: https://screenshot.googleplex.com/Boo3JDxkd7dtT68.png https://screenshot.googleplex.com/4HKEYCmHFDLDjYJ.png https://screenshot.googleplex.com/9g44QZqX2k5758F.png https://screenshot.googleplex.com/7bWWVCGDHejkW67.png Change-Id: Icdbc5dda10f3571a2fbe399ddfe6d4da4069b57c Reviewed-on: https://go-review.googlesource.com/c/website/+/407334 Reviewed-by: Julie Qiu <firstname.lastname@example.org> TryBot-Result: Gopher Robot <email@example.com> Run-TryBot: Zvonimir Pavlinovic <firstname.lastname@example.org> Reviewed-by: Jonathan Amsterdam <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.