cmd/golangorg: redirect etc to etc

People might learn to type instead of
but not the subdirectory part, meaning we expect to get
requests for things like Make them work.

Change-Id: I2827fff42e896abe2df409ddc4f67e28d881ae95
Trust: Russ Cox <>
Run-TryBot: Russ Cox <>
TryBot-Result: Go Bot <>
Website-Publish: Russ Cox <>
Reviewed-by: Jamal Carvalho <>
2 files changed
tree: f370fe2ce2172ef70b15dc9bc1736f9967495eab
  1. .eslintrc.json
  2. .gitattributes
  3. .prettierrc
  4. .prettierrc.yaml
  5. .stylelintrc.json
  12. _content/
  13. _later/
  14. cmd/
  15. codereview.cfg
  16. content.go
  18. go.mod
  19. go.sum
  20. internal/
  21. tour/

Go website

Go Reference

This repo holds content and serving programs for the and web sites.

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

To run the combined server to preview local content changes, use:

go run ./cmd/golangorg

The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for and (They do not use the _content/ directories.)

Each command directory has its own explaining deployment.

JS/CSS Formatting

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 blog is automatically deployed to App Engine. If the CL is submitted with a Website-Publish +1 vote, the new deployment automatically becomes Otherwise, the new deployment can be found in the App Engine versions list and verified and manually promoted.

If the automatic deployment is not working, or to check on the status of a pending deployment, see the “website-redeploy-go-dev” trigger in the Cloud Build console.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see

The main issue tracker for the website repository is located at Prefix your issue with “x/website:” in the subject line, so it is easy to find.