Merge commit '14e369b961943a0b977776899e24e8bea63834df'

docs/content/en/content-management/build-options.md

@@ -0,0 +1,94 @@
+---
+title: Build Options
+linktitle: Build Options
+description: Build options help define how Hugo must treat a given page when building the site.
+date: 2020-03-02
+publishdate: 2020-03-02
+keywords: [build,content,front matter, page resources]
+categories: ["content management"]
+menu:
+  docs:
+    parent: "content-management"
+    weight: 31
+weight: 31	#rem
+draft: false
+aliases: [/content/build-options/]
+toc: true
+---
+
+They are stored in a reserved Front Matter object named `_build` with the following defaults:
+
+```yaml
+_build:
+  render: true
+  list: true
+  publishResources: true
+```
+
+#### render
+If true, the page will be treated as a published page, holding its dedicated output files (`index.html`, etc...) and permalink.
+
+#### list
+If true, the page will be treated as part of the project's collections and, when appropriate, returned by Hugo's listing methods (`.Pages`, `.RegularPages` etc...).
+
+#### publishResources
+
+If set to true the [Bundle's Resources]({{< relref "content-management/page-bundles" >}}) will be published. 
+Setting this to false will still publish Resources on demand (when a resource's `.Permalink` or `.RelPermalink` is invoked from the templates) but will skip the others.
+
+{{% note %}}
+Any page, regardless of their build options, will always be available using the [`.GetPage`]({{< relref "functions/GetPage" >}}) methods.
+{{% /note %}}
+
+------
+
+### Illustrative use cases
+
+#### Not publishing a page
+Project needs a "Who We Are" content file for Front Matter and body to be used by the homepage but nowhere else.
+
+```yaml
+# content/who-we-are.md`
+title: Who we are
+_build:
+ list: false
+ render: false
+```
+
+```go-html-template
+{{/* layouts/index.html */}}
+<section id="who-we-are">
+{{ with site.GetPage "who-we-are" }}
+  {{ .Content }}
+{{ end }}
+</section>
+```
+
+#### Listing pages without publishing them
+
+Website needs to showcase a few of the hundred "testimonials" available as content files without publishing any of them.
+
+To avoid setting the build options on every testimonials, one can use [`cascade`]({{< relref "/content-management/front-matter#front-matter-cascade" >}}) on the testimonial section's content file.
+
+```yaml
+#content/testimonials/_index.md
+title: Testimonials
+# section build options:
+_build:
+  render: true
+# children build options with cascade
+cascade:
+  _build:
+    render: false
+    list: true # default
+```
+
+```go-html-template
+{{/* layouts/_defaults/testimonials.html */}}
+<section id="testimonials">
+{{ range first 5 .Pages }}
+  <blockquote cite="{{ .Params.cite }}">
+    {{ .Content }}
+  </blockquote>
+{{ end }}
+</section>

docs/content/en/content-management/image-processing/index.md

@@ -101,6 +101,17 @@ TAG: {{ $k }}: {{ $v }}
 {{ end }}
 ```
 
+Or individually access EXIF data with dot access, e.g.:
+
+```go-html-template
+{{ with $img.Exif }}
+Date: {{ .Date }}
+Lat/Long: {{ .Lat }}/{{ .Long }}
+Aperture: {{ .Tags.ApertureValue }}
+Focal Length: {{ .Tags.FocalLength }}
+{{ end }}
+```
+
 #### Exif fields
 
 Date

docs/content/en/content-management/shortcodes.md

@@ -59,7 +59,7 @@ You can pass multiple lines as parameters to a shortcode by using raw string lit
 
 ```
 {{</*  myshortcode `This is some <b>HTML</b>,
-and a new line with a "quouted string".` */>}}
+and a new line with a "quoted string".` */>}}
 ```
 
 ### Shortcodes with Markdown