content/go1.15-proposals.article: revert "use relative links for other blog articles"

This reverts CL 216626 (commit 8bf1296992b6579acabcba62cc6cd0efe039c38a).

We cannot rely on relative links in blog posts to stay relative to
blog.golang.org, because blog posts are also embedded on golang.org.
This change caused those links to point to
https://golang.org/go2-here-we-come, which is 404.

Fixes golang/go#36930
Updates golang/go#36944

Change-Id: Ie5ca8f112ff6465328d258b283d540c07e909a54
Reviewed-on: https://go-review.googlesource.com/c/blog/+/217239
Reviewed-by: Robert Griesemer <gri@golang.org>
1 file changed
tree: d8f456a7c195cdf61a221db8b85f370825cfcf93
  1. .gcloudignore
  2. .gitattributes
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. PATENTS
  8. README.md
  9. app.yaml
  10. appengine.go
  11. blog.go
  12. codereview.cfg
  13. content/
  14. go.mod
  15. go.sum
  16. local.go
  17. local_test.go
  18. rewrite.go
  19. static/
  20. support/
  21. template/
README.md

Go Blog

This repository holds the Go Blog server code and content.

Download/Install

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.

Contributing

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.

Deploying

  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.