mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
ba45da9d03
32356e4e Fix typo in header of shortcode-templates.md c8f1a2d2 Correct code example for index template function bfa6a55d Escape code fencing ff8b2f99 Fix typos in deployment with wercker tutorial 557c36e8 theme: Merge commit '7fbb4bed25001182bfeb91f79db0f0c1936582ee' 7fbb4bed Squashed 'themes/gohugoioTheme/' changes from 7dd8a302..ca53082d ce31cee0 Add "See Also" config 158cee1b Make the tags into keywords 61600be6 Add a note to the related section 49edb5a2 Relase 0.27.1 c9bbc001 releaser: Add release notes to /docs for release of 0.27.1 213c6c3b Add bugs poster 8b4590cd Add KeyCDN integration tutorial 2b277859 Add tutorial videos to several docs pages 950fef1f Update roadmap to link to the correct milestones page 496f5bf6 Rename relnotes d6f9378d Bump Netlify versions to 0.27 087fde7f Update 0.27 release notes 603f94ae docs: Document Related Content 3790f6a3 releaser: Bump versions for release of 0.27 0948868c releaser: Add release notes to /docs for release of 0.27 git-subtree-dir: docs git-subtree-split: 32356e4eabe357ae914f4d1d59e8ae31ce936723
179 lines
4.3 KiB
Markdown
179 lines
4.3 KiB
Markdown
---
|
||
title: Menus
|
||
linktitle: Menus
|
||
description: Hugo has a simple yet powerful menu system.
|
||
date: 2017-02-01
|
||
publishdate: 2017-02-01
|
||
lastmod: 2017-03-31
|
||
categories: [content management]
|
||
keywords: [menus]
|
||
draft: false
|
||
menu:
|
||
docs:
|
||
parent: "content-management"
|
||
weight: 120
|
||
weight: 120 #rem
|
||
aliases: [/extras/menus/]
|
||
toc: true
|
||
---
|
||
|
||
{{% note "Lazy Blogger"%}}
|
||
If all you want is a simple menu for your sections, see the ["Section Menu for Lazy Bloggers" in Menu Templates](/templates/menu-templates/#section-menu-for-lazy-blogger).
|
||
{{% /note %}}
|
||
|
||
You can do this:
|
||
|
||
* Place content in one or many menus
|
||
* Handle nested menus with unlimited depth
|
||
* Create menu entries without being attached to any content
|
||
* Distinguish active element (and active branch)
|
||
|
||
## What is a Menu in Hugo?
|
||
|
||
A **menu** is a named array of menu entries accessible by name via the [`.Site.Menus` site variable][sitevars]. For example, you can access your site's `main` menu via `.Site.Menus.main`.
|
||
|
||
{{% note "Menus on Multilingual Sites" %}}
|
||
If you make use of the [multilingual feature](/content-management/multilingual/), you can define language-independent menus.
|
||
{{% /note %}}
|
||
|
||
A menu entry has the following properties (i.e., variables) available to it:
|
||
|
||
`.URL`
|
||
: string
|
||
|
||
`.Name`
|
||
: string
|
||
|
||
`.Menu`
|
||
: string
|
||
|
||
`.Identifier`
|
||
: string
|
||
|
||
`.Pre`
|
||
: template.HTML
|
||
|
||
`.Post`
|
||
: template.HTML
|
||
|
||
`.Weight`
|
||
: int
|
||
|
||
`.Parent`
|
||
: string
|
||
|
||
`.Children`
|
||
: Menu
|
||
|
||
Note that menus also have the following functions available as well:
|
||
|
||
`.HasChildren`
|
||
: boolean
|
||
|
||
Additionally, there are some relevant functions available to menus on a page:
|
||
|
||
`.IsMenuCurrent`
|
||
: (menu string, menuEntry *MenuEntry ) boolean
|
||
|
||
`.HasMenuCurrent`
|
||
: (menu string, menuEntry *MenuEntry) boolean
|
||
|
||
## Add content to menus
|
||
|
||
Hugo allows you to add content to a menu via the content's [front matter](/content-management/front-matter/).
|
||
|
||
### Simple
|
||
|
||
If all you need to do is add an entry to a menu, the simple form works well.
|
||
|
||
#### A Single Menu
|
||
|
||
```
|
||
---
|
||
menu: "main"
|
||
---
|
||
```
|
||
|
||
#### Multiple Menus
|
||
|
||
```
|
||
---
|
||
menu: ["main", "footer"]
|
||
---
|
||
```
|
||
|
||
#### Advanced
|
||
|
||
|
||
```
|
||
---
|
||
menu:
|
||
docs:
|
||
parent: 'extras'
|
||
weight: 20
|
||
---
|
||
```
|
||
|
||
## Add Non-content Entries to a Menu
|
||
|
||
You can also add entries to menus that aren’t attached to a piece of content. This takes place in your Hugo project's [`config` file][config].
|
||
|
||
Here’s an example snippet pulled from a `config.toml`:
|
||
|
||
{{< code file="config.toml" >}}
|
||
[[menu.main]]
|
||
name = "about hugo"
|
||
pre = "<i class='fa fa-heart'></i>"
|
||
weight = -110
|
||
identifier = "about"
|
||
url = "/about/"
|
||
[[menu.main]]
|
||
name = "getting started"
|
||
pre = "<i class='fa fa-road'></i>"
|
||
weight = -100
|
||
url = "/getting-started/"
|
||
{{< /code >}}
|
||
|
||
Here's the equivalent snippet in a `config.yaml`:
|
||
|
||
{{< code file="config.yml" >}}
|
||
---
|
||
menu:
|
||
docs:
|
||
- Name: "about hugo"
|
||
Pre: "<i class='fa fa-heart'></i>"
|
||
Weight: -110
|
||
Identifier: "about"
|
||
URL: "/about/"
|
||
- Name: "getting started"
|
||
Pre: "<i class='fa fa-road'></i>"
|
||
Weight: -100
|
||
URL: "/getting-started/"
|
||
---
|
||
{{< /code >}}
|
||
|
||
{{% note %}}
|
||
The URLs must be relative to the context root. If the `baseURL` is `https://example.com/mysite/`, then the URLs in the menu must not include the context root `mysite`. Using an absolute URL will overide the baseURL. If the value used for `URL` in the above example is `https://subdomain.example.com/`, the output will be `https://subdomain.example.com`.
|
||
{{% /note %}}
|
||
|
||
## Nesting
|
||
|
||
All nesting of content is done via the `parent` field.
|
||
|
||
The parent of an entry should be the identifier of another entry. The identifier should be unique (within a menu).
|
||
|
||
The following order is used to determine an Identifier:
|
||
|
||
`.Name > .LinkTitle > .Title`
|
||
|
||
This means that `.Title` will be used unless `.LinkTitle` is present, etc. In practice, `.Name` and `.Identifier` are only used to structure relationships and therefore never displayed.
|
||
|
||
In this example, the top level of the menu is defined in your [site `config` file][config]). All content entries are attached to one of these entries via the `.Parent` field.
|
||
|
||
## Render Menus
|
||
|
||
See [Menu Templates](/templates/menu-templates/) for information on how to render your site menus within your templates.
|
||
|
||
[config]: /getting-started/configuration/
|
||
[multilingual]: /content-management/multilingual/
|
||
[sitevars]: /variables/
|