2019-10-21 04:22:28 -04:00
---
title: Menu Templates
2023-05-22 10:43:12 -04:00
description: Use menu variables and methods in your templates to render a menu.
2019-10-21 04:22:28 -04:00
categories: [templates]
keywords: [lists,sections,menus]
menu:
docs:
2023-05-22 10:43:12 -04:00
parent: templates
2019-10-21 04:22:28 -04:00
weight: 130
2023-05-22 10:43:12 -04:00
toc: true
2019-10-21 04:22:28 -04:00
weight: 130
aliases: [/templates/menus/]
---
2023-05-22 10:43:12 -04:00
## Overview
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
After [defining menu entries], use [menu variables and methods] to render a menu.
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
Three factors determine how to render a menu:
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
1. The method used to define the menu entries: [automatic], [in front matter], or [in site configuration]
1. The menu structure: flat or nested
1. The method used to [localize the menu entries]: site configuration or translation tables
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
The example below handles every combination.
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
## Example
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
This partial template recursively "walks" a menu structure, rendering a localized, accessible nested list.
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
{{< code file = "layouts/partials/menu.html" > }}
{{- $page := .page }}
{{- $menuID := .menuID }}
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
{{- with index site.Menus $menuID }}
< nav >
< ul >
{{- partial "inline/menu/walk.html" (dict "page" $page "menuEntries" .) }}
< / ul >
< / nav >
{{- end }}
{{- define "partials/inline/menu/walk.html" }}
{{- $page := .page }}
{{- range .menuEntries }}
{{- $attrs := dict "href" .URL }}
{{- if $page.IsMenuCurrent .Menu . }}
{{- $attrs = merge $attrs (dict "class" "active" "aria-current" "page") }}
{{- else if $page.HasMenuCurrent .Menu .}}
{{- $attrs = merge $attrs (dict "class" "ancestor" "aria-current" "true") }}
{{- end }}
< li >
< a
{{- range $k, $v := $attrs }}
{{- with $v }}
{{- printf " %s=%q" $k $v | safeHTMLAttr }}
{{- end }}
{{- end -}}
>{{ or (T .Identifier) .Name | safeHTML }}< / a >
{{- with .Children }}
< ul >
{{- partial "inline/menu/walk.html" (dict "page" $page "menuEntries" .) }}
< / ul >
{{- end }}
< / li >
{{- end }}
{{- end }}
{{< / code > }}
2022-09-13 14:34:24 -04:00
2023-05-22 10:43:12 -04:00
Call the partial above, passing a menu ID and the current page in context.
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
{{< code file = "layouts/_default/single.html" > }}
{{ partial "menu.html" (dict "menuID" "main" "page" .) }}
{{ partial "menu.html" (dict "menuID" "footer" "page" .) }}
{{< / code > }}
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
## Page references
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
Regardless of how you [define menu entries], an entry associated with a page has access to page variables and methods.
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
This simplistic example renders a page parameter named `version` next to each entry's `name` . Code defensively using `with` or `if` to handle entries where (a) the entry points to an external resource, or (b) the `version` parameter is not defined.
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
{{< code file = "layouts/_default/single.html" > }}
{{- range site.Menus.main }}
< a href = "{{ .URL }}" >
{{ .Name }}
{{- with .Page }}
{{- with .Params.version -}}
({{ . }})
{{- end }}
{{- end }}
< / a >
{{- end }}
{{< / code > }}
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
## Menu entry parameters
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
When you define menu entries [in site configuration] or [in front matter], you can include a `params` key as shown in these examples:
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
- [Menu entry defined in site configuration]
- [Menu entry defined in front matter]
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
This simplistic example renders a `class` attribute for each anchor element. Code defensively using `with` or `if` to handle entries where `params.class` is not defined.
2019-10-21 04:22:28 -04:00
2023-05-22 10:43:12 -04:00
{{< code file = "layouts/partials/menu.html" > }}
{{- range site.Menus.main }}
< a { { with . Params . class - } } class = "{{ . }}" { { end - } } href = "{{ .URL }}" >
{{ .Name }}
< / a >
{{- end }}
{{< / code > }}
## Localize
Hugo provides two methods to localize your menu entries. See [multilingual].
[automatic]: /content-management/menus/#define-automatically
[define menu entries]: /content-management/menus/
[defining menu entries]: /content-management/menus/
[in front matter]: /content-management/menus/#define-in-front-matter
[in site configuration]: /content-management/menus/#define-in-site-configuration
[localize the menu entries]: /content-management/multilingual/#menus
[menu entry defined in front matter]: /content-management/menus/#example-front-matter
[menu entry defined in site configuration]: /content-management/menus/#example-site-configuration
[menu variables and methods]: /variables/menus/
[multilingual]: /content-management/multilingual/#menus