commit | 6cf1d5f27d1aa8a40325c0f3d873755c957e41a2 | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Tue Feb 16 23:04:51 2021 -0500 |
committer | Russ Cox <rsc@golang.org> | Wed Feb 24 17:35:29 2021 +0000 |
tree | c98d6b98fbd63bd467753861140d03f34164265c | |
parent | d86265880f5d431e0a20b04d06bbbcdc228690d2 [diff] |
internal/godoc: fork golang.org/x/tools/godoc@123adc86bc This is a straight copy of golang.org/x/tools/godoc@123adc86bc (CL 291669) with internal import paths updated, gofmt run, and go17_test.go folded into godoc_test.go (we are well past Go 1.7 now). The next CL will change cmd/golangorg to use it, and then we can start making adjustments to delete lots of unused code, without worrying about affecting any external importers of the original. This CL brings in 16,290 lines of code, but less than 2,000 will actually remain once all the no-longer-needed code is deleted in followup CLs. Change-Id: I40ff57fe610b252df8bd6bb5de1114cdd7a750a2 Reviewed-on: https://go-review.googlesource.com/c/website/+/293420 Trust: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
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.
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.