commit | cecdbb6e8ed6cf33babe1e9217a00197a4845765 | [log] [tgz] |
---|---|---|
author | Russ Cox <rsc@golang.org> | Wed Nov 17 15:57:04 2021 -0500 |
committer | Russ Cox <rsc@golang.org> | Mon Nov 22 16:40:01 2021 +0000 |
tree | 9cb1e3af7d30ec2fa4fb9eb5dddf9e97dec33107 | |
parent | 961523a99713328508cc63167192db63311e474b [diff] |
website: merge golang.org → go.dev As described in https://go.dev/blog/tidy-web, redirect golang.org to go.dev. The golang.org home page is retired - go.dev now has all the same info and links, and it doesn't have ten-year-old videos of me. All the other golang.org pages are now served directly from go.dev, styled differently but with the same content. A followup CL will merge the _content directories. Change-Id: Ib7f3d951842c021280981f9b926c4943f4d9cb52 Reviewed-on: https://go-review.googlesource.com/c/website/+/364859 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Jamal Carvalho <jamal@golang.org>
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.