alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-12-28 04:54:29 +01:00
Code Releases Activity
85924be657
hugo-theme-bootstrap4-blog/layouts/_default/baseof.html

102 lines
3.2 KiB
HTML
Raw Normal View History

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
<!DOCTYPE html>
layouts/_default/baseof.html: Use current language for html element's lang attribute You know you gotta specify the page content's language if possible, right? https://www.w3.org/International/questions/qa-http-and-lang
2016-10-04 10:22:53 +02:00
<html lang="{{ .Lang }}">
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
<head>
layouts: Rename metadata partial
2016-09-26 08:23:13 +02:00
{{ partial "head-meta.html" . }}
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
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
{{ block "schema-dot-org" . }}
<!-- schema.org metadata differs for Nodes and Pages -->
{{ 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
<link rel="canonical" href="{{ .Permalink }}">
<title>{{ block "title" . }}{{ .Site.Title }}{{ end }}</title>
{{ "<!-- combined, minified CSS -->" | safeHTML }}
layouts/_default/baseof.html: Allow disabling of SRI Some sites using edge caching like that on a CDN or S3 might have issues with assets being cached too long, causing user agents to refuse to load assets due to SRI hash mismatch. These sites should disable the use of sub-resource integrity hashes using this config option in their config: disable_sri = true
2017-04-12 20:38:10 +02:00
<link href="{{ .Site.BaseURL }}css/style.css" rel="stylesheet"{{ if not .Site.Params.disable_sri }} integrity="{{ .Site.Data.sri.style}}" crossorigin="anonymous"{{ end }}>
Add RSS feed for posts to base layout Not sure who uses RSS anymore but Hugo automatically generates the feed so we might as well advertise it.
2016-09-19 09:00:28 +02:00
Rename RSSlink to RSSLink The former will be deprecated and eventually removed from Hugo. Note: Currently both of them exist in Hugo, which is the reason for the cleanup.
2016-11-17 09:12:17 +01:00
{{ if .RSSLink }}
layouts/_default/baseof.html: Don't indent go blocks They get indented doubly in the generated HTML and look funny.
2016-11-09 14:42:39 +01:00
{{ "<!-- RSS 2.0 feed -->" | safeHTML }}
Rename RSSlink to RSSLink The former will be deprecated and eventually removed from Hugo. Note: Currently both of them exist in Hugo, which is the reason for the cleanup.
2016-11-17 09:12:17 +01:00
<link href="{{ .RSSLink }}" rel="alternate" type="application/rss+xml" title="{{ .Site.Title }}" />
layouts/_default/baseof.html: Improve handling of RSS We are explicitly using the site's RSS feed, but after reading the Hugo RSS docs I think it's better if we use the contextual version of the RSSlink. This will make the RSS plumbing show a feed for the current category, tag, section, etc. The example code also adds a bit of markup to help browsers find the content more easily. See: https://gohugo.io/templates/rss/
2016-11-09 14:39:23 +01:00
{{ end }}
layouts/_default/baseof.html: Add support for Google Analytics Sites only need to add their Google Analytics tracking ID to their config: googleAnalytics = "UA-123-45" This uses the async version of the Google Analytics code.
2016-10-15 04:10:01 +02:00
{{ template "_internal/google_analytics_async.html" . }}
Add plumbing for cookie consent Set the cookie_consent_info_url parameter in your site's config to display a message about cookie usage to your users. See the config in `exampleSite/config.toml` for more info.
2016-11-13 13:13:17 +01:00
{{ if .Site.Params.cookie_consent_info_url }}
{{ partial "cookie-consent.html" . }}
{{ end }}
Add ability to insert custom code into the global <head>. (#17) * Add ability to insert custom code into the global <head>. * Fix indentation.
2016-11-22 20:11:50 +01:00
{{ partial "head-custom.html" . }}
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
</head>
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
<body>
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
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +01:00
{{ block "masthead" . }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
<div class="blog-masthead">
<div class="container">
<nav class="nav blog-nav">
<a class="nav-link {{ if .IsHome }}active{{ end }}" href="{{ .Site.BaseURL | absLangURL }}">{{ i18n "home" }}</a>
layouts/_default/baseof.html: Don't create whitespace Cleans up some template logic so that extra, unnecessary whitespace isn't created during site generation.
2017-04-04 11:21:52 +02:00
{{- $currentURL := .URL | absLangURL -}}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
{{ if .Site.Params.custom_navbar }}
Add custom navbar support - default behaviour is backward compatible: all non-post pages - optionally enable custom navbar using hugo menu functionality
2016-11-17 11:04:14 +01:00
{{ range .Site.Menus.navbar }}
layouts/: Use absLangURL to determine active page in menu On sites with multiple languages we need to use the absolute URL in the test to determine if the current page should be marked "active" in the menu bar. Perhaps a bug with Hugo that relative links end up like "/bg/bg/about" instead of "/bg/about".
2017-04-04 11:03:07 +02:00
{{ $menuURL := .URL | absLangURL }}
layouts/_default/baseof.html: Don't create whitespace Cleans up some template logic so that extra, unnecessary whitespace isn't created during site generation.
2017-04-04 11:21:52 +02:00
<a class="nav-link{{ if eq $menuURL $currentURL }} active{{ end }}" href="{{.URL | absURL }}">{{ .Name }}</a>
layouts/_default/baseof.html: Remove trailing whitespace
2017-04-04 10:54:30 +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
{{ else }}
layouts/_default/baseof.html: Use .Site.RegularPages instead of .Site.Pages Hugo 0.18 changes the pages returned by .Site.Pages, so we need to use .Site.RegularPages in order to test the type. See: https://github.com/spf13/hugo/releases/tag/v0.18 See: https://gohugo.io/templates/variables#site-variables
2016-12-25 16:56:24 +01:00
{{ range where .Site.RegularPages "Type" "!=" "post" }}
layouts/: Use absLangURL to determine active page in menu On sites with multiple languages we need to use the absolute URL in the test to determine if the current page should be marked "active" in the menu bar. Perhaps a bug with Hugo that relative links end up like "/bg/bg/about" instead of "/bg/about".
2017-04-04 11:03:07 +02:00
{{ $permalinkURL := .Permalink | absLangURL }}
layouts/_default/baseof.html: Don't create whitespace Cleans up some template logic so that extra, unnecessary whitespace isn't created during site generation.
2017-04-04 11:21:52 +02:00
<a class="nav-link{{ if eq $permalinkURL $currentURL }} active{{ end }}" href="{{ .Permalink }}">{{ .Title }}</a>
Add custom navbar support - default behaviour is backward compatible: all non-post pages - optionally enable custom navbar using hugo menu functionality
2016-11-17 11:04:14 +01: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
{{ end }}
</nav>
</div>
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
</div>
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +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
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +01:00
{{ block "header" . }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
<header class="blog-header">
<div class="container">
<h1 class="blog-title"><a href="{{ .Site.BaseURL }}" rel="home">{{ .Site.Title | safeHTML }}</a></h1>
{{ if .Site.Params.description }}<p class="lead blog-description">{{ .Site.Params.description | markdownify }}</p>{{ end }}
</div>
</header>
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +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
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +01:00
{{ block "body" . }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
<div class="container">
<div class="row">
<div class="col-sm-8 blog-main">
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
{{ block "main" . }}
<!-- The part of the page that begins to differ between templates -->
{{ 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
</div> {{ "<!-- /.blog-main -->" | safeHTML }}
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
{{ partial "sidebar.html" . }}
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
</div> {{ "<!-- /.row -->" | safeHTML }}
</div> {{ "<!-- /.container -->" | safeHTML }}
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +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
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +01:00
{{ block "footer" . }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
<footer class="blog-footer">
<p>
layouts/_default/baseof.html: Allow configuration of footer text Uses the "copyright" parameter from the site's config that is pretty standard among Hugo themes. Content can contain Markdown.
2016-10-09 12:36:07 +02:00
{{ if .Site.Copyright }}
{{ .Site.Copyright | markdownify }}
{{ else }}
layouts/_default/baseof.html: Give credit to @mdo for theme
2016-10-09 12:38:49 +02:00
Blog template created by <a href="https://twitter.com/mdo">@mdo</a>, ported to Hugo by <a href='https://twitter.com/mralanorth'>@mralanorth</a>.
layouts/_default/baseof.html: Allow configuration of footer text Uses the "copyright" parameter from the site's config that is pretty standard among Hugo themes. Content can contain Markdown.
2016-10-09 12:36:07 +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
</p>
<p>
layouts/_default/baseof.html: Revert to simple "read more" link Prepending the site's URL to relative links was a hack but at the time I couldn't understand why href="#" didn't take us to the top of the page. It turns out that this was because of the <base> tag that I have now removed.
2017-01-05 14:23:09 +01:00
<a href="#">{{ i18n "backToTop" }}</a>
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
</p>
</footer>
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +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
</body>
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
</html>
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