blob: 30c8a9837886e8f4461acb9e8d89f83a4bcdb3a4 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
---
title: Section
description: Returns the name of the top level section in which the given page resides.
categories: []
keywords: []
action:
related:
- methods/page/Type
returnType: string
signatures: [PAGE.Section]
---
With this content structure:
```text
content/
├── lessons/
│ ├── math/
│ │ ├── _index.md
│ │ ├── lesson-1.md
│ │ └── lesson-2.md
│ └── _index.md
└── _index.md
```
When rendering lesson-1.md:
```go-html-template
{{ .Section }} → lessons
```
In the example above "lessons" is the top level section.
The `Section` method is often used with the [`where`] function to build a page collection.
```go-html-template
{{ range where .Site.RegularPages "Section" "lessons" }}
<h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
{{ end }}
```
This is similar to using the [`Type`] method with the `where` function
```go-html-template
{{ range where .Site.RegularPages "Type" "lessons" }}
<h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
{{ end }}
```
However, if the `type` field in front matter has been defined on one or more pages, the page collection based on `Type` will be different than the page collection based on `Section`.
[`where`]: /functions/collections/where
[`Type`]: /methods/page/type
|
