Clearer page sorting comment
This commit is contained in:
parent
7cea0bb432
commit
c6a1c8be5c
|
@ -159,7 +159,7 @@ to newest (at the bottom).
|
|||
`reverse` has no effect on `page.later`/`page.earlier` or `page.heavier`/`page.lighter`.
|
||||
|
||||
## Sorting subsections
|
||||
Sorting sections is a bit less flexible: sections are always sorted by `weight`,
|
||||
Sorting sections is a bit less flexible: sections can only be sorted by `weight`,
|
||||
and do not have variables that point to the heavier/lighter sections.
|
||||
|
||||
By default, the lightest (lowest `weight`) subsections will be at
|
||||
|
|
|
@ -80,7 +80,9 @@ path: String;
|
|||
components: Array<String>;
|
||||
permalink: String;
|
||||
extra: HashMap<String, Any>;
|
||||
// Pages directly in this section, sorted if asked
|
||||
// Pages directly in this section. By default, the pages are not sorted. Please set the "sorted_by"
|
||||
// variable in the _index.md file of the corresponding section to "date" or "weight" for sorting by
|
||||
// date and weight, respectively.
|
||||
pages: Array<Page>;
|
||||
// Direct subsections to this section, sorted by subsections weight
|
||||
// This only contains the path to use in the `get_section` Tera function to get
|
||||
|
|
Loading…
Reference in New Issue