_content/doc: update local tour installation instructions

We already use go install for the installation instructions in the
tour itself, but the command shown in the root doc document still uses
go get, which by itself won't install any binary in recent Go
versions. Switch to go install there too.

Fixes golang/go#48347

Change-Id: Iad6b22010c92ff0f60df47804fabdd3a3ac2d5c2
Reviewed-on: https://go-review.googlesource.com/c/website/+/349529
Trust: Alberto Donizetti <alb.donizetti@gmail.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
1 file changed
tree: a1638f2ec1c0cee3c6df4284ccf3737d30ce42d3
  1. .gitattributes
  2. .prettierrc
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. PATENTS
  8. README.md
  9. _content/
  10. cmd/
  11. codereview.cfg
  12. content.go
  13. go-app-deploy.sh
  14. go.dev/
  15. go.mod
  16. go.sum
  17. internal/
  18. tour/
README.md

Go website

Go Reference

This repo holds content and serving programs for the golang.org and go.dev web sites.

Content is in _content/ (golang.org), go.dev/_content/ (go.dev), and tour/ (tour.golang.org). Server code is in cmd/ and internal/.

To run the combined golang.org+go.dev 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.

JS/CSS Formatting

This repository uses prettier to format JS and CSS files.

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.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

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.