aboutsummaryrefslogtreecommitdiff
path: root/content/organizing-go-code.article
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2020-03-14 09:44:01 -0400
committerRuss Cox <rsc@golang.org>2020-03-17 20:58:41 +0000
commitfaf1e2da2d911edc717993e8edb24fe88f99b2b5 (patch)
tree3b7d10f5f95b7bc9ca63d0591bd120b8d8f015b6 /content/organizing-go-code.article
parentaf5018f64e406aaa646dae066f28de57321ea5ce (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>
Diffstat (limited to 'content/organizing-go-code.article')
-rw-r--r--content/organizing-go-code.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/organizing-go-code.article b/content/organizing-go-code.article
index ff87bf4..13ea8f5 100644
--- a/content/organizing-go-code.article
+++ b/content/organizing-go-code.article
@@ -1,7 +1,7 @@
# Organizing Go code
16 Aug 2012
Tags: godoc, gopath, interface, libraries, tools, technical
-Summary: Go code is organized differently to that of other languages. This post discusses how to name and package the elements of your Go program to best serve its users.
+Summary: How to name and package the parts of your Go program to best serve your users.
Andrew Gerrand