Clone this repo:
  1. 80af5f5 ref/mod: add a warning against checking in files by Michael Matloob · 8 weeks ago master
  2. 2197f42 go.mod: update dependencies by Gopher Robot · 12 days ago
  3. 7189aba internal/history: document Go 1.22.4 and 1.21.11 releases by Michael Anthony Knyszek · 12 days ago
  4. dc220e6 _content/doc/tutorial: fix mixup between "module" and "workspace" by Michael Matloob · 13 days ago
  5. bc501ff cmd/golangorg: fall back to embedded content when _content is not nearby by Dmitri Shuralyov · 13 days ago

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/TS/CSS Formatting

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.

Installing npm Dependencies:

  1. Install docker
  2. Create a .gitignore file at repo root
  3. Add .gitignore and node_modules to .gitignore
  4. Run ./npm install

Run ESlint

./npx eslint [options] [file] [dir]

Run Stylelint

./npx stylelint [input] [options]

TypeScript Support

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.

Run Jest

./npx jest [TestPathPattern]


Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/ for details.

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.