mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
83bef6955e
e161ea09d Add one more Chinese file to workaround reflect: Zero(nil) b595b3a21 Add more Chinese translation 56e4e95d9 Use lang.Merge to "fill in the gaps" for untranslated pages ef079406c Merge commit '650fac3a4e7d256f4505402ab44cfc3c804b8dea' 650fac3a4 Squashed 'themes/gohugoioTheme/' changes from a1768ebb..f31a3dc8 322eff899 Add Chinese language for menus d90b886e0 Fix Markdown table syntax in previous commit 737f3dfca Update the leaf bundle vs branch bundle table 09fa1bc4e Clarify that `.Now` is obsolete 879ea3f6a Make release notes somewhat more consistent 0113e2051 Move 0.40.2-relnotes into content/en/news 77578f5bf Move content/ into new contentDir content/en/ 4dcf7c709 Fix "reflect: Zero(nil)" error in showcase 63dd25505 Release 0.40.2 2076c0d56 releaser: Prepare repository for 0.41-DEV 070fe565e releaser: Add release notes to /docs for release of 0.40.2 4ce52e913 releaser: Bump versions for release of 0.40.2 41907c487 Fix typos in syntax-highlighting.md 91753ef3d Add missing backtick b77274301 Remove duplicate release notes (0.27, 0.27.1, 0.35) 6e00da316 Remove obsolete content/release-notes/ directory 00a6d8c02 Change en dash back to `--` in 0.38.2-relnotes 51b32dc00 Update archetypes.md d0e5c2307 Release 0.40.1 4538a6d5b releaser: Prepare repository for 0.41-DEV 91b391d70 releaser: Add release notes to /docs for release of 0.40.1 e0979d143 releaser: Bump versions for release of 0.40.1 7983967c2 Clean images fe3fdd77d Polish showcase for Flesland Flis e6dde3989 Showcase - Flesland Flis AS by Absoluttweb 73aa62290 Revive @spf13's special Hugo font add67b335 Release Hugo 0.40 c0a26e5a6 Merge branch 'temp40' beeabaaae releaser: Prepare repository for 0.41-DEV e67d5e985 releaser: Add release notes to /docs for release of 0.40 6cdd95273 releaser: Bump versions for release of 0.40 bee21fb9b Revive the other Hugo logos too 4f45e8fe1 Fix the link type attribute for RSS in examples 8c67dc89a Fix example in delimit doc e7f6c00d5 Revive the logo used on the forum 82b0cd26e Merge commit 'a215abf70e018f4bf40d6c09d8bd148d8684b33d' 119c8ca58 Merge commit 'd2ec1a06df8ab6b17ad05cb008d5701b40327d47' db4683bd2 Improve .Get docs 05260b886 .Get function: fix syntax signature git-subtree-dir: docs git-subtree-split: e161ea09d33e3199f4998e4d2e9068d5a850f042
162 lines
4.9 KiB
Markdown
162 lines
4.9 KiB
Markdown
---
|
|
title: Menu Templates
|
|
linktitle: Menu Templates
|
|
description: Menus are a powerful but simple feature for content management but can be easily manipulated in your templates to meet your design needs.
|
|
date: 2017-02-01
|
|
publishdate: 2017-02-01
|
|
lastmod: 2017-02-01
|
|
categories: [templates]
|
|
keywords: [lists,sections,menus]
|
|
menu:
|
|
docs:
|
|
title: "how to use menus in templates"
|
|
parent: "templates"
|
|
weight: 130
|
|
weight: 130
|
|
sections_weight: 130
|
|
draft: false
|
|
aliases: [/templates/menus/]
|
|
toc: false
|
|
---
|
|
|
|
Hugo makes no assumptions about how your rendered HTML will be
|
|
structured. Instead, it provides all of the functions you will need to be
|
|
able to build your menu however you want.
|
|
|
|
The following is an example:
|
|
|
|
{{< code file="layouts/partials/sidebar.html" download="sidebar.html" >}}
|
|
<!-- sidebar start -->
|
|
<aside>
|
|
<ul>
|
|
{{ $currentPage := . }}
|
|
{{ range .Site.Menus.main }}
|
|
{{ if .HasChildren }}
|
|
<li class="{{ if $currentPage.HasMenuCurrent "main" . }}active{{ end }}">
|
|
<a href="#">
|
|
{{ .Pre }}
|
|
<span>{{ .Name }}</span>
|
|
</a>
|
|
</li>
|
|
<ul class="sub-menu">
|
|
{{ range .Children }}
|
|
<li class="{{ if $currentPage.IsMenuCurrent "main" . }}active{{ end }}">
|
|
<a href="{{ .URL }}">{{ .Name }}</a>
|
|
</li>
|
|
{{ end }}
|
|
</ul>
|
|
{{ else }}
|
|
<li>
|
|
<a href="{{ .URL }}">
|
|
{{ .Pre }}
|
|
<span>{{ .Name }}</span>
|
|
</a>
|
|
</li>
|
|
{{ end }}
|
|
{{ end }}
|
|
<li>
|
|
<a href="#" target="_blank">Hardcoded Link 1</a>
|
|
</li>
|
|
<li>
|
|
<a href="#" target="_blank">Hardcoded Link 2</a>
|
|
</li>
|
|
</ul>
|
|
</aside>
|
|
{{< /code >}}
|
|
|
|
{{% note "`absLangURL` and `relLangURL`" %}}
|
|
Use the [`absLangUrl`](/functions/abslangurl) or [`relLangUrl`](/functions/rellangurl) functions if your theme makes use of the [multilingual feature](/content-management/multilingual/). In contrast to `absURL` and `relURL`, these two functions add the correct language prefix to the url.
|
|
{{% /note %}}
|
|
|
|
## Section Menu for Lazy Bloggers
|
|
|
|
To enable this menu, configure `sectionPagesMenu` in your site `config`:
|
|
|
|
```
|
|
sectionPagesMenu = "main"
|
|
```
|
|
|
|
The menu name can be anything, but take a note of what it is.
|
|
|
|
This will create a menu with all the sections as menu items and all the sections' pages as "shadow-members". The _shadow_ implies that the pages isn't represented by a menu-item themselves, but this enables you to create a top-level menu like this:
|
|
|
|
```
|
|
<nav class="sidebar-nav">
|
|
{{ $currentPage := . }}
|
|
{{ range .Site.Menus.main }}
|
|
<a class="sidebar-nav-item{{if or ($currentPage.IsMenuCurrent "main" .) ($currentPage.HasMenuCurrent "main" .) }} active{{end}}" href="{{ .URL }}" title="{{ .Title }}">{{ .Name }}</a>
|
|
{{ end }}
|
|
</nav>
|
|
```
|
|
|
|
In the above, the menu item is marked as active if on the current section's list page or on a page in that section.
|
|
|
|
|
|
## Site Config menus
|
|
|
|
The above is all that's needed. But if you want custom menu items, e.g. changing weight, name, or link title attribute, you can define them manually in the site config file:
|
|
|
|
{{< code-toggle file="config" >}}
|
|
[[menu.main]]
|
|
name = "This is the blog section"
|
|
title = "blog section"
|
|
weight = -110
|
|
identifier = "blog"
|
|
url = "/blog/"
|
|
{{</ code-toggle >}}
|
|
|
|
{{% note %}}
|
|
The `identifier` *must* match the section name.
|
|
{{% /note %}}
|
|
|
|
## Menu Entries from the Page's front matter
|
|
|
|
It's also possible to create menu entries from the page (i.e. the `.md`-file).
|
|
|
|
Here is a `yaml` example:
|
|
|
|
```
|
|
---
|
|
title: Menu Templates
|
|
linktitle: Menu Templates
|
|
menu:
|
|
docs:
|
|
title: "how to use menus in templates"
|
|
parent: "templates"
|
|
weight: 130
|
|
---
|
|
...
|
|
```
|
|
|
|
{{% note %}}
|
|
You can define more than one menu. It also doesn't have to be a complex value,
|
|
`menu` can also be a string, an array of strings, or an array of complex values
|
|
like in the example above.
|
|
{{% /note %}}
|
|
|
|
### Using .Page in Menus
|
|
|
|
If you use the front matter method of defining menu entries, you'll get access to the `.Page` variable.
|
|
This allows to use every variable that's reachable from the [page variable](/variables/page/).
|
|
|
|
This variable is only set when the menu entry is defined in the page's front matter.
|
|
Menu entries from the site config don't know anything about `.Page`.
|
|
|
|
That's why you have to use the go template's `with` keyword or something similar in your templating language.
|
|
|
|
Here's an example:
|
|
|
|
```
|
|
<nav class="sidebar-nav">
|
|
{{ range .Site.Menus.main }}
|
|
<a href="{{ .URL }}" title="{{ .Title }}">
|
|
{{- .Name -}}
|
|
{{- with .Page -}}
|
|
<span class="date">
|
|
{{- dateFormat " (2006-01-02)" .Date -}}
|
|
</span>
|
|
{{- end -}}
|
|
</a>
|
|
{{ end }}
|
|
</nav>
|
|
```
|