content: fix broken links and use HTTPS on godoc.article

The article contains links to code for strings.HasPrefix that reference
the wrong line number and URL to search for "Deprecated:" identifier
which also not working anymore.

This commit fix the line number link for strings.HasPrefix and
remove the line that describe examples for searching "Deprecated:"

While at it, use HTTPS for link to Docstring and update the link
on Javadoc to latest location (according to the page redirect URL).

Signed-off-by: shulhan <>
Change-Id: Ife267af49c0816df2b3934d075c7a9a09eaac83e
Reviewed-by: Ian Lance Taylor <>
1 file changed
tree: 54dc248c29f992f8a1e17eb8e6dd3bc81078874d
  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

Go Reference

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.