Google Git
Sign in
go / website / daaa3e0ec4b0c6dbbcc016702208c3a2e86e2755
commitdaaa3e0ec4b0c6dbbcc016702208c3a2e86e2755[log] [tgz]
authorJamal Carvalho <jamal@golang.org>Fri Nov 19 19:42:01 2021 +0000
committerJamal Carvalho <jamal@golang.org>Thu Dec 02 19:45:23 2021 +0000
treee478a9e34b47ca7150719b16b0eb8a500c8c66f5
parentd8d1119db18fe30646b8a74350ecee5ab1c90a09 [diff]
_content/learn: add a tutorials section

Adds a section with cards for Go tutorials below the
Google Cloud Self-Paced Labs.

Change-Id: I459f5fab9052b84a07ff2509ffbc41c5ff8bdb75
Reviewed-on: https://go-review.googlesource.com/c/website/+/367914
Trust: Jamal Carvalho <jamal@golang.org>
Trust: Nooras Saba‎ <saba@golang.org>
Run-TryBot: Jamal Carvalho <jamal@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Julie Qiu <julie@golang.org>
2 files changed
tree: e478a9e34b47ca7150719b16b0eb8a500c8c66f5
  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.