commit | 94530e9339079a34a73f64c639d830b164cfa6a9 | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Thu Dec 07 14:37:39 2023 -0500 |
committer | Gopher Robot <gobot@golang.org> | Fri Dec 08 03:23:25 2023 +0000 |
tree | bc24e5ba8635bc900bcb3cc1e7923abf299c09e2 | |
parent | 2d2fc5b9cbef2597ca48ddb6615b086f37fe60f5 [diff] |
_content/talks: fix many stale or broken links Change to not use https://go.dev/ directly in the link, preferring relative links. Also fix many stale or broken links. Makes talks safe for upcoming link-checking test. Change-Id: I9c19e052b4df842561c3c153be630c99102a790c Reviewed-on: https://go-review.googlesource.com/c/website/+/548061 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
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.