diff options
| author | Russ Cox <rsc@golang.org> | 2021-08-03 00:54:24 -0400 |
|---|---|---|
| committer | Russ Cox <rsc@golang.org> | 2021-08-18 19:48:35 +0000 |
| commit | 6c6d3e7c40fa86abd6fe6d0dd6ddaf0155d738f6 (patch) | |
| tree | d2b09af3aee08b81789abf8404f3eef669718e77 /_content/ref | |
| parent | 9b8de9f9de492b179320c9aa0716a2cd2a631839 (diff) | |
| download | go-x-website-6c6d3e7c40fa86abd6fe6d0dd6ddaf0155d738f6.tar.xz | |
cmd/golangorg: move blog from blog.golang.org to go.dev/blog
This is the first of a sequence of consolidations of web sites into
the single site go.dev. An accompanying blog post (next CL) will
explain the change.
The blog/_content tree moves to go.dev/_content/blog.
The *.article files were converted to *.md files using rsc.io/tmp/blog2md.
The old dot directives are now template function invocations,
so that blog content files are now exactly the same format and
semantics as regular site content files.
All the old blog redirects are carried forward, of course.
Also add exhaustive test that every .md file renders correctly.
Also rename rawhtml to raw, because it gets used for raw Markdown too.
The raw Markdown issue is working around a bigger problem
(html/template is not really right for Markdown) that we will have
to solve at some point, but not in this CL.
Change-Id: Ifa9b3b8d656a72af30d0d4e57e4c7bc8dacbc386
Reviewed-on: https://go-review.googlesource.com/c/website/+/342091
Trust: Russ Cox <rsc@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
Diffstat (limited to '_content/ref')
| -rw-r--r-- | _content/ref/mod.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/_content/ref/mod.md b/_content/ref/mod.md index d8a78aec..8594378f 100644 --- a/_content/ref/mod.md +++ b/_content/ref/mod.md @@ -1573,7 +1573,7 @@ rsc.io/pdf v0.1.1 ``` The `Module` struct has a `String` method that formats this line of output, so -that the default format is equivalent to {{rawhtml "`-f '{{.String}}'`"}}. +that the default format is equivalent to {{raw "`-f '{{.String}}'`"}}. Note that when a module has been replaced, its `Replace` field describes the replacement module module, and its `Dir` field is set to the replacement @@ -2192,9 +2192,9 @@ A version query may be one of the following: specific version. See [Versions](#versions) for syntax. * A semantic version prefix, such as `v1` or `v1.2`, which selects the highest available version with that prefix. -* A semantic version comparison, such as {{rawhtml "`<v1.2.3` or `>=v1.5.6`"}}, which selects +* A semantic version comparison, such as {{raw "`<v1.2.3` or `>=v1.5.6`"}}, which selects the nearest available version to the comparison target (the lowest version - for `>` and `>=`, and the highest version for {{rawhtml "`<` and `<=`"}}). + for `>` and `>=`, and the highest version for {{raw "`<` and `<=`"}}). * A revision identifier for the underlying source repository, such as a commit hash prefix, revision tag, or branch name. If the revision is tagged with a semantic version, this query selects that version. Otherwise, this query @@ -2228,7 +2228,7 @@ loading `retract` directives. [Release versions](#glos-release-version) are preferred over pre-release versions. For example, if versions `v1.2.2` and `v1.2.3-pre` are available, the `latest` query will select `v1.2.2`, even though `v1.2.3-pre` is higher. The -{{rawhtml "`<v1.2.4`"}} query would also select `v1.2.2`, even though `v1.2.3-pre` is closer +{{raw "`<v1.2.4`"}} query would also select `v1.2.2`, even though `v1.2.3-pre` is closer to `v1.2.4`. If no release or pre-release version is available, the `latest`, `upgrade`, and `patch` queries will select a pseudo-version for the commit at the tip of the repository's default branch. Other queries will report |