releaser: Add release notes to /docs for release of 0.45

[ci skip]
releaser: Bump versions for release of 0.45
2026-08-30 18:22:37 +00:00 · 2018-07-22 12:09:26 +00:00 · 2018-07-22 12:09:26 +00:00 · 2018-07-22 14:04:01 +02:00 · 2018-07-22 10:07:03 +00:00 · 2018-07-22 00:35:09 +02:00
162 changed files with 1766 additions and 779 deletions
@@ -24,34 +24,52 @@ type Partition struct {
 	Load func() (map[string]interface{}, error)
 }

-type lazyPartition struct {
+// Lazy represents a lazily loaded cache.
+type Lazy struct {
 	initSync sync.Once
+	initErr  error
 	cache    map[string]interface{}
 	load     func() (map[string]interface{}, error)
 }

-func (l *lazyPartition) init() error {
-	var err error
+// NewLazy creates a lazy cache with the given load func.
+func NewLazy(load func() (map[string]interface{}, error)) *Lazy {
+	return &Lazy{load: load}
+}
+
+func (l *Lazy) init() error {
 	l.initSync.Do(func() {
-		var c map[string]interface{}
-		c, err = l.load()
+		c, err := l.load()
 		l.cache = c
+		l.initErr = err
+
 	})

-	return err
+	return l.initErr
+}
+
+// Get initializes the cache if not already initialized, then looks up the
+// given key.
+func (l *Lazy) Get(key string) (interface{}, bool, error) {
+	l.init()
+	if l.initErr != nil {
+		return nil, false, l.initErr
+	}
+	v, found := l.cache[key]
+	return v, found, nil
 }

 // PartitionedLazyCache is a lazily loaded cache paritioned by a supplied string key.
 type PartitionedLazyCache struct {
-	partitions map[string]*lazyPartition
+	partitions map[string]*Lazy
 }

 // NewPartitionedLazyCache creates a new NewPartitionedLazyCache with the supplied
 // partitions.
 func NewPartitionedLazyCache(partitions ...Partition) *PartitionedLazyCache {
-	lazyPartitions := make(map[string]*lazyPartition, len(partitions))
+	lazyPartitions := make(map[string]*Lazy, len(partitions))
 	for _, partition := range partitions {
-		lazyPartitions[partition.Key] = &lazyPartition{load: partition.Load}
+		lazyPartitions[partition.Key] = NewLazy(partition.Load)
 	}
 	cache := &PartitionedLazyCache{partitions: lazyPartitions}

@@ -67,11 +85,12 @@ func (c *PartitionedLazyCache) Get(partition, key string) (interface{}, error) {
 		return nil, nil
 	}

-	if err := p.init(); err != nil {
+	v, found, err := p.Get(key)
+	if err != nil {
 		return nil, err
 	}

-	if v, found := p.cache[key]; found {
+	if found {
 		return v, nil
 	}

@@ -24,8 +24,6 @@ import (

 	"github.com/spf13/cobra"

-	"github.com/gohugoio/hugo/utils"
-
 	"github.com/spf13/afero"

 	"github.com/gohugoio/hugo/hugolib"
@@ -308,7 +306,7 @@ func (c *commandeer) loadConfig(mustHaveConfigFile, running bool) error {
 			cacheDir = cacheDir + helpers.FilePathSeparator
 		}
 		isDir, err := helpers.DirExists(cacheDir, sourceFs)
-		utils.CheckErr(cfg.Logger, err)
+		checkErr(cfg.Logger, err)
 		if !isDir {
 			mkdir(cacheDir)
 		}
@@ -14,9 +14,12 @@
 package commands

 import (
+	"os"
+
 	"github.com/gohugoio/hugo/config"
 	"github.com/gohugoio/hugo/helpers"
 	"github.com/spf13/cobra"
+	jww "github.com/spf13/jwalterweatherman"

 	"github.com/spf13/nitro"
 )
@@ -241,3 +244,39 @@ func (cc *hugoBuilderCommon) handleFlags(cmd *cobra.Command) {
 	_ = cmd.Flags().SetAnnotation("destination", cobra.BashCompSubdirsInDir, []string{})
 	_ = cmd.Flags().SetAnnotation("theme", cobra.BashCompSubdirsInDir, []string{"themes"})
 }
+
+func checkErr(logger *jww.Notepad, err error, s ...string) {
+	if err == nil {
+		return
+	}
+	if len(s) == 0 {
+		logger.CRITICAL.Println(err)
+		return
+	}
+	for _, message := range s {
+		logger.ERROR.Println(message)
+	}
+	logger.ERROR.Println(err)
+}
+
+func stopOnErr(logger *jww.Notepad, err error, s ...string) {
+	if err == nil {
+		return
+	}
+
+	defer os.Exit(-1)
+
+	if len(s) == 0 {
+		newMessage := err.Error()
+		// Printing an empty string results in a error with
+		// no message, no bueno.
+		if newMessage != "" {
+			logger.CRITICAL.Println(newMessage)
+		}
+	}
+	for _, message := range s {
+		if message != "" {
+			logger.CRITICAL.Println(message)
+		}
+	}
+}
@@ -43,7 +43,6 @@ import (
 	"github.com/gohugoio/hugo/helpers"
 	"github.com/gohugoio/hugo/hugolib"
 	"github.com/gohugoio/hugo/livereload"
-	"github.com/gohugoio/hugo/utils"
 	"github.com/gohugoio/hugo/watcher"
 	"github.com/spf13/afero"
 	"github.com/spf13/cobra"
@@ -351,7 +350,7 @@ func (c *commandeer) build() error {
 		c.Logger.FEEDBACK.Println("Watching for changes in", c.hugo.PathSpec.AbsPathify(c.Cfg.GetString("contentDir")))
 		c.Logger.FEEDBACK.Println("Press Ctrl+C to stop")
 		watcher, err := c.newWatcher(watchDirs...)
-		utils.CheckErr(c.Logger, err)
+		checkErr(c.Logger, err)
 		defer watcher.Close()

 		var sigs = make(chan os.Signal)
@@ -813,7 +812,7 @@ func (c *commandeer) newWatcher(dirList ...string) (*watcher.Batcher, error) {
 						c.Logger.FEEDBACK.Printf("Syncing all static files\n")
 						_, err := c.copyStatic()
 						if err != nil {
-							utils.StopOnErr(c.Logger, err, "Error copying static files to publish dir")
+							stopOnErr(c.Logger, err, "Error copying static files to publish dir")
 						}
 					} else {
 						if err := staticSyncer.syncsStaticEvents(staticEvents); err != nil {
@@ -23,5 +23,5 @@ func init() {

  You need to open cmd.exe and run Hugo from there.
  
-  Visit http://gohugo.io/ for more information.`
+  Visit https://gohugo.io/ for more information.`
 }
@@ -17,6 +17,7 @@ import (
 	"fmt"
 	"net/http"
 	"os"
+	"runtime"
 	"testing"
 	"time"

@@ -27,6 +28,10 @@ import (
 )

 func TestServer(t *testing.T) {
+	if isWindowsCI() {
+		// TODO(bep) not sure why server tests have started to fail on the Windows CI server.
+		t.Skip("Skip server test on appveyor")
+	}
 	assert := require.New(t)
 	dir, err := createSimpleTestSite(t)
 	assert.NoError(err)
@@ -107,3 +112,7 @@ func TestFixURL(t *testing.T) {
 		}
 	}
 }
+
+func isWindowsCI() bool {
+	return runtime.GOOS == "windows" && os.Getenv("CI") != ""
+}
@@ -34,7 +34,6 @@ section = [ "HTML", "RSS"]

 [mediaTypes]
 [mediaTypes."text/netlify"]
-suffix = ""
 delimiter = ""

 [outputFormats]
@@ -70,7 +69,7 @@ twitter = "GoHugoIO"
 [params]
  description = "The world’s fastest framework for building websites"
  ## Used for views in rendered HTML (i.e., rather than using the .Hugo variable)
-  release = "0.44"
+  release = "0.45"
  ## Setting this to true will add a "noindex" to *EVERY* page on the site
  removefromexternalsearch = false
  ## Gh repo for site footer (include trailing slash)
@@ -167,7 +166,11 @@ anchor = "smart"
  weight = 35
  identifier = "variables"
  url = "/variables/"
-
+[[menu.docs]]
+  name = "Hugo Pipes"
+  weight = 36
+  identifier = "pipes"
+  url = "/hugo-pipes/"
 [[menu.docs]]
  name = "CLI"
  weight = 40
@@ -24,7 +24,7 @@ This documentation belongs in other places in this documentation site, but is pu

 Also see this demo project from [bep](https://github.com/bep/), the clever Norwegian behind these new features:

-* http://hugotest.bep.is/
+* https://temp.bep.is/hugotest/
 * https://github.com/bep/hugotest (source)

 ## Page Resources
@@ -43,27 +43,23 @@ Hugo is for people building a blog, a company site, a portfolio site, documentat

 [@spf13]: https://twitter.com/@spf13
 [Aerobatic]: https://www.aerobatic.com/
-[Amazon S3]: http://aws.amazon.com/s3/
+[Amazon S3]: https://aws.amazon.com/s3/
 [Azure]: https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/
-[CloudFront]: http://aws.amazon.com/cloudfront/ "Amazon CloudFront"
-[contributing to it]: https://github.com/gohugoio/hugo
-[DreamHost]: http://www.dreamhost.com/
+[CloudFront]: https://aws.amazon.com/cloudfront/ "Amazon CloudFront"
+[DreamHost]: https://www.dreamhost.com/
 [Firebase]: https://firebase.google.com/docs/hosting/ "Firebase static hosting"
 [GitHub Pages]: https://pages.github.com/
 [GitLab Pages]: https://about.gitlab.com/features/pages/
 [Go language]: https://golang.org/
 [GoDaddy]: https://www.godaddy.com/ "Godaddy.com Hosting"
-[Google Cloud Storage]: http://cloud.google.com/storage/
+[Google Cloud Storage]: https://cloud.google.com/storage/
 [Heroku]: https://www.heroku.com/
-[Jekyll]: http://jekyllrb.com/
 [Jekyll]: https://jekyllrb.com/
 [Middleman]: https://middlemanapp.com/
-[Middleman]: https://middlemanapp.com/
-[Nanoc]: http://nanoc.ws/
 [Nanoc]: https://nanoc.ws/
 [Netlify]: https://netlify.com
+[Rackspace]: https://www.rackspace.com/cloud/files
+[Surge]: https://surge.sh
+[contributing to it]: https://github.com/gohugoio/hugo
 [rackspace]: https://www.rackspace.com/cloud/files
 [static site generator]: /about/benefits/
-[Rackspace]: https://www.rackspace.com/cloud/files
-[static site generator]: /about/benefits/
-[Surge]: https://surge.sh
@@ -170,7 +170,7 @@ Last but not least, we have to create the second list that contains all publicat
 The layout for this page can be defined in the template `layouts/taxonomy/author.html`.

 {{< code file="layouts/taxonomy/author.html" download="author.html" >}}
-{{ range .Data.Pages }}
+{{ range .Pages }}
    <h2><a href="{{ .Permalink }}">{{ .Title }}</a></h2>
    <span>written by {{ .Author.DisplayName }}</span>
    {{ .Summary }}
@@ -1,6 +1,6 @@
 ---
 title: Links and Cross References
-description: Hugo makes it easy to link documents together.
+description: Shortcodes for creating links to documents.
 date: 2017-02-01
 publishdate: 2017-02-01
 lastmod: 2017-03-31
@@ -16,114 +16,72 @@ toc: true
 ---


- The `ref` and `relref` shortcodes link documents together, both of which are [built-in Hugo shortcodes][]. These shortcodes are also used to provide links to headings inside of your content, whether across documents or within a document. The only difference between `ref` and `relref` is whether the resulting URL is absolute (`http://1.com/about/`) or relative (`/about/`), respectively.
+The `ref` and `relref` shortcode resolves the absolute or relative permalink given a path to a document.

 ## Use `ref` and `relref`

-```
+```go-html-template
 {{</* ref "document.md" */>}}
 {{</* ref "#anchor" */>}}
 {{</* ref "document.md#anchor" */>}}
+{{</* ref "/blog/my-post" */>}}
+{{</* ref "/blog/my-post.md" */>}}
 {{</* relref "document.md" */>}}
 {{</* relref "#anchor" */>}}
 {{</* relref "document.md#anchor" */>}}
 ```

-The single parameter to `ref` is a string with a content `documentname` (e.g., `about.md`) with or without an appended in-document `anchor` (`#who`) without spaces.
+The single parameter to `ref` is a string with a content `documentname` (e.g., `about.md`) with or without an appended in-document `anchor` (`#who`) without spaces. Hugo is flexible in how we search for documents, so the file suffix may be omitted.

-### Document Names
+**Paths without a leading `/` will first  be tried resolved relative to the current page.**

-The `documentname` is the name of a document, including the format extension; this may be just the filename, or the relative path from the `content/` directory. With a document `content/blog/post.md`, either format will produce the same result:
+You will get an error if you document could not be uniquely resolved. The error behaviour can be configured, see below.

-```
-{{</* relref "blog/post.md" */>}} => `/blog/post/`
-{{</* relref "post.md" */>}} => `/blog/post/`
+### Link to another language version
+
+Link to another language version of a document, you need to use this syntax:
+
+```go-html-template
+{{</* relref path="document.md" lang="jp" */>}}
 ```

-If you have the same filename used across multiple sections, you should only use the relative path format; otherwise, the behavior will be `undefined`. This is best illustrated with an example `content` directory:
+### Get another Output Format

-```
-.
-└── content
-    ├── events
-    │   └── my-birthday.md
-    ├── galleries
-    │   └── my-birthday.md
-    ├── meta
-    │   └── my-article.md
-    └── posts
-        └── my-birthday.md
-```
+To link to a given Output Format of a document, you can use this syntax:

-To be sure to get the correct reference in this case, use the full path: 
-
-{{< code file="content/meta/my-article.md" copy="false" >}}
-{{</* relref "events/my-birthday.md" */>}} => /events/my-birthday/
-{{< /code >}}
-
-### With Multiple Output Formats
-
-If the page exists in multiple [output formats][], `ref` or `relref` can be used with a output format name:
-
-```
- [Neat]({{</* ref "blog/neat.md" "amp" */>}})
+```go-html-template
+{{</* relref path="document.md" outputFormat="rss" */>}}
 ```

 ### Anchors

 When an `anchor` is provided by itself, the current page’s unique identifier will be appended; when an `anchor` is provided appended to `documentname`, the found page's unique identifier will be appended:

-```
+```go-html-template
 {{</* relref "#anchors" */>}} => #anchors:9decaf7
-{{</* relref "about-hugo/hugo-features.md#content" */>}} => /blog/post/#who:badcafe
 ```

 The above examples render as follows for this very page as well as a reference to the "Content" heading in the Hugo docs features pageyoursite

-```
+```go-html-template
 {{</* relref "#who" */>}} => #who:9decaf7
-{{</* relref "blog/post.md#who" */>}} => /blog/post/#who:badcafe
+{{</* relref "/blog/post.md#who" */>}} => /blog/post/#who:badcafe
 ```

 More information about document unique identifiers and headings can be found [below]({{< ref "#hugo-heading-anchors" >}}).

-### Examples

-* `{{</* ref "blog/post.md" */>}}` => `https://example.com/blog/post/`
-* `{{</* ref "post.md#tldr" */>}}` => `https://example.com/blog/post/#tldr:caffebad`
-* `{{</* relref "post.md" */>}}` => `/blog/post/`
-* `{{</* relref "blog/post.md#tldr" */>}}` => `/blog/post/#tldr:caffebad`
-* `{{</* ref "#tldr" */>}}` => `#tldr:badcaffe`
-* `{{</* relref "#tldr" */>}}` => `#tldr:badcaffe`
+## Ref and RelRef Configuration

-## Hugo Heading Anchors
+The behaviour can, since Hugo 0.45, be configured in `config.toml`:

-When using Markdown document types, Hugo generates heading anchors automatically. The generated anchor for this section is `hugo-heading-anchors`. Because the heading anchors are generated automatically, Hugo takes some effort to ensure that heading anchors are unique both inside a document and across the entire site.
+refLinksErrorLevel ("ERROR") 
+: When using `ref` or `relref` to resolve page links and a link cannot resolved, it will be logged with this logg level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`).

-Ensuring heading uniqueness across the site is accomplished with a unique identifier for each document based on its path. Unless a document is renamed or moved between sections *in the filesystem*, the unique identifier for the document will not change: `blog/post.md` will always have a unique identifier of `81df004c333b392d34a49fd3a91ba720`.
+refLinksNotFoundURL
+: URL to be used as a placeholder when a page reference cannot be found in `ref` or `relref`. Is used as-is.

-`ref` and `relref` were added so you can make these reference links without having to know the document’s unique identifier. (The links in document tables of contents are automatically up-to-date with this value.)

-```
-{{</* relref "content-management/cross-references.md#hugo-heading-anchors" */>}}
-/content-management/cross-references/#hugo-heading-anchors:77cd9ea530577debf4ce0f28c8dca242
-```
-
-### Manually Specifying Anchors
-
-For Markdown content files, if the `headerIds` [Blackfriday extension][bfext] is
-enabled (which it is by default), user can manually specify the anchor for any
-heading.
-
-Few examples:
-
-```
-## Alpha 101 {#alpha}
-
-## Version 1.0 {#version-1-dot-0}
-```
-
-[built-in Hugo shortcodes]: /content-management/shortcodes/#using-the-built-in-shortcodes
 [lists]: /templates/lists/
 [output formats]: /templates/output-formats/
 [shortcode]: /content-management/shortcodes/
@@ -36,47 +36,7 @@ A **menu** is a named array of menu entries accessible by name via the [`.Site.M
 If you make use of the [multilingual feature](/content-management/multilingual/), you can define language-independent menus.
 {{% /note %}}

-A menu entry has the following properties (i.e., variables) available to it:
-
-`.URL`
-: string
-
-`.Name`
-: string
-
-`.Menu`
-: string
-
-`.Identifier`
-: string
-
-`.Pre`
-: template.HTML
-
-`.Post`
-: template.HTML
-
-`.Weight`
-: int
-
-`.Parent`
-: string
-
-`.Children`
-: Menu
-
-Note that menus also have the following functions available as well:
-
-`.HasChildren`
-: boolean
-
-Additionally, there are some relevant functions available to menus on a page:
-
-`.IsMenuCurrent`
-: (menu string, menuEntry *MenuEntry ) boolean
-
-`.HasMenuCurrent`
-: (menu string, menuEntry *MenuEntry) boolean
+See the [Menu Entry Properties][me-props] for all the variables and functions related to a menu entry.

 ## Add content to menus

@@ -139,7 +99,7 @@ The URLs must be relative to the context root. If the `baseURL` is `https://exam
 {{% /note %}}

 ## Nesting
- 
+
 All nesting of content is done via the `parent` field.

 The parent of an entry should be the identifier of another entry. The identifier should be unique (within a menu).
@@ -159,3 +119,4 @@ See [Menu Templates](/templates/menu-templates/) for information on how to rende
 [config]: /getting-started/configuration/
 [multilingual]: /content-management/multilingual/
 [sitevars]: /variables/
+[me-props]: /variables/menus/
@@ -97,7 +97,7 @@ anywhere:
 But you can get it by `.Site.GetPage`. Here is an example:

 ```go-html-template
-{{ $headless := .Site.GetPage "page" "some-headless-bundle" }}
+{{ $headless := .Site.GetPage "/some-headless-bundle" }}
 {{ $reusablePages := $headless.Resources.Match "author*" }}
 <h2>Authors</h2>
 {{ range $reusablePages }}
@@ -39,7 +39,7 @@ To list up to 5 related pages is as simple as including something similar to thi
 Read [this blog article](https://regisphilibert.com/blog/2018/04/hugo-optmized-relashionships-with-related-content/) for a great explanation of more advanced usage of this feature.
 {{% /note %}}

-The full set of methods available on the page lists can bee seen in this Go interface:
+The full set of methods available on the page lists can be seen in this Go interface:

 ```go
 // A PageGenealogist finds related pages in a page collection. This interface is implemented
@@ -178,7 +178,7 @@ This shortcode will convert the source code provided into syntax-highlighted HTM
 <section id="main">
  <div>
   <h1 id="title">{{ .Title }}</h1>
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
        {{ .Render "summary"}}
    {{ end }}
  </div>
@@ -194,7 +194,7 @@ The `highlight` shortcode example above would produce the following HTML when th
 <span style="color: #f92672">&lt;section</span> <span style="color: #a6e22e">id=</span><span style="color: #e6db74">&quot;main&quot;</span><span style="color: #f92672">&gt;</span>
  <span style="color: #f92672">&lt;div&gt;</span>
   <span style="color: #f92672">&lt;h1</span> <span style="color: #a6e22e">id=</span><span style="color: #e6db74">&quot;title&quot;</span><span style="color: #f92672">&gt;</span>{{ .Title }}<span style="color: #f92672">&lt;/h1&gt;</span>
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
        {{ .Render &quot;summary&quot;}}
    {{ end }}
  <span style="color: #f92672">&lt;/div&gt;</span>
@@ -1,6 +1,6 @@
 ---
 title: Static Files
-description: "The `static` folder is where you place all your **static files**."
+description: "Files that get served **statically** (as-is, no modification) on the site root."
 date: 2017-11-18
 categories: [content management]
 keywords: [source, directories]
@@ -13,36 +13,58 @@ aliases: [/static-files]
 toc: true
 ---

-The `static` folder is where you place all your **static files**, e.g. stylesheets, JavaScript, images etc.
+By default, the `static/` directory in the site project is used for
+all **static files** (e.g. stylesheets, JavaScript, images).

-You can set the name of the static folder to use in your configuration file.  From **Hugo 0.31** you can configure as many static directories as you need. All the files in all the static directories will form a union filesystem.
+Hugo can be configured to look into a different directory, or even
+**multiple directories** for such static files by configuring the
+`staticDir` parameter in the [site config][]. All the files in all the
+static directories will form a union filesystem.

-Example:
+This union filesystem will be served from your site root. So a file
+`<SITE PROJECT>/static/me.png` will be accessible as
+`<MY_BASEURL>/me.png`.
+
+Here's an example of setting `staticDir` and `staticDir2` for a
+multi-language site:

 {{< code-toggle copy="false" file="config" >}}
 staticDir = ["static1", "static2"]
-[languages]
-[languages.no]
-staticDir = ["staticDir_override", "static_no"]
-baseURL = "https://example.no"
-languageName = "Norsk"
-weight = 1
-title = "På norsk"

+[languages]
 [languages.en]
 staticDir2 = "static_en"
 baseURL = "https://example.com"
 languageName = "English"
 weight = 2
 title = "In English"
+[languages.no]
+staticDir = ["staticDir_override", "static_no"]
+baseURL = "https://example.no"
+languageName = "Norsk"
+weight = 1
+title = "På norsk"
 {{</ code-toggle >}}

 In the above, with no theme used:

-* The English site will get its static files as a union of "static1", "static2" and "static_en". On file duplicates, the right-most version will win.
-* The Norwegian site will get its static files as a union of "staticDir_override" and "static_no".
+- The English site will get its static files as a union of "static1",
+  "static2" and "static_en". On file duplicates, the right-most
+  version will win.
+- The Norwegian site will get its static files as a union of
+  "staticDir_override" and "static_no".

-**Note:** The `2` `static2` (can be a number between 0 and 10) is added to tell Hugo that you want to **add** this directory to the global set of static directories. Using `staticDir` on the language level would replace the global value.
+Note 1
+: The **2** (can be a number between 0 and 10) in `staticDir2` is
+  added to tell Hugo that you want to **add** this directory to the
+  global set of static directories defined using `staticDir`. Using
+  `staticDir` on the language level would replace the global value (as
+  can be seen in the Norwegian site case).
+
+Note 2
+: The example above is a [multihost setup][]. In a regular setup, all
+  the static directories will be available to all sites.


-**Note:** The example above is a [multihost setup](/content-management/multilingual/#configure-multilingual-multihost). In a regular setup, all the static directories will be available to all sites.
+[site config]: /getting-started/configuration/#all-configuration-settings
+[multihost setup]: /content-management/multilingual/#configure-multilingual-multihost
@@ -1,7 +1,7 @@
 ---
 title: Content Summaries
 linktitle: Summaries
-description: Hugo generates summaries of your content. 
+description: Hugo generates summaries of your content.
 date: 2017-01-10
 publishdate: 2017-01-10
 lastmod: 2017-01-10
@@ -57,7 +57,7 @@ Be careful to enter <code>&#60;&#33;&#45;&#45;more&#45;&#45;&#62;</code> exactly
 You can show content summaries with the following code. You could use the following snippet, for example, in a [section template][].

 {{< code file="page-list-with-summaries.html" >}}
-{{ range first 10 .Data.Pages }}
+{{ range first 10 .Pages }}
    <article>
      <!-- this <div> includes the title summary -->
      <div>
@@ -78,4 +78,4 @@ Note how the `.Truncated` boolean valuable may be used to hide the "Read More...

 [org]: /content-management/formats/
 [pagevariables]: /variables/page/
-[section template]: /templates/section-templates/
+[section template]: /templates/section-templates/
@@ -134,7 +134,7 @@ Highlighting is carried out via the [built-in shortcode](/content-management/sho
 <section id="main">
  <div>
    <h1 id="title">{{ .Title }}</h1>
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
      {{ .Render "summary"}}
    {{ end }}
  </div>
@@ -157,7 +157,7 @@ It is also possible to add syntax highlighting with GitHub flavored code fences.
 <section id="main">
  <div>
    <h1 id="title">{{ .Title }}</h1>
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
      {{ .Render "summary"}}
    {{ end }}
  </div>
@@ -1,6 +1,6 @@
 ---
 title: .GetPage
-description: "Gets a `Page` of a given `Kind` and `path`."
+description: "Gets a `Page` of a given `path`."
 godocref:
 date: 2017-02-01
 publishdate: 2017-02-01
@@ -10,7 +10,7 @@ menu:
  docs:
    parent: "functions"
 keywords: [sections,lists,indexes]
-signature: [".GetPage KIND PATH"]
+signature: [".GetPage PATH"]
 workson: []
 hugoversion:
 relatedfuncs: []
@@ -18,35 +18,42 @@ deprecated: false
 aliases: []
 ---

-Every `Page` has a [`Kind` attribute][page_kinds] that shows what kind of page it is. While this attribute can be used to list pages of a certain `kind` using `where`, often it can be useful to fetch a single page by its path.
-
-`.GetPage` returns a page of a given `Kind` and `path`.
+`.GetPage` returns a page of a given `path`. Both `Site` and `Page` implements this method. The `Page` variant will, if given a relative path -- i.e. a path without a leading `/` -- try look for the page relative to the current page.

 {{% note %}}
-If the `path` is `"foo/bar.md"`, it can be written as exactly that, or broken up
-into multiple strings as `"foo" "bar.md"`.
+**Note:** We overhauled and simplified the `.GetPage` API in Hugo 0.45. Before that you needed to provide a `Kind` attribute in addition to the path, e.g. `{{ .Site.GetPage "section" "blog" }}`. This will still work, but is now superflous.
 {{% /note %}}

-```
-{{ with .Site.GetPage "section" "blog" }}{{ .Title }}{{ end }}
+
+```go-html-template
+{{ with .Site.GetPage "/blog" }}{{ .Title }}{{ end }}
 ```

 This method wil return `nil` when no page could be found, so the above will not print anything if the blog section is not found.

-For a regular page (whose `Kind` is `page`):
+To fund a regular page in the blog section::

-```
-{{ with .Site.GetPage "page" "blog/my-post.md" }}{{ .Title }}{{ end }}
+```go-html-template
+{{ with .Site.GetPage "/blog/my-post.md" }}{{ .Title }}{{ end }}
 ```

-Note that the `path` can also be supplied like this, where the slash-separated
-path elements are added as separate strings:
+And since `Page` also provides a `.GetPage` method, the above is the same as:

-```
-{{ with .Site.GetPage "page" "blog" "my-post.md" }}{{ .Title }}{{ end }}
+```go-html-template
+{{ with .Site.GetPage "/blog" }}
+{{ with .GetPage "my-post.md" }}{{ .Title }}{{ end }}
+{{ end }}
 ```

-## `.GetPage` Example
+## .GetPage and Multilingual Sites
+
+The previous examples have used the full content filename to lookup the post. Depending on how you have organized your content (whether you have the language code in the file name or not, e.g. `my-post.en.md`), you may want to do the lookup without extension. This will get you the current language's version of the page:
+
+```go-html-template
+{{ with .Site.GetPage "/blog/my-post" }}{{ .Title }}{{ end }}
+```
+
+## .GetPage Example

 This code snippet---in the form of a [partial template][partials]---allows you to do the following:

@@ -57,7 +64,7 @@ This code snippet---in the form of a [partial template][partials]---allows you t

 {{< code file="grab-top-two-tags.html" >}}
 <ul class="most-popular-tags">
-{{ $t := .Site.GetPage "taxonomyTerm" "tags" }}
+{{ $t := .Site.GetPage "/tags" }}
 {{ range first 2 $t.Data.Terms.ByCount }}
    <li>{{ . }}</li>
 {{ end }}
@@ -39,7 +39,7 @@ You can use `after` in combination with the [`first` function][] and Hugo's [pow
 {{ define "main" }}
 <section class="row featured-article">
    <h2>Featured Article</h2>
-    {{ range first 1 .Data.Pages.ByPublishDate.Reverse }}
+    {{ range first 1 .Pages.ByPublishDate.Reverse }}
     <header>
        <h3><a href="{{.Permalink}}">{{.Title}}</a></h3>
    </header>
@@ -48,7 +48,7 @@ You can use `after` in combination with the [`first` function][] and Hugo's [pow
 </section>
 <div class="row recent-articles">
    <h2>Recent Articles</h2>
-    {{ range first 3 (after 1 .Data.Pages.ByPublishDate.Reverse) }}
+    {{ range first 3 (after 1 .Pages.ByPublishDate.Reverse) }}
        <section class="recent-article">
            <header>
                <h3><a href="{{.Permalink}}">{{.Title}}</a></h3>
@@ -21,8 +21,7 @@ aliases: []


 ```
-{{ range first 10 .Data.Pages }}
+{{ range first 10 .Pages }}
    {{ .Render "summary" }}
 {{ end }}
 ```
-
@@ -10,14 +10,18 @@ menu:
  docs:
    parent: "functions"
 keywords: [menus]
-signature: ["HasMenuCurrent"]
+signature: ["PAGE.HasMenuCurrent MENU MENUENTRY"]
 workson: [menus]
 hugoversion:
-relatedfuncs: []
+relatedfuncs: ["IsMenuCurrent"]
 deprecated: false
 toc: false
-draft: true
+draft: false
 aliases: []
 ---

-Used in [menu templates](/templates/menu-templates/).
+`.HasMenuCurrent` is a method in `Page` object returning a _boolean_ value. It
+returns `true` if the PAGE is the same object as the `.Page` in one of the
+**children menu entries** under MENUENTRY in a given MENU.
+
+You can find its example use in [menu templates](/templates/menu-templates/).
@@ -10,14 +10,18 @@ menu:
  docs:
    parent: "functions"
 keywords: [menus]
-signature: ["IsMenuCurrent"]
+signature: ["PAGE.IsMenuCurrent MENU MENUENTRY"]
 workson: [menus]
 hugoversion:
-relatedfuncs: []
+relatedfuncs: ["HasMenuCurrent"]
 deprecated: false
-draft: true
+draft: false
 aliases: []
 needsexample: true
 ---

-Used in [menu templates](/templates/menu-templates/).
+`.IsMenuCurrent` is a method in `Page` object returning a _boolean_ value. It
+returns `true` if the PAGE is the same object as the `.Page` in MENUENTRY in a
+given MENU.
+
+You can find its example use in [menu templates](/templates/menu-templates/).
@@ -23,8 +23,7 @@ aliases: []


 ```
-{{ range last 10 .Data.Pages }}
+{{ range last 10 .Pages }}
    {{ .Render "summary" }}
 {{ end }}
 ```
-
@@ -26,7 +26,7 @@ This function is only available when applied to a single piece of content within
 This example could render a piece of content using the content view located at `/layouts/_default/summary.html`:

 ```
-{{ range .Data.Pages }}
+{{ range .Pages }}
    {{ .Render "summary"}}
 {{ end }}
 ```
@@ -33,11 +33,19 @@ See [this Go issue](https://github.com/golang/go/issues/10608) for the main moti
 For a detailed analysis of `.Scratch` and in context use cases, see this [post](https://regisphilibert.com/blog/2017/04/hugo-scratch-explained-variable/).
 {{% /note %}}

-## Methods
+## Get a Scratch

-`Scratch` is added to both `Page` and `Shortcode` -- with following methods:
+From Hugo `0.43` you can also create a locally scoped `Scratch` by calling `newScratch`:
+
+```go-html-template
+$scratch := newScratch
+$scratch.Set "greeting" "Hello"
+```
+
+A `Scratch` is also added to both `Page` and `Shortcode`. `Sratch` have the following methods:

 #### .Set
+
 Set the given value to a given key

 ```go-html-template
@@ -23,7 +23,7 @@ needsexample: true
 `where` filters an array to only the elements containing a matching value for a given field.

 ```go-html-template
-{{ range where .Data.Pages "Section" "post" }}
+{{ range where .Pages "Section" "post" }}
  {{ .Content }}
 {{ end }}
 ```
@@ -45,7 +45,7 @@ series: golang
 It can also be used with the logical operators `!=`, `>=`, `in`, etc. Without an operator, `where` compares a given field with a matching value equivalent to `=`.

 ```go-html-template
-{{ range where .Data.Pages "Section" "!=" "post" }}
+{{ range where .Pages "Section" "!=" "post" }}
   {{ .Content }}
 {{ end }}
 ```
@@ -104,7 +104,7 @@ You can also put the returned value of the `where` clauses into a variable:
 The following grabs the first five content files in `post` using the [default ordering](/templates/lists/) for lists (i.e., `weight => date`):

 {{< code file="where-with-first.html" >}}
-{{ range first 5 (where .Data.Pages "Section" "post") }}
+{{ range first 5 (where .Pages "Section" "post") }}
   {{ .Content }}
 {{ end }}
 {{< /code >}}
@@ -114,7 +114,7 @@ The following grabs the first five content files in `post` using the [default or
 You can also nest `where` clauses to drill down on lists of content by more than one parameter. The following first grabs all pages in the "blog" section and then ranges through the result of the first `where` clause and finds all pages that are *not* featured:

 ```go-html-template
-{{ range where (where .Data.Pages "Section" "blog" ) ".Params.featured" "!=" "true" }}
+{{ range where (where .Pages "Section" "blog" ) ".Params.featured" "!=" "true" }}
 ```

 ## Unset Fields
@@ -129,7 +129,7 @@ Only the following operators are available for `nil`
 * `!=`, `<>`, `ne`: True if the given field is set.

 ```go-html-template
-{{ range where .Data.Pages ".Params.specialpost" "!=" nil }}
+{{ range where .Pages ".Params.specialpost" "!=" nil }}
   {{ .Content }}
 {{ end }}
 ```
@@ -183,6 +183,12 @@ related
 relativeURLs (false)
 : Enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs.

+refLinksErrorLevel ("ERROR") 
+: When using `ref` or `relref` to resolve page links and a link cannot resolved, it will be logged with this logg level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`).
+
+refLinksNotFoundURL
+: URL to be used as a placeholder when a page reference cannot be found in `ref` or `relref`. Is used as-is.
+
 rssLimit (unlimited)
 : Maximum number of items in the RSS feed.

@@ -193,7 +199,7 @@ sitemap
 : Default [sitemap configuration](/templates/sitemap-template/#configure-sitemap-xml).

 staticDir ("static")
-: Relative directory from where Hugo reads static files.
+: A directory or a list of directories from where Hugo reads [static files][static-files].

 stepAnalysis (false)
 : Display memory and timing of different steps of the program.
@@ -405,3 +411,4 @@ Hugo v0.20 introduced the ability to render your content to multiple output form
 [templates]: /templates/
 [toml]: https://github.com/toml-lang/toml
 [yaml]: http://yaml.org/spec/
+[static-files]: /content-management/static-files/
@@ -1,7 +1,7 @@
 ---
 title: Install Hugo
 linktitle: Install Hugo
-description: Install Hugo on macOS, Windows, Linux, FreeBSD, and on any machine where the Go compiler tool chain can run.
+description: Install Hugo on macOS, Windows, Linux, OpenBSD, FreeBSD, and on any machine where the Go compiler tool chain can run.
 date: 2016-11-01
 publishdate: 2016-11-01
 lastmod: 2018-01-02
@@ -31,6 +31,7 @@ Hugo currently provides pre-built binaries for the following:
 * macOS (Darwin) for x64, i386, and ARM architectures
 * Windows
 * Linux
+* OpenBSD
 * FreeBSD

 Hugo may also be compiled from source wherever the Go compiler tool chain can run; e.g., on other operating systems such as DragonFly BSD, OpenBSD, Plan&nbsp;9, Solaris, and others. See <https://golang.org/doc/install/source> for the full set of supported combinations of target operating systems and compilation architectures.
@@ -451,7 +452,7 @@ Hugo-as-a-snap can write only inside the user’s `$HOME` directory---and gvfs-m
 You can also install Hugo from the Arch Linux [community](https://www.archlinux.org/packages/community/x86_64/hugo/) repository. Applies also for derivatives such as Manjaro.

 ```
-sudo pacman -Sy hugo
+sudo pacman -Syu hugo
 ```

 ### Fedora
@@ -468,6 +469,14 @@ sudo dnf install hugo

 See the [related discussion in the Hugo forums][redhatforum].

+## OpenBSD
+
+OpenBSD provides a package for Hugo via `pkg_add`: 
+
+```
+doas pkg_add hugo
+```
+
 ## Upgrade Hugo

 Upgrading Hugo is as easy as downloading and replacing the executable you’ve placed in your `PATH` or run `brew upgrade hugo` if using Homebrew.
@@ -0,0 +1,15 @@
+---
+title: Hugo Pipes Overview
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 10
+weight: 10
+sections_weight: 10
+draft: false
+---
@@ -0,0 +1,26 @@
+---
+title: Asset bundling
+description: Hugo Pipes can bundle any number of assets together.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 60
+weight: 60
+sections_weight: 60
+draft: false
+---
+
+
+Asset files of the same MIME type can be bundled into one resource using `resources.Concat` which takes two arguments, a target path and a slice of resource objects.
+
+
+```go-html-template
+{{ $plugins := resources.Get "js/plugins.js" }}
+{{ $global := resources.Get "js/global.js" }}
+{{ $js := slice $plugins $global | resources.Concat "js/bundle.js" }}
+```
@@ -0,0 +1,29 @@
+---
+title: Fingerprinting and SRI
+description: Hugo Pipes allows Fingerprinting and Subresource Integrity.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 70
+weight: 70
+sections_weight: 70
+draft: false
+---
+
+
+Fingerprinting and [SRI](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) can be applied to any asset file using `resources.Fingerpint` which takes two arguments, the resource object and a [hash function](https://en.wikipedia.org/wiki/Cryptographic_hash_function). 
+
+The default hash function is `sha256`. Other available functions are `sha512` and `md5`.
+
+Any so processed asset will bear a `.Data.Integrity` property containing an integrity string, which is made up of the name of the hash function, one hyphen and the base64-encoded hash sum.
+
+```go-html-template
+{{ $js := resources.Get "js/global.js" }}
+{{ $secureJS := $js | resources.Fingerprint "sha512" }}
+<script type="text/javascript" src="{{ $secureJS.Permalink }}" integrity="{{ $secureJS.Data.Integrity }}"></script>
+```
@@ -0,0 +1,52 @@
+---
+title: Hugo Pipes Introduction
+description: Hugo Pipes is Hugo's asset processing set of functions.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 20
+weight: 01
+sections_weight: 01
+draft: false
+aliases: [/assets/]
+--- 
+
+### Asset directory
+
+Asset files must be stored in the asset directory. This is `/assets` by default, but can be configured via the configuration file's `assetDir` key.
+
+### From file to resource
+
+In order to process an asset with Hugo Pipes, it must be retrieved as a resource using `resources.Get`, which takes one argument: the filepath of the file relative to the asset directory.
+
+```go-html-template
+{{ $style := resources.Get "sass/main.scss" }}
+```
+
+### Asset publishing
+
+Assets will only be published (to `/public`) if `.Permalink` or `.RelPermalink` is used.
+
+### Go Pipes
+
+For improved readability, the Hugo Pipes examples of this documentation will be written using [Go Pipes](/templates/introduction/#pipes):
+```go-html-template
+{{ $style := resources.Get "sass/main.scss" | resources.ToCSS | resources.Minify | resources.Fingerprint }}
+<link rel="stylesheet" href="{{ $style.Permalink }}">
+```
+
+### Method aliases
+
+Each Hugo Pipes `resources` transformation method uses a __camelCased__ alias (`toCSS` for `resources.ToCSS`).
+Non-transformation methods deprived of such aliases are `resources.Get`, `resources.FromString` and `resources.ExecuteAsTemplate`.
+
+The example above can therefore also be written as follows:
+```go-html-template
+{{ $style := resources.Get "sass/main.scss" | toCSS | minify | fingerprint }}
+<link rel="stylesheet" href="{{ $style.Permalink }}">
+```
@@ -0,0 +1,25 @@
+---
+title: Asset minification
+description: Hugo Pipes allows the minification of any CSS, JS, JSON, HTML, SVG or XML resource.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 50
+weight: 50
+sections_weight: 50
+draft: false
+---
+
+
+Any resource of the aforementioned types can be minifed using `resources.Minify` which takes for argument the resource object.
+
+
+```go-html-template
+{{ $css := resources.Get "css/main.css" }}
+{{ $style := $css | resources.Minify }}
+```
@@ -0,0 +1,56 @@
+---
+title: PostCSS
+description: Hugo Pipes can process CSS files with PostCSS.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 40
+weight: 40
+sections_weight: 40
+draft: false
+---
+
+
+Any asset file can be processed using `resources.PostCSS` which takes for argument the resource object and a slice of options listed below. 
+
+The resource will be processed using the project's or theme's own `postcss.config.js` or any file set with the `config` option.
+
+
+```go-html-template
+{{ $css := resources.Get "css/main.css" }}
+{{ $style := $css | resources.PostCSS }}
+```
+
+{{% note %}}
+Hugo Pipe's PostCSS requires `postcss-cli` javascript package to be installed on the environement along with any PostCSS plugin used.
+{{% /note %}}
+### Options
+
+config [string]
+: Path to the PostCSS configuration file
+
+noMap [bool]
+: Default is `true`. Disable the default inline sourcemaps
+
+_If no configuration file is used:_
+
+use [string]
+: List of PostCSS plugins to use
+
+parser [string]
+: Custom PostCSS parser
+
+stringifier [string]
+: Custom PostCSS stringifier
+
+syntax [string]
+: Custom postcss syntax
+
+```go-html-template
+{{ $style := resources.Get "css/main.css" | resources.PostCSS (dict "config" "customPostCSS.js" "noMap" true) }}
+```
@@ -0,0 +1,31 @@
+---
+title: Creating a resource from a string
+linkTitle: Resource from String
+description: Hugo Pipes allows the creation of a resource from a string.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 90
+weight: 90
+sections_weight: 90
+draft: false
+---
+
+It is possible to create a resource directly from the template using `resources.FromString` which takes two arguments, the given string and the resource target path.
+
+The following example creates a resource file containing localized variables for every project's languages.
+
+```go-html-template
+{{ $string := (printf "var rootURL: '%s'; var apiURL: '%s';" (absURL "/") (.Param "API_URL")) }}
+{{ $targetPath := "js/vars.js" }}
+{{ $vars := $string | resources.FromString $targetPath }}
+{{ $global := resources.Get "js/global.js" | resources.Minify }}
+
+<script type="text/javascript" src="{{ $vars.Permalink }}"></script>
+<script type="text/javascript" src="{{ $global.Permalink }}"></script>
+```
@@ -0,0 +1,38 @@
+---
+title: Creating a resource from template
+linkTitle: Resource from Template
+description: Hugo Pipes allows the creation of a resource from an asset file using Go Template.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 80
+weight: 80
+sections_weight: 80
+draft: false
+---
+
+In order to use Hugo Pipes function on an asset file containing Go Template magic the function `resources.ExecuteAsTemplate` must be used.
+
+The function takes three arguments, the resource object, the resource target path and the template context.
+
+```go-html-template
+// assets/sass/template.scss
+$backgroundColor: {{ .Param "backgroundColor" }};
+$textColor: {{ .Param "textColor" }};
+body{
+	background-color:$backgroundColor;
+	color: $textColor;
+}
+// [...]
+```
+
+
+```go-html-template
+{{ $sassTemplate := resources.Get "sass/template.scss" }}
+{{ $style := $sassTemplate | resources.ExecuteAsTemplate "main.scss" . | resources.ToCSS }}
+```
@@ -0,0 +1,42 @@
+---
+title: SASS / SCSS
+description: Hugo Pipes allows the processing of SASS and SCSS files.
+date: 2018-07-14
+publishdate: 2018-07-14
+lastmod: 2018-07-14
+categories: [asset management]
+keywords: []
+menu:
+  docs:
+    parent: "pipes"
+    weight: 30
+weight: 02
+sections_weight: 02
+draft: false
+---
+
+
+Any SASS or SCSS file can be transformed into a CSS file using `resources.ToCSS` which takes two arguments, the resource object and a map of options listed below.
+
+```go-html-template
+{{ $sass := resources.Get "sass/main.scss" }}
+{{ $style := $sass | resources.ToCSS }}
+```
+
+### Options
+targetPath [string]
+: If not set, the resource's target path will be the asset file original path with its extension replaced by `.css`.
+
+outputStyle [string]
+: Default is `nested`. Other available output styles are `expanded`, `compact` and `compressed`.
+
+precision [int]
+: Precision of floating point math.
+
+enableSourceMap [bool]
+: When enabled, a source map will be generated.
+
+```go-html-template
+{{ $options := (dict "targetPath" "style.css" "outputStyle" "compressed" "enableSourceMap" true) }}
+{{ $style := resources.Get "sass/main.scss" | resources.ToCSS $options }}
+```
@@ -9,7 +9,7 @@ images:
 ---

 	
-Hugo `0.30` is the **Race Car Edition**. Hugo is already very very fast, but much wants more. So we added **Fast Render Mode**. It is hard to explain, so start the Hugo development server with `hugo server` and start editing. Live reloads just got so much faster! The "how and what" is discussed at length in [other places](https://github.com/gohugoio/hugo/pull/3959), but the short version is that we now re-render only the parts of the site that you are working on.
+Hugo `0.30` is the **Race Car Edition**. Hugo is already very very fast, but wants much more. So we added **Fast Render Mode**. It is hard to explain, so start the Hugo development server with `hugo server` and start editing. Live reloads just got so much faster! The "how and what" is discussed at length in [other places](https://github.com/gohugoio/hugo/pull/3959), but the short version is that we now re-render only the parts of the site that you are working on.

 The second performance-related feature is a follow-up to the Template Metrics added in Hugo `0.29`. Now, if you add the flag `--templateMetricsHints`, we will calculate a score for how your partials can be cached (with the `partialCached` template func).

@@ -1,8 +1,8 @@

 ---
 date: 2018-07-09
-title: "0.43"
-description: "0.43"
+title: "And Now: Hugo Pipes!"
+description: "Hugo 0.43 adds a powerful and simple to use assets pipeline with SASS/SCSS and much, much more …"
 categories: ["Releases"]
 ---

@@ -1,8 +1,8 @@

 ---
 date: 2018-07-13
-title: "0.44"
-description: "0.44"
+title: "Hugo 0.44: Friday the 13th Edition"
+description: "A sequel to the very popular Hugo Pipes Edition; bug-fixes and enhancements …"
 categories: ["Releases"]
 ---

@@ -0,0 +1,107 @@
+
+---
+date: 2018-07-22
+title: "0.45"
+description: "0.45"
+categories: ["Releases"]
+---
+
+	
+Hugo `0.45` is the **revival of ref, relref and GetPage**. [@vassudanagunta](https://github.com/vassudanagunta) and [@bep](https://github.com/bep) have done some great work improving the API and implementation for the helper functions used to **get one page**. Before this release, the API was a little bit clumsy and the result potentially ambiguous in some situations.
+
+Now you can simply do:
+
+```go-html-template
+{{ with .Site.GetPage "/blog/my-post.md" }}{{ .Title }}{{ end }}
+```
+
+Or two get a section page:
+
+
+```go-html-template
+{{ with .Site.GetPage "/blog" }}{{ .Title }}{{ end }}
+```
+
+We have also added a `.GetPage` method on `Page` and added support for page-relative linking. This means that the leading slash (`/`) now has a meaning. For `.Site.GetPage`, all lookups will start at the content root. But for lookups with a `Page` context, paths without a leading slash will be treated as relative to the page.
+
+This means that the following example will find the page in the current section:
+
+```go-html-template
+{{</* ref "my-post.md" */>}}
+```
+
+You can also use the `..` to refer to a page one level up etc.:
+
+```go-html-template
+{{</* ref "../my-post.md" */>}}
+```
+
+We have now also added language support to `ref` and `relref`, so you can link to a page in another language:
+
+```go-html-template
+{{</* relref path="document.md" lang="jp" */>}}
+```
+
+To link to a given Output Format of a document, you can use this syntax:
+
+```go-html-template
+{{</* relref path="document.md" outputFormat="rss" */>}}
+```
+
+To make working with these reflinks on bigger sites easier to work with, we have also improved the error logging, and added two new configuration settings:
+
+* refLinksErrorLevel: ERROR (default, will fail the build when a reflink cannot be resolved) or WARNING.
+* refLinksNotFoundURL: Set this to an URL placeholder used when no reference could be resolved.
+
+Visit the [Hugo Docs](https://gohugo.io/content-management/cross-references) for more information.
+
+We have also done some important improvements and fixes in **Hugo Pipes** in this release: SCSS source maps on Windows now works, we now support project-local `PostCSS` installation, and we have added `IncludePaths` to `SCSS` options, making it possible to include, say, a path below `node_modules` in the SASS/SCSS build.
+
+This release represents **31 contributions by 4 contributors** to the main Hugo code base.
+[@bep](https://github.com/bep) leads the Hugo development with a significant amount of contributions, but also a big shoutout to [@vassudanagunta](https://github.com/vassudanagunta), [@hairmare](https://github.com/hairmare), and [@garrmcnu](https://github.com/garrmcnu) for their ongoing contributions.
+And a big thanks to [@digitalcraftsman](https://github.com/digitalcraftsman) for his relentless work on keeping the themes site in pristine condition and to [@kaushalmodi](https://github.com/kaushalmodi) for his great work on the documentation site.
+
+Many have also been busy writing and fixing the documentation in [hugoDocs](https://github.com/gohugoio/hugoDocs), 
+which has received **10 contributions by 8 contributors**. A special thanks to [@kaushalmodi](https://github.com/kaushalmodi), [@Hanzei](https://github.com/Hanzei), [@KurtTrowbridge](https://github.com/KurtTrowbridge), and [@regisphilibert](https://github.com/regisphilibert) for their work on the documentation site.
+
+
+Hugo now has:
+
+* 27334+ [stars](https://github.com/gohugoio/hugo/stargazers)
+* 443+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)
+* 238+ [themes](http://themes.gohugo.io/)
+
+## Notes
+* `.Site.GetPage` with more than 2 arguments will not work anymore. This means that `{{ .Site.GetPage "page" "blog" "my-post.md" }}` will fail. `{{ .Site.GetPage "page" "blog/my-post.md" }}` will work, but we recommend you use the simpler `{{ .Site.GetPage "/blog/my-post.md" }}`
+* Relative paths in `relref` or `ref` that finds its match not relative to the page itself will work, but we now print a warning saying that you should correct it to an absolute path. E.g. `{{</* ref "blog/my-post.md" */>}}` => `{{</* ref "/blog/my-post.md" */>}}`.
+
+## Enhancements
+
+* Print a WARNING about relative non-relative ref/relref matches [a451c49f](https://github.com/gohugoio/hugo/commit/a451c49fde1da6e2cc436a2b7d383ee772b1f893) [@bep](https://github.com/bep) [#4973](https://github.com/gohugoio/hugo/issues/4973)
+* Allow untyped nil to be merged in lang.Merge [ff16c42e](https://github.com/gohugoio/hugo/commit/ff16c42ed0965e1c8acf6e6a6dcda3ea50c107f2) [@bep](https://github.com/bep) [#4977](https://github.com/gohugoio/hugo/issues/4977)
+* Get rid of the utils package [062510cf](https://github.com/gohugoio/hugo/commit/062510cf1f7b79aed2efe88c5b9340d009bdec0e) [@bep](https://github.com/bep) 
+* Update hugo_windows.go [4e1d0cd9](https://github.com/gohugoio/hugo/commit/4e1d0cd9f1d43d133d669a019a84117cadd41955) [@bep](https://github.com/bep) 
+* Add IncludePaths config option [166483fe](https://github.com/gohugoio/hugo/commit/166483fe1227b0c59c6b4d88cfdfaf7d7b0d79c5) [@bep](https://github.com/bep) [#4921](https://github.com/gohugoio/hugo/issues/4921)
+* Increase refLinker test coverage [8278384b](https://github.com/gohugoio/hugo/commit/8278384b9680cfdcecef9c668638ad483012857f) [@vassudanagunta](https://github.com/vassudanagunta) 
+* Add test coverage for recent ref overhaul [2bac3715](https://github.com/gohugoio/hugo/commit/2bac3715448e90e197ada7cc73c87f696c19def6) [@vassudanagunta](https://github.com/vassudanagunta) [#4969](https://github.com/gohugoio/hugo/issues/4969)
+* Update ref, relref, GetPage docs [1eb8b36b](https://github.com/gohugoio/hugo/commit/1eb8b36b3802e72bc2c16965461ef1899bb073b3) [@bep](https://github.com/bep) 
+* Document refLinksErrorLevel and refLinksNotFoundURL [00c74ee7](https://github.com/gohugoio/hugo/commit/00c74ee7ffae71fd5f47d555160354a775e26151) [@bep](https://github.com/bep) [#4964](https://github.com/gohugoio/hugo/issues/4964)
+* Add configurable ref/relref error handling and notFoundURL [e25aa655](https://github.com/gohugoio/hugo/commit/e25aa655f4227ac064be5fe770d517a80acd46b2) [@bep](https://github.com/bep) [#4964](https://github.com/gohugoio/hugo/issues/4964)
+* Try node_modules/postcss-cli/bin/postcss first [ebe4d39f](https://github.com/gohugoio/hugo/commit/ebe4d39f175f73e4f130972cb3d74ef0af5d5761) [@bep](https://github.com/bep) [#4952](https://github.com/gohugoio/hugo/issues/4952)
+* Add optional lang as argument to rel/relref [d741064b](https://github.com/gohugoio/hugo/commit/d741064bebe2f4663a7ba12556dccc3dffe08629) [@bep](https://github.com/bep) [#4956](https://github.com/gohugoio/hugo/issues/4956)
+* Simplify .Site.GetPage etc. [3eb313fe](https://github.com/gohugoio/hugo/commit/3eb313fef495a39731dafa6bddbf77760090230d) [@bep](https://github.com/bep) [#4147](https://github.com/gohugoio/hugo/issues/4147)[#4727](https://github.com/gohugoio/hugo/issues/4727)[#4728](https://github.com/gohugoio/hugo/issues/4728)[#4728](https://github.com/gohugoio/hugo/issues/4728)[#4726](https://github.com/gohugoio/hugo/issues/4726)[#4652](https://github.com/gohugoio/hugo/issues/4652)
+* Unify page lookups [b93417aa](https://github.com/gohugoio/hugo/commit/b93417aa1d3d38a9e56bad25937e0e638a113faf) [@vassudanagunta](https://github.com/vassudanagunta) [#4147](https://github.com/gohugoio/hugo/issues/4147)[#4727](https://github.com/gohugoio/hugo/issues/4727)[#4728](https://github.com/gohugoio/hugo/issues/4728)[#4728](https://github.com/gohugoio/hugo/issues/4728)[#4726](https://github.com/gohugoio/hugo/issues/4726)[#4652](https://github.com/gohugoio/hugo/issues/4652)
+* Improve error message [4c240800](https://github.com/gohugoio/hugo/commit/4c240800a4275244c9e0847cd6707383180f1ac3) [@bep](https://github.com/bep) 
+* Remove unused code [2f2bc7ff](https://github.com/gohugoio/hugo/commit/2f2bc7ff70b90fb11580cc092ef3883bf68d8ad7) [@bep](https://github.com/bep) 
+
+## Fixes
+
+* Avoid server panic on TOML mistake in i18n [75acff5f](https://github.com/gohugoio/hugo/commit/75acff5f20d0d41ffa1ae20402001c7a82f077cb) [@bep](https://github.com/bep) [#4942](https://github.com/gohugoio/hugo/issues/4942)
+* Only set 'allThemes' if there are themes in the config file [38204c4a](https://github.com/gohugoio/hugo/commit/38204c4ab6fa2aa2ab8bd06ddb3e07b66e5f9646) [@garrmcnu](https://github.com/garrmcnu) [#4851](https://github.com/gohugoio/hugo/issues/4851)
+* Fix potential server panic with drafts/future enabled [1ab4658c](https://github.com/gohugoio/hugo/commit/1ab4658c0d5ea2927f04bd748206e5b139a6326e) [@bep](https://github.com/bep) [#4965](https://github.com/gohugoio/hugo/issues/4965)
+* Mark shortcode changes as content changes in server mode [12679b40](https://github.com/gohugoio/hugo/commit/12679b408362a93a3c6159588d6291a3b7ed5548) [@bep](https://github.com/bep) [#4965](https://github.com/gohugoio/hugo/issues/4965)
+* Fix source maps on Windows [f01505c9](https://github.com/gohugoio/hugo/commit/f01505c910a325acc18742ac6b3637aa01975e37) [@bep](https://github.com/bep) [#4968](https://github.com/gohugoio/hugo/issues/4968)
+* Fix typo-logic bug in GetPage [b56d9a12](https://github.com/gohugoio/hugo/commit/b56d9a1294e692d096bff442e0b1fec61a8c2b0f) [@vassudanagunta](https://github.com/vassudanagunta) 
+* Enable test case fixed by commit 501543d4 [d6fde8fa](https://github.com/gohugoio/hugo/commit/d6fde8fa131f3852fa98a8ec5c360e736486cf54) [@vassudanagunta](https://github.com/vassudanagunta) 
+* Fix theme config for Work Fs [5c9d5413](https://github.com/gohugoio/hugo/commit/5c9d5413a4e2cc8d44a8b2d7dff04e6523ba2a29) [@bep](https://github.com/bep) [#4951](https://github.com/gohugoio/hugo/issues/4951)
+* Fix addkit link to account for i18n [fd1f4a78](https://github.com/gohugoio/hugo/commit/fd1f4a7860c4b989865b47c727239cf924a52fa4) [@hairmare](https://github.com/hairmare) 
@@ -59,7 +59,7 @@ Hugo has stuck with the sub-zero versions to signal active development, with a n

 ### The Road to 1.0

-We have some more technical tasks that needs to be done (there is ongoing work to get the page quries into a more consistent state, also a simpler `.GetPage` method), but also some cool new functionality. The following roadmap is taken from memory, and may not be complete, but should be a good indication of what's ahead.
+We have some more technical tasks that needs to be done (there is ongoing work to get the page queries into a more consistent state, also a simpler `.GetPage` method), but also some cool new functionality. The following roadmap is taken from memory, and may not be complete, but should be a good indication of what's ahead.

 Pages from "other data sources"
 : Currently, in addition to Hugo's list pages, every URL must be backed by a content file (Markdown, HTML etc.). This covers most use cases, but we need a flexible way to generate pages from other data sources. Think product catalogues and similar.
@@ -67,7 +67,7 @@ Pages from "other data sources"
 Upgrade Blackfriday to v2
 : [Blackfriday](https://github.com/russross/blackfriday) is the main content renderer in Hugo. It has been rewritten to a more flexible architecture, which should allow us to fix some of the current shortcomings.

-We should be able to create a better and easier-to-use data structure from the rendered content: Summary, the content after the summary, being able to range over the footnotes and the ToC. Having ToC as a proper data structure also open up a few other potential uses; using it as an index in [Related Content](https://gohugo.io/content-management/related/) would be one example.
+We should be able to create a better and easier-to-use data structure from the rendered content: Summary, the content after the summary, being able to range over the footnotes and the ToC. Having ToC as a proper data structure also opens up a few other potential uses; using it as an index in [Related Content](https://gohugo.io/content-management/related/) would be one example.

 This should also enable us to _do more_ with [Custom Output Formats](/templates/output-formats). It is already very powerful. GettyPubs are using it in [Quire](https://github.com/gettypubs/quire) to build [beautiful multi-platform publications](http://www.getty.edu/publications/digital/digitalpubs.html). But it can be improved. For rendering of content files, you are currently restricted to HTML. It would be great if we could configure alternative renderers per output format, such as LaTeX and EPUB.

@@ -75,7 +75,7 @@ Related to this is also to add a configurable "Markdown URL rewriter", which sho

 ### The Road to the Future

-These are the items that first comes to mind if you ask me to think even further ahead:
+These are the items that first come to mind if you ask me to think even further ahead:

 Dependency manager for Theme Components
 : In Hugo `0.42` we added [Theme Components](/themes/theme-components/) and Theme Inheritance. With SCSS support in Hugo `0.43`, which also follows the same project/themes precedence order (add `_variables.scss` to your project, configure SASS colour variables in `config.toml`), we have a solid foundation for creating easy to use and extensible themes. But we are missing some infrastructure around this. We have a site with 235+ [themes](https://themes.gohugo.io/)[^themes] listed, but you currently need to do some added work to get the theme up and running for your site. In the Go world, we don't have NPM to use, which is a curse and a blessing, but I have some ideas about building a simple dependency manager into Hugo, modelled after how Go is doing it (`hugo install`). You should be able to configure what theme and theme components you want to use, and Hugo should handle the installation of the correct versions. This should make it easier for the user, but it would also enable community driven and even commercial "theme stores".
@@ -90,19 +90,19 @@ The "New York Times on Hugo" Use Case
 : There are recurring questions on the support forum from [really big sites](https://discourse.gohugo.io/t/transition-2m-posts-from-wordpress-to-hugo/12704) that want to move to Hugo. There are many [good reasons](https://www.netlify.com/blog/2016/05/18/9-reasons-your-site-should-be-static/) why they want this (security, cost-saving, EU regulations etc.). And while there have been reports about companies building 600 000 pages with Hugo on very powerful hardware, we will have to rethink the build model to make this usable. Keywords are: streaming builds, segmented builds, partial rebuilds. There are other site generators also talking about this. It should be possible, and my instinct tells me that it should be easier to do when your starting point is "really fast". But this is not a small weekend project for me, and I have already talked to several companies about sponsoring this.

 Plugins
-: A Theme Component could also be called a plugin. But there are several potential plugin hooks into Hugo's build pipeline: Resource transformations, content rendering etc. We will eventually get there, but we should do it without giving up too much of the Hugo speed and simplicity.
+: A Theme Component could also be called a plugin. But there are several potential plugin hooks into Hugo's build pipeline: resource transformations, content rendering, etc. We will eventually get there, but we should do it without giving up too much of the Hugo speed and simplicity.


 ## Thanks

-So, thanks to everyone who have contributed to getting Hugo where it is today. It is hard to single out individuals, but a big shout-out to all the Hugo experts and moderators helping out making the [discourse.gohugo.io](https://discourse.gohugo.io/) a very active and possibly one of the best support forums out there.
+So, thanks to everyone who has contributed to getting Hugo where it is today. It is hard to single out individuals, but a big shout-out to all the Hugo experts and moderators helping out making [discourse.gohugo.io](https://discourse.gohugo.io/) a very active and possibly one of the best support forums out there.

-And the last shout-out goes to two maintainers who have been there more or less from the start. [@digitalcraftsman](https://github.com/digitalcraftsman/) has been doing a fantastic job keeping the fast growing theme site and [repository](https://github.com/gohugoio/hugoThemes) in pristine condition. I have it on my watch list, but that is just out of curiosity. There are lots of activity, but it runs as clock work. [Anthony Fok](https://github.com/anthonyfok) has contributed with a variety of things but is most notable as the Linux expert on the team. He manages the Debian build and is the one to thank for up-to-date binaries on Debian and Ubuntu.
+And the last shout-out goes to two maintainers who have been there more or less from the start. [@digitalcraftsman](https://github.com/digitalcraftsman/) has been doing a fantastic job keeping the fast growing theme site and [repository](https://github.com/gohugoio/hugoThemes) in pristine condition. I have it on my watch list, but that is just out of curiosity. There is lots of activity, but it runs as clock work. [Anthony Fok](https://github.com/anthonyfok) has contributed with a variety of things but is most notable as the Linux expert on the team. He manages the Debian build and is the one to thank for up-to-date binaries on Debian and Ubuntu.

 One final note: If you have not done so already, please visit [github.com/gohugoio/hugo](https://github.com/gohugoio/hugo) and push the "star button".

 Gopher artwork by [Ashley McNamara](https://github.com/ashleymcnamara/gophers/) (licensed under [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/)). Inspired by [Renee French](https://reneefrench.blogspot.com/).

-[^2]: Numbers from Google Analytics. The Hugo websites are https://discourse.gohugo.io/, https://gohugo.io/ and https://themes.gohugo.io/. It is rumoured that when [Matt Biilman](https://twitter.com/biilmann?lang=en), CEO and Co-founder of Netlify, opened the first power bill after sponsoring Hugo's hosting, said: "Du må lave fis med mig, those Hugo sites have lots of web traffic!"
+[^2]: Numbers from Google Analytics. The Hugo websites are https://discourse.gohugo.io, https://gohugo.io and https://themes.gohugo.io. It is rumoured that when [Matt Biilman](https://twitter.com/biilmann?lang=en), CEO and Co-founder of Netlify, opened the first power bill after sponsoring Hugo's hosting, said: "Du må lave fis med mig, those Hugo sites have lots of web traffic!"
 [^sgen]: That was at the time of writing this article. _Next_, a React based static site generator, has momentum and is closing in on Hugo's 2nd place. 
-[^themes]: We pull all the themes from GitHub and build the theme site and 235 demo sites on Netlify in 4 minutes. And that is impressing.
+[^themes]: We pull all the themes from GitHub and build the theme site and 235 demo sites on Netlify in 4 minutes. That is impressive.
@@ -1,39 +0,0 @@
-`.URL`
-: string
-
-`.Name`
-: string
-
-`.Menu`
-: string
-
-`.Identifier`
-: string
-
-`.Pre`
-: template.HTML
-
-`.Post`
-: template.HTML
-
-`.Weight`
-: int
-
-`.Parent`
-: string
-
-`.Children`
-: Menu
-
-Note that menus also have the following functions available as well:
-
-[`.HasChildren`](/functions/haschildren/)
-: boolean
-
-Additionally, there are some relevant functions available to menus on a page:
-
-[`.IsMenuCurrent`](/functions/ismenucurrent/)
-: (menu string, menuEntry *MenuEntry ) boolean
-
-[`.HasMenuCurrent`](/functions/hasmenucurrent/)
-: (menu string, menuEntry *MenuEntry) boolean
@@ -21,7 +21,7 @@ When using Hugo with [GitHub Pages](http://pages.github.com/), you can provide y

 404 pages will have all the regular [page variables][pagevars] available to use in the templates.

-In addition to the standard page variables, the 404 page has access to all site content accessible from `.Data.Pages`.
+In addition to the standard page variables, the 404 page has access to all site content accessible from `.Pages`.

 ```
 ▾ layouts/
@@ -90,7 +90,7 @@ From the above base template, you can define a [default list template][hugolists
 {{< code file="layouts/_default/list.html" download="list.html" >}}
 {{ define "main" }}
  <h1>Posts</h1>
-  {{ range .Data.Pages }}
+  {{ range .Pages }}
    <article>
      <h2>{{ .Title }}</h2>
      {{ .Content }}
@@ -36,9 +36,9 @@ The homepage, similar to other [list pages in Hugo][lists], accepts content and

 See the homepage template below or [Content Organization][contentorg] for more information on the role of `_index.md` in adding content and front matter to list pages.

-## `.Data.Pages` on the Homepage
+## `.Pages` on the Homepage

-In addition to the standard [page variables][pagevars], the homepage template has access to *all* site content via `.Data.Pages`.
+In addition to the standard [page variables][pagevars], the homepage template has access to *all* site content via `.Pages`.

 ## Example Homepage Template

@@ -58,8 +58,8 @@ The following is an example of a homepage template that uses [partial][partials]
        {{.Content}}
      </div>
      <div>
-        <!-- Note that .Data.Pages is the equivalent of .Site.Pages on the homepage template. -->
-        {{ range first 10 .Data.Pages }}
+        <!-- Note that .Pages is the same as .Site.RegularPages on the homepage template. -->
+        {{ range first 10 .Pages }}
            {{ .Render "summary"}}
        {{ end }}
      </div>
@@ -504,7 +504,7 @@ Go allows you to do more than what's shown here. Using Hugo's [`where` function]
 {{< code file="layouts/partials/upcoming-events.html" download="upcoming-events.html" >}}
 <h4>Upcoming Events</h4>
 <ul class="upcoming-events">
-{{ range where .Data.Pages.ByDate "Section" "events" }}
+{{ range where .Pages.ByDate "Section" "events" }}
  {{ if ge .Date.Unix .Now.Unix }}
    <li>
    <!-- add span for event type -->
@@ -101,7 +101,7 @@ You can now access this `_index.md`'s' content in your list template:
    </article>
    <ul>
    <!-- Ranges through content/post/*.md -->
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
        <li>
            <a href="{{.Permalink}}">{{.Date.Format "2006-01-02"}} | {{.Title}}</a>
        </li>
@@ -172,7 +172,7 @@ This list template has been modified slightly from a template originally used in
   <h1>{{ .Title }}</h1>
        <ul>
        <!-- Renders the li.html content view for each content/post/*.md -->
-            {{ range .Data.Pages }}
+            {{ range .Pages }}
                {{ .Render "li"}}
            {{ end }}
        </ul>
@@ -189,7 +189,7 @@ This list template has been modified slightly from a template originally used in
  <div>
   <h1>{{ .Title }}</h1>
   <!-- ranges through each of the content files associated with a particular taxonomy term and renders the summary.html content view -->
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
        {{ .Render "summary"}}
    {{ end }}
  </div>
@@ -205,7 +205,7 @@ Hugo lists render the content based on metadata you provide in [front matter][].

 {{< code file="layouts/partials/default-order.html" >}}
 <ul>
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -220,7 +220,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs

 {{< code file="layouts/partials/by-weight.html" >}}
 <ul>
-    {{ range .Data.Pages.ByWeight }}
+    {{ range .Pages.ByWeight }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -234,7 +234,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs
 {{< code file="layouts/partials/by-date.html" >}}
 <ul>
    <!-- orders content according to the "date" field in front matter -->
-    {{ range .Data.Pages.ByDate }}
+    {{ range .Pages.ByDate }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -248,7 +248,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs
 {{< code file="layouts/partials/by-publish-date.html" >}}
 <ul>
    <!-- orders content according to the "publishdate" field in front matter -->
-    {{ range .Data.Pages.ByPublishDate }}
+    {{ range .Pages.ByPublishDate }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -261,7 +261,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs

 {{< code file="layouts/partials/by-expiry-date.html" >}}
 <ul>
-    {{ range .Data.Pages.ByExpiryDate }}
+    {{ range .Pages.ByExpiryDate }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -275,7 +275,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs
 {{< code file="layouts/partials/by-last-mod.html" >}}
 <ul>
    <!-- orders content according to the "lastmod" field in front matter -->
-    {{ range .Data.Pages.ByLastmod }}
+    {{ range .Pages.ByLastmod }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -289,7 +289,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs
 {{< code file="layouts/partials/by-length.html" >}}
 <ul>
    <!-- orders content according to content length in ascending order (i.e., the shortest content will be listed first) -->
-    {{ range .Data.Pages.ByLength }}
+    {{ range .Pages.ByLength }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -303,7 +303,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs
 {{< code file="layouts/partials/by-title.html" >}}
 <ul>
    <!-- ranges through content in ascending order according to the "title" field set in front matter -->
-    {{ range .Data.Pages.ByTitle }}
+    {{ range .Pages.ByTitle }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -317,7 +317,7 @@ Lower weight gets higher precedence. So content with lower weight will come firs
 {{< code file="layouts/partials/by-link-title.html" >}}
 <ul>
    <!-- ranges through content in ascending order according to the "linktitle" field in front matter. If a "linktitle" field is not set, the range will start with content that only has a "title" field and use that value for .LinkTitle -->
-    {{ range .Data.Pages.ByLinkTitle }}
+    {{ range .Pages.ByLinkTitle }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .LinkTitle }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -332,7 +332,7 @@ Order based on the specified front matter parameter. Content that does not have

 {{< code file="layouts/partials/by-rating.html" >}}
 <!-- Ranges through content according to the "rating" field set in front matter -->
-{{ range (.Data.Pages.ByParam "rating") }}
+{{ range (.Pages.ByParam "rating") }}
  <!-- ... -->
 {{ end }}
 {{< /code >}}
@@ -340,7 +340,7 @@ Order based on the specified front matter parameter. Content that does not have
 If the targeted front matter field is nested beneath another field, you can access the field using dot notation.

 {{< code file="layouts/partials/by-nested-param.html" >}}
-{{ range (.Data.Pages.ByParam "author.last_name") }}
+{{ range (.Pages.ByParam "author.last_name") }}
  <!-- ... -->
 {{ end }}
 {{< /code >}}
@@ -351,7 +351,7 @@ Reversing order can be applied to any of the above methods. The following uses `

 {{< code file="layouts/partials/by-date-reverse.html" >}}
 <ul>
-    {{ range .Data.Pages.ByDate.Reverse }}
+    {{ range .Pages.ByDate.Reverse }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -368,7 +368,7 @@ Hugo provides some functions for grouping pages by Section, Type, Date, etc.

 {{< code file="layouts/partials/by-page-field.html" >}}
 <!-- Groups content according to content section. The ".Key" in this instance will be the section's title. -->
-{{ range .Data.Pages.GroupBy "Section" }}
+{{ range .Pages.GroupBy "Section" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -385,7 +385,7 @@ In the above example, you may want `{{.Title}}` to point the `title` field you h

 {{< code file="layouts/partials/by-page-field.html" >}}
 <!-- Groups content according to content section.-->
-{{ range .Data.Pages.GroupBy "Section" }}
+{{ range .Pages.GroupBy "Section" }}
 <!-- Checks for existence of _index.md for a section; if available, pulls from "title" in front matter -->
 {{ with $.Site.GetPage "section" .Key }}
 <h3>{{.Title}}</h3>
@@ -408,7 +408,7 @@ In the above example, you may want `{{.Title}}` to point the `title` field you h

 {{< code file="layouts/partials/by-page-date.html" >}}
 <!-- Groups content by month according to the "date" field in front matter -->
-{{ range .Data.Pages.GroupByDate "2006-01" }}
+{{ range .Pages.GroupByDate "2006-01" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -425,7 +425,7 @@ In the above example, you may want `{{.Title}}` to point the `title` field you h

 {{< code file="layouts/partials/by-page-publish-date.html" >}}
 <!-- Groups content by month according to the "publishdate" field in front matter -->
-{{ range .Data.Pages.GroupByPublishDate "2006-01" }}
+{{ range .Pages.GroupByPublishDate "2006-01" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -442,7 +442,7 @@ In the above example, you may want `{{.Title}}` to point the `title` field you h

 {{< code file="layouts/partials/by-page-param.html" >}}
 <!-- Groups content according to the "param_key" field in front matter -->
-{{ range .Data.Pages.GroupByParam "param_key" }}
+{{ range .Pages.GroupByParam "param_key" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -461,7 +461,7 @@ The following template takes grouping by `date` a step further and uses Go's lay

 {{< code file="layouts/partials/by-page-param-as-date.html" >}}
 <!-- Groups content by month according to the "param_key" field in front matter -->
-{{ range .Data.Pages.GroupByParamDate "param_key" "2006-01" }}
+{{ range .Pages.GroupByParamDate "param_key" "2006-01" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -483,21 +483,21 @@ While these are logical defaults, they are not always the desired order. There a
 #### 1. Adding the Reverse Method

 ```
-{{ range (.Data.Pages.GroupBy "Section").Reverse }}
+{{ range (.Pages.GroupBy "Section").Reverse }}
 ```

 ```
-{{ range (.Data.Pages.GroupByDate "2006-01").Reverse }}
+{{ range (.Pages.GroupByDate "2006-01").Reverse }}
 ```

 #### 2. Providing the Alternate Direction

 ```
-{{ range .Data.Pages.GroupByDate "2006-01" "asc" }}
+{{ range .Pages.GroupByDate "2006-01" "asc" }}
 ```

 ```
-{{ range .Data.Pages.GroupBy "Section" "desc" }}
+{{ range .Pages.GroupBy "Section" "desc" }}
 ```

 ### Order Within Groups
@@ -511,7 +511,7 @@ Here is the ordering for the example that follows:
 3. Pages within each respective group are ordered alphabetically according to the `title`.

 {{< code file="layouts/partials/by-group-by-page.html" >}}
-{{ range .Data.Pages.GroupByDate "2006-01" "asc" }}
+{{ range .Pages.GroupByDate "2006-01" "asc" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages.ByTitle }}
@@ -536,8 +536,8 @@ Sometimes you only want to list a subset of the available content. A common is t
 2. `key` *or* `field name`
 3. `match value`

-{{< code file="layouts/_default/.html" >}}
-{{ range where .Data.Pages "Section" "post" }}
+{{< code file="layouts/_default/index.html" >}}
+{{ range where .Pages "Section" "post" }}
   {{ .Content }}
 {{ end }}
 {{< /code >}}
@@ -552,7 +552,7 @@ You can see more examples in the [functions documentation for `where`][wherefunc
 2. `number of elements`

 {{< code file="layout/_default/section.html" >}}
-{{ range first 10 .Data.Pages }}
+{{ range first 10 .Pages }}
  {{ .Render "summary" }}
 {{ end }}
 {{< /code >}}
@@ -563,7 +563,7 @@ Using `first` and `where` together can be very powerful:

 {{< code file="first-and-where-together.html" >}}
 <!-- Orders the content inside the "posts" section by the "title" field and then ranges through only the first 5 posts -->
-{{ range first 5 (where .Data.Pages "Section" "post").ByTitle }}
+{{ range first 5 (where .Pages "Section" "post").ByTitle }}
   {{ .Content }}
 {{ end }}
 {{< /code >}}
@@ -35,7 +35,7 @@ This list template is used for [spf13.com](http://spf13.com/). It makes use of [
  <div>
   <h1 id="title">{{ .Title }}</h1>
        <ul id="list">
-            {{ range .Data.Pages }}
+            {{ range .Pages }}
                {{ .Render "li"}}
            {{ end }}
        </ul>
@@ -51,7 +51,7 @@ This list template is used for [spf13.com](http://spf13.com/). It makes use of [
 <section id="main">
  <div>
   <h1 id="title">{{ .Title }}</h1>
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
        {{ .Render "summary"}}
    {{ end }}
  </div>
@@ -70,7 +70,7 @@ your list templates:

 {{< code file="layouts/partials/order-default.html" >}}
 <ul class="pages">
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
        <li>
            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>
            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>
@@ -82,7 +82,7 @@ your list templates:
 ### By Weight

 {{< code file="layouts/partials/by-weight.html" >}}
-{{ range .Data.Pages.ByWeight }}
+{{ range .Pages.ByWeight }}
    <li>
    <a href="{{ .Permalink }}">{{ .Title }}</a>
    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
@@ -93,7 +93,7 @@ your list templates:
 ### By Date

 {{< code file="layouts/partials/by-date.html" >}}
-{{ range .Data.Pages.ByDate }}
+{{ range .Pages.ByDate }}
    <li>
    <a href="{{ .Permalink }}">{{ .Title }}</a>
    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
@@ -104,7 +104,7 @@ your list templates:
 ### By Publish Date

 {{< code file="layouts/partials/by-publish-date.html" >}}
-{{ range .Data.Pages.ByPublishDate }}
+{{ range .Pages.ByPublishDate }}
    <li>
    <a href="{{ .Permalink }}">{{ .Title }}</a>
    <div class="meta">{{ .PublishDate.Format "Mon, Jan 2, 2006" }}</div>
@@ -115,7 +115,7 @@ your list templates:
 ### By Expiration Date

 {{< code file="layouts/partials/by-expiry-date.html" >}}
-{{ range .Data.Pages.ByExpiryDate }}
+{{ range .Pages.ByExpiryDate }}
    <li>
    <a href="{{ .Permalink }}">{{ .Title }}</a>
    <div class="meta">{{ .ExpiryDate.Format "Mon, Jan 2, 2006" }}</div>
@@ -126,7 +126,7 @@ your list templates:
 ### By Last Modified Date

 {{< code file="layouts/partials/by-last-mod.html" >}}
-{{ range .Data.Pages.ByLastmod }}
+{{ range .Pages.ByLastmod }}
    <li>
    <a href="{{ .Permalink }}">{{ .Title }}</a>
    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
@@ -137,7 +137,7 @@ your list templates:
 ### By Length

 {{< code file="layouts/partials/by-length.html" >}}
-{{ range .Data.Pages.ByLength }}
+{{ range .Pages.ByLength }}
    <li>
    <a href="{{ .Permalink }}">{{ .Title }}</a>
    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
@@ -149,7 +149,7 @@ your list templates:
 ### By Title

 {{< code file="layouts/partials/by-title.html" >}}
-{{ range .Data.Pages.ByTitle }}
+{{ range .Pages.ByTitle }}
    <li>
    <a href="{{ .Permalink }}">{{ .Title }}</a>
    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
@@ -160,7 +160,7 @@ your list templates:
 ### By Link Title

 {{< code file="layouts/partials/by-link-title.html" >}}
-{{ range .Data.Pages.ByLinkTitle }}
+{{ range .Pages.ByLinkTitle }}
    <li>
    <a href="{{ .Permalink }}">{{ .LinkTitle }}</a>
    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
@@ -175,7 +175,7 @@ Order based on the specified front matter parameter. Content that does not have
 The below example sorts a list of posts by their rating.

 {{< code file="layouts/partials/by-rating.html" >}}
-{{ range (.Data.Pages.ByParam "rating") }}
+{{ range (.Pages.ByParam "rating") }}
  <!-- ... -->
 {{ end }}
 {{< /code >}}
@@ -184,7 +184,7 @@ If the front matter field of interest is nested beneath another field, you can
 also get it:

 {{< code file="layouts/partials/by-nested-param.html" >}}
-{{ range (.Data.Pages.ByParam "author.last_name") }}
+{{ range (.Pages.ByParam "author.last_name") }}
  <!-- ... -->
 {{ end }}
 {{< /code >}}
@@ -194,7 +194,7 @@ also get it:
 Reversing order can be applied to any of the above methods. The following uses `ByDate` as an example:

 {{< code file="layouts/partials/by-date-reverse.html" >}}
-{{ range .Data.Pages.ByDate.Reverse }}
+{{ range .Pages.ByDate.Reverse }}
 <li>
 <a href="{{ .Permalink }}">{{ .Title }}</a>
 <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>
@@ -209,7 +209,7 @@ Hugo provides some functions for grouping pages by Section, Type, Date, etc.
 ### By Page Field

 {{< code file="layouts/partials/by-page-field.html" >}}
-{{ range .Data.Pages.GroupBy "Section" }}
+{{ range .Pages.GroupBy "Section" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -225,7 +225,7 @@ Hugo provides some functions for grouping pages by Section, Type, Date, etc.
 ### By Page date

 {{< code file="layouts/partials/by-page-date.html" >}}
-{{ range .Data.Pages.GroupByDate "2006-01" }}
+{{ range .Pages.GroupByDate "2006-01" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -241,7 +241,7 @@ Hugo provides some functions for grouping pages by Section, Type, Date, etc.
 ### By Page publish date

 {{< code file="layouts/partials/by-page-publish-date.html" >}}
-{{ range .Data.Pages.GroupByPublishDate "2006-01" }}
+{{ range .Pages.GroupByPublishDate "2006-01" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -257,7 +257,7 @@ Hugo provides some functions for grouping pages by Section, Type, Date, etc.
 ### By Page Param

 {{< code file="layouts/partials/by-page-param.html" >}}
-{{ range .Data.Pages.GroupByParam "param_key" }}
+{{ range .Pages.GroupByParam "param_key" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -273,7 +273,7 @@ Hugo provides some functions for grouping pages by Section, Type, Date, etc.
 ### By Page Param in Date Format

 {{< code file="layouts/partials/by-page-param-as-date.html" >}}
-{{ range .Data.Pages.GroupByParamDate "param_key" "2006-01" }}
+{{ range .Pages.GroupByParamDate "param_key" "2006-01" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages }}
@@ -295,22 +295,22 @@ While these are logical defaults, they are not always the desired order. There a
 #### Reverse Method

 ```
-{{ range (.Data.Pages.GroupBy "Section").Reverse }}
+{{ range (.Pages.GroupBy "Section").Reverse }}
 ```

 ```
-{{ range (.Data.Pages.GroupByDate "2006-01").Reverse }}
+{{ range (.Pages.GroupByDate "2006-01").Reverse }}
 ```


 #### Provide the Alternate Direction

 ```
-{{ range .Data.Pages.GroupByDate "2006-01" "asc" }}
+{{ range .Pages.GroupByDate "2006-01" "asc" }}
 ```

 ```
-{{ range .Data.Pages.GroupBy "Section" "desc" }}
+{{ range .Pages.GroupBy "Section" "desc" }}
 ```

 ### Order Within Groups
@@ -321,7 +321,7 @@ In the following example, groups are ordered chronologically and then content
 within each group is ordered alphabetically by title.

 {{< code file="layouts/partials/by-group-by-page.html" >}}
-{{ range .Data.Pages.GroupByDate "2006-01" "asc" }}
+{{ range .Pages.GroupByDate "2006-01" "asc" }}
 <h3>{{ .Key }}</h3>
 <ul>
    {{ range .Pages.ByTitle }}
@@ -346,8 +346,8 @@ Sometimes you only want to list a subset of the available content. A common requ
 2. `key` or `field name`
 3. `match value`

-{{< code file="layouts/_default/.html" >}}
-{{ range where .Data.Pages "Section" "post" }}
+{{< code file="layouts/_default/index.html" >}}
+{{ range where .Pages "Section" "post" }}
   {{ .Content }}
 {{ end }}
 {{< /code >}}
@@ -360,7 +360,7 @@ Sometimes you only want to list a subset of the available content. A common requ
 2. `number of elements`

 {{< code file="layout/_default/section.html" >}}
-{{ range first 10 .Data.Pages }}
+{{ range first 10 .Pages }}
  {{ .Render "summary" }}
 {{ end }}
 {{< /code >}}
@@ -370,7 +370,7 @@ Sometimes you only want to list a subset of the available content. A common requ
 Using `first` and `where` together can be very powerful:

 {{< code file="first-and-where-together.html" >}}
-{{ range first 5 (where .Data.Pages "Section" "post") }}
+{{ range first 5 (where .Pages "Section" "post") }}
   {{ .Content }}
 {{ end }}
 {{< /code >}}
@@ -43,19 +43,19 @@ Setting `Paginate` to a positive value will split the list pages for the homepag
 There are two ways to configure and use a `.Paginator`:

 1. The simplest way is just to call `.Paginator.Pages` from a template. It will contain the pages for *that page*.
-2. Select a subset of the pages with the available template functions and ordering options, and pass the slice to `.Paginate`, e.g. `{{ range (.Paginate ( first 50 .Data.Pages.ByTitle )).Pages }}`.
+2. Select a subset of the pages with the available template functions and ordering options, and pass the slice to `.Paginate`, e.g. `{{ range (.Paginate ( first 50 .Pages.ByTitle )).Pages }}`.

 For a given **Page**, it's one of the options above. The `.Paginator` is static and cannot change once created.

 The global page size setting (`Paginate`) can be overridden by providing a positive integer as the last argument. The examples below will give five items per page:

 * `{{ range (.Paginator 5).Pages }}`
-* `{{ $paginator := .Paginate (where .Data.Pages "Type" "post") 5 }}`
+* `{{ $paginator := .Paginate (where .Pages "Type" "post") 5 }}`

 It is also possible to use the `GroupBy` functions in combination with pagination:

 ```
-{{ range (.Paginate (.Data.Pages.GroupByDate "2006")).PageGroups  }}
+{{ range (.Paginate (.Pages.GroupByDate "2006")).PageGroups  }}
 ```

 ## Build the navigation
@@ -75,7 +75,7 @@ If you use any filters or ordering functions to create your `.Paginator` *and* y
 The following example shows how to create `.Paginator` before its used:

 ```
-{{ $paginator := .Paginate (where .Data.Pages "Type" "post") }}
+{{ $paginator := .Paginate (where .Pages "Type" "post") }}
 {{ template "_internal/pagination.html" . }}
 {{ range $paginator.Pages }}
   {{ .Title }}
@@ -42,7 +42,7 @@ The following is an example `robots.txt` layout:
 {{< code file="layouts/robots.txt" download="robots.txt" >}}
 User-agent: *

-{{range .Data.Pages}}
+{{range .Pages}}
 Disallow: {{.RelPermalink}}
 {{end}}
 {{< /code >}}
@@ -73,7 +73,7 @@ This is the default RSS template that ships with Hugo. It adheres to the [RSS 2.
    {{ with .OutputFormats.Get "RSS" }}
        {{ printf "<atom:link href=%q rel=\"self\" type=%q />" .Permalink .MediaType | safeHTML }}
    {{ end }}
-    {{ range .Data.Pages }}
+    {{ range .Pages }}
    <item>
      <title>{{ .Title }}</title>
      <link>{{ .Permalink }}</link>
@@ -41,7 +41,7 @@ This template respects the version 0.9 of the [Sitemap Protocol](http://www.site

 ```
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
-  {{ range .Data.Pages }}
+  {{ range .Pages }}
  <url>
    <loc>{{ .Permalink }}</loc>{{ if not .Lastmod.IsZero }}
    <lastmod>{{ safeHTML ( .Lastmod.Format "2006-01-02T15:04:05-07:00" ) }}</lastmod>{{ end }}{{ with .Sitemap.ChangeFreq }}
@@ -72,4 +72,4 @@ Defaults for `<changefreq>`, `<priority>` and `filename` values can be set in th

 The same fields can be specified in an individual content file's front matter in order to override the value assigned to that piece of content at render time.

-[pagevars]: /variables/page/
+[pagevars]: /variables/page/
@@ -103,11 +103,11 @@ type WeightedPages []WeightedPage

 ## Displaying custom metadata in Taxonomy Terms Templates

-If you need to display custom metadata for each taxonomy term, you will need to create a page for that term at `/content/<TAXONOMY>/<TERM>/_index.md` and add your metadata in it's front matter, [as explained in the taxonomies documentation](/content-management/taxonomies/#add-custom-meta-data-to-a-taxonomy-term). Based on the Actors taxonomy example shown there, within your taxonomy terms template, you may access your custom fields by iterating through the variable `.Data.Pages` as such:
+If you need to display custom metadata for each taxonomy term, you will need to create a page for that term at `/content/<TAXONOMY>/<TERM>/_index.md` and add your metadata in it's front matter, [as explained in the taxonomies documentation](/content-management/taxonomies/#add-custom-meta-data-to-a-taxonomy-term). Based on the Actors taxonomy example shown there, within your taxonomy terms template, you may access your custom fields by iterating through the variable `.Pages` as such:

 ```
 <ul>
-  {{ range .Data.Pages }}
+  {{ range .Pages }}
     <li>
       <a href="{{ .Permalink }}">{{ .Title }}</a>
       {{ .Params.wikipedia }}
@@ -51,14 +51,14 @@ This will print out a list of all the variables scoped to the current context
 When developing a [homepage][], what does one of the pages you're looping through look like?

 ```
-{{ range .Data.Pages }}
+{{ range .Pages }}
    {{/* The context, ".", is now each one of the pages as it goes through the loop */}}
    {{ printf "%#v" . }}
 {{ end }}
 ```

-{{% note "`.Data.Pages` on the Homepage" %}}
-`.Data.Pages` on the homepage is equivalent to `.Site.Pages`.
+{{% note "`.Pages` on the Homepage" %}}
+`.Pages` on the homepage is equivalent to `.Site.RegularPages`.
 {{% /note %}}

 ## Why Am I Showing No Defined Variables?
@@ -78,4 +78,4 @@ This example will render the header partial, but the header partial will not hav
 The dot (`.`) is considered fundamental to understanding Hugo templating. For more information, see [Introduction to Hugo Templating][tempintro].

 [homepage]: /templates/homepage/
-[tempintro]: /templates/introduction/
+[tempintro]: /templates/introduction/
@@ -73,7 +73,7 @@ In this example, `.Render` is passed into the template to call the [render funct
 <main id="main">
  <div>
  <h1 id="title">{{ .Title }}</h1>
-  {{ range .Data.Pages }}
+  {{ range .Pages }}
    {{ .Render "summary"}}
  {{ end }}
  </div>
@@ -30,11 +30,11 @@ The following starter kits are developed by active members of the Hugo community
 * [Atlas][]. Atlas is a Hugo boilerplate designed to speed up development with support for Netlify, Netlify CMS, Gulp, Linting, SCSS, ES6 & more. It's actively maintained and contributions are always welcome.


-[addkit]: https://github.com/gohugoio/hugo/edit/master/docs/content/tools/starter-kits.md
+[addkit]: https://github.com/gohugoio/hugo/edit/master/docs/content/en/tools/starter-kits.md
 [amp]: https://www.ampproject.org/
 [Blaupause]: https://github.com/fspoettel/blaupause
 [GOHUGO AMP]: https://github.com/wildhaber/gohugo-amp
 [gohugodocs]: https://gohugo-amp.gohugohq.com/
 [hugulp]: https://github.com/jbrodriguez/hugulp
 [Victor Hugo]: https://github.com/netlify/victor-hugo
-[Atlas]: https://github.com/indigotree/atlas
+[Atlas]: https://github.com/indigotree/atlas
@@ -1,7 +1,7 @@
 ---
-title: Menu Variables
-linktitle: Menu Variables
-description: A menu entry in a menu template has specific variables and functions to make menu management easier.
+title: Menu Entry Properties
+linktitle: Menu Entry Properties
+description: A menu entry in a menu-template has specific variables and functions to make menu management easier.
 date: 2017-03-12
 publishdate: 2017-03-12
 lastmod: 2017-03-12
@@ -19,49 +19,106 @@ aliases: [/variables/menu/]
 toc: false
 ---

-The [menu template][] has the following properties:
-
-.URL
-: string
-
-.Name
-: string
-
-.Title
-: string
-
-This is a link title, meant to be used in `title`-Attributes of the menu's `<a>`-tags.
-By default it returns `.Page.LinkTitle`, as long as the menu entry was created
-through the page's front matter and not through the site config.
-Setting it explicitly in the site config or the page's front matter overrides this behaviour.
-
-.Page
-: [Page Object](/variables/page/)
-
-The `.Page` variable holds a reference to the page.
-It's only set when the menu entry is created from the page's front matter,
-not when it's created from the site config.
+A **menu entry** has the following properties available that can be used in a
+[menu template][menu-template].

+## Menu Entry Variables

 .Menu
-: string
+: _string_ <br />
+Name of the **menu** that contains this **menu entry**.
+
+.URL
+: _string_ <br />
+URL that the menu entry points to. The `url` key, if set for the menu entry,
+sets this value. If that key is not set, and if the menu entry is set in a page
+front-matter, this value defaults to the page's `.RelPermalink`.
+
+.Page
+: _\*Page_ <br />
+Reference to the [page object][page-object] associated with the menu entry. This
+will be non-nil if the menu entry is set via a page's front-matter and not via
+the site config.
+
+.Name
+: _string_ <br />
+Name of the menu entry. The `name` key, if set for the menu entry, sets
+this value. If that key is not set, and if the menu entry is set in a page
+front-matter, this value defaults to the page's `.LinkTitle`.

 .Identifier
-: string
+: _string_ <br />
+Value of the `identifier` key if set for the menu entry. This value must be
+unique for each menu entry. **It is necessary to set a unique identifier
+manually if two or more menu entries have the same `.Name`.**

 .Pre
-: template.HTML
+: _template.HTML_ <br />
+Value of the `pre` key if set for the menu entry. This value typically contains
+a string representing HTML.

 .Post
-: template.HTML
+: _template.HTML_ <br />
+Value of the `post` key if set for the menu entry. This value typically contains
+a string representing HTML.

 .Weight
-: int
+: _int_ <br />
+Value of the `weight` key if set for the menu entry. If that key is not set,
+and if the menu entry is set in a page front-matter, this value defaults to the
+page's `.Weight`.

 .Parent
-: string
+: _string_ <br />
+Name (or Identifier if present) of this menu entry's parent **menu entry**. The
+`parent` key, if set for the menu entry, sets this value. If this key is set,
+this menu entry nests under that parent entry, else it nests directly under the
+`.Menu`.

 .Children
-: Menu
+: _Menu_ <br />
+This value is auto-populated by Hugo. It is a collection of children menu
+entries, if any, under the current menu entry.

-[menu template]: /templates/menu-templates/
+## Menu Entry Functions
+
+Menus also have the following functions available:
+
+[.HasChildren](/functions/haschildren/)
+: _boolean_ <br />
+Returns `true` if `.Children` is non-nil.
+
+.KeyName
+: _string_ <br />
+Returns the `.Identifier` if present, else returns the `.Name`.
+
+.IsEqual
+: _boolean_ <br />
+Returns `true` if the two compared menu entries represent the same menu entry.
+
+.IsSameResource
+: _boolean_ <br />
+Returns `true` if the two compared menu entries have the same `.URL`.
+
+.Title
+: _string_ <br />
+Link title, meant to be used in the `title` attribute of a menu entry's
+`<a>`-tags.  Returns the menu entry's `title` key if set. Else, if the menu
+entry was created through a page's front-matter, it returns the page's
+`.LinkTitle`. Else, it just returns an empty string.
+
+## Other Menu-related Functions
+
+Additionally, here are some relevant methods available to menus on a page:
+
+.IsMenuCurrent
+: _(menu string, menuEntry *MenuEntry ) boolean_ <br />
+See [`.IsMenuCurrent` method](/functions/ismenucurrent/).
+
+.HasMenuCurrent
+: _(menu string, menuEntry *MenuEntry) boolean_ <br />
+See [`.HasMenuCurrent` method](/functions/hasmenucurrent/).
+
+
+[menu-template]: /templates/menu-templates/
+[page-object]: /variables/page/
@@ -106,7 +106,9 @@ See also `.ExpiryDate`, `.Date`, `.PublishDate`, and [`.GitInfo`][gitinfo].
 : contains all formats, including the current format, for a given page. Can be combined the with [`.Get` function](/functions/get/) to grab a specific format. (See [Output Formats](/templates/output-formats/).)

 .Pages
-: a collection of associated pages. This value will be `nil` for regular content pages. `.Pages` is an alias for `.Data.Pages`.
+: a collection of associated pages. `.Pages` is an alias for
+  `.Data.Pages`. This value will be `nil` within the context of
+  regular content pages.

 .Permalink
 : the Permanent link for this page; see [Permalinks](/content-management/urls/)
@@ -90,7 +90,7 @@ From the above base template, you can define a [default list template][hugolists
 {{< code file="layouts/_default/list.html" download="list.html" >}}
 {{ define "main" }}
  <h1>Posts</h1>
-  {{ range .Data.Pages }}
+  {{ range .Pages }}
    <article>
      <h2>{{ .Title }}</h2>
      {{ .Content }}
@@ -3,7 +3,7 @@ publish = "public"
 command = "hugo"

 [context.production.environment]
-HUGO_VERSION = "0.42.2"
+HUGO_VERSION = "0.44"
 HUGO_ENV = "production"
 HUGO_ENABLEGITINFO = "true"

@@ -11,20 +11,20 @@ HUGO_ENABLEGITINFO = "true"
 command = "hugo --enableGitInfo"

 [context.split1.environment]
-HUGO_VERSION = "0.42.2"
+HUGO_VERSION = "0.44"
 HUGO_ENV = "production"

 [context.deploy-preview]
 command = "hugo --buildFuture -b $DEPLOY_PRIME_URL"

 [context.deploy-preview.environment]
-HUGO_VERSION = "0.42.2"
+HUGO_VERSION = "0.44"

 [context.branch-deploy]
 command = "hugo -b $DEPLOY_PRIME_URL"

 [context.branch-deploy.environment]
-HUGO_VERSION = "0.42.2"
+HUGO_VERSION = "0.44"

 [context.next.environment]
 HUGO_ENABLEGITINFO = "true"
@@ -1 +1,7 @@
-Theme for gohugo.io sites. More info to come.
+# GoHugo Sites Theme
+
+Theme for gohugo.io sites:
+* [https://gohugo.io/](https://gohugo.io/)
+* [https://themes.gohugo.io/](https://themes.gohugo.io/)
+
+More info to come.
@@ -1,4 +1,4 @@
 {{ define "main" }}
-  {{ $section_to_display :=  .Data.Pages }}
+  {{ $section_to_display := .Pages }}
  {{ partial "pagelayout.html" (dict "context" . "section_to_display" $section_to_display ) }}
 {{ end }}
@@ -1,6 +1,6 @@
 {{/* {{ define "header" }}{{ partial "page-header" . }}{{ end }} */}}
 {{ define "main" }}
-{{ $section_to_display :=  .Data.Pages }}
+{{ $section_to_display := .Pages }}
 <div class="w-100 ph4 pb5 pb6-ns pt1 pt3-ns">

  <div class="flex">
@@ -3,7 +3,7 @@
    <!-- <a href="/news/" class="link accent-color tr-ns f6 w-100 w-50-m w-10-l bg-animate hover-bg-accent-color hover-white pv3 pv4-l ph3 ph4-l dib">
      Latest News:
    </a> -->
-    {{ range first 4 ( sort (where .Data.Pages "Section" "news") "Date" "desc" ) }}
+    {{ range first 4 ( sort (where .Pages "Section" "news") "Date" "desc" ) }}
      <!-- only show 2 boxes on mobile -->
      {{ $.Scratch.Add "i" 1 }}{{ $i := $.Scratch.Get "i" }}
      <a href="{{ .URL }}" class="link lh-copy light-gray f6 w-100 w-50-m w-25-l bg-animate hover-bg-accent-color hover-white pv3 pv4-ns ph3 ph4-ns{{ if ge $i 3 }} dn dib-l{{ else }} dib{{ end }}">
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
hugoreleaser	48d7a641d0	releaser: Add release notes to /docs for release of 0.45 [ci skip]	2018-07-22 12:09:26 +00:00
hugoreleaser	2c5a036def	releaser: Bump versions for release of 0.45 [ci skip]	2018-07-22 12:09:26 +00:00
Bjørn Erik Pedersen	592c5b3072	Update release notes 0.45	2018-07-22 14:04:01 +02:00
hugoreleaser	a0c4a3660e	releaser: Add release notes draft for 0.45 Rename to *-ready.md to continue. [ci skip]	2018-07-22 10:07:03 +00:00
Bjørn Erik Pedersen	062510cf1f	Get rid of the utils package	2018-07-22 00:35:09 +02:00
Bjørn Erik Pedersen	4e1d0cd9f1	Update hugo_windows.go	2018-07-22 00:09:46 +02:00
Bjørn Erik Pedersen	a451c49fde	hugolib: Print a WARNING about relative non-relative ref/relref matches Fixes #4973	2018-07-21 11:42:07 +02:00
Bjørn Erik Pedersen	ff16c42ed0	hugolib: Allow untyped nil to be merged in lang.Merge Fixes #4977	2018-07-21 11:41:23 +02:00
Bjørn Erik Pedersen	166483fe12	resource/scss: Add IncludePaths config option Takes paths relative to the current working dir. Fixes #4921	2018-07-20 17:50:44 +02:00
Bjørn Erik Pedersen	f01505c910	resource/scss: Fix source maps on Windows I have tested this OK on * Windows 10 (it did not work before this commit) * MacOS Fixes #4968	2018-07-20 08:00:26 +02:00
Vas Sudanagunta	8278384b96	Increase refLinker test coverage	2018-07-20 07:02:41 +02:00
Bjørn Erik Pedersen	65e610e161	hugolib: Avoid nilpointer in absoluteSourceRef	2018-07-19 22:39:24 +02:00
Vas Sudanagunta	b56d9a1294	Fix typo-logic bug in GetPage	2018-07-19 21:36:10 +02:00
Vas Sudanagunta	d6fde8fa13	Enable test case fixed by commit `501543d4`	2018-07-19 20:40:50 +02:00
Vas Sudanagunta	2bac371544	Add test coverage for recent ref overhaul Closes #4969	2018-07-19 18:32:23 +02:00
Bjørn Erik Pedersen	9b4b97a722	hugolib: Create an adapter from old to new getPage To make sure we confirm that the existing tests run the correct code path. Updates #4969	2018-07-19 18:26:10 +02:00
Bjørn Erik Pedersen	501543d4b6	hugolib: Only do page-relative getPage for relative paths Updates #4969	2018-07-19 17:47:05 +02:00
Bjørn Erik Pedersen	6ffa882349	hugolib: Improve error handling in refLink	2018-07-19 17:17:35 +02:00
Bjørn Erik Pedersen	1eb8b36b38	docs: Update ref, relref, GetPage docs	2018-07-19 17:02:03 +02:00
Bjørn Erik Pedersen	00c74ee7ff	docs: Document refLinksErrorLevel and refLinksNotFoundURL See #4964	2018-07-19 15:04:00 +02:00
Bjørn Erik Pedersen	e25aa655f4	Add configurable ref/relref error handling and notFoundURL Two new settings: * refLinksErrorLevel: ERROR (default) or WARNING. ERROR will fail the build. * refLinksNotFoundURL: Used as a placeholder when page references cannot be found. Fixes #4964	2018-07-19 14:32:43 +02:00
Bjørn Erik Pedersen	12679b4083	hugolib: Mark shortcode changes as content changes in server mode This is unfortunate, but is needed to re-create the taxonomies collections etc. that may be referenced from them. Fixes #4965	2018-07-19 13:58:18 +02:00
Bjørn Erik Pedersen	c39ac5738d	Revert "hugolib: Fix potential server panic with drafts/future enabled" This had a side-effect. I have understand this better to apply the correct fix. Will come soon. This reverts commit `1ab4658c0d`.	2018-07-19 12:20:01 +02:00
Bjørn Erik Pedersen	9da617912b	Merge commit 'a3535c8486b2ce762b1a8a9c30b03985c3e02cee'	2018-07-19 09:18:11 +02:00
Bjørn Erik Pedersen	a3535c8486	Squashed 'docs/' changes from cfe89ecbc..a4fa0d1d6 `a4fa0d1d6` Typos and grammatical changes `513884600` Add hugo pipes documentation git-subtree-dir: docs git-subtree-split: `a4fa0d1d64`	2018-07-19 09:18:11 +02:00
Bjørn Erik Pedersen	1ab4658c0d	hugolib: Fix potential server panic with drafts/future enabled Fixes #4965	2018-07-18 17:01:50 +02:00
Bjørn Erik Pedersen	75acff5f20	hugolib: Avoid server panic on TOML mistake in i18n Fixes #4942	2018-07-18 11:53:04 +02:00
Bjørn Erik Pedersen	5c9d5413a4	hugolib/filesystems: Fix theme config for Work Fs Which was the reason why `PostCSS´ from theme(s) was not picked up. Fixes #4951	2018-07-18 11:39:04 +02:00
Bjørn Erik Pedersen	59ebc83d72	Merge commit 'b6b37a1f00f808f3c0d2715f65ca2d3091f36495'	2018-07-18 11:05:58 +02:00
Bjørn Erik Pedersen	b6b37a1f00	Squashed 'docs/' changes from f59b3ab06..cfe89ecbc `cfe89ecbc` Set all *.png files under static/images to mode 0644 `d847ccd8b` More spelling error fixes `bf1405d92` Correction: .Pages on homepage is same as .Site.RegularPages `7efa41ff5` Merge commit 'd137efe0222269e09b427325176f0044558e3cc5' `d137efe02` Squashed 'themes/gohugoioTheme/' changes from f31a3dc8..66249819 `50df8bfb8` Replace .Data.Pages with .Pages `85d3712d0` Mention the newScratch template func `1c234db1b` Release 0.44 `a51cb3e36` Merge branch 'temp44' `ec424a5e2` releaser: Prepare repository for 0.45-DEV `425e85574` releaser: Add release notes to /docs for release of 0.44 `e6f9c65a2` releaser: Bump versions for release of 0.44 `45548a5c9` Arch Linux: Partial upgrades are unsupported `c0430f8f9` Update MenuEntry properties documentation `79109b685` Refresh the documentation on staticDir config parameter `80ed4592b` Remove duplicate links; also sort them alphabetically `f00a4e232` HTTPS links to third-party sites `2f6f682ba` Fixed a typo `4be105202` add openbsd howto install `39808f50a` Fix typo `b55c0f3a0` Fix URL to hugotest `2fb157237` Release Hugo 0.43 `e8af6a970` Merge branch 'temp43' `563dd4173` Adjust release notes `50aed2e52` releaser: Prepare repository for 0.44-DEV `363b363ff` releaser: Add release notes to /docs for release of 0.43 `93bfbef62` releaser: Bump versions for release of 0.43 `893a27d33` Fix typos `fe5908257` Celebrate: a few typo and grammar fixes `bb20442df` Merge commit '98293eaa1570b5aff4452021c8b6d6c8560b3f06' `ef3d63936` Add a newScratch template func `bf100a3cd` Merge branch 'release-0.42.2' `f1133c544` releaser: Prepare repository for 0.43-DEV `2ce058057` releaser: Add release notes to /docs for release of 0.42.2 `6073927c6` releaser: Bump versions for release of 0.42.2 `3bafddd52` releaser: Prepare repository for 0.43-DEV `8b9f805bd` releaser: Add release notes to /docs for release of 0.42.1 `efb6638ba` releaser: Bump versions for release of 0.42.1 `1e74ffbe0` releaser: Prepare repository for 0.43-DEV `2d2d0f8ab` releaser: Add release notes to /docs for release of 0.42 `17f685813` releaser: Bump versions for release of 0.42 `67ef1a0e1` docs: Update theme documentation `d74874e1e` docs: Remove some files now moved `771d50cf3` Merge commit 'b239595af5a9fc1fc9a1ccc666c3ab06ccc32f04' `f9b5fd2d2` tplimpl: Remove speakerdeck shortcode `523206579` tpl/strings: strings.RuneCount `b389efc88` tpl: Add strings.Repeat `a41ad0254` Add a BlackFriday option for rel="noreferrer" on external links `a6e279362` Add a BlackFriday option for rel="nofollow" on external links `7e2c9846e` releaser: Prepare repository for 0.42-DEV `b4f81c38a` releaser: Add release notes to /docs for release of 0.41 `55667b3a1` releaser: Bump versions for release of 0.41 `afceb02d3` docs: Document the GDPR Privacy Config `8b8289027` Merge commit 'd2b1030060d3c91d5f9ffa3456418da16bd74f1d' `be04a8886` Merge branch 'release-0.40.3' `33ca0b8da` releaser: Prepare repository for 0.41-DEV `8c9a5a850` releaser: Add release notes to /docs for release of 0.40.3 `85845a4fd` releaser: Bump versions for release of 0.40.3 `9af79e531` Merge commit '83bef6955e014d40c0f00db9cebe09113154e999' `c4200dd0e` Fix typo `8f8323336` releaser: Prepare repository for 0.41-DEV `9fab87505` releaser: Add release notes to /docs for release of 0.40.2 `83648c666` releaser: Bump versions for release of 0.40.2 `e6434d104` releaser: Prepare repository for 0.41-DEV `9389b2973` releaser: Add release notes to /docs for release of 0.40.1 `32979e28a` releaser: Bump versions for release of 0.40.1 `196174a76` releaser: Prepare repository for 0.41-DEV `490a997bb` releaser: Add release notes to /docs for release of 0.40 `018aa6471` releaser: Bump versions for release of 0.40 `92221934c` Merge commit 'a215abf70e018f4bf40d6c09d8bd148d8684b33d' `0a58ef56e` Merge commit 'd2ec1a06df8ab6b17ad05cb008d5701b40327d47' `312ab58c6` Improve .Get docs `e43e8cee3` .Get function: fix syntax signature `bb16150bc` releaser: Prepare repository for 0.40-DEV `8cc80fed9` releaser: Add release notes to /docs for release of 0.39 `f7aa0d1c5` releaser: Bump versions for release of 0.39 `42e48706a` Merge commit '047c4188dfc854f658d16f1e4a9501f9c97a31c7' `76acab68b` releaser: Prepare repository for 0.39-DEV `d270600b0` releaser: Add release notes to /docs for release of 0.38.2 `97be36992` releaser: Bump versions for release of 0.38.2 `cd29b8b79` releaser: Prepare repository for 0.39-DEV `9983a4bdf` releaser: Add release notes to /docs for release of 0.38.1 `7774afd01` releaser: Bump versions for release of 0.38.1 `b89157f20` releaser: Prepare repository for 0.39-DEV `af4d0bf62` releaser: Add release notes to /docs for release of 0.38 `ca98e7d4f` releaser: Bump versions for release of 0.38 `8b773833a` Merge commit 'ed8bf081fdbf336e026517b7e1b123c039014ab5' `24202bb71` docs: Generate docshelper data `43d15975d` Add .Site.IsServer `6f99d3d65` Merge commit '0a23baa6a90901f772c234107c4f12c16c76f4aa' `17487ccdd` hugolib: Add Reset method to delete key from Scratch `ccbf7a05c` docs: Add docs for lang.Merge `5ad46d78e` Merge commit '3886fc1fef6ac19d58b9ba1bb642d0c6c9a54031' `ac403c280` docs: Add docs on the new front matter configuration `6066c60e6` Merge commit 'c0290655825e7bb36e13fb39f89d85b392cf1adc' `ee605c7ae` releaser: Prepare repository for 0.38-DEV `31a4de966` releaser: Add release notes to /docs for release of 0.37.1 `9dd3dafe1` releaser: Bump versions for release of 0.37.1 `141750aec` releaser: Prepare repository for 0.38-DEV `c9bb39bc3` releaser: Add release notes to /docs for release of 0.37 `c7009f064` releaser: Bump versions for release of 0.37 `9f727d916` Merge commit '900b5f6cfe5a377ef369d26cd700201be4cf6b06' `87fd97853` Merge commit '374d184e6747678364fd61f5faf328ec9205eb6b' `244deafc2` Fix typos in development contribution doc `608c80f72` Merge branch 'release-0.36.1' `0f8ffbd5c` releaser: Prepare repository for 0.37-DEV `5028ee849` releaser: Add release notes to /docs for release of 0.36.1 `9ccc7cb11` releaser: Bump versions for release of 0.36.1 `3db31be07` Merge commit '9cc9bab46288d8d5f9fda7009c5f746258cec1b4' `9468246c5` Add "target" and "rel" parameters to figure shortcode `6d7fa89f9` releaser: Prepare repository for 0.37-DEV `1aec7ad81` releaser: Add release notes to /docs for release of 0.36 `b522da389` releaser: Bump versions for release of 0.36 `bb78bea13` docs: Add documentation for smart cropping etc. `930f16cae` Merge commit 'c305e44f5f081e4436195923a4593e396f07cd49' `0e4c80ab9` releaser: Prepare repository for 0.36-DEV `e0d4c6bcd` releaser: Add release notes to /docs for release of 0.35 `f4ac67eb3` releaser: Bump versions for release of 0.35 `229a50b1f` docs: Regenerate CLI docs `72958eb9c` Merge commit '337d0c5f516ee085205e8abefdb7f87e6d33ca05' `d998ca4c0` command: Remove undraft command `34a0052ef` docs: Re-generate CLI docs `fa04ff331` releaser: Prepare repository for 0.35-DEV `55e595720` releaser: Add release notes to /docs for release of 0.34 `bf4d0e8fb` releaser: Bump versions for release of 0.34 `07673370e` releaser: Prepare repository for 0.34-DEV `921ea8920` releaser: Add release notes to /docs for release of 0.33 `3307f61bd` releaser: Bump versions for release of 0.33 `792a4410d` Merge commit '3cf4300097610bb8b5bd0686d96d1df5db641895' `6d8a9f657` releaser: Prepare repository for 0.33-DEV `e3afccf6f` releaser: Add release notes to /docs for release of 0.32.4 `7f29cb196` releaser: Bump versions for release of 0.32.4 `baa364436` releaser: Prepare repository for 0.33-DEV `60c775166` releaser: Add release notes to /docs for release of 0.32.3 `9cbab1803` releaser: Bump versions for release of 0.32.3 `51823efee` releaser: Prepare repository for 0.33-DEV `71e03684c` releaser: Add release notes to /docs for release of 0.32.2 `e18bf56fb` releaser: Bump versions for release of 0.32.2 `54aa93927` Merge commit 'eb738cd35cca1ffc68c5ed688dbe2a19108e8761' `5e8123994` releaser: Prepare repository for 0.33-DEV `a55b78124` releaser: Add release notes to /docs for release of 0.32.1 `7de53ff41` releaser: Bump versions for release of 0.32.1 `e6e58785d` releaser: Prepare repository for 0.33-DEV `58cf5009d` releaser: Add release notes to /docs for release of 0.32 `031719821` Merge commit 'f3cd083961f36dc96d05e98aaf67f650102bc757' `b9183604b` Add Pandoc support, refactor external helpers `3f9b9474c` releaser: Prepare repository for 0.32-DEV `11e4ce514` releaser: Add release notes to /docs for release of 0.31.1 `aebb1504b` releaser: Bump versions for release of 0.31.1 `d70b54d4a` releaser: Prepare repository for 0.32-DEV `cdc10468e` releaser: Add release notes to /docs for release of 0.31 `38bd41cab` releaser: Bump versions for release of 0.31 `1c581a11d` Merge commit '30c0d485eaff6d70df1be0353911ddca485d52bf' `b88e46d02` Merge commit '05e42bc643f1840ed2ad9c2eff82a269d1381683' `a45ab174e` Handle Taxonomy permalinks `9f27354f6` Add support for height argument to figure shortcode `acc8e49c1` releaser: Prepare repository for 0.31-DEV `977266b19` releaser: Add release notes to /docs for release of 0.30.2 `31b672844` releaser: Bump versions for release of 0.30.2 `b8f6b72a8` Merge commit '325009c3fd4ac90021897b7e3e025c14e70ce162' `c6e3dae71` releaser: Prepare repository for 0.31-DEV `2a3c7c7d9` releaser: Add release notes to /docs for release of 0.30.1 `4c014117a` releaser: Bump versions for release of 0.30.1 `1da61da06` releaser: Prepare repository for 0.31-DEV `24864a46b` releaser: Add release notes to /docs for release of 0.30 `3011aa44a` releaser: Bump versions for release of 0.30 `bcbf3237b` Merge commit 'ecf5e081b5540e69f4af330233f39a07baf53846' `ab68b99ed` Merge commit 'dae5a7c61cceeb0de59f2d755f63e453f71dd9b2' `0ae435725` tpl: Add errorf template function `ac3fb3808` Change SummaryLength to be configurable (#3924) `3c0e4fa70` tpl: Add os.fileExists template function `9290f3983` Merge commit '9d68f695e782c6a83c77aff13317c7a22c694c98' `394e8b3f6` tpl: Add float template function `c0c48c2ea` releaser: Prepare repository for 0.30-DEV `0806d910b` releaser: Add release notes to /docs for release of 0.29 `0d1101836` releaser: Bump versions for release of 0.29 `5d92b552b` releaser: Prepare repository for 0.29-DEV `1ef521182` releaser: Add release notes to /docs for release of 0.28 `c5441cff1` releaser: Bump versions for release of 0.28 `46c2786f1` Merge commit '61c27b58b353c73772aae572c7d822fdfdf7791b' `6fed4008f` Merge commit '30694a133a88d5f76a51d0372646e10cbeca7691' `595752e2f` Merge commit '7a89dce53bfbd67a17442a8f9be8fa895fc4f9b1' `af14cae0c` Merge commit 'ba45da9d03056447e4873de13d4e0f8d658a769b' `d0bb30963` releaser: Prepare repository for 0.28-DEV `469bf26aa` releaser: Add release notes to /docs for release of 0.27.1 `06ea00c12` releaser: Bump versions for release of 0.27.1 `0668af58e` releaser: Prepare repository for 0.28-DEV `4ce00c84d` releaser: Add release notes to /docs for release of 0.27 `68f318d0b` releaser: Bump versions for release of 0.27 `509ad6cc0` docs: Merge commit '1b4319be62ba071f79e90ef32dbe92eb893429f7' `c625ae1ce` docs: Document Related Content `ecd5c24f5` docs: Merge commit '7d63a23b0c68d9cd7c7c09c2755619237bc03485' `b97b84f9d` Update docs versiona and README `2238f7a4a` Merge commit 'ec4e6f9df2ab9ffdc62a3f59675369096e0d3f77' as 'docs' git-subtree-dir: docs git-subtree-split: `cfe89ecbc2`	2018-07-18 11:04:57 +02:00
Bjørn Erik Pedersen	ebe4d39f17	resource/postcss: Try node_modules/postcss-cli/bin/postcss first Fixes #4952	2018-07-18 10:00:50 +02:00
Bjørn Erik Pedersen	1b0aeeaaf0	commands: Disable flaky server tests on Windows CI	2018-07-18 09:43:31 +02:00
Bjørn Erik Pedersen	a4c513caeb	commands: Increase sleep in server teset to make it less shaky on Windows	2018-07-18 00:35:42 +02:00
Bjørn Erik Pedersen	d741064beb	Add optional lang as argument to rel/relref Fixes #4956	2018-07-18 00:07:20 +02:00
Bjørn Erik Pedersen	3eb313fef4	Simplify .Site.GetPage etc. This commit is a follow up to a recent overhaul of the GetPage/ref/relref implemenation. The most important change in this commit is the update to `.Site.GetPage`: * To reduce the amount of breakage in the wild to its minimum, I have reworked .Site.GetPage with some rules: * We cannot support more than 2 arguments, i.e. .Site.GetPage "page" "posts" "mypage.md" will now throw an error. I think this is the most uncommon syntax and should be OK. It is an easy fix to change the above to .Site.GetPage "/posts/mypage.md" or similar. * .Site.GetPage "home", .Site.GetPage "home" "" and .Site.GetPage "home" "/" will give you the home page. This means that if you have page in root with the name home.md you need to do .Site.GetPage "/home.md" or similar This commit also fixes some multilingual issues, most notable it is now possible to do cross-language ref/relref lookups by prepending the language code to the path, e.g. `/jp/posts/mypage.md`. This commit also reverts the site building tests related to this to "Hugo 0.44 state", to get better control of the changes made. Closes #4147 Closes #4727 Closes #4728 Closes #4728 Closes #4726 Closes #4652	2018-07-18 00:07:20 +02:00
Vas Sudanagunta	b93417aa1d	Unify page lookups This commit unifies the core internal page index for all page kinds. This enables the `ref` and `relref` shortcodes to support all pages kinds, and adds a new page-relative `.GetPage` method with simplified signature. See #4147 See #4727 See #4728 See #4728 See #4726 See #4652	2018-07-18 00:07:20 +02:00
Lucas Bickel	fd1f4a7860	Fix addkit link to account for i18n	2018-07-16 21:23:27 +02:00
Bjørn Erik Pedersen	4c240800a4	resource/bundler: Improve error message	2018-07-16 10:42:07 +02:00
Garry McNulty	38204c4ab6	hugolib: Only set 'allThemes' if there are themes in the config file When the 'allThemes' configuration setting is read, it will panic if there are no themes. This was a regression introduced in Hugo 0.42. Also updated a unit test to check for this. Fixes #4851	2018-07-15 16:13:48 +02:00
Bjørn Erik Pedersen	2f2bc7ff70	resource/integrity: Remove unused code	2018-07-14 11:17:48 +02:00
Bjørn Erik Pedersen	242b297f57	releaser: Remove flag on Windows build	2018-07-13 08:40:09 +02:00
hugoreleaser	f44c9ab9cd	releaser: Prepare repository for 0.45-DEV [ci skip]	2018-07-13 06:05:41 +00:00