commit | 6e77c30404d84b1333899747891b375134f4579f | [log] [tgz] |
---|---|---|
author | Jay Conrod <jayconrod@google.com> | Mon Aug 10 15:06:17 2020 -0400 |
committer | Jay Conrod <jayconrod@google.com> | Wed Sep 09 14:23:24 2020 +0000 |
tree | 9d417291c2b0dbb2e07c97e05623caf7203a0257 | |
parent | c1a7e8072ea1c3565f9ba65db77d14a4527aa2c9 [diff] |
content/static/doc: add introduction, resolve several TODOs * Added Introduction. This should say generally what modules are. It should also say this is a reference document, and point to tutorials for folks looking for those. * Edited some text in introductory sessions. * Replaced emphasis on new terms with <dfn> tags. Dropped emphasis from terms that are being mentioned, not defined. * Added glossary term for "vendor directory". * Removed some TODOs that are no longer relevant. For golang/go#33637 Change-Id: Iae6dcd28b392a4cd94351bc645a059ead3a7dfa8 Reviewed-on: https://go-review.googlesource.com/c/website/+/247758 Reviewed-by: Bryan C. Mills <bcmills@google.com> Reviewed-by: Michael Matloob <matloob@golang.org>
This repository holds the Go website server code and content.
To download and run the golang.org web server locally:
git clone https://go.googlesource.com/website
cd website
go run ./cmd/golangorg
See cmd/golangorg/README.md for more details.
To make basic changes to the golang.org website content:
content/static
directory.go run ./cmd/golangorg
.go generate ./content/static
go run ./cmd/golangorg
See content/README.md for more sophisticated instructions.
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.