aboutsummaryrefslogtreecommitdiff
path: root/content/wire.article
Commit message (Collapse)AuthorAge
* content: write real summary for each articleRuss Cox2020-03-17
| | | | | | | | | | | | | | | | | | 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>
* content: convert to Markdown-enabled present inputsRuss Cox2020-03-17
| | | | | | | | | | | | Converted blog to Markdown-enabled present (CL 222846) using present2md (CL 222847). For golang/go#33955. Change-Id: Ib39fa1ddd9a46f9c7a62a2ca7b96e117635553e8 Reviewed-on: https://go-review.googlesource.com/c/blog/+/222848 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Andrew Bonventre <andybons@golang.org>
* content: use tabs consistently for code blocks + indentationRuss Cox2020-03-11
| | | | | | | | | | | | A few articles used four spaces instead. The present format will convert to four spaces for indentation on its own; use tabs. The present format does not care what indentation is used, but use tabs everywhere for consistency. For golang/go#33955. Change-Id: I2bab8aa72fa2f68d48fb833b7317f87d7624a05f Reviewed-on: https://go-review.googlesource.com/c/blog/+/222840 Reviewed-by: Ian Lance Taylor <iant@golang.org>
* content: wrap long lines using new program wrap.goRuss Cox2020-03-11
| | | | | | | | | | | Wrapping long lines will make diffs easier to read for the eventual conversion to Markdown. For golang/go#33955. Change-Id: Ibcc1b5a84ccc9144b5fcdc9266f2da3e2cf3c5a3 Reviewed-on: https://go-review.googlesource.com/c/blog/+/222839 Reviewed-by: Ian Lance Taylor <iant@golang.org>
* content/wire: update links and prose to reflect new Wire repositoryRoss Light2018-11-30
| | | | | | Change-Id: Id2ce0b666aca9514a628355d2f9b73c186bb5c37 Reviewed-on: https://go-review.googlesource.com/c/151697 Reviewed-by: Andrew Bonventre <andybons@golang.org>
* blog: Use correct link to Wire tutorialEno Compton2018-10-10
| | | | | | Change-Id: I29df505dab3f2ce353fe3dc708ecf281e9fc3c41 Reviewed-on: https://go-review.googlesource.com/c/141137 Reviewed-by: Ross Light <light@google.com>
* blog: Make minor formatting fixes to Wire postEno Compton2018-10-09
| | | | | | Change-Id: I0d3ae8456eae6dc98429874746789479925223a8 Reviewed-on: https://go-review.googlesource.com/c/140718 Reviewed-by: Andrew Bonventre <andybons@golang.org>
* blog: add wire.articleEno Compton2018-10-08
Change-Id: I5d15c3d80da6ded6b419384a33071dcbddf61142 Reviewed-on: https://go-review.googlesource.com/c/140557 Reviewed-by: Cassandra Salisbury <cls@golang.org> Reviewed-by: Robert van Gent <rvangent@google.com> Reviewed-by: Andrew Bonventre <andybons@golang.org>
Powered by cgit, Themed by Ted Yin.