| commit | fea2f6fad6e6af234474e178717c69a68779bddb | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Tue May 25 23:29:16 2021 -0400 |
| committer | Russ Cox <rsc@golang.org> | Wed May 26 13:23:13 2021 +0000 |
| tree | 4a64117c973742f883c7ee7097f1baaf8a6e4952 | |
| parent | 212bb63fb0e7677bf1f7b9c00752b5ae51417f5b [diff] |
blog: delete per-repo files, update README.md, go.mod It would be nice to delete go.mod and let the directory be part of the x/website module, but right now x/website requires Go 1.16 and the blog runs on App Engine which doesn't yet support Go 1.16. So the blog is actually requiring an older, pre-Go 1.16 version of x/website. Once App Engine updates to Go 1.16 we can take that next step of making blog not a submodule. Or perhaps before that we will get to the point of serving the blog from the cmd/golangorg server. One way or another, this will get even simpler. Change-Id: I04f9b4d4433009c8b204acba9043b2d8a6261189 Reviewed-on: https://go-review.googlesource.com/c/website/+/322791 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.