commit | 55e51100fd01a1f063821a936fb9809c4b6c9ab5 | [log] [tgz] |
---|---|---|
author | Julie Qiu <julie@golang.org> | Wed Aug 10 21:40:21 2022 -0400 |
committer | Julie Qiu <julieqiu@google.com> | Thu Aug 11 18:34:01 2022 +0000 |
tree | 3dd87447c3f9dd8a831eae82ea728661819b578d | |
parent | d849247f0eb05bdb62cf6ea414e796525de8a542 [diff] |
_content: add link to CNA policy Change-Id: Ia73a66e50bfd521113470a327814d5bc0f18e737 Reviewed-on: https://go-review.googlesource.com/c/website/+/422755 Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Julie Qiu <julieqiu@google.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.
This repository uses eslint to format JS and TS files, and stylelint to format CSS files.
See also:
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.
./npm install
./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
TypeScript files served from _content are transformed into JavaScript. Reference .ts files in html templates as module code.
<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.