blogs/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2026-09-03 04:02:38 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
0c770e40be014ae87b1237a9a8ef9099a262bb7f
hugo/content/templates/base.md
T
Bud Parr 6896947058 Update content to use Hugo's built-in menu 
* add generic menu declaration
* update about section
* commands
* update content management section
* update contribute section
* functions
* update getting started section
* update hosting and deployment section
* fix mailing list entry (no menu)
* update news section
* update Templates section
* update tools section
* update themes section
* troubleshooting
* update variables section

Fixes rdwatters/hugo-docs-concept#45
See PR rdwatters/hugo-docs-concept#62
2017-03-31 17:50:49 -05:00

5.2 KiB
Raw Blame History

title, linktitle, description, godocref, date, publishdate, lastmod, categories, tags, menu, weight, draft, aliases, toc
title linktitle description godocref date publishdate lastmod categories tags menu weight draft aliases toc
Base Templates and Blocks The base and block constructs allow you to define the outer shell of your master templates (i.e., the chrome of the page). https://golang.org/pkg/text/template/#example_Template_block 2017-02-01 2017-02-01 2017-02-01
templates
blocks
base
fundamentals
main
parent weight
Templates 20
20 false
/templates/blocks/
/templates/base-templates-and-blocks/
true

Go 1.6 includes a powerful new keyword, block. This construct allows you to define the outer shell of your pages' one or more master template(s) and then fill in or override portions as necessary.

Base Template Lookup Order

The lookup order for base templates is as follows:

  1. /layouts/section/<TYPE>-baseof.html
  2. /themes/<THEME>/layouts/section/<TYPE>-baseof.html
  3. /layouts/<TYPE>/baseof.html
  4. /themes/<THEME>/layouts/<TYPE>/baseof.html
  5. /layouts/section/baseof.html
  6. /themes/<THEME>/layouts/section/baseof.html
  7. /layouts/_default/post-baseof.html
  8. /themes/<THEME>/layouts/_default/post-baseof.html
  9. /layouts/_default/baseof.html
  10. /themes/<THEME>/layouts/_default/baseof.html

Variables are denoted by capitalized text set within <>. Note that Hugo's default behavior is for type to inherit from section unless otherwise specified.

Example Base Template Lookup Order

As an example, let's assume your site is using a theme called "mytheme" when rendering the section list for a post section. Hugo picks layout/section/post.html as the template for rendering the section. The {{define}} block in this template tells Hugo that the template is an extension of a base template.

Here is the lookup order for the post base template:

  1. /layouts/section/post-baseof.html
  2. /themes/mytheme/layouts/section/post-baseof.html
  3. /layouts/post/baseof.html
  4. /themes/mytheme/layouts/post/baseof.html
  5. /layouts/section/baseof.html
  6. /themes/mytheme/layouts/section/baseof.html
  7. /layouts/_default/post-baseof.html
  8. /themes/mytheme/layouts/_default/post-baseof.html
  9. /layouts/_default/baseof.html
  10. /themes/mytheme/layouts/_default/baseof.html

Defining the Base Template

The following defines a simple base template at _default/baseof.html. As a default template, it is the shell from which all your pages will be rendered unless you specify another *baseof.html closer to the beginning of the lookup order..

{{% code file="layouts/_default/baseof.html" download="baseof.html" %}}

<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <title>{{ block "title" . }}
      <!-- Blocks may include default content. -->
      {{ .Site.Title }}
    {{ end }}</title>
  </head>
  <body>
    <!-- Code that all your templates share, like a header -->
    {{ block "main" . }}
      <!-- The part of the page that begins to differ between templates -->
    {{ end }}
    {{ block "footer" . }}
    <!-- More shared code, perhaps a footer but that can be overridden if need be in  -->
    {{ end }}
  </body>
</html>

{{% /code %}}

Overriding the Base Template

From the above base template, you can define a default list template. The default list template will inherit all of the code defined above and can then implement its own "main" block from:

{{% code file="layouts/_default/list.html" download="list.html" %}}

{{ define "main" }}
  <h1>Posts</h1>
  {{ range .Data.Pages }}
    <article>
      <h2>{{ .Title }}</h2>
      {{ .Content }}
    </article>
  {{ end }}
{{ end }}

{{% /code %}}

{{% note "No Go Context "the dot" in Block Definitions" %}} When using the define keyword, you do not need to use Go templates context reference (i.e., "the dot"). (Read more on "the dot" in Templates Introduction.) {{% /note %}}

This replaces the contents of our (basically empty) "main" block with something useful for the list template. In this case, we didn't define a "title" block, so the contents from our base template remain unchanged in lists.

{{% warning %}} Code that you put outside the block definitions can break your layout. This even includes HTML comments. For example:

<!-- Seemingly harmless HTML comment..that will break your layout at build -->
{{ define "main" }}
...your code here
{{ end }}

See this thread from the Hugo discussion forums. {{% /warning %}}

The following shows how you can override both the "main" and "title" block areas from the base template with code unique to your default single page template:

{{% code file="layouts/_default/single.html" download="single.html" %}}

{{ define "title" }}
  <!-- This will override the default value set in baseof.html; i.e., "{{.Site.Title}}" in the original example-->
  {{ .Title }} &ndash; {{ .Site.Title }}
{{ end }}
{{ define "main" }}
  <h1>{{ .Title }}</h1>
  {{ .Content }}
{{ end }}

{{% /code %}}

Reference in New Issue View Git Blame Copy Permalink