alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-12-25 19:54:31 +01:00
Code Releases Activity
e8ee0c68b7
hugo-theme-bootstrap4-blog/layouts/_default/baseof.html

69 lines
2.1 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>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
{{ "<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->" | safeHTML }}
layouts/_default/baseof.html: Smarter meta description Use the post's meta description if it exists, otherwise use the one from the site's config. Set them using the "description" key in frontmatter or site config. Note: this means there is no way to NOT have a description. You must have *at least* a site-wide description and *optionally* a description for each page/post's front matter.
2016-09-14 12:43:52 +02:00
<meta name="description" content="{{ .Params.description | default .Site.Params.description }}">
layouts/_default/baseof.html: Smarter meta author tag Use the post's author from frontmatter, or else use the author from the site's config. You MUST have one of these set or else you will get an error during site generation. I think it's better to force the user to define an author tag rather than only printing it if it is defined because it is a good practice to help bots understand content.
2016-09-14 13:05:36 +02:00
<meta name="author" content="{{ .Params.author | default .Site.Params.author }}">
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
Allow optional addition of Google Webmaster Tools verification string Add to the site's configuration like so: [params] google_verify_meta = "BAi69DROASu2b2mkVNA_EyUsobfH7Mq8BmSg2Rn-Zp4"
2016-09-13 15:26:30 +02:00
{{ if .Site.Params.google_verify_meta }}<meta name="google-site-verification" content="{{ .Site.Params.google_verify_meta }}">{{ 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
{{ .Hugo.Generator }}
<base href="{{ .Site.BaseURL }}">
<link rel="canonical" href="{{ .Permalink }}">
<title>{{ block "title" . }}{{ .Site.Title }}{{ end }}</title>
{{ "<!-- combined, minified CSS -->" | safeHTML }}
<link href="{{ .Site.BaseURL }}css/style.css" rel="stylesheet">
</head>
<body>
<div class="blog-masthead">
<div class="container">
<nav class="nav blog-nav">
<a class="nav-link" href="{{ .Site.BaseURL }}">Home</a>
</nav>
</div>
</div>
Use HTML5 header tag for blog header Makes it easier for computers to understand content by using tags that have explicit meaning. See: http://diveinto.html5doctor.com/semantics.html
2016-09-02 14:56:40 +02:00
<header class="blog-header">
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 class="container">
Make site header text clickable (to home) This is a pretty standard convention in blogs.
2016-09-14 11:24:38 +02:00
<h1 class="blog-title"><a href="{{ .Site.BaseURL }}" rel="home">{{ .Site.Title | safeHTML }}</a></h1>
Allow site description to be Markdown
2016-09-07 15:47:59 +02:00
{{ if .Site.Params.description }}<p class="lead blog-description">{{ .Site.Params.description | markdownify }}</p>{{ 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
</div>
Use HTML5 header tag for blog header Makes it easier for computers to understand content by using tags that have explicit meaning. See: http://diveinto.html5doctor.com/semantics.html
2016-09-02 14:56:40 +02:00
</header>
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 class="container">
<div class="row">
<div class="col-sm-8 blog-main">
{{ block "main" . }}
<!-- The part of the page that begins to differ between templates -->
{{ end }}
</div> {{ "<!-- /.blog-main -->" | safeHTML }}
{{ if not .Site.Params.sidebar.hide }}
{{ partial "sidebar.html" . }}
{{ end }}
</div> {{ "<!-- /.row -->" | safeHTML }}
</div> {{ "<!-- /.container -->" | safeHTML }}
<footer class="blog-footer">
<p>
Blog template built by <a href='https://twitter.com/mralanorth'>@mralanorth</a>.
</p>
</footer>
</body>
</html>
Copy Permalink