commit | 8b900b4d8ebf2a146a3869ecc6844525e4477608 | [log] [tgz] |
---|---|---|
author | Alice Merrick <amerrick@google.com> | Fri Apr 15 22:27:52 2022 +0000 |
committer | Todd Kulesza <tkulesza@google.com> | Tue Apr 19 20:20:40 2022 +0000 |
tree | 91092e49cf4d3a155362b14740891fe4fc694139 | |
parent | a7771c216c3644fb0629a54db706c941d5123532 [diff] |
blog: 2021 Go developer survey results. Change-Id: Ib0dfa65046193764d53930a458521856780d9acc Reviewed-on: https://go-review.googlesource.com/c/website/+/400316 Reviewed-by: Todd Kulesza <tkulesza@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.