| commit | 2b23ec4809fbb9dabc982f7662a75ff4f14d8f8e | [log] [tgz] |
|---|---|---|
| author | Dmitri Shuralyov <dmitshur@golang.org> | Fri Aug 27 18:06:53 2021 -0500 |
| committer | Dmitri Shuralyov <dmitshur@google.com> | Tue Jan 04 19:56:33 2022 +0000 |
| tree | c3df9c38f23e1b67e24b260ee8e9d83239179353 | |
| parent | 995577f14f28bed40e5f61132f1b78adbdbbb3d9 [diff] |
website: 2022 and onwards are the Years of the Gopher The Go contribution guide was created in 2009 (commit 38a41eec67e5) as part of the initial public release of Go. It defined the standard copyright header for files in the Go tree. Since files are copyrighted the year they are added, having the current year in the header means it can be copied and pasted into newly created files without further modification. Given the year (2009 at the time) was written in a plain HTML file, it needed to be updated every year to stay current. Over the last 12 years, gophers assembled and performed this task: • commit 38a41eec67e5 contribute.html (initial commit) • go.dev/cl/184055 doc/contribute.html: change copyright year • go.dev/cl/3907042 doc: contribution copyright year 2011 • go.dev/cl/5531048 doc: use 2012 for year in model standard copyright header • go.dev/cl/7034044 doc: update standard copyright header • go.dev/cl/46660043 2014: Year of the Gopher. • go.dev/cl/2087 doc: 2015 will be the Year of the Gopher. • go.dev/cl/18117 doc: 2016 is the Year of the Gopher. • go.dev/cl/35240 doc: 2017 is the Year of the Gopher • go.dev/cl/85775 doc: 2018 is the Year of the Gopher • go.dev/cl/155928 doc: 2019 is the Year of the Gopher • go.dev/cl/213017 doc: 2020 is the Year of the Gopher • go.dev/cl/280163 doc: 2021 is the Year of the Gopher In a way, this yearly tradition of updating HTML by hand was fun¹, but we've now reached a convenient time to share the joy with our friendly robot gophers. Previously, the contribution guide lived in the main Go repository, and a part of the website serving code was still in x/tools/godoc. In 2021, Russ consolidated the remaining Go website content and code all in x/website (for example, see CL 291693 and CL 293420). So now everything we need is in one repo, making this trivial to automate, and in doing so mark 2022 and beyond as the Years of the Gopher. ¹ See the commit messages and conversations in the linked CLs. Change-Id: Ieab904b77d764c3e191f75923369ce461d7102c6 Reviewed-on: https://go-review.googlesource.com/c/website/+/375056 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jamal Carvalho <jamalcarvalho@google.com>
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.
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 code is deployed to App Engine. See cmd/golangorg/README.md for details.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
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.