| commit | faf1e2da2d911edc717993e8edb24fe88f99b2b5 | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Sat Mar 14 09:44:01 2020 -0400 |
| committer | Russ Cox <rsc@golang.org> | Tue Mar 17 20:58:41 2020 +0000 |
| tree | 3b7d10f5f95b7bc9ca63d0591bd120b8d8f015b6 | |
| parent | af5018f64e406aaa646dae066f28de57321ea5ce [diff] |
content: write real summary for each article The pre-Markdown blog invented a summary by copying the first paragraph of text. Often this was nonsense or at least useless. The new Markdown-enabled present format adds an explicit Summary line. The conversion populated these with the same first paragraph that the old format would have used implicitly. This commit rewrites them all to be proper short summaries. Change-Id: If2e1e101b95558d7ecd53c613f733a7f89c680f1 Reviewed-on: https://go-review.googlesource.com/c/blog/+/223598 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Andrew Bonventre <andybons@golang.org>
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.
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.
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.
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.
Check that the deployed version looks OK (click the version link in GCP).
If all is well, click “Migrate Traffic” to move 100% of the blog.golang.org traffic to the new version.
You're done.