alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-12-19 00:52:19 +01:00
Code Releases Activity
9e0b00038a
hugo-theme-bootstrap4-blog/layouts/_default/list.html

46 lines
1.3 KiB
HTML
Raw Normal View History

Add Schema.org implementation based on JSON-LD This replaces the metadata that Hugo's own schema.html template had been providing, but does so in JSON-LD notation rather than via the use of <meta> tags (this is Google's currently recommended form of specifying this markup). There are a few exceptions where I did not follow the conventions used in Hugo's template, for example the use of up to six images from a post's frontmatter, because Google's tool only recognizes one image, as well as different logic for a post's publish and modified dates (using enableGitInfo = true). Using this new markup, Google's Structured Data Testing Tool is now able to understand site metadata much better (before it was reading none). The implementation here is a mix of the elements and types from the official Schema.org types—for example, Blog and BlogPosting—as well as from Google's search documentation. Note that Google's docs are geared towards AMP, where some metadata is required, while for non- AMP pages the metadata is just recommended. We will have to re-evaluate this in the future, for example to add height and width information to image metadata. See: https://schema.org/Blog See: https://schema.org/BlogPosting See: https://developers.google.com/search/docs/data-types/data-type-selector See: https://search.google.com/structured-data/testing-tool
2017-01-20 14:56:33 +01:00
{{ define "schema-dot-org" }}
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "Blog",
Clean up empty whitespace in JSON-LD Use secret formatting feature of Go templates, adding - to blocks to clear whitespace around the tags.
2017-03-24 15:49:26 +01:00
{{- /* Google recommends the headline be no more than 110 characters */}}
layouts: Quote some parameters in JSON LD Current Hugo 0.19-DEV doesn't quote these anymore, so we need to add quotes manually. I'm not sure if this is a design decision or not on Hugo's part.
2017-02-21 07:17:19 +01:00
"headline": "{{ substr .Site.Title 0 110 }}",
"url" : "{{ printf "%s" .Permalink }}",
Add Schema.org implementation based on JSON-LD This replaces the metadata that Hugo's own schema.html template had been providing, but does so in JSON-LD notation rather than via the use of <meta> tags (this is Google's currently recommended form of specifying this markup). There are a few exceptions where I did not follow the conventions used in Hugo's template, for example the use of up to six images from a post's frontmatter, because Google's tool only recognizes one image, as well as different logic for a post's publish and modified dates (using enableGitInfo = true). Using this new markup, Google's Structured Data Testing Tool is now able to understand site metadata much better (before it was reading none). The implementation here is a mix of the elements and types from the official Schema.org types—for example, Blog and BlogPosting—as well as from Google's search documentation. Note that Google's docs are geared towards AMP, where some metadata is required, while for non- AMP pages the metadata is just recommended. We will have to re-evaluate this in the future, for example to add height and width information to image metadata. See: https://schema.org/Blog See: https://schema.org/BlogPosting See: https://developers.google.com/search/docs/data-types/data-type-selector See: https://search.google.com/structured-data/testing-tool
2017-01-20 14:56:33 +01:00
"author": {
"@type": "Person",
layouts: Quote some parameters in JSON LD Current Hugo 0.19-DEV doesn't quote these anymore, so we need to add quotes manually. I'm not sure if this is a design decision or not on Hugo's part.
2017-02-21 07:17:19 +01:00
"name": "{{ .Site.Params.author }}"
Add Schema.org implementation based on JSON-LD This replaces the metadata that Hugo's own schema.html template had been providing, but does so in JSON-LD notation rather than via the use of <meta> tags (this is Google's currently recommended form of specifying this markup). There are a few exceptions where I did not follow the conventions used in Hugo's template, for example the use of up to six images from a post's frontmatter, because Google's tool only recognizes one image, as well as different logic for a post's publish and modified dates (using enableGitInfo = true). Using this new markup, Google's Structured Data Testing Tool is now able to understand site metadata much better (before it was reading none). The implementation here is a mix of the elements and types from the official Schema.org types—for example, Blog and BlogPosting—as well as from Google's search documentation. Note that Google's docs are geared towards AMP, where some metadata is required, while for non- AMP pages the metadata is just recommended. We will have to re-evaluate this in the future, for example to add height and width information to image metadata. See: https://schema.org/Blog See: https://schema.org/BlogPosting See: https://developers.google.com/search/docs/data-types/data-type-selector See: https://search.google.com/structured-data/testing-tool
2017-01-20 14:56:33 +01:00
},
Clean up empty whitespace in JSON-LD Use secret formatting feature of Go templates, adding - to blocks to clear whitespace around the tags.
2017-03-24 15:49:26 +01:00
{{- $ISO8601 := "2006-01-02T15:04:05-07:00" }}
{{- if not .Date.IsZero }}
Remove escape characters in formatted date Without the quotes in the template the '+' character will no longer needlessly be escaped as '\x2b'
2019-06-13 00:07:36 +02:00
"dateModified": {{ .Date.Format $ISO8601 }},
Clean up empty whitespace in JSON-LD Use secret formatting feature of Go templates, adding - to blocks to clear whitespace around the tags.
2017-03-24 15:49:26 +01:00
{{- end }}
{{- /* all of the site's categories/tags, from Hugo's tpl/template_embedded.go */}}
layouts: Remove quoting of structured data I don't understand it, but quoting these values causes Hugo to use escape codes for non-ASCII (?) characters. For example: "description": "A thriving oasis in Jordan\x27s desert is at risk of disappearing." Google's Search Console shows the following error: Unparsable structured data > Bad escape sequence in string We had a similar issue with dates that was fixed in #111 and the solution is the same here.
2020-03-19 14:22:29 +01:00
"keywords": {{ range $plural, $terms := .Site.Taxonomies }}{{ range $term, $val := $terms }}{{ printf "%s," $term }}{{ end }}{{ end }}
Clean up empty whitespace in JSON-LD Use secret formatting feature of Go templates, adding - to blocks to clear whitespace around the tags.
2017-03-24 15:49:26 +01:00
{{- with .Site.Params.description -}}
Add Schema.org implementation based on JSON-LD This replaces the metadata that Hugo's own schema.html template had been providing, but does so in JSON-LD notation rather than via the use of <meta> tags (this is Google's currently recommended form of specifying this markup). There are a few exceptions where I did not follow the conventions used in Hugo's template, for example the use of up to six images from a post's frontmatter, because Google's tool only recognizes one image, as well as different logic for a post's publish and modified dates (using enableGitInfo = true). Using this new markup, Google's Structured Data Testing Tool is now able to understand site metadata much better (before it was reading none). The implementation here is a mix of the elements and types from the official Schema.org types—for example, Blog and BlogPosting—as well as from Google's search documentation. Note that Google's docs are geared towards AMP, where some metadata is required, while for non- AMP pages the metadata is just recommended. We will have to re-evaluate this in the future, for example to add height and width information to image metadata. See: https://schema.org/Blog See: https://schema.org/BlogPosting See: https://developers.google.com/search/docs/data-types/data-type-selector See: https://search.google.com/structured-data/testing-tool
2017-01-20 14:56:33 +01:00
,
layouts: Remove quoting of structured data I don't understand it, but quoting these values causes Hugo to use escape codes for non-ASCII (?) characters. For example: "description": "A thriving oasis in Jordan\x27s desert is at risk of disappearing." Google's Search Console shows the following error: Unparsable structured data > Bad escape sequence in string We had a similar issue with dates that was fixed in #111 and the solution is the same here.
2020-03-19 14:22:29 +01:00
"description": {{- . -}}
Clean up empty whitespace in JSON-LD Use secret formatting feature of Go templates, adding - to blocks to clear whitespace around the tags.
2017-03-24 15:49:26 +01:00
{{- end }}
Add Schema.org implementation based on JSON-LD This replaces the metadata that Hugo's own schema.html template had been providing, but does so in JSON-LD notation rather than via the use of <meta> tags (this is Google's currently recommended form of specifying this markup). There are a few exceptions where I did not follow the conventions used in Hugo's template, for example the use of up to six images from a post's frontmatter, because Google's tool only recognizes one image, as well as different logic for a post's publish and modified dates (using enableGitInfo = true). Using this new markup, Google's Structured Data Testing Tool is now able to understand site metadata much better (before it was reading none). The implementation here is a mix of the elements and types from the official Schema.org types—for example, Blog and BlogPosting—as well as from Google's search documentation. Note that Google's docs are geared towards AMP, where some metadata is required, while for non- AMP pages the metadata is just recommended. We will have to re-evaluate this in the future, for example to add height and width information to image metadata. See: https://schema.org/Blog See: https://schema.org/BlogPosting See: https://developers.google.com/search/docs/data-types/data-type-selector See: https://search.google.com/structured-data/testing-tool
2017-01-20 14:56:33 +01:00
}
</script>
{{ end }}
Start using Go 1.6's blocks Partials are nice, but blocks are a better base construct. Right now there is basically only layouts/_default/baseof.html that is doing most of the work. See: https://gohugo.io/templates/blocks
2016-09-01 16:37:27 +02:00
{{ define "main" }}
Add option to control post truncation.
2017-04-03 05:54:42 +02:00
{{ $truncate := default true .Site.Params.truncate }}
Use RegularPages instead of Pages in list.html
2018-08-09 15:06:28 +02:00
{{ $paginator := .Paginate (where .Site.RegularPages "Section" "in" .Site.Params.mainSections) }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ range $paginator.Pages }}
Add option to control post truncation.
2017-04-03 05:54:42 +02:00
{{ if $truncate }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ .Render "summary" }}
Add option to control post truncation.
2017-04-03 05:54:42 +02:00
{{ else }}
{{ .Render "content" }}
{{ end }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ end }}
Start using Go 1.6's blocks Partials are nice, but blocks are a better base construct. Right now there is basically only layouts/_default/baseof.html that is doing most of the work. See: https://gohugo.io/templates/blocks
2016-09-01 16:37:27 +02:00
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ if or (.Paginator.HasPrev) (.Paginator.HasNext) }}
layouts/_default/list.html: Use pagination partial Now that we're using the same pagination code on lists and taxonomy pages we should reuse the code by putting it in a partial.
2018-04-19 17:20:35 +02:00
{{ partial "pagination.html" . }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ end }}
Add Vim Modeline Comments to Files (#18) * Add Vim modeline comments to all relevent template files. * Add Vim modeline comments to a few other files. * Move modeline comments inside the template definitions in list and single. For some odd reason, putting them outside breaks the page generation. * Use template comments for modeline comments in templates. * Fix form 2 modelines.
2016-11-24 13:33:56 +01:00
Start using Go 1.6's blocks Partials are nice, but blocks are a better base construct. Right now there is basically only layouts/_default/baseof.html that is doing most of the work. See: https://gohugo.io/templates/blocks
2016-09-01 16:37:27 +02:00
{{ end }}
Add Vim Modeline Comments to Files (#18) * Add Vim modeline comments to all relevent template files. * Add Vim modeline comments to a few other files. * Move modeline comments inside the template definitions in list and single. For some odd reason, putting them outside breaks the page generation. * Use template comments for modeline comments in templates. * Fix form 2 modelines.
2016-11-24 13:33:56 +01:00
{{- /* vim: set ts=2 sw=2 et: */}}
Copy Permalink