|author||Katie Hockman <email@example.com>||Fri Jun 04 09:59:55 2021 -0400|
|committer||Katie Hockman <firstname.lastname@example.org>||Fri Jun 04 19:19:27 2021 +0000|
blog/_content/fuzz-beta.article: fix link to file issue The link provided to file an issue defaulted to a template which cleared out the body. Remove that part of the link so the issue defaults to the regular issue body template. Change-Id: I8b82a297394fd11c70e802cdba551bffc3f98508 Reviewed-on: https://go-review.googlesource.com/c/website/+/325069 Trust: Katie Hockman <email@example.com> Run-TryBot: Katie Hockman <firstname.lastname@example.org> TryBot-Result: Go Bot <email@example.com> Reviewed-by: Roland Shoemaker <firstname.lastname@example.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.