_content/package-names: remove usage of "stutter"

Replace the use of "stutter" with a word which
more clearly conveys the meaning.

Change-Id: Ib1278d9eb24f5c84ed1f6e121493b6690f549687
Reviewed-on: https://go-review.googlesource.com/c/blog/+/322633
Trust: Katie Hockman <katie@golang.org>
Run-TryBot: Katie Hockman <katie@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Sameer Ajmani <ajmani@gmail.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
1 file changed
tree: e43b6f86f330d90712d0b820315161f2ef79995a
  1. _content/
  2. _static/
  3. _template/
  4. .gcloudignore
  5. .gitattributes
  6. app.yaml
  7. appengine.go
  9. blog.go
  10. codereview.cfg
  13. go.mod
  14. go.sum
  16. local.go
  17. local_test.go
  19. README.md
  20. rewrite.go

Go Blog

Go Reference

This repository holds the Go Blog server code and content.


The easiest way to install is to run go get -u golang.org/x/blog. You can also manually git clone the repository to $GOPATH/src/golang.org/x/blog.

Running Locally

To run the blog server locally:

go run . -reload

and then visit http://localhost:8080/ in your browser.


Articles are written in the x/tools/present format. Articles on the blog should have broad interest to the Go community, and are mainly written by Go contributors. We encourage you to share your experiences using Go on your own website, and to share them with the Go community. Hugo is a static site server written in Go that makes it easy to write and share your stories.

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 blog is located at https://github.com/golang/go/issues. Prefix your issue with “x/blog:” in the subject line, so it is easy to find.


  1. To deploy blog.golang.org, run:

    GO111MODULE=on gcloud --project=golang-org app deploy --no-promote app.yaml

    This will create a new version, which can be viewed within the golang-org GCP project.

  2. Check that the deployed version looks OK (click the version link in GCP).

  3. If all is well, click “Migrate Traffic” to move 100% of the blog.golang.org traffic to the new version.

  4. You're done.