alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-11-15 08:47:03 +01:00
Code Releases Activity
ab444c93b5
hugo-theme-bootstrap4-blog/layouts/_default/baseof.html

106 lines
3.7 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: Use right-to-left text for Farsi
2019-12-04 08:56:41 +01:00
<html lang="{{ .Lang }}" {{ if or (eq .Lang "ar") (eq .Lang "fa") }}dir="rtl"{{ 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
<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>
layouts: Use right-to-left text for Farsi
2019-12-04 08:56:41 +01:00
{{ if or (eq .Lang "ar") (eq .Lang "fa") }}
layouts/_default/baseof.html: Fix comment about RTL It's not just Arabic anymore now that I added Farsi strings!
2020-01-23 18:46:05 +01:00
{{ "<!-- RTL -->" | safeHTML }}
Use Hugo's built-in subresource integrity support We can use Hugo's built-in SRI support instead of using our custom SRI generator script (as cool as it was at the time). This is more clean and gives us the added benefit of adding fingerprints to the CSS and JS filenames, which acts as a cache buster. See: https://gohugo.io/hugo-pipes/introduction/ See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/issues/120
2020-01-23 18:34:21 +01:00
{{ $styleRtl := resources.Get "css/style.rtl.css" | resources.Fingerprint }}
<link href="{{ $styleRtl.Permalink }}" rel="stylesheet"{{ if not .Site.Params.disable_sri }} integrity="{{ $styleRtl.Data.Integrity }}" crossorigin="anonymous"{{ end }}>
Add right-to-left version of CSS This uses rtlcss to make a right-to-left version of the CSS and then utilizes Hugo's Language variable to conditionally include it. Also, we set the "dir" attribute on the HTML tag if the currently rendered language is Arabic.
2019-04-18 21:19:42 +02:00
{{ else }}
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
{{ "<!-- combined, minified CSS -->" | safeHTML }}
Use Hugo's built-in subresource integrity support We can use Hugo's built-in SRI support instead of using our custom SRI generator script (as cool as it was at the time). This is more clean and gives us the added benefit of adding fingerprints to the CSS and JS filenames, which acts as a cache buster. See: https://gohugo.io/hugo-pipes/introduction/ See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/issues/120
2020-01-23 18:34:21 +01:00
{{ $style := resources.Get "css/style.css" | resources.Fingerprint }}
<link href="{{ $style.Permalink }}" rel="stylesheet"{{ if not .Site.Params.disable_sri }} integrity="{{ $style.Data.Integrity }}" crossorigin="anonymous"{{ end }}>
Add right-to-left version of CSS This uses rtlcss to make a right-to-left version of the CSS and then utilizes Hugo's Language variable to conditionally include it. Also, we set the "dir" attribute on the HTML tag if the currently rendered language is Arabic.
2019-04-18 21:19:42 +02:00
{{ 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
Use Font Awesome SVGs via JavaScript This is a bit of "one step forward, two steps back" in that we are now using the much more lean SVG icons—and only the ones we are ac tually using—instead of having to download the two ~70KiB web font files, but it means we need to use JavaScript. This approache was inspired by the work @xekon did in #127. See: https://fontawesome.com/how-to-use/on-the-web/advanced/svg-javascript-core See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/pull/127
2020-01-27 17:10:58 +01:00
{{ "<!-- minified Font Awesome for SVG icons -->" | safeHTML }}
{{ $fontawesome := resources.Get "js/fontawesome.min.js" | resources.Fingerprint }}
<script defer src="{{ $fontawesome.Permalink }}" integrity="{{ $fontawesome.Data.Integrity }}" crossorigin="anonymous"></script>
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 }}
layouts: Update for Hugo 0.55.0 See: https://github.com/gohugoio/hugo/releases/tag/v0.55.0
2019-04-14 15:25:35 +02:00
{{ with .OutputFormats.Get "rss" -}}
{{ printf `<link rel="%s" type="%s" href="%s" title="%s" />` .Rel .MediaType.Type .Permalink $.Site.Title | safeHTML }}
{{ 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
layouts: Test for existence of Google Analytics ID Previously we showed the Cookie Usage banner if the site's config had a cookie consent URL specified. As of 2018-05 (GDPR) it makes more sense to only display this banner if the site has a Google Analytics ID set. Because we are using Haven for consent manage- ment we can now inject Google Analytics automatically after the user has agreed, so we no longer need to use Hugo's internal te- mplate.
2020-05-17 21:32:12 +02:00
{{ if .Site.GoogleAnalytics }}
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
{{ 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: Update navbar menu template Uses the same code as the Hugo menu template example, which should be more robust with nested menus.
2018-03-09 19:29:11 +01:00
{{- $currentPage := . -}}
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: Update navbar menu template Uses the same code as the Hugo menu template example, which should be more robust with nested menus.
2018-03-09 19:29:11 +01:00
<a class="nav-link{{ if or ($currentPage.IsMenuCurrent "navbar" .) ($currentPage.HasMenuCurrent "navbar" .) }} active{{end}}" href="{{ .URL }}" title="{{ .Title }}">{{ .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
</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" . }}
Used different syntax for accessing site parameters.
2018-08-28 15:50:21 +02:00
{{ if (ne .Site.Params.header_visible false) }}
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">
Fixed invalid URL if blog is not in domain root
2019-10-09 21:23:02 +02:00
<h1 class="blog-title" dir="auto"><a href="{{ .Site.BaseURL | absURL }}" rel="home">{{ .Site.Title | safeHTML }}</a></h1>
layouts: Set dir="auto" on some HTML elements When a site is rendered in Arabic the root HTML element gets the dir="rtl" attribute, but even Arabic sites might have an English title or footer, etc so we should set dir="auto" on those elements.
2019-04-18 22:38:53 +02:00
{{ if .Site.Params.description }}<p class="lead blog-description" dir="auto">{{ .Site.Params.description | markdownify }}</p>{{ end }}
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
</div>
</header>
blocks for masthead, header, body and footer
2018-01-02 22:51:28 +01:00
{{ end }}
Added 'header_visible' parameter to allow switching off the header.
2018-08-25 17:11:15 +02: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">
layouts: Set dir="auto" on some HTML elements When a site is rendered in Arabic the root HTML element gets the dir="rtl" attribute, but even Arabic sites might have an English title or footer, etc so we should set dir="auto" on those elements.
2019-04-18 22:38:53 +02:00
<p dir="auto">
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