github/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2024-11-30 04:03:30 -05:00
Code Issues Projects Releases Packages Wiki Activity

Doc Data Files: Add section about themes and expanded the example a bit

Browse source
This commit is contained in:
bep 2015-02-12 09:09:35 +01:00
parent 1217632307
commit 4820683330
2 changed files with 22 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
docs/content/extras/datafiles.md
View file

@ -17,6 +17,8 @@ Hugo supports loading data from [YAML](http://yaml.org/), [JSON](http://www.json
**It even works with [LiveReload](/extras/livereload/).** **It even works with [LiveReload](/extras/livereload/).**
Data Files can also be used in [themes](/themes/overview/), but note: If the same `key` is used in both the main data folder and in the theme's data folder, the main one will win. So, for theme authors, for theme specific data items that shouldn't be overridden, it can be wise to prefix the folder structure with a namespace, e.g. `mytheme/data/mytheme/somekey/...`. To check if any such duplicate exists, run hugo with the `-v` flag, e.g. `hugo -v`.
## The Data Folder ## The Data Folder
As explained in [Source Organization](/overview/source-directory/), the `data` folder is where you can store additional data for Hugo to use when generating your site. These files must be YAML, JSON or TOML files (using either the `.yml`, `.yaml`, `.json` or `toml` extension) and the data will be accessible as a `map` in `.Site.Data`. As explained in [Source Organization](/overview/source-directory/), the `data` folder is where you can store additional data for Hugo to use when generating your site. These files must be YAML, JSON or TOML files (using either the `.yml`, `.yaml`, `.json` or `toml` extension) and the data will be accessible as a `map` in `.Site.Data`.
@ -27,11 +29,16 @@ This is best explained with an example:
## Example: Jaco Pastorius' Solo Discography ## Example: Jaco Pastorius' Solo Discography
[Jaco Pastorius](http://en.wikipedia.org/wiki/Jaco_Pastorius_discography) was a great bass player, but his solo discography is short enough to use as an example. [Jaco Pastorius](http://en.wikipedia.org/wiki/Jaco_Pastorius_discography) was a great bass player, but his solo discography is short enough to use as an example. [John Patitucci](http://en.wikipedia.org/wiki/John_Patitucci) is another bass giant.
The example below uses TOML as file format. The example below is a bit constructed, but it illustrates the flexibility of Data Files. It uses TOML as file format.
Given the file `data/jazz/bass/jacopastorius.toml` with the content below: Given the files:
* `data/jazz/bass/jacopastorius.toml`
* `data/jazz/bass/johnpatitucci.toml`
`jacopastorius.toml` contains the content below, `johnpatitucci.toml` contains a similar list:
``` ```
discography = [ discography = [
@ -53,16 +60,24 @@ discography = [
] ]
``` ```
This list can be accessed via `.Site.Data.jazz.bass.jacopastorius.discography`. The list of bass players can be accessed via `.Site.Data.jazz.bass`, a single bass player by adding the filename without the suffix, e.g. `.Site.Data.jazz.bass.jacopastorius`.
You can now render the list of recordings in a template: You can now render the list of recordings for all the bass players in a template:
```
{{ range $.Site.Data.jazz.bass }}
{{ partial "artist.html" . }}
{{ end }}
```
And then in `partial/artist.html`:
``` ```
<ul> <ul>
{{ range $.Site.Data.jazz.bass.jacopastorius.discography }} {{ range .discography }}
<li>{{ . }}</li> <li>{{ . }}</li>
{{ end }} {{ end }}
</ul> </ul>
``` ```
Discover a new favourite bass player? Just add another TOML-file.

0
docs/nohup.out Normal file
View file