commit | 5be32adfba3980d69063805dfaee9c91e947ec32 | [log] [tgz] |
---|---|---|
author | Eli Bendersky <eliben@golang.org> | Mon Jan 10 07:29:34 2022 -0800 |
committer | DO NOT USE <iant@google.com> | Mon Jan 10 21:28:36 2022 +0000 |
tree | f82b39c4413dde980c21266bc4eea02f876cae3d | |
parent | 41ad36154ea299e93f97776c35c4b345444774df [diff] |
_content/doc: fix a small typo it's --> its Change-Id: Ia3d64b636704ce0108161c3c194233258c4b3d06 Reviewed-on: https://go-review.googlesource.com/c/website/+/377194 Reviewed-by: Russ Cox <rsc@golang.org> Run-TryBot: Emmanuel Odeke <emmanuel@orijtech.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: DO NOT USE <iant@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">
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.