alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-11-17 17:57:04 +01:00
Code Releases Activity
2e6a27300e
hugo-theme-bootstrap4-blog/layouts/_default/list.html

57 lines
2.1 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",
{{/* 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
},
layouts/_default/list.html: Use .Date for modification time on nodes I'm not sure if it really matters to bots who will parse this (it's much more important on content pages of course), but using .Date on nodes like the homepage and taxonomy terms pages will set the date to be that of the latest post in that range—to me this does indeed seem to be "time when the object was last updated"[0]. [0] https://developers.facebook.com/docs/reference/opengraph/object-type/website/
2017-01-22 13:58:13 +01:00
{{ $ISO8601 := "2006-01-02T15:04:05-07:00" }}
{{ if not .Date.IsZero }}
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
"dateModified": "{{ .Date.Format $ISO8601 }}",
layouts/_default/list.html: Use .Date for modification time on nodes I'm not sure if it really matters to bots who will parse this (it's much more important on content pages of course), but using .Date on nodes like the homepage and taxonomy terms pages will set the date to be that of the latest post in that range—to me this does indeed seem to be "time when the object was last updated"[0]. [0] https://developers.facebook.com/docs/reference/opengraph/object-type/website/
2017-01-22 13:58:13 +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
{{ with .Site.Social.GooglePlus }}
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
"publisher": "{{ printf "%s" . }}",
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
{{ end }}
{{/* all of the site's categories/tags, from Hugo's tpl/template_embedded.go */}}
"keywords": "{{ range $plural, $terms := .Site.Taxonomies }}{{ range $term, $val := $terms }}{{ printf "%s," $term }}{{ end }}{{ end }}"
{{ with .Site.Params.description }}
,
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
"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
{{ end }}
}
</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" }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ $paginator := .Paginate (where .Data.Pages "Type" "post") }}
{{ range $paginator.Pages }}
{{ .Render "summary" }}
{{ 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) }}
<nav class="blog-pagination">
{{ if and (.Paginator.HasPrev) (.Paginator.HasNext) }}
add previous and next relations (#55) * add previous and next relations https://www.w3.org/TR/html5/links.html#link-type-next * undo rel's on disabled buttons
2017-03-24 09:59:41 +01:00
<a class="btn btn-outline-primary" href="{{ .Paginator.Prev.URL }}" rel="prev" role="button">{{ i18n "paginatorPrevious" }}</a>
<a class="btn btn-outline-primary" href="{{ .Paginator.Next.URL }}" rel="next" role="button">{{ i18n "paginatorNext" }}</a>
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ end }}
{{ if and (.Paginator.HasPrev) (not .Paginator.HasNext) }}
add previous and next relations (#55) * add previous and next relations https://www.w3.org/TR/html5/links.html#link-type-next * undo rel's on disabled buttons
2017-03-24 09:59:41 +01:00
<a class="btn btn-outline-primary" href="{{ .Paginator.Prev.URL }}" rel="prev" role="button">{{ i18n "paginatorPrevious" }}</a>
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
<a class="btn btn-outline-primary disabled" href="#" role="button" aria-disabled="true">{{ i18n "paginatorNext" }}</a>
layouts/_default/list.html: Only show pagination if necessary
2016-10-19 04:53:14 +02:00
{{ end }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ if and (not .Paginator.HasPrev) (.Paginator.HasNext) }}
<a class="btn btn-outline-primary disabled" href="#" role="button" aria-disabled="true">{{ i18n "paginatorPrevious" }}</a>
add previous and next relations (#55) * add previous and next relations https://www.w3.org/TR/html5/links.html#link-type-next * undo rel's on disabled buttons
2017-03-24 09:59:41 +01:00
<a class="btn btn-outline-primary" href="{{ .Paginator.Next.URL }}" rel="next" role="button">{{ i18n "paginatorNext" }}</a>
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ end }}
</nav>
{{ 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