commit | 3bee3041b4cb3b0190774d594a01c9292f7e592a | [log] [tgz] |
---|---|---|
author | Dmitri Shuralyov <dmitshur@golang.org> | Fri Aug 20 18:33:18 2021 -0400 |
committer | Dmitri Shuralyov <dmitshur@golang.org> | Mon Aug 23 18:13:21 2021 +0000 |
tree | 0c467108204c81dcb2acb70078e20394aac49861 | |
parent | 0c7c710b59be8d02fe95a34030ee2defbfa899bc [diff] |
internal/dl: highlight Windows ARM64 installer The windows/arm64 port is new to Go 1.17 and one of its key features. Highlight the Windows ARM64 installer, just like the Windows AMD64 installer is highlighted. (Keep the zip archives and 386 installer not highlighted.) For golang/go#36439. Change-Id: Ib57e80465d0ca090d165e14e3c4afdb2efca0c11 Reviewed-on: https://go-review.googlesource.com/c/website/+/344070 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
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.
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.
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.