| commit | ddb58f2a774bb611e4a2f5ed07fe936e19752abb | [log] [tgz] |
|---|---|---|
| author | Hana <hyangah@gmail.com> | Fri Sep 03 09:56:26 2021 -0400 |
| committer | Hyang-Ah Hana Kim <hyangah@gmail.com> | Fri Sep 03 14:47:29 2021 +0000 |
| tree | 9e31415e939ef6ca4fbc3ae471448da0e4227d3e | |
| parent | 32d2054556308d1bc5b370cbd4edaea75b027e72 [diff] |
all: replace the example repo import path github.com/golang/example is actually a mirror of go.googlesource.com/example which hosts the golang.org/x/example module. The path mismatches causes build failures. This CL replaces github.com/golang/example with golang.org/x/example when appropriate. I think the use case in _content/doc/articles/go_command.html is better served with a repo in github.com or widely known source hosting sites. Otherwise, the flow may be confusing. So, I used github.com/golang/protobuf. Also replaced godoc.org links with pkg.go.dev links. Still not sure if the instructions in the old blog posts and articles continue to work though. For blog posts, I am not sure what to do - there is historical merit in preserving old contents (that's the point of blogs, isn't it?) However, old, broken examples can be confusing for new users. Keeping all blog posts up-to-date isn't scalable either. The gopath_code.html and go_command.html can be confusing for users who use latest go. I think we need to make them more clear that they are obsolete or archive(?) them. Change-Id: Iefe0cc94b0690dc52933ebce214104e94d9b6808 Reviewed-on: https://go-review.googlesource.com/c/website/+/347551 Trust: Hyang-Ah Hana Kim <hyangah@gmail.com> Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Russ Cox <rsc@golang.org> Website-Publish: Russ Cox <rsc@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.