commit | 1a42f6637b1194f14f8ab13939a883d9791c607d | [log] [tgz] |
---|---|---|
author | Eli Bendersky <eliben@golang.org> | Thu Oct 12 05:49:48 2023 -0700 |
committer | Eli Bendersky <eliben@google.com> | Thu Oct 12 15:34:40 2023 +0000 |
tree | c1386fbbddf0e17a3368d93050260df36b7b3336 | |
parent | ed33edc86c1301afe3cf39cc12976d34e8681aa5 [diff] |
_content/doc: remove link to old blog post from a prominent place The linked blog post is from the days of GOPATH and can be confusing with modern Go; we have a more official documentation page on organizing Go modules now. Change-Id: I01b67f750055a83d9ecc25c596719ffd842ef7ed Reviewed-on: https://go-review.googlesource.com/c/website/+/534795 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Eli Bendersky <eliben@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Ian Lance Taylor <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">
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.