_content/doc: update release branch mention to in install-source

We've updated most pages on the website to recommend using specific
release tags when building a release from source (we used to suggest
checking out the release branch, but that might give a commit that
doesn't correspond to any final release). Fix one more.

Change-Id: If4dbffacf61e3d32c8b8c0a3548ead2de6f2e76e
Reviewed-on: https://go-review.googlesource.com/c/website/+/299370
Trust: Dmitri Shuralyov <dmitshur@golang.org>
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Steve Traut <straut@google.com>
Reviewed-by: Alexander Rakoczy <alex@golang.org>
1 file changed
tree: 865c3d5a7ff2607cef86925edfd5e1c8b6b4ef3f
  1. .prettierrc
  7. README.md
  8. _content/
  9. cmd/
  10. codereview.cfg
  11. content.go
  12. go.mod
  13. go.sum
  14. internal/

Go website

Go Reference

This repo holds content and serving programs for the golang.org web site.

Content is in _content/. Server code is in cmd/ and internal/.

To run the 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/ directory.)

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.