TheCloud/hugoDocs
1
0
Fork 0
mirror of https://github.com/gohugoio/hugoDocs.git synced 2025-09-13 11:06:36 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix sample data for sort function (#1363)

Browse Source
This commit is contained in:
Joe Mooring 2021-03-16 07:16:30 -07:00 committed by GitHub
parent 2beb1c0edf
commit 05c8619f48
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/en/functions/sort.md
View File

@ -23,7 +23,7 @@ A sorted array of map values will be returned with the keys eliminated. There ar
```
+++
keywords: [ "tag3", "tag1", "tag2" ]
tags = [ "tag1", "tag3", "tag2" ]
+++
// Site config
@ -62,4 +62,3 @@ Authors: {{ range sort .Site.Params.authors "lastName" "desc" }}{{ .lastName }}
→ Outputs Authors: Perkins Linsley Bergevin
```

12
content/en/getting-started/usage.md
View File

@ -120,15 +120,15 @@ in 90 ms
Hugo allows you to set `draft`, `publishdate`, and even `expirydate` in your content's [front matter][]. By default, Hugo will not publish:
1. Content with a future `publishdate` value
2. Content with `draft: true` status
3. Content with a past `expirydate` value
1. Content with `draft: true` status
2. Content with a past `expirydate` value
3. Content with a future `publishdate` value
All three of these can be overridden during both local development *and* deployment by adding the following flags to `hugo` and `hugo server`, respectively, or by changing the boolean values assigned to the fields of the same name (without `--`) in your [configuration][config]:
1. `--buildFuture`
2. `--buildDrafts`
3. `--buildExpired`
`-D` or `--buildDrafts`\
`-E` or `--buildExpired`\
`-F` or `--buildFuture`\
## LiveReload