Page Not Found
+
+ Go Home
+
+ 
+```
diff --git a/content/getting-started/directory-structure.md b/content/getting-started/directory-structure.md
index 8ffa13e51..9946f2cef 100644
--- a/content/getting-started/directory-structure.md
+++ b/content/getting-started/directory-structure.md
@@ -11,7 +11,6 @@ weight: 50
draft: false
needsreview: true
aliases: [/overview/source-directory/]
-notesforauthors:
---
diff --git a/content/getting-started/installing.md b/content/getting-started/installing.md
index d75a9e772..4dfe62fef 100644
--- a/content/getting-started/installing.md
+++ b/content/getting-started/installing.md
@@ -54,7 +54,7 @@ For more detailed explanations, read the installation guides that follow for [Wi
* [Git][installgit]
* [Go 1.5+][installgo]
-#### Get directly from GitHub
+#### Get Hugo Directly from GitHub
```sh
export GOPATH=$HOME/go
@@ -303,7 +303,7 @@ The following aims to be a complete guide to installing Hugo on your Windows PC.
2. You will use `C:\Hugo\Sites` as the starting point for your site.
3. You will use `C:\Hugo\bin` to store executable files.
-### Setup Your Directories
+### Set up Your Directories
You'll need a place to store the Hugo executable, your content (the files that you build), and the generated files (the HTML that Hugo builds for you).
@@ -326,7 +326,7 @@ You'll need a place to store the Hugo executable, your content (the files that y
3. Find the Windows files near the bottom (they're in alphabetical order, so Windows is last) – download either the 32-bit or 64-bit file depending on whether you have 32-bit or 64-bit Windows. (If you don't know, [see here](https://esupport.trendmicro.com/en-us/home/pages/technical-support/1038680.aspx).)
4. Move the ZIP file into your `C:\Hugo\bin` folder.
5. Double-click on the ZIP file and extract its contents. Be sure to extract the contents into the same `C:\Hugo\bin` folder – Windows will do this by default unless you tell it to extract somewhere else.
-6. You should now have three new files: hugo executable (example: hugo_0.18_windows_amd64.exe), license.md, and readme.md. (you can delete the ZIP download now.). Rename that hugo executable (hugo_hugo-version_platform_arch.exe) to hugo.exe for ease of use.
+6. You should now have three new files: hugo executable (e.g. `hugo_0.18_windows_amd64.exe`), `license.md`, and `readme.md`. (You can delete the ZIP download now.) Rename that hugo executable (`hugo_hugo-version_platform_arch.exe`) to `hugo.exe` for ease of use.
7. Now add Hugo to your Windows PATH settings:
##### For Windows 10 users:
diff --git a/content/hosting-and-deployment/hosting-on-netlify.md b/content/hosting-and-deployment/hosting-on-netlify.md
new file mode 100644
index 000000000..2a3eb74e0
--- /dev/null
+++ b/content/hosting-and-deployment/hosting-on-netlify.md
@@ -0,0 +1,17 @@
+---
+title: Hosting on Netlify
+linktitle: Hosting on Netlify
+description:
+date: 2017-02-01
+publishdate: 2017-02-01
+lastmod: 2017-02-25
+categories: [hosting and deployment]
+tags: [netlify,hosting,deployment]
+authors: [Ryan Watters]
+weight: 20
+draft: false
+aliases: []
+toc: true
+needsreview:
+notesforauthors:
+---
diff --git a/content/templates/homepage-template.md b/content/templates/homepage-template.md
index 7f0297ea1..ca42879d7 100644
--- a/content/templates/homepage-template.md
+++ b/content/templates/homepage-template.md
@@ -11,7 +11,6 @@ weight: 30
draft: false
aliases: [/layout/homepage/,/templates/homepage/]
toc: false
-needsreview: true
---
The homepage of a website is often formatted differently than the other pages. In Hugo you can define your own homepage template.
@@ -19,7 +18,7 @@ The homepage of a website is often formatted differently than the other pages. I
Homepage is a `Page` and therefore has all the [page variables][pagevars] and [site variables][sitevars] available for use.
{{% note "The Only Required Template" %}}
-The homepage template is the *only* required template for building a site and useful when bootstrapping a new site and template. It is also the only required template if you are developing a single page site.
+The homepage template is the *only* required template for building a site and therefore useful when bootstrapping a new site and template. It is also the only required template if you are developing a single-page website.
{{% /note %}}
## Homepage Template Lookup Order
diff --git a/content/templates/partials.md b/content/templates/partials.md
index 287fce3cc..983aaa3bf 100644
--- a/content/templates/partials.md
+++ b/content/templates/partials.md
@@ -11,26 +11,18 @@ weight: 90
draft: false
aliases: [/templates/partials/,/layout/chrome/,/extras/analytics/]
toc: true
-notesforauthors:
+needsreview: true
---
## Partials vs Templates
-In practice, it's very convenient to split out common template portions into a
-partial template that can be included anywhere. As you create the rest of your
-templates, you will include templates from the `/layouts/partials/` directory
-or from arbitrary partial subdirectories like `/layouts/partials/post/tag/`.
+In practice, it's very convenient to split out common template portions into a partial template that can be included anywhere. As you create the rest of your templates, you will include templates from the `/layouts/partials/` directory or from arbitrary partial subdirectories like `/layouts/partials/post/tag/`.
Partials are especially important for [themes][] because they give theme users an opportunity to [overwrite just a small portion of a theme][customize] while maintaining compatibility with the theme's upstream.
-Theme developers may want to include a few partials with empty HTML
-files in the theme just so end users have an easy place to inject their
-customized content.
+Theme developers may want to include a few partials with empty HTML files in the theme just so end users have an easy place to inject their customized content.
-I've found it helpful to include a header and footer template in
-partials so I can include those in all the full page layouts. There is
-nothing special about header.html and footer.html other than they seem
-like good names to use for inclusion in your other templates.
+I've found it helpful to include a header and footer template in partials so I can include those in all the full page layouts. There is nothing special about header.html and footer.html other than they seem like good names to use for inclusion in your other templates.
```bash
▾ layouts/
@@ -41,17 +33,13 @@ like good names to use for inclusion in your other templates.
## Partial vs Template
-Version v0.12 of Hugo introduced the `partial` call inside the template system.
-This is a change to the way partials were handled previously inside the
-template system. In earlier versions, Hugo didn’t treat partials specially, and
-you could include a partial template with the `template` call in the standard
-template language.
+Version v0.12 of Hugo introduced the `partial` call inside the template system. This is a change to the way partials were handled previously inside the template system. In earlier versions, Hugo didn’t treat partials specially, and you could include a partial template with the `template` call in the standard template language.
With the addition of the theme system in v0.11, it became apparent that a theme & override-aware partial was needed.
When using Hugo v0.12 and above, please use the `partial` call (and leave out the “partial/” path). The old approach would still work, but wouldn’t benefit from the ability to have users override the partial theme file with local layouts.
-## Example header.html
+## Example `header.html`
This header template is used for [spf13.com](http://spf13.com/):
@@ -75,7 +63,7 @@ This header template is used for [spf13.com](http://spf13.com/):
```
{{% /code %}}
-## Example footer.html
+## Example `footer.html`
This footer template is used for [spf13.com](http://spf13.com/):
@@ -120,7 +108,7 @@ Note that the subdirectories you create under /layouts/partials can be named wha
For more examples of referencing these templates, see [single content templates](/templates/content/), [list templates](/templates/list/) and [homepage templates](/templates/homepage/).
-## Variable scoping
+## Variable Scoping
As you might have noticed, `partial` calls receive two parameters.
diff --git a/content/templates/rendering-lists.md b/content/templates/rendering-lists.md
index 228bfb53d..6ec946c96 100644
--- a/content/templates/rendering-lists.md
+++ b/content/templates/rendering-lists.md
@@ -334,26 +334,9 @@ within each group in alphabetical order by title.
{{ end }}
```
-## Filtering and Limiting Content
+## Filtering and Limiting List Content
-Sometimes you only want to list a subset of the available content. A common
-request is to only display “Posts” on the homepage. Using the `where` function,
-you can do just that.
-
-### `first`
-
-`first` works in a similar manner to the [`limit` keyword in SQL][limitkeyword]. It reduces the array to only the `first N` elements. It takes the array and number of elements as input. `first` takes two arguments:
-
-1. `array` or `slice of maps or structs`
-2. `number of elements`
-
-{{% code file="layout/_default/section.html" %}}
-```golang
-{{ range first 10 .Data.Pages }}
- {{ .Render "summary" }}
-{{ end }}
-```
-{{% /code %}}
+Sometimes you only want to list a subset of the available content. A common request is to only display “Posts” on the homepage. Using the `where` function, you can do just that.
### `where`
@@ -371,6 +354,21 @@ you can do just that.
```
{{% /code %}}
+### `first`
+
+`first` works in a similar manner to the [`limit` keyword in SQL][limitkeyword]. It reduces the array to only the `first N` elements. It takes the array and number of elements as input. `first` takes two arguments:
+
+1. `array` or `slice of maps or structs`
+2. `number of elements`
+
+{{% code file="layout/_default/section.html" %}}
+```golang
+{{ range first 10 .Data.Pages }}
+ {{ .Render "summary" }}
+{{ end }}
+```
+{{% /code %}}
+
### `first` and `where` Together
Using `first` and `where` together can be very powerful:
diff --git a/content/templates/robots.md b/content/templates/robots.md
index 58a464964..d972fb19b 100644
--- a/content/templates/robots.md
+++ b/content/templates/robots.md
@@ -14,10 +14,9 @@ toc: false
needsreview: true
---
-Hugo can generated a customized [robots.txt](http://www.robotstxt.org/) in the
-[same way as any other templates]({{< ref "templates/go-templates.md" >}}).
+Hugo can generate a customized [robots.txt][robots] in the same way as any other template.
-To enable it, just set `enableRobotsTXT` option to `true` in the [configuration file]({{< ref "overview/configuration.md" >}}). By default, it generates a robots.txt, which allows everything, with the following content:
+To enable creating your robots.txt as a template, set the `enableRobotsTXT` value to `true` in your [project's configuration file][config]. By default, this option generates a robots.txt with the following content, which tells search engines that they are allowed to crawl everything:
```http
User-agent: *
@@ -30,15 +29,22 @@ The [lookup order][lookup] for the `robots.txt` template is as follows:
* `/layouts/robots.txt`
* `/themes/