Google Git
Sign in
go / website / c97685a94022a2e826f644e1f62e9976d5d62544
commitc97685a94022a2e826f644e1f62e9976d5d62544[log] [tgz]
authorNicholas S. Husin <nsh@golang.org>Fri Jan 02 16:35:19 2026 -0500
committerNicholas Husin <nsh@golang.org>Fri Jan 02 15:11:59 2026 -0800
tree68300fc6ebd9a092938475c58a715ab56d122329
parent94286c9833eaa5e462a2d6363ff307224fd46f83 [diff]
_content/js: do not use indented subheading to start the 2nd column of a TOC

Currently, the entries for our generated TOC are split across two
columns without regards on whether an entry is a regular heading vs an
indented subheading. As a result, it is possible for the 2nd column of
our generated TOC to start with an indented subheading, which is
visually confusing and hard to associate with the last regular heading
in the 1st column.

This CL changes our TOC generation so that any indented subheadings will
always be placed in the same column as its parent heading.

Fixes golang/go#76980

Change-Id: I8f5ae689ae9fc70da856b198f5453e18d692780d
Reviewed-on: https://go-review.googlesource.com/c/website/+/733720
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Nicholas Husin <husin@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
1 file changed
tree: 68300fc6ebd9a092938475c58a715ab56d122329
  1. _content/
  2. cmd/
  3. internal/
  4. tour/
  5. .eslintrc.yaml
  6. .gitattributes
  7. .prettierrc.yaml
  8. .stylelintrc.yaml
  9. codereview.cfg
  10. content.go
  11. content_test.go
  12. CONTRIBUTING.md
  13. go-app-deploy.sh
  14. go.mod
  15. go.sum
  16. jest-transform.cjs
  17. LICENSE
  18. npm
  19. npx
  20. package-lock.json
  21. package.json
  22. PATENTS
  23. README.md
  24. tsconfig.json
README.md

Go website

Go Reference

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.

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]

Deploying

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

Report Issues / Send Patches

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

The git repository is https://go.googlesource.com/website.

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