content: fix code block in Publishing Go Modules article

When indentation is used to create a code block immediately following
a list, Markdown syntax is ambiguous: it can be interpreted as another
text paragraph belonging to the last list entry, or as a standalone
code block.

The original behavior in CL 197637 made this unambiguously a code block
because the present format did not support lists. This changed when the
article was converted to use Markdown syntax in CL 222848.

Start using a fenced code block instead of indentation to resolve the
Markdown ambiguity and restore original behavior.

For golang/go#33955.

Change-Id: I9537bc72d7a32f90592942591b2688fb2f26c452
Reviewed-by: Jean de Klerk <>
1 file changed
tree: 61d766d5c741877f3de7eff41a7a3aec2f6f390e
  1. content/
  2. static/
  3. support/
  4. template/
  5. .gcloudignore
  6. .gitattributes
  7. app.yaml
  8. appengine.go
  10. blog.go
  11. codereview.cfg
  14. go.mod
  15. go.sum
  17. local.go
  18. local_test.go
  21. rewrite.go

Go Blog

This repository holds the Go Blog server code and content.


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

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

The main issue tracker for the blog is located at Prefix your issue with “x/blog:” in the subject line, so it is easy to find.


  1. To deploy, 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 traffic to the new version.

  4. You're done.