mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
aa5ac36a3e
39a7fac34 Add .hugo_build.lock to .gitignore 920c716a4 fix a typo: to -> two (#1545) 6f0ba9593 Remove godocref from front matter (#1543) 8ec3d5948 remove link to wercker (#1544) b56008719 Delete deployment-with-wercker.md (#1542) e33d29b02 Fix broken links (#1538) 29e9d4c21 Sort commenting systems (#1541) 0b7ea60a7 Delete the news page "HTTP/2 Server Push in Hugo" 6e1515857 Fix quick-start.md (#1525) 62168ab35 Update comments.md (#1535) d92191512 Small typo (#1539) 129c8834a Correct the PostCSS noMap default value (#1534) 6a5b29fcc Add example to index function (#1536) e3dd8c507 Update output-formats.md 0c9321ca0 Remove reference to using LiveReload in production environment 4072d6776 Mod testing 09fabf7d6 Fix typo (#1524) 2fce813c8 Fix grammatical error in quick-start.md (#1523) 45230ab4a Hugo Mod testing 2dd4cd9e7 Update index.md 2c3ed62fd netlify: Bump to 0.88.1 648e2a007 Merge branch 'tempv0.88.1' f216eade1 releaser: Add release notes to /docs for release of 0.88.1 8a7b64d4b Fix typographical errors in 0.88.0 release notes a4bf86300 Release 0.88 738bb8f38 releaser: Add release notes to /docs for release of 0.88.0 8fcf2c55d highlight: Remove some pygments references f2b173de2 HTTPS link c88881c8e Adding link to nginx documentation 6b0a74fe0 Fix typos in docs (#1516) 498b8f0f1 Fix typos in time.Format (#1515) 28723fad6 Fix taxonomy and term examples (#1514) 3ffd00e12 Update front-matter.md 7cc1da82e Fix grammar in 0.86.1 release notes (#1510) 0009c51c3 Update docs helper 7e2f430f4 Update index.md 7857eae7e releaser: Add release notes to /docs for release of 0.87.0 1f08b684b releaser: Add release notes to /docs for release of 0.87.0 36a9e701c docs: Adjust config docs 0f588438e docs: Regen CLI docs 1b4682cd8 docs: Regen docs helper bc8bbaae9 Merge commit 'bd77f6e1c99e04a476f0b1bb4e44569134e02399' into release-0.87.0 6f2480643 docs: Adjust time zone docs git-subtree-dir: docs git-subtree-split: 39a7fac343c289906db644c96079fdcc0298582f
100 lines
3.1 KiB
Markdown
100 lines
3.1 KiB
Markdown
---
|
|
title: index
|
|
linktitle: index
|
|
description: Looks up the index(es) or key(s) of the data structure passed into it.
|
|
date: 2017-02-01
|
|
publishdate: 2017-02-01
|
|
lastmod: 2017-02-01
|
|
categories: [functions]
|
|
menu:
|
|
docs:
|
|
parent: "functions"
|
|
keywords: []
|
|
signature: ["index COLLECTION INDEXES", "index COLLECTION KEYS"]
|
|
workson: []
|
|
hugoversion:
|
|
relatedfuncs: []
|
|
deprecated: false
|
|
aliases: [/functions/index/]
|
|
needsexample: true
|
|
---
|
|
|
|
The `index` functions returns the result of indexing its first argument by the following arguments. Each indexed item must be a map or a slice, e.g.:
|
|
|
|
```go-text-template
|
|
{{ $slice := slice "a" "b" "c" }}
|
|
{{ index $slice 1 }} => b
|
|
{{ $map := dict "a" 100 "b" 200 }}
|
|
{{ index $map "b" }} => 200
|
|
```
|
|
|
|
The function takes multiple indices as arguments, and this can be used to get nested values, e.g.:
|
|
|
|
```go-text-template
|
|
{{ $map := dict "a" 100 "b" 200 "c" (slice 10 20 30) }}
|
|
{{ index $map "c" 1 }} => 20
|
|
{{ $map := dict "a" 100 "b" 200 "c" (dict "d" 10 "e" 20) }}
|
|
{{ index $map "c" "e" }} => 20
|
|
```
|
|
|
|
You may write multiple indices as a slice:
|
|
|
|
```go-text-template
|
|
{{ $map := dict "a" 100 "b" 200 "c" (dict "d" 10 "e" 20) }}
|
|
{{ $slice := slice "c" "e" }}
|
|
{{ index $map $slice }} => 20
|
|
```
|
|
|
|
## Example: Load Data from a Path Based on Front Matter Params
|
|
|
|
Assume you want to add a `location = ""` field to your front matter for every article written in `content/vacations/`. You want to use this field to populate information about the location at the bottom of the article in your `single.html` template. You also have a directory in `data/locations/` that looks like the following:
|
|
|
|
```
|
|
.
|
|
└── data
|
|
└── locations
|
|
├── abilene.toml
|
|
├── chicago.toml
|
|
├── oslo.toml
|
|
└── provo.toml
|
|
```
|
|
|
|
Here is an example:
|
|
|
|
{{< code-toggle file="data/locations/oslo" >}}
|
|
website = "https://www.oslo.kommune.no"
|
|
pop_city = 658390
|
|
pop_metro = 1717900
|
|
{{< /code-toggle >}}
|
|
|
|
The example we will use will be an article on Oslo, whose front matter should be set to exactly the same name as the corresponding file name in `data/locations/`:
|
|
|
|
```
|
|
title = "My Norwegian Vacation"
|
|
location = "oslo"
|
|
```
|
|
|
|
The content of `oslo.toml` can be accessed from your template using the following node path: `.Site.Data.locations.oslo`. However, the specific file you need is going to change according to the front matter.
|
|
|
|
This is where the `index` function is needed. `index` takes 2 parameters in this use case:
|
|
|
|
1. The node path
|
|
2. A string corresponding to the desired data; e.g.—
|
|
|
|
```
|
|
{{ index .Site.Data.locations “oslo” }}
|
|
```
|
|
|
|
The variable for `.Params.location` is a string and can therefore replace `oslo` in the example above:
|
|
|
|
```
|
|
{{ index .Site.Data.locations .Params.location }}
|
|
=> map[website:https://www.oslo.kommune.no pop_city:658390 pop_metro:1717900]
|
|
```
|
|
|
|
Now the call will return the specific file according to the location specified in the content's front matter, but you will likely want to write specific properties to the template. You can do this by continuing down the node path via dot notation (`.`):
|
|
|
|
```
|
|
{{ (index .Site.Data.locations .Params.location).pop_city }}
|
|
=> 658390
|
|
```
|