commit | b5115077be4a6997a307c1e69ace80df80cd716e | [log] [tgz] |
---|---|---|
author | Jorge Troncoso <jatron@google.com> | Tue Jan 04 23:12:27 2022 -0800 |
committer | Dmitri Shuralyov <dmitshur@google.com> | Thu Jan 06 17:36:12 2022 +0000 |
tree | 1acf163d7c9145f2da6a01bae0c963a98dd8e7c9 | |
parent | 58a5fe9a90ad72665d16c5570585a0c8c8503e9c [diff] |
_content/doc: fix a link in code.html Change the anchor to point to the "Remote import paths" section. Previously the anchor pointed to the "Relative import paths" section, even though the paragraph was about "Remote import paths." Change-Id: I376d5f99149041edcc4d6370522bdfbfe80eceb4 Reviewed-on: https://go-review.googlesource.com/c/website/+/375554 Run-TryBot: Jean de Klerk <deklerk@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jamal Carvalho <jamalcarvalho@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Trust: Dmitri Shuralyov <dmitshur@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 prettier to format JS and CSS files.
See also:
The version of prettier
used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.
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.