| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Now that the blog can handle Markdown,
minor HTML adjustments can be made directly
in the article files, so inline those instead of
using .html commands.
Change-Id: I5069f18ab98b38cdb8528ae2d5529abf06baf1ef
Reviewed-on: https://go-review.googlesource.com/c/blog/+/223600
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Go blog started out on Blogger
(http://web.archive.org/web/20100325005843/http://blog.golang.org/).
Later, we moved to the current self-hosted blog server
with extra Go-specific functionality like playground snippets.
The old Blogger posts have very long URLs that Blogger chose
for us, such as "go-programming-language-turns-two" or
"two-go-talks-lexical-scanning-in-go-and", predating
the convention of giving posts shorter, more share-friendly,
typeable names.
The conversion of the old Blogger posts also predated
the convention of putting supporting files in a subdirectory.
The result is that although we've established new conventions,
you wouldn't know by listing the directory - the old Blogger
content presents a conflicting picture.
This commit renames the posts with very long names
to have shorter, more share-friendly names, and it moves
all supporting files to subdirectories. It also adds a README
documenting the conventions.
For example, blog.golang.org/go-programming-language-turns-two
is now blog.golang.org/2years, matching our more recent birthday
post URLs, and its supporting files are moved to the new 2years/ directory.
The old URLs redirect to the new ones.
Change-Id: I9f46a790c2c8fab8459aeda73d4e3d2efc86d88f
Reviewed-on: https://go-review.googlesource.com/c/blog/+/223599
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Remove repeated blank lines, trailing spaces, trailing blank lines
Remove comments from survey2018.article (only article using them).
Remove blank lines between successive ".commands".
For golang/go#33955.
Change-Id: I90cae37a859a8e39549520569d5f10bc455415d3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222841
Reviewed-by: Ian Lance Taylor <iant@golang.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
talks.golang.org
blog.golang.org
godoc.org
swtch.com
And few misc ones done by hand.
Change-Id: Ia2c4fee630814a1ef3b143098bbac3edd6a45064
Reviewed-on: https://go-review.googlesource.com/106977
Reviewed-by: Andrew Bonventre <andybons@golang.org>
|
| |
|
|
|
|
| |
Change-Id: I270148b9ae9afde304144a57c43faae872a66bfa
Reviewed-on: https://go-review.googlesource.com/13819
Reviewed-by: Andrew Gerrand <adg@golang.org>
|
|
|
Change-Id: I05cb4a4d4b0f0436181ee5d1ec59c10c757edf8d
Reviewed-on: https://go-review.googlesource.com/12786
Reviewed-by: Rob Pike <r@golang.org>
|