From 1a4522b3ed63294408cbf439852fb8cf8b6e7146 Mon Sep 17 00:00:00 2001 From: Joe Mooring Date: Fri, 18 Aug 2023 20:33:55 -0700 Subject: [PATCH] Format examples --- content/en/templates/lists/index.md | 348 ++++++++++++++-------------- 1 file changed, 174 insertions(+), 174 deletions(-) diff --git a/content/en/templates/lists/index.md b/content/en/templates/lists/index.md index ec397c32b..f488f6fe9 100644 --- a/content/en/templates/lists/index.md +++ b/content/en/templates/lists/index.md @@ -88,23 +88,23 @@ You can now access this `_index.md`'s' content in your list template: {{< code file="layouts/_default/list.html" >}} {{ define "main" }} -
-
-
-

{{ .Title }}

-
- - {{ .Content }} -
- -
+
+
+
+

{{ .Title }}

+
+ + {{ .Content }} +
+ +
{{ end }} {{< /code >}} @@ -113,17 +113,17 @@ This above will output the following HTML: {{< code file="example.com/posts/index.html" copy=false >}}
-
-
-

My Go Journey

-
-

I decided to start learning Go in March 2017.

-

Follow my journey through this new blog.

-
- +
+
+

My Go Journey

+
+

I decided to start learning Go in March 2017.

+

Follow my journey through this new blog.

+
+
{{< /code >}} @@ -137,16 +137,16 @@ Using this same `layouts/_default/list.html` template and applying it to the `qu {{< code file="example.com/quote/index.html" copy=false >}}
-
-
- -

Quotes

-
-
- +
+
+ +

Quotes

+
+
+
{{< /code >}} @@ -202,12 +202,12 @@ Hugo lists render the content based on metadata you provide in [front matter]. I {{< code file="layouts/partials/default-order.html" >}} {{< /code >}} @@ -217,12 +217,12 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-weight.html" >}} {{< /code >}} @@ -230,13 +230,13 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-date.html" >}} {{< /code >}} @@ -244,13 +244,13 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-publish-date.html" >}} {{< /code >}} @@ -258,12 +258,12 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-expiry-date.html" >}} {{< /code >}} @@ -271,13 +271,13 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-last-mod.html" >}} {{< /code >}} @@ -285,13 +285,13 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-length.html" >}} {{< /code >}} @@ -299,13 +299,13 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-title.html" >}} {{< /code >}} @@ -313,13 +313,13 @@ Lower weight gets higher precedence. So content with lower weight will come firs {{< code file="layouts/partials/by-link-title.html" >}} {{< /code >}} @@ -348,12 +348,12 @@ Reversing order can be applied to any of the above methods. The following uses ` {{< code file="layouts/partials/by-date-reverse.html" >}} {{< /code >}} @@ -366,15 +366,15 @@ Hugo provides some functions for grouping pages by Section, Type, Date, etc. {{< code file="layouts/partials/by-page-field.html" >}} {{ range .Pages.GroupBy "Section" }} -

{{ .Key }}

- {{ end }} {{< /code >}} @@ -383,21 +383,21 @@ In the above example, you may want `{{ .Title }}` to point the `title` field you {{< code file="layouts/partials/by-page-field.html" >}} {{ range .Pages.GroupBy "Section" }} - -{{ with $.Site.GetPage "section" .Key }} -

{{ .Title }}

-{{ else }} - -

{{ .Key | title }}

-{{ end }} - {{ end }} {{< /code >}} @@ -406,15 +406,15 @@ In the above example, you may want `{{ .Title }}` to point the `title` field you {{< code file="layouts/partials/by-page-date.html" >}} {{ range .Pages.GroupByDate "2006-01" }} -

{{ .Key }}

- {{ end }} {{< /code >}} @@ -425,15 +425,15 @@ In the above example, you may want `{{ .Title }}` to point the `title` field you {{< code file="layouts/partials/by-page-publish-date.html" >}} {{ range .Pages.GroupByPublishDate "2006-01" }} -

{{ .Key }}

- {{ end }} {{< /code >}} @@ -445,15 +445,15 @@ In the above example, you may want `{{ .Title }}` to point the `title` field you {{< code file="layouts/partials/by-page-expiry-date.html" >}} {{ range .Pages.GroupByExpiryDate "2006-01" }} -

{{ .Key }}

- {{ end }} {{< /code >}} @@ -464,15 +464,15 @@ In the above example, you may want `{{ .Title }}` to point the `title` field you {{< code file="layouts/partials/by-page-lastmod.html" >}} {{ range .Pages.GroupByLastmod "2006-01" }} -

{{ .Key }}

- {{ end }} {{< /code >}} @@ -483,16 +483,16 @@ In the above example, you may want `{{ .Title }}` to point the `title` field you {{< code file="layouts/partials/by-page-param.html" >}} {{ range .Pages.GroupByParam "param_key" }} -

{{ .Key }}

- + {{ end }} {{< /code >}} ### By page parameter in date format @@ -502,15 +502,15 @@ The following template takes grouping by `date` a step further and uses Go's lay {{< code file="layouts/partials/by-page-param-as-date.html" >}} {{ range .Pages.GroupByParamDate "param_key" "2006-01" }} -

{{ .Key }}

- {{ end }} {{< /code >}} @@ -552,15 +552,15 @@ Here is the ordering for the example that follows: {{< code file="layouts/partials/by-group-by-page.html" >}} {{ range .Pages.GroupByDate "2006-01" "asc" }} -

{{ .Key }}

- {{ end }} {{< /code >}}