commit | 0258b1acda43f662e8952a1a2db45d0cc6f5c2ba | [log] [tgz] |
---|---|---|
author | Alice Merrick <amerrick@google.com> | Tue Jan 17 21:51:52 2023 +0000 |
committer | Todd Kulesza <tkulesza@google.com> | Wed Jan 18 17:30:06 2023 +0000 |
tree | 5a8a70bac0c348d4ca9ec6126d34592858ba165f | |
parent | bf6873ed19d3076de3d82cb6cb47de35da2c941a [diff] |
_content/blog/survey2023-q1: survey announcement Announce the 2023 January edition of the Go Developer Survey. Change-Id: If632432074d33c5682d7fc04a1b5149a0d2965bd Reviewed-on: https://go-review.googlesource.com/c/website/+/461637 TryBot-Bypass: Todd Kulesza <tkulesza@google.com> Reviewed-by: Todd Kulesza <tkulesza@google.com> Reviewed-by: Cameron Balahan <cbalahan@google.com> Reviewed-by: Alice Merrick <amerrick@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.