_content: unhide various reference links in China

Sites like blog, play, talks, and tour (.golang.org)
were not available in China: we have just the one URL golang.google.cn.
But now:
 - Everything is consolidated to a single site, go.dev.
 - golang.google.cn serves the go.dev content.
 - We've arranged to use relative links for all the content on go.dev
   that points elsewhere on go.dev, so that it all works as golang.google.cn too.

So we can unhide various reference links that were previously hidden
to avoid advertising dead links.

Change-Id: I5e1bf84de61817b0df95049b1f6fc773139d6cf6
Reviewed-on: https://go-review.googlesource.com/c/website/+/365496
Trust: Russ Cox <rsc@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
3 files changed
tree: 50f11960b31718c8f85daca20a8551f5c6441fe2
  1. _content/
  2. _later/
  3. cmd/
  4. internal/
  5. tour/
  6. .eslintrc.json
  7. .gitattributes
  8. .prettierrc
  9. .prettierrc.yaml
  10. .stylelintrc.json
  11. AUTHORS
  12. codereview.cfg
  13. content.go
  14. CONTRIBUTING.md
  15. CONTRIBUTORS
  16. go-app-deploy.sh
  17. go.mod
  18. go.sum
  19. LICENSE
  20. PATENTS
  21. README.md
README.md

Go website

Go Reference

This repo holds content and serving programs for the golang.org and go.dev web sites.

Content is in _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.

JS/CSS Formatting

This repository uses prettier to format JS and CSS files.

See also:

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.

Deploying

Each time a CL is reviewed and submitted, the blog is automatically deployed to App Engine. If the CL is submitted with a Website-Publish +1 vote, the new deployment automatically becomes https://go.dev/. Otherwise, the new deployment can be found in the App Engine versions list and verified and manually promoted.

If the automatic deployment is not working, or to check on the status of a pending deployment, see the “website-redeploy-go-dev” trigger in the Cloud Build console.

Report Issues / Send Patches

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.