shithub: hugo

--- /dev/null

+++ b/.gitmodules

@@ -1,0 +1,3 @@

+[submodule "themes/gohugoioTheme"]

+	path = themes/gohugoioTheme

+	url = https://github.com/gohugoio/gohugoioTheme.git

--- /dev/null

+++ b/LICENSE.md

@@ -1,0 +1,194 @@

+Apache License

+==============

+_Version 2.0, January 2004_

+_&lt;<http://www.apache.org/licenses/>&gt;_

+### Terms and Conditions for use, reproduction, and distribution

+#### 1. Definitions

+“License” shall mean the terms and conditions for use, reproduction, and

+distribution as defined by Sections 1 through 9 of this document.

+“Licensor” shall mean the copyright owner or entity authorized by the copyright

+owner that is granting the License.

+“Legal Entity” shall mean the union of the acting entity and all other entities

+that control, are controlled by, or are under common control with that entity.

+For the purposes of this definition, “control” means **(i)** the power, direct or

+indirect, to cause the direction or management of such entity, whether by

+contract or otherwise, or **(ii)** ownership of fifty percent (50%) or more of the

+outstanding shares, or **(iii)** beneficial ownership of such entity.

+“You” (or “Your”) shall mean an individual or Legal Entity exercising

+permissions granted by this License.

+“Source” form shall mean the preferred form for making modifications, including

+but not limited to software source code, documentation source, and configuration

+files.

+“Object” form shall mean any form resulting from mechanical transformation or

+translation of a Source form, including but not limited to compiled object code,

+generated documentation, and conversions to other media types.

+“Work” shall mean the work of authorship, whether in Source or Object form, made

+available under the License, as indicated by a copyright notice that is included

+in or attached to the work (an example is provided in the Appendix below).

+“Derivative Works” shall mean any work, whether in Source or Object form, that

+is based on (or derived from) the Work and for which the editorial revisions,

+annotations, elaborations, or other modifications represent, as a whole, an

+original work of authorship. For the purposes of this License, Derivative Works

+shall not include works that remain separable from, or merely link (or bind by

+name) to the interfaces of, the Work and Derivative Works thereof.

+“Contribution” shall mean any work of authorship, including the original version

+of the Work and any modifications or additions to that Work or Derivative Works

+thereof, that is intentionally submitted to Licensor for inclusion in the Work

+by the copyright owner or by an individual or Legal Entity authorized to submit

+on behalf of the copyright owner. For the purposes of this definition,

+“submitted” means any form of electronic, verbal, or written communication sent

+to the Licensor or its representatives, including but not limited to

+communication on electronic mailing lists, source code control systems, and

+issue tracking systems that are managed by, or on behalf of, the Licensor for

+the purpose of discussing and improving the Work, but excluding communication

+that is conspicuously marked or otherwise designated in writing by the copyright

+owner as “Not a Contribution.”

+“Contributor” shall mean Licensor and any individual or Legal Entity on behalf

+of whom a Contribution has been received by Licensor and subsequently

+incorporated within the Work.

+#### 2. Grant of Copyright License

+Subject to the terms and conditions of this License, each Contributor hereby

+grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,

+irrevocable copyright license to reproduce, prepare Derivative Works of,

+publicly display, publicly perform, sublicense, and distribute the Work and such

+Derivative Works in Source or Object form.

+#### 3. Grant of Patent License

+Subject to the terms and conditions of this License, each Contributor hereby

+grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,

+irrevocable (except as stated in this section) patent license to make, have

+made, use, offer to sell, sell, import, and otherwise transfer the Work, where

+such license applies only to those patent claims licensable by such Contributor

+that are necessarily infringed by their Contribution(s) alone or by combination

+of their Contribution(s) with the Work to which such Contribution(s) was

+submitted. If You institute patent litigation against any entity (including a

+cross-claim or counterclaim in a lawsuit) alleging that the Work or a

+Contribution incorporated within the Work constitutes direct or contributory

+patent infringement, then any patent licenses granted to You under this License

+for that Work shall terminate as of the date such litigation is filed.

+#### 4. Redistribution

+You may reproduce and distribute copies of the Work or Derivative Works thereof

+in any medium, with or without modifications, and in Source or Object form,

+provided that You meet the following conditions:

+* **(a)** You must give any other recipients of the Work or Derivative Works a copy of

+this License; and

+* **(b)** You must cause any modified files to carry prominent notices stating that You

+changed the files; and

+* **(c)** You must retain, in the Source form of any Derivative Works that You distribute,

+all copyright, patent, trademark, and attribution notices from the Source form

+of the Work, excluding those notices that do not pertain to any part of the

+Derivative Works; and

+* **(d)** If the Work includes a “NOTICE” text file as part of its distribution, then any

+Derivative Works that You distribute must include a readable copy of the

+attribution notices contained within such NOTICE file, excluding those notices

+that do not pertain to any part of the Derivative Works, in at least one of the

+following places: within a NOTICE text file distributed as part of the

+Derivative Works; within the Source form or documentation, if provided along

+with the Derivative Works; or, within a display generated by the Derivative

+Works, if and wherever such third-party notices normally appear. The contents of

+the NOTICE file are for informational purposes only and do not modify the

+License. You may add Your own attribution notices within Derivative Works that

+You distribute, alongside or as an addendum to the NOTICE text from the Work,

+provided that such additional attribution notices cannot be construed as

+modifying the License.

+You may add Your own copyright statement to Your modifications and may provide

+additional or different license terms and conditions for use, reproduction, or

+distribution of Your modifications, or for any such Derivative Works as a whole,

+provided Your use, reproduction, and distribution of the Work otherwise complies

+with the conditions stated in this License.

+#### 5. Submission of Contributions

+Unless You explicitly state otherwise, any Contribution intentionally submitted

+for inclusion in the Work by You to the Licensor shall be under the terms and

+conditions of this License, without any additional terms or conditions.

+Notwithstanding the above, nothing herein shall supersede or modify the terms of

+any separate license agreement you may have executed with Licensor regarding

+such Contributions.

+#### 6. Trademarks

+This License does not grant permission to use the trade names, trademarks,

+service marks, or product names of the Licensor, except as required for

+reasonable and customary use in describing the origin of the Work and

+reproducing the content of the NOTICE file.

+#### 7. Disclaimer of Warranty

+Unless required by applicable law or agreed to in writing, Licensor provides the

+Work (and each Contributor provides its Contributions) on an “AS IS” BASIS,

+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied,

+including, without limitation, any warranties or conditions of TITLE,

+NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are

+solely responsible for determining the appropriateness of using or

+redistributing the Work and assume any risks associated with Your exercise of

+permissions under this License.

+#### 8. Limitation of Liability

+In no event and under no legal theory, whether in tort (including negligence),

+contract, or otherwise, unless required by applicable law (such as deliberate

+and grossly negligent acts) or agreed to in writing, shall any Contributor be

+liable to You for damages, including any direct, indirect, special, incidental,

+or consequential damages of any character arising as a result of this License or

+out of the use or inability to use the Work (including but not limited to

+damages for loss of goodwill, work stoppage, computer failure or malfunction, or

+any and all other commercial damages or losses), even if such Contributor has

+been advised of the possibility of such damages.

+#### 9. Accepting Warranty or Additional Liability

+While redistributing the Work or Derivative Works thereof, You may choose to

+offer, and charge a fee for, acceptance of support, warranty, indemnity, or

+other liability obligations and/or rights consistent with this License. However,

+in accepting such obligations, You may act only on Your own behalf and on Your

+sole responsibility, not on behalf of any other Contributor, and only if You

+agree to indemnify, defend, and hold each Contributor harmless for any liability

+incurred by, or claims asserted against, such Contributor by reason of your

+accepting any such warranty or additional liability.

+_END OF TERMS AND CONDITIONS_

+### APPENDIX: How to apply the Apache License to your work

+To apply the Apache License to your work, attach the following boilerplate

+notice, with the fields enclosed by brackets `[]` replaced with your own

+identifying information. (Don't include the brackets!) The text should be

+enclosed in the appropriate comment syntax for the file format. We also

+recommend that a file or class name and description of purpose be included on

+the same “printed page” as the copyright notice for easier identification within

+third-party archives.

+    Copyright [yyyy] [name of copyright owner]

+    Licensed under the Apache License, Version 2.0 (the "License");

+    you may not use this file except in compliance with the License.

+    You may obtain a copy of the License at

+      http://www.apache.org/licenses/LICENSE-2.0

+    Unless required by applicable law or agreed to in writing, software

+    distributed under the License is distributed on an "AS IS" BASIS,

+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

+    See the License for the specific language governing permissions and

+    limitations under the License.

--- a/archetypes/default.md

+++ b/archetypes/default.md

@@ -1,6 +1,13 @@

-+++

-weight = 5

-[menu]

-  [menu.main]

-    parent = "x"

-+++

+---

+linktitle: ""

+description: ""

+godocref: ""

+publishdate: ""

+lastmod: ""

+categories: []

+tags: []

+weight: 00

+slug: ""

+aliases: []

+toc: false

+---

--- /dev/null

+++ b/archetypes/functions.md

@@ -1,0 +1,17 @@

+---

+linktitle: ""

+description: ""

+godocref: ""

+publishdate: ""

+lastmod: ""

+categories: [functions]

+tags: []

+ns: ""

+signature: []

+workson: []

+hugoversion: ""

+aliases: []

+relatedfuncs: []

+toc: false

+deprecated: false

+---

\ No newline at end of file

--- a/archetypes/showcase.md

+++ b/archetypes/showcase.md

@@ -1,14 +1,13 @@

---

-date: 2013-07-01T07:32:00Z

 description: ""

+lastmod: ""

 license: ""

 licenseLink: ""

-sitelink: http://spf13.com/

-sourceLink: https://github.com/spf13/spf13.com

-tags:

-- personal

-- blog

-thumbnail: /img/spf13-tn.jpg

-title: spf13.com

----

+sitelink: ""

+sourcelink: ""

+categories: [showcase]

+tags: []

+image: ""

+toc: false

+notesforauthors: "Go to gohugo.io/contribute/documentation for more info"

+---

\ No newline at end of file

--- /dev/null

+++ b/archetypes/tutorials.md

@@ -1,0 +1,16 @@

+---

+linktitle: ""

+description: ""

+godocref: ""

+publishdate: ""

+lastmod: ""

+categories: [tutorials]

+tags: []

+author: ""

+authorurl: ""

+originalurl: ""

+draft: false

+aliases: []

+notesforauthors: "Go to gohugo.io/contribute/documentation for more info."

+---

--- a/config.toml

+++ b/config.toml

@@ -1,13 +1,21 @@

+baseURL = "https://gohugo.io/"

+paginate =  100

+defaultContentLanguage = "en"

+enableEmoji = true

+# Set the unicode character used for the "return" link in page footnotes.

+footnotereturnlinkcontents = "↩"

+languageCode = "en-us"

+metaDataFormat = "yaml"

 title = "Hugo: A Fast and Flexible Website Generator"

-baseurl = "http://gohugo.io/"

-MetaDataFormat = "yaml"

+theme = "gohugoioTheme"

+googleAnalytics = "UA-7131036-4"

 pluralizeListTitles = false

 # We do redirects via Netlify's _redirects file, generated by Hugo (see "outputs" below).

 disableAliases = true

-[blackfriday]

-  plainIDAnchors = true

 [outputs]

 home = [ "HTML", "RSS", "REDIR" ]

@@ -23,113 +31,191 @@

 isPlainText = true

 notAlternative = true

+[social]

+twitter = "GoHugoIO"

+#CUSTOM PARAMS

 [params]

-  description = "Documentation of Hugo, a fast and flexible static site generator built with love by spf13, bep and friends in Go"

-  author = "Steve Francia (spf13) and friends"

-  release = "0.24.1"

+  description = "The world’s fastest framework for building websites"

+  ## Used for views in rendered HTML (i.e., rather than using the .Hugo variable)

+  release = "Hugo-Next"

+  ## Setting this to true will add a "noindex" to *EVERY* page on the site

+  removefromexternalsearch = false

+  ## Gh repo for site footer (include trailing slash)

+  ghrepo = "https://github.com/gohugoio/hugoDocs/"

+  ### Edit content repo (set to automatically enter "edit" mode; this is good for "improve this page" links)

+  ghdocsrepo = "https://github.com/gohugoio/hugoDocs/tree/master/docs"

+  ## Gitter URL

+  gitter = "https://gitter.im/spf13/hugo"

+  ## Discuss Forum URL

+  forum = "https://discourse.gohugo.io/"

+  ## Google Tag Manager

+  gtmid = ""

+  # First one is picked as the Twitter card image if not set on page.

+  images = ["images/gohugoio-card.png"]

+  flex_box_interior_classes = "flex-auto w-100 w-40-l mr3 mb3 bg-white ba b--moon-gray nested-copy-line-height"

+  #sidebar_direction = "sidebar_left"

+# MARKDOWN

+## Configuration for BlackFriday markdown parser: https://github.com/russross/blackfriday

+[blackfriday]

+	plainIDAnchors = true

+	hrefTargetBlank = true

+  angledQuotes = false

+  latexDashes = true

+## As of v0.20, all content files include a default "categories" value that's the same as the section. This was a cheap future-proofing method and should/could be changed accordingly.

 [taxonomies]

-  tag = "tags"

-  group = "groups"

+  category = "categories"

-[[menu.main]]

-    name = "Download Hugo"

-    pre = "<i class='fa fa-download'></i>"

-    url = "https://github.com/gohugoio/hugo/releases"

-    weight = -200

-[[menu.main]]

-    name = "Site Showcase"

-    pre = "<i class='fa fa-cubes'></i>"

-    url = "/showcase/"

-    weight = -180

-[[menu.main]]

-    name = "Theme Showcase"

-    pre = "<i class='fa fa-puzzle-piece'></i>"

-    url = "http://themes.gohugo.io"

-    weight = -170

-[[menu.main]]

-    name = "Press & Articles"

-    pre = "<i class='fa fa-bullhorn'></i>"

-    url = "/community/press/"

-    weight = -160

-[[menu.main]]

-    name = "Discuss Hugo"

-    pre = "<i class='fa fa-comments'></i>"

-    url = "https://discourse.gohugo.io/"

-    weight = -150

-[[menu.main]]

-    name = "About Hugo"

-    identifier = "about"

-    pre = "<i class='fa fa-heart'></i>"

-    weight = -110

-[[menu.main]]

-    name = "Release Notes"

-     url = "/release-notes/"

-    pre = "<i class='fa fa-newspaper-o'></i>"

-    weight = -111

-[[menu.main]]

-    name = "Getting Started"

-    identifier = "getting started"

-    pre = "<i class='fa fa-road'></i>"

-    weight = -100

-[[menu.main]]

-    name = "Content"

-    identifier = "content"

-    pre = "<i class='fa fa-file-text'></i>"

-    weight = -90

-[[menu.main]]

+# High level items

+[[menu.docs]]

+  name = "About Hugo"

+  weight = 1

+  identifier = "about"

+  url = "/about/"

+[[menu.docs]]

+  name = "Getting Started"

+  weight = 5

+  identifier = "getting-started"

+  url = "/getting-started/"

+[[menu.docs]]

+  name = "Themes"

+  weight = 15

+  identifier = "themes"

+  post = "break"

+  url = "/themes/"

+# Core Menus

+[[menu.docs]]

+  name = "Content Management"

+  weight = 20

+  identifier = "content-management"

+  post = "expanded"

+  url = "/content-management/"

+[[menu.docs]]

+  name = "Templates"

+  weight = 25

+  identifier = "templates"

+  url = "/templates/"

+[[menu.docs]]

+  name = "Functions"

+  weight = 30

+  identifier = "functions"

+  url = "/functions/"

+[[menu.docs]]

+  name = "Variables"

+  weight = 35

+  identifier = "variables"

+  url = "/variables/"

+[[menu.docs]]

+  name = "CLI"

+  weight = 40

+  post = "break"

+  identifier = "commands"

+  url = "/commands/"

+# LOW LEVEL ITEMS

+[[menu.docs]]

+  name = "Troubleshooting"

+  weight = 60

+  identifier = "troubleshooting"

+  url = "/troubleshooting/"

+[[menu.docs]]

+  name = "Tools"

+  weight = 70

+  identifier = "tools"

+  url = "/tools/"

+[[menu.docs]]

+  name = "Hosting & Deployment"

+  weight = 80

+  identifier = "hosting-and-deployment"

+  url = "/hosting-and-deployment/"

+[[menu.docs]]

+  name = "Contribute"

+  weight = 100

+  post = "break"

+  identifier = "contribute"

+  url = "/contribute/"

+#[[menu.docs]]

+#  name = "Tags"

+#  weight = 120

+#  identifier = "tags"

+#  url = "/tags/"

+# [[menu.docs]]

+#   name = "Categories"

+#   weight = 140

+#   identifier = "categories"

+#   url = "/categories/"

+######## QUICKLINKS

+  [[menu.quicklinks]]

+    name = "Fundamentals"

+    weight = 1

+    identifier = "fundamentals"

+    url = "/tags/fundamentals/"

+######## GLOBAL ITEMS TO BE SHARED WITH THE HUGO SITES

+[[menu.global]]

+    name = "News"

+    weight = 1

+    identifier = "news"

+    url = "/news/"

+  [[menu.global]]

+    name = "Docs"

+    weight = 5

+    identifier = "docs"

+    url = "/documentation/"

+  [[menu.global]]

     name = "Themes"

+    weight = 10

     identifier = "themes"

-    pre = "<i class='fa fa-desktop'></i>"

-    weight = -85

-[[menu.main]]

-    parent = "themes"

-    name = "Theme Showcase"

-    url = "http://themes.gohugo.io"

-    weight = -170

-[[menu.main]]

-    name = "Templates"

-    identifier = "layout"

-    pre = "<i class='fa fa-columns'></i>"

-    weight = -80

-[[menu.main]]

-    name = "Taxonomies"

-    identifier = "taxonomy"

-    pre = "<i class='fa fa-tags'></i>"

-    weight = -70

-[[menu.main]]

-    name = "Extras"

-    identifier = "extras"

-    pre = "<i class='fa fa-gift'></i>"

-    weight = -60

-[[menu.main]]

+    url = "https://themes.gohugo.io/"

+  # Anything with a weight > 100 gets an external icon

+  [[menu.global]]

     name = "Community"

+    weight = 150

+    icon = true

     identifier = "community"

-    pre = "<i class='fa fa-group'></i>"

-    weight = -50

-[[menu.main]]

-    parent = "community"

-    name = "Discussion Forum"

+    post = "external"

     url = "https://discourse.gohugo.io/"

-    weight = 150

-[[menu.main]]

-    name = "Tutorials"

-    identifier = "tutorials"

-    pre = "<i class='fa fa-book'></i>"

-    weight = -40

-[[menu.main]]

-    name = "Troubleshooting"

-    identifier = "troubleshooting"

-    pre = "<i class='fa fa-wrench'></i>"

-    weight = -30

-[[menu.main]]

-    name = "Tools"

-    url = "/tools/"

-    pre = "<i class='fa fa-cogs'></i>"

-    weight = -25

-[[menu.main]]

-    name = "Hugo Cmd Reference"

-    identifier = "commands"

-    pre = "<i class='fa fa-space-shuttle'></i>"

-    weight = -20

-    url = "/commands/"

+  [[menu.global]]

+    name = "GitHub"

+    weight = 200

+    identifier = "github"

+    post = "external"

+    url = "https://github.com/gohugoio/hugo"

--- /dev/null

+++ b/content/_index.md

@@ -1,0 +1,49 @@

+---

+title: "Hugo: A Fast and Flexible Website Generator"

+date: 2017-03-02T12:00:00-05:00

+features:

+  - heading: Blistering Speed

+    image_path: /images/icon-fast.svg

+    tagline: What's modern about waiting for your site to build?

+    copy: Hugo is the fastest tool of its kind. At <1 ms per page, the average site builds in less than a second.

+  - heading: Robust Content Management

+    image_path: /images/icon-content-management.svg

+    tagline: Flexibility rules. Hugo is a content strategist's dream.

+    copy: Hugo supports unlimited content types, taxonomies, menus, dynamic API-driven content, and more, all without plugins.

+  - heading: Shortcodes

+    image_path: /images/icon-shortcodes.svg

+    tagline: Hugo's shortcodes are Markdown's hidden superpower.

+    copy: We love the beautiful simplicity of markdown’s syntax, but there are times when we want more flexibility. Hugo shortcodes allow for both beauty and flexibility.

+  - heading: Built-in Templates

+    image_path: /images/icon-built-in-templates.svg

+    tagline: Hugo has common patterns to get your work done quickly.

+    copy: Hugo ships with pre-made templates to make quick work of SEO, commenting, analytics and other functions. One line of code, and you're done.

+  - heading: Multilingual and i18n

+    image_path: /images/icon-multilingual2.svg

+    tagline: Polyglot baked in.

+    copy: Hugo provides full i18n support for multi-language sites with the same straightforward development experience Hugo users love in single-language sites.

+  - heading: Custom Outputs

+    image_path: /images/icon-custom-outputs.svg

+    tagline: HTML not Enough?

+    copy: Hugo allows you to output your content in multiple formats, including JSON or AMP, and makes it easy to create your own.

+sections:

+  - heading: "100s of Themes"

+    cta: Check out the Hugo's themes.

+    link: http://themes.gohugo.io/

+    color_classes: bg-accent-color white

+    image: /images/homepage-screenshot-hugo-themes.jpg

+    copy: "Hugo provides a robust theming system that is easy to implement but capable of producing even the most complicated websites."

+  - heading: "Capable Templating"

+    cta: Get Started.

+    link: templates/

+    color_classes: bg-primary-color-light black

+    image: /images/home-page-templating-example.png

+    copy: "Hugo's Go-based templating provides just the right amount of logic to build anything from the simple to complex. If you prefer Jade/Pug-like syntax, you can also use Amber, Ace, or any combination of the three."

+---

+Hugo is one of the most popular open-source static site generators. With its amazing speed and flexibility, Hugo makes building websites fun again.

--- /dev/null

+++ b/content/about/_index.md

@@ -1,0 +1,20 @@

+---

+title: About Hugo

+linktitle: Overview

+description: Hugo's features, roadmap, license, and motivation.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: []

+#tags: []

+menu:

+  docs:

+    parent: "about"

+    weight: 1

+weight: 1

+draft: false

+aliases: [/about-hugo/,/docs/]

+toc: false

+---

+Hugo is not your average static site generator.

--- /dev/null

+++ b/content/about/benefits.md

@@ -1,0 +1,43 @@

+---

+title: The Benefits of Static Site Generators

+linktitle: The Benefits of Static

+description: Improved performance, security and ease of use are just a few of the reasons static site generators are so appealing.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [ssg,static,performance,security]

+menu:

+  docs:

+    parent: "about"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+aliases: []

+toc: false

+---

+The purpose of website generators is to render content into HTML files. Most are "dynamic site generators." That means the HTTP server---i.e., the program that sends files to the browser to be viewed---runs the generator to create a new HTML file every time an end user requests a page.

+Over time, dynamic site generators were programmed to cache their HTML files to prevent unnecessary delays in delivering pages to end users. A cached page is a static version of a web page.

+Hugo takes caching a step further and all HTML files are rendered on your computer. You can review the files locally before copying them to the computer hosting the HTTP server. Since the HTML files aren't generated dynamically, we say that Hugo is a *static site generator*.

+This has many benefits. The most noticeable is performance. HTTP servers are *very* good at sending files---so good, in fact, that you can effectively serve the same number of pages with a fraction of the memory and CPU needed for a dynamic site.

+## More on Static Site Generators

+* ["An Introduction to Static Site Generators", David Walsh][]

+* ["Hugo vs. Wordpress page load speed comparison: Hugo leaves WordPress in its dust", GettingThingsTech][hugovwordpress]

+* ["Static Site Generators", O-Reilly][]

+* [StaticGen: Top Open-Source Static Site Generators (GitHub Stars)][]

+* ["Top 10 Static Website Generators", Netlify blog][]

+* ["The Resurgence of Static", dotCMS][dotcms]

+["An Introduction to Static Site Generators", David Walsh]: https://davidwalsh.name/introduction-static-site-generators

+["Static Site Generators", O-Reilly]: /documents/oreilly-static-site-generators.pdf

+["Top 10 Static Website Generators", Netlify blog]: https://www.netlify.com/blog/2016/05/02/top-ten-static-website-generators/

+[hugovwordpress]: https://gettingthingstech.com/hugo-vs.-wordpress-page-load-speed-comparison-hugo-leaves-wordpress-in-its-dust/

+[StaticGen: Top Open-Source Static Site Generators (GitHub Stars)]: https://www.staticgen.com/

+[dotcms]: https://dotcms.com/blog/post/the-resurgence-of-static

--- /dev/null

+++ b/content/about/features.md

@@ -1,0 +1,90 @@

+---

+title: Hugo Features

+linktitle: Hugo Features

+description: Hugo boasts blistering speed, robust content management, and a powerful templating language making it a great fit for all kinds of static websites.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+menu:

+  docs:

+    parent: "about"

+    weight: 20

+weight: 20

+sections_weight: 20

+draft: false

+aliases: [/about/features]

+toc: true

+---

+## General

+* [Extremely fast][] build times (&lt; 1 ms per page)

+* Completely cross platform, with [easy installation][install] on macOS, Linux, Windows, and more

+* Renders changes on the fly with [LiveReload][] as you develop

+* [Powerful theming][]

+* [Host your site anywhere][hostanywhere]

+## Organization

+* Straightforward [organization for your projects][], including website sections

+* Customizable [URLs][]

+* Support for configurable [taxonomies][], including categories and tags

+* [Sort content][] as you desire through powerful template [functions][]

+* Automatic [table of contents][] generation

+* [Dynamic menu][] creation

+* [Pretty URLs][] support

+* [Permalink][] pattern support

+* Redirects via [aliases][]

+## Content

+* Native Markdown and Emacs Org-Mode support, as well as other languages via *external helpers* (see [supported formats][])

+* TOML, YAML, and JSON metadata support in [front matter][]

+* Customizable [homepage][]

+* Multiple [content types][]

+* Automatic and user defined [content summaries][]

+* [Shortcodes][] to enable rich content inside of Markdown

+* ["Minutes to Read"][pagevars] functionality

+* ["Wordcount"][pagevars] functionality

+## Additional Features

+* Integrated [Disqus][] comment support

+* Integrated [Google Analytics][] support

+* Automatic [RSS][] creation

+* Support for [Go][], [Amber], and [Ace][] HTML templates

+* [Syntax highlighting][] powered by [Pygments][]

+See what's coming next in the [Hugo roadmap][].

+[Ace]: /templates/alternatives/

+[aliases]: /content-management/urls/#aliases

+[Amber]: https://github.com/eknkc/amber

+[content summaries]: /content-management/summaries/

+[content types]: /content-management/types/

+[Disqus]: https://disqus.com/

+[Dynamic menu]: /templates/menus/

+[Extremely fast]: https://github.com/bep/hugo-benchmark

+[front matter]: /content-management/front-matter/

+[functions]: /functions/

+[Go]: http://golang.org/pkg/html/template/

+[Google Analytics]: https://google-analytics.com/

+[homepage]: /templates/homepage/

+[hostanywhere]: /hosting-and-deployment/

+[Hugo roadmap]: /about/roadmap

+[install]: /getting-started/installing/

+[LiveReload]: /getting-started/usage/

+[organization for your projects]: /getting-started/directory-structure/

+[pagevars]: /variables/page/

+[Permalink]: /content-management/urls/#permalinks

+[Powerful theming]: /themes/

+[Pretty URLs]: /content-management/urls/

+[Pygments]: http://pygments.org/

+[RSS]: /templates/rss/

+[Shortcodes]: /content-management/shortcodes/

+[sort content]: /templates/

+[supported formats]: /content-management/formats/

+[Syntax highlighting]: /tools/syntax-highlighting/

+[table of contents]: /content-management/toc/

+[taxonomies]: /content-management/taxonomies/

+[URLs]: /content-management/urls/

--- /dev/null

+++ b/content/about/license.md

@@ -1,0 +1,167 @@

+---

+title: Apache License

+linktitle: License

+description: Hugo v0.15 and later are released under the Apache 2.0 license.

+date: 2016-02-01

+publishdate: 2016-02-01

+lastmod: 2016-03-02

+categories: ["about hugo"]

+#tags: ["License","apache"]

+menu:

+  docs:

+    parent: "about"

+    weight: 60

+weight: 60

+sections_weight: 60

+aliases: [/meta/license]

+toc: true

+---

+{{% note %}}

+Hugo v0.15 and later are released under the Apache 2.0 license.

+Earlier versions of Hugo were released under the [Simple Public License](https://opensource.org/licenses/Simple-2.0).

+{{% /note %}}

+_Version 2.0, January 2004_ <br>

+<http://www.apache.org/licenses/LICENSE-2.0>

+*Terms and Conditions for use, reproduction, and distribution*

+## 1. Definitions

+“License” shall mean the terms and conditions for use, reproduction, and

+distribution as defined by Sections 1 through 9 of this document.

+“Licensor” shall mean the copyright owner or entity authorized by the copyright

+owner that is granting the License.

+“Legal Entity” shall mean the union of the acting entity and all other entities

+that control, are controlled by, or are under common control with that entity.

+For the purposes of this definition, “control” means **(i)** the power, direct or

+indirect, to cause the direction or management of such entity, whether by

+contract or otherwise, or **(ii)** ownership of fifty percent (50%) or more of the

+outstanding shares, or **(iii)** beneficial ownership of such entity.

+“You” (or “Your”) shall mean an individual or Legal Entity exercising

+permissions granted by this License.

+“Source” form shall mean the preferred form for making modifications, including

+but not limited to software source code, documentation source, and configuration

+files.

+“Object” form shall mean any form resulting from mechanical transformation or

+translation of a Source form, including but not limited to compiled object code,

+generated documentation, and conversions to other media types.

+“Work” shall mean the work of authorship, whether in Source or Object form, made

+available under the License, as indicated by a copyright notice that is included

+in or attached to the work (an example is provided in the Appendix below).

+“Derivative Works” shall mean any work, whether in Source or Object form, that

+is based on (or derived from) the Work and for which the editorial revisions,

+annotations, elaborations, or other modifications represent, as a whole, an

+original work of authorship. For the purposes of this License, Derivative Works

+shall not include works that remain separable from, or merely link (or bind by

+name) to the interfaces of, the Work and Derivative Works thereof.

+“Contribution” shall mean any work of authorship, including the original version

+of the Work and any modifications or additions to that Work or Derivative Works

+thereof, that is intentionally submitted to Licensor for inclusion in the Work

+by the copyright owner or by an individual or Legal Entity authorized to submit

+on behalf of the copyright owner. For the purposes of this definition,

+“submitted” means any form of electronic, verbal, or written communication sent

+to the Licensor or its representatives, including but not limited to

+communication on electronic mailing lists, source code control systems, and

+issue tracking systems that are managed by, or on behalf of, the Licensor for

+the purpose of discussing and improving the Work, but excluding communication

+that is conspicuously marked or otherwise designated in writing by the copyright

+owner as “Not a Contribution.”

+“Contributor” shall mean Licensor and any individual or Legal Entity on behalf

+of whom a Contribution has been received by Licensor and subsequently

+incorporated within the Work.

+## 2. Grant of Copyright License

+Subject to the terms and conditions of this License, each Contributor hereby

+grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,

+irrevocable copyright license to reproduce, prepare Derivative Works of,

+publicly display, publicly perform, sublicense, and distribute the Work and such

+Derivative Works in Source or Object form.

+## 3. Grant of Patent License

+Subject to the terms and conditions of this License, each Contributor hereby

+grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,

+irrevocable (except as stated in this section) patent license to make, have

+made, use, offer to sell, sell, import, and otherwise transfer the Work, where

+such license applies only to those patent claims licensable by such Contributor

+that are necessarily infringed by their Contribution(s) alone or by combination

+of their Contribution(s) with the Work to which such Contribution(s) was

+submitted. If You institute patent litigation against any entity (including a

+cross-claim or counterclaim in a lawsuit) alleging that the Work or a

+Contribution incorporated within the Work constitutes direct or contributory

+patent infringement, then any patent licenses granted to You under this License

+for that Work shall terminate as of the date such litigation is filed.

+## 4. Redistribution

+You may reproduce and distribute copies of the Work or Derivative Works thereof

+in any medium, with or without modifications, and in Source or Object form,

+provided that You meet the following conditions:

+* **(a)** You must give any other recipients of the Work or Derivative Works a copy of

+this License; and

+* **(b)** You must cause any modified files to carry prominent notices stating that You

+changed the files; and

+* **\(c)** You must retain, in the Source form of any Derivative Works that You distribute,

+all copyright, patent, trademark, and attribution notices from the Source form

+of the Work, excluding those notices that do not pertain to any part of the

+Derivative Works; and

+* **(d)** If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

+You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

+## 5. Submission of Contributions

+Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

+## 6. Trademarks

+This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

+## 7. Disclaimer of Warranty

+Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

+## 8. Limitation of Liability

+In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

+## 9. Accepting Warranty or Additional Liability

+While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

+_END OF TERMS AND CONDITIONS_

+## APPENDIX: How to apply the Apache License to your work

+To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets `[]` replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same “printed page” as the copyright notice for easier identification within third-party archives.

+{{% code file="apache-notice.txt" download="apache-notice.txt" %}}

+```

+Copyright [yyyy] [name of copyright owner]

+Licensed under the Apache License, Version 2.0 (the "License");

+you may not use this file except in compliance with the License.

+You may obtain a copy of the License at

+  http://www.apache.org/licenses/LICENSE-2.0

+Unless required by applicable law or agreed to in writing, software

+distributed under the License is distributed on an "AS IS" BASIS,

+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

+See the License for the specific language governing permissions and

+limitations under the License.

+```

+{{% /code %}}

--- /dev/null

+++ b/content/about/roadmap.md

@@ -1,0 +1,51 @@

+---

+title: Roadmap

+linktitle: Roadmap

+description: Take a look at what's in the pipeline for future versions of the Hugo project.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [about hugo]

+#tags: [about,contribute,roadmap]

+menu:

+  docs:

+    parent: "about"

+    weight: 50

+weight: 50

+sections_weight: 50

+draft: false

+aliases: [/meta/roadmap]

+toc: false

+---

+To track Hugo's progress, see our [GitHub Milestones][milestones].

+In no particular order, here are some other features currently being worked on:

+* Even easier deployment to S3, SSH, GitHub, rsync. Give the [hosting and deployment][] section a shot.

+* Import from other website systems. There are already [existing migration tools][migrate], but they don’t cover all major platforms.

+* An interactive web-based editor (See the [related forum thread][])

+* Additional [themes][], which are always ongoing and [contributions are welcome][themescontrib]!

+* Dynamic image resizing via shortcodes ({{< gh 1014 >}})

+* Native support for additional content formats (AsciiDoc {{< gh 1435>}}, reST {{< gh 1436 >}})

+* And, last but not least, [***your*** best ideas!][]

+## Contributions Welcome

+Feel free to [contribute to Hugo's development][devcontribute], [improve Hugo's documentation][doccontribute], or [open a new issue][newissue] if you have an idea for a new feature.

+[#98]: https://github.com/gohugoio/hugo/issues/98

+[#1014]: https://github.com/gohugoio/hugo/issues/1014

+[#1435]: https://github.com/gohugoio/hugo/issues/1435

+[#1436]: https://github.com/gohugoio/hugo/issues/1436

+[devcontribute]: /contribute/development/

+[doccontribute]: /contribute/documentation/

+[hosting and deployment]: /hosting-and-deployment/

+[migrate]: /tools/migrations/

+[milestones]: https://github.com/gohugoio/hugo/milestone/14

+[newissue]: https://github.com/gohugoio/hugo/issues/

+[related forum thread]: https://disourse.gohugo.io/t/web-based-editor/155

+[themes]: /themes/

+[themescontrib]: /contribute/themes/

+[tutorials]: /tutorials

+[***your*** best ideas!]: /contribute/

--- /dev/null

+++ b/content/about/what-is-hugo.md

@@ -1,0 +1,69 @@

+---

+title: What is Hugo

+linktitle: What is Hugo

+description: Hugo is a fast and modern static site generator written in Go, and designed to make website creation fun again.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+layout: single

+menu:

+  main:

+    parent: "about"

+    weight: 10

+weight: 10

+sections_weight: 10

+draft: false

+aliases: [/overview/introduction/,/about/why-i-built-hugo/]

+toc: true

+---

+Hugo is a general-purpose website framework. Technically speaking, Hugo is a [static site generator][]. Unlike systems that dynamically build a page with each visitor request, Hugo builds pages when you create or update your content. Since websites are viewed far more often than they are edited, Hugo is designed to provide an optimal viewing experience for your website's end users and an ideal writing experience for website authors.

+Websites built with Hugo are extremely fast and secure. Hugo sites can be hosted anywhere, including [Netlify][], [Heroku][], [GoDaddy][], [DreamHost][], [GitHub Pages][], [Surge][], [Aerobatic][], [Firebase][], [Google Cloud Storage][], [Amazon S3][], [Rackspace][], [Azure][], and [CloudFront][] and work well with CDNs. Hugo sites run without the need for a database or dependencies on expensive runtimes like Ruby, Python, or PHP.

+We think of Hugo as the ideal website creation tool with nearly instant build times, able to rebuild whenever a change is made.

+## How Fast is Hugo?

+{{< youtube "CdiDYZ51a2o" >}}

+## What Does Hugo Do?

+In technical terms, Hugo takes a source directory of files and templates and uses these as input to create a complete website.

+## Who Should Use Hugo?

+Hugo is for people that prefer writing in a text editor over a browser.

+Hugo is for people who want to hand code their own website without worrying about setting up complicated runtimes, dependencies and databases.

+Hugo is for people building a blog, a company site, a portfolio site, documentation, a single landing page, or a website with thousands of pages.

+[@spf13]: https://twitter.com/@spf13

+[Aerobatic]: https://www.aerobatic.com/

+[Amazon S3]: http://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/

+[Firebase]: https://firebase.google.com/docs/hosting/ "Firebase static hosting"

+[GitHub Pages]: https://pages.github.com/

+[GitLab]: https://about.gitlab.com

+[Go language]: https://golang.org/

+[GoDaddy]: https://www.godaddy.com/ "Godaddy.com Hosting"

+[Google Cloud Storage]: http://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

+[static site generator]: /about/benefits/

+[Rackspace]: https://www.rackspace.com/cloud/files

+[static site generator]: /about/benefits/

+[Surge]: https://surge.sh

--- /dev/null

+++ b/content/commands/_index.md

@@ -1,0 +1,22 @@

+---

+title: Command Line Reference

+linktitle: CLI Overview

+description: Comprehensive list of Hugo templating functions, including basic and advanced usage examples.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [commands]

+#tags: [cli,command line]

+menu:

+  docs:

+    parent: "commands"

+    weight: 1

+weight: 01	#rem

+draft: false

+aliases: [/cli/]

+---

+The following list contains auto-generated and up-to-date (thanks to [Cobra][]) documentation for all the CLI commands in Hugo.

+[Cobra]: https://github.com/spf13/cobra

--- a/content/commands/hugo.md

+++ b/content/commands/hugo.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo"

 slug: hugo

 url: /commands/hugo/

@@ -74,7 +74,7 @@

 * [hugo list](/commands/hugo_list/)	 - Listing out various types of content

 * [hugo new](/commands/hugo_new/)	 - Create new content for your site

 * [hugo server](/commands/hugo_server/)	 - A high performance webserver

-* [hugo undraft](/commands/hugo_undraft/)	 - Undraft changes the content's draft status from 'True' to 'False'

+* [hugo undraft](/commands/hugo_undraft/)	 - Undraft resets the content's draft status

 * [hugo version](/commands/hugo_version/)	 - Print the version number of Hugo

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_benchmark.md

+++ b/content/commands/hugo_benchmark.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo benchmark"

 slug: hugo_benchmark

 url: /commands/hugo_benchmark/

@@ -69,4 +69,4 @@

 ### SEE ALSO

 * [hugo](/commands/hugo/)	 - hugo builds your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_check.md

+++ b/content/commands/hugo_check.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo check"

 slug: hugo_check

 url: /commands/hugo_check/

@@ -34,4 +34,4 @@

 * [hugo](/commands/hugo/)	 - hugo builds your site

 * [hugo check ulimit](/commands/hugo_check_ulimit/)	 - Check system ulimit settings

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_check_ulimit.md

+++ b/content/commands/hugo_check_ulimit.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo check ulimit"

 slug: hugo_check_ulimit

 url: /commands/hugo_check_ulimit/

@@ -38,4 +38,4 @@

 ### SEE ALSO

 * [hugo check](/commands/hugo_check/)	 - Contains some verification checks

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_config.md

+++ b/content/commands/hugo_config.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo config"

 slug: hugo_config

 url: /commands/hugo_config/

@@ -37,4 +37,4 @@

 ### SEE ALSO

 * [hugo](/commands/hugo/)	 - hugo builds your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_convert.md

+++ b/content/commands/hugo_convert.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo convert"

 slug: hugo_convert

 url: /commands/hugo_convert/

@@ -41,4 +41,4 @@

 * [hugo convert toTOML](/commands/hugo_convert_totoml/)	 - Convert front matter to TOML

 * [hugo convert toYAML](/commands/hugo_convert_toyaml/)	 - Convert front matter to YAML

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_convert_toJSON.md

+++ b/content/commands/hugo_convert_toJSON.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo convert toJSON"

 slug: hugo_convert_toJSON

 url: /commands/hugo_convert_tojson/

@@ -41,4 +41,4 @@

 ### SEE ALSO

 * [hugo convert](/commands/hugo_convert/)	 - Convert your content to different formats

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_convert_toTOML.md

+++ b/content/commands/hugo_convert_toTOML.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo convert toTOML"

 slug: hugo_convert_toTOML

 url: /commands/hugo_convert_totoml/

@@ -41,4 +41,4 @@

 ### SEE ALSO

 * [hugo convert](/commands/hugo_convert/)	 - Convert your content to different formats

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_convert_toYAML.md

+++ b/content/commands/hugo_convert_toYAML.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo convert toYAML"

 slug: hugo_convert_toYAML

 url: /commands/hugo_convert_toyaml/

@@ -41,4 +41,4 @@

 ### SEE ALSO

 * [hugo convert](/commands/hugo_convert/)	 - Convert your content to different formats

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_env.md

+++ b/content/commands/hugo_env.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo env"

 slug: hugo_env

 url: /commands/hugo_env/

@@ -37,4 +37,4 @@

 ### SEE ALSO

 * [hugo](/commands/hugo/)	 - hugo builds your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_gen.md

+++ b/content/commands/hugo_gen.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo gen"

 slug: hugo_gen

 url: /commands/hugo_gen/

@@ -36,4 +36,4 @@

 * [hugo gen doc](/commands/hugo_gen_doc/)	 - Generate Markdown documentation for the Hugo CLI.

 * [hugo gen man](/commands/hugo_gen_man/)	 - Generate man pages for the Hugo CLI

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_gen_autocomplete.md

+++ b/content/commands/hugo_gen_autocomplete.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo gen autocomplete"

 slug: hugo_gen_autocomplete

 url: /commands/hugo_gen_autocomplete/

@@ -55,4 +55,4 @@

 ### SEE ALSO

 * [hugo gen](/commands/hugo_gen/)	 - A collection of several useful generators.

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_gen_doc.md

+++ b/content/commands/hugo_gen_doc.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo gen doc"

 slug: hugo_gen_doc

 url: /commands/hugo_gen_doc/

@@ -44,4 +44,4 @@

 ### SEE ALSO

 * [hugo gen](/commands/hugo_gen/)	 - A collection of several useful generators.

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_gen_man.md

+++ b/content/commands/hugo_gen_man.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo gen man"

 slug: hugo_gen_man

 url: /commands/hugo_gen_man/

@@ -40,4 +40,4 @@

 ### SEE ALSO

 * [hugo gen](/commands/hugo_gen/)	 - A collection of several useful generators.

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_import.md

+++ b/content/commands/hugo_import.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo import"

 slug: hugo_import

 url: /commands/hugo_import/

@@ -36,4 +36,4 @@

 * [hugo](/commands/hugo/)	 - hugo builds your site

 * [hugo import jekyll](/commands/hugo_import_jekyll/)	 - hugo import from Jekyll

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_import_jekyll.md

+++ b/content/commands/hugo_import_jekyll.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo import jekyll"

 slug: hugo_import_jekyll

 url: /commands/hugo_import_jekyll/

@@ -40,4 +40,4 @@

 ### SEE ALSO

 * [hugo import](/commands/hugo_import/)	 - Import your site from others.

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_list.md

+++ b/content/commands/hugo_list.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo list"

 slug: hugo_list

 url: /commands/hugo_list/

@@ -39,4 +39,4 @@

 * [hugo list expired](/commands/hugo_list_expired/)	 - List all posts already expired

 * [hugo list future](/commands/hugo_list_future/)	 - List all posts dated in the future

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_list_drafts.md

+++ b/content/commands/hugo_list_drafts.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo list drafts"

 slug: hugo_list_drafts

 url: /commands/hugo_list_drafts/

@@ -38,4 +38,4 @@

 ### SEE ALSO

 * [hugo list](/commands/hugo_list/)	 - Listing out various types of content

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_list_expired.md

+++ b/content/commands/hugo_list_expired.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo list expired"

 slug: hugo_list_expired

 url: /commands/hugo_list_expired/

@@ -39,4 +39,4 @@

 ### SEE ALSO

 * [hugo list](/commands/hugo_list/)	 - Listing out various types of content

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_list_future.md

+++ b/content/commands/hugo_list_future.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo list future"

 slug: hugo_list_future

 url: /commands/hugo_list_future/

@@ -39,4 +39,4 @@

 ### SEE ALSO

 * [hugo list](/commands/hugo_list/)	 - Listing out various types of content

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_new.md

+++ b/content/commands/hugo_new.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo new"

 slug: hugo_new

 url: /commands/hugo_new/

@@ -47,4 +47,4 @@

 * [hugo new site](/commands/hugo_new_site/)	 - Create a new site (skeleton)

 * [hugo new theme](/commands/hugo_new_theme/)	 - Create a new theme

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_new_site.md

+++ b/content/commands/hugo_new_site.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo new site"

 slug: hugo_new_site

 url: /commands/hugo_new_site/

@@ -42,4 +42,4 @@

 ### SEE ALSO

 * [hugo new](/commands/hugo_new/)	 - Create new content for your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_new_theme.md

+++ b/content/commands/hugo_new_theme.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo new theme"

 slug: hugo_new_theme

 url: /commands/hugo_new_theme/

@@ -41,4 +41,4 @@

 ### SEE ALSO

 * [hugo new](/commands/hugo_new/)	 - Create new content for your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_server.md

+++ b/content/commands/hugo_server.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo server"

 slug: hugo_server

 url: /commands/hugo_server/

@@ -55,6 +55,7 @@

   -l, --layoutDir string           filesystem path to layout directory

       --meminterval string         interval to poll memory usage (requires --memstats), valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". (default "100ms")

       --memstats string            log memory usage to this file

+      --navigateToChanged          navigate to changed content file on live browser reload

       --noChmod                    don't sync permission mode of files

       --noTimes                    don't sync modification time of files

       --pluralizeListTitles        pluralize titles in lists using inflect (default true)

@@ -83,4 +84,4 @@

 ### SEE ALSO

 * [hugo](/commands/hugo/)	 - hugo builds your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_undraft.md

+++ b/content/commands/hugo_undraft.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo undraft"

 slug: hugo_undraft

 url: /commands/hugo_undraft/

@@ -6,12 +6,12 @@

---

 ## hugo undraft

-Undraft changes the content's draft status from 'True' to 'False'

+Undraft resets the content's draft status

 ### Synopsis

-Undraft changes the content's draft status from 'True' to 'False'

+Undraft resets the content's draft status

 and updates the date to the current date and time.

 If the content's draft status is 'False', nothing is done.

@@ -39,4 +39,4 @@

 ### SEE ALSO

 * [hugo](/commands/hugo/)	 - hugo builds your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/commands/hugo_version.md

+++ b/content/commands/hugo_version.md

@@ -1,5 +1,5 @@

---

-date: 2017-06-29T08:42:09+02:00

+date: 2017-07-16T23:23:14+02:00

 title: "hugo version"

 slug: hugo_version

 url: /commands/hugo_version/

@@ -37,4 +37,4 @@

 ### SEE ALSO

 * [hugo](/commands/hugo/)	 - hugo builds your site

-###### Auto generated by spf13/cobra on 29-Jun-2017

+###### Auto generated by spf13/cobra on 16-Jul-2017

--- a/content/community/contributing.md

+++ /dev/null

@@ -1,111 +1,0 @@

----

-aliases:

-- /doc/contributing/

-- /meta/contributing/

-lastmod: 2015-02-12

-date: 2013-07-01

-menu:

-  main:

-    parent: community

-next: /tutorials/automated-deployments

-prev: /community/mailing-list

-title: Contributing to Hugo

-weight: 30

----

-All contributions to Hugo are welcome. Whether you want to scratch an itch or simply contribute to the project, feel free to pick something from the [roadmap]({{< relref "meta/roadmap.md" >}}) or contact the dev team via the [Forums](https://discourse.gohugo.io/) or [Gitter](https://gitter.im/gohugoio/hugo) about what may make sense to do next.

-You should fork the project and make your changes.  *We encourage pull requests to discuss code changes.*

-When you're ready to create a pull request, be sure to:

-  * Have test cases for the new code.  If you have questions about how to do it, please ask in your pull request.

-  * Run `go fmt`.

-  * Squash your commits into a single commit.  `git rebase -i`.  It's okay to force update your pull request.

-  * Run `make check` and ensure it succeeds.  [Travis CI](https://travis-ci.org/gohugoio/hugo) and [Appveyor](https://ci.appveyor.com/project/gohugoio/hugo) will runs these checks and fail the build if `make check` fails.

-## Contribution Overview

-We wrote a [detailed guide]({{< relref "tutorials/how-to-contribute-to-hugo.md" >}}) for newcomers that guides you step by step to your first contribution. If you are more experienced, follow the guide below.

-# Building from source

-## Vendored Dependencies

-Hugo uses [govendor][] to vendor dependencies, but we don't commit the vendored packages themselves to the Hugo git repository.

-Therefore, a simple `go get` is not supported since `go get` is not vendor-aware.

-You **must use govendor** to fetch Hugo's dependencies.

-## Fetch the Sources

-    go get github.com/kardianos/govendor

-    govendor get github.com/gohugoio/hugo

-## Running Hugo

-    cd $HOME/go/src/github.com/gohugoio/hugo

-    go run main.go

-## Building Hugo

-    cd $HOME/go/src/github.com/gohugoio/hugo

-    make build

-    # or to install to $HOME/go/bin:

-    make install

-# Showcase additions

-You got your new website running and it's powered by Hugo? Great. You can add your website with a few steps to the [showcase](/showcase/).

-First, make sure that you created a [fork](https://help.github.com/articles/fork-a-repo/) of the [`hugoDocs`](https://github.com/gohugoio/hugodocs) repository on GitHub and cloned your fork on your local computer. **Next, create a separate branch for your additions**:

-```

-# You can choose a different descriptive branch name if you like

-git checkout -b showcase-addition

-```

-Let's create a new document that contains some metadata of your homepage. Replace `example` in the following examples with something unique like the name of your website. Inside the terminal enter the following commands:

-```

-cd docs

-hugo new showcase/example.md

-```

-You should find the new file at `content/showcase/example.md`. Open it in an editor. The file should contain a frontmatter with predefined variables like below:

-```

----

-date: 2016-02-12T21:01:18+01:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://spf13.com/

-sourceLink: https://github.com/spf13/spf13.com

-tags:

-- personal

-- blog

-thumbnail: /img/spf13-tn.jpg

-title: example

----

-```

-Add at least values for `sitelink`, `title`,  `description` and a path for `thumbnail`.

-Furthermore, we need to create the thumbnail of your website. **It's important that the thumbnail has the required dimensions of 600px by 400px.** Give your thumbnail a name like `example-tn.png`. Save it under `static/img/`.

-Check a last time that everything works as expected. Start Hugo's built-in server in order to inspect your local copy of the showcase in the browser:

-    hugo server

-If everything looks fine, we are ready to commit your additions. For the sake of best practices, please make sure that your commit follows our [code contribution guideline](https://github.com/gohugoio/hugo#code-contribution-guideline).

-    git commit -m"Add example.com to the showcase"

-Last but not least, we're ready to create a [pull request](https://github.com/gohugoio/hugoDocs/compare).

-Don't forget to accept the contributor license agreement. Click on the yellow badge in the automatically added comment in the pull request.

-[govendor]: https://github.com/kardianos/govendor

--- a/content/community/mailing-list.md

+++ /dev/null

@@ -1,51 +1,0 @@

----

-lastmod: 2015-05-25

-date: 2013-07-01

-menu:

-  main:

-    parent: community

-next: /community/contributing

-prev: /extras/urls

-title: Mailing List

-weight: 10

----

-## Discussion Forum

-Hugo has its own [discussion forum](https://discourse.gohugo.io/) powered by [Discourse](http://www.discourse.org/).

-Please use this for all discussions, questions, etc.

-### Twitter

-Get the latest bite-sized news and themes from the Hugo community on Twitter by following [@gohugoio](http://twitter.com/gohugoio).

-## Mailing List

-Hugo has two mailing lists:

-### Announcements

-Very low traffic. Only releases will be emailed here.

-https://groups.google.com/forum/#!forum/hugo-announce

-### Discussion (Archive)

-**This has been replaced with the [Hugo discussion forum](https://discourse.gohugo.io/).**

-It is available for archival purposes.

-https://groups.google.com/forum/#!forum/hugo-discuss

-## Other Resources

-### GoNuts

-For general Go questions or discussion please refer to the Go mailing list.

-https://groups.google.com/forum/#!forum/golang-nuts

-### GitHub Issues

-https://github.com/gohugoio/hugo/issues

--- a/content/community/press.md

+++ /dev/null

@@ -1,141 +1,0 @@

----

-lastmod: 2017-03-02

-date: 2014-03-24T20:00:00Z

-linktitle: Press

-notoc: true

-title: Press, Blogs and Media Coverage

-weight: 20

----

-### Help keep this list up to date

-Know of a post, article or tutorial on Hugo? [Add it to this list](https://github.com/gohugoio/hugo/edit/master/docs/content/community/press.md).

-## Press and Articles

-Hugo has been featured in the following Blog Posts, Press and Media.

-| Title                                                                                                                                                                                                    | Author                                                                  | Date                   |

-| ------                                                                                                                                                                                                   | ------                                                                  | -----:                 |

-| [Build, Test, And Deploy Statically Generated Websites With Hugo & CircleCI](https://circleci.com/blog/build-test-deploy-hugo-sites/)| Ricardo N Feliciano | 2017-05-31 |

-| [Hugo Easy Gallery - Automagical PhotoSwipe image gallery with a one-line shortcode](https://www.liwen.id.au/heg/)| Li-Wen Yip | 2017-03-25 |

-| [Hugo Tutorial: How to Build & Host a (Very Fast) Static E-Commerce Site](https://snipcart.com/blog/hugo-tutorial-static-site-ecommerce) | Snipcart | 2017-03-12 |

-| [Automagical image gallery in Hugo with PhotoSwipe and jQuery](https://www.liwen.id.au/photoswipe/)| Li-Wen Yip | 2017-03-04 |

-| [Adding Isso Comments to Hugo](https://stiobhart.net/2017-02-24-isso-comments/) | Stíobhart Matulevicz | 2017-02-24 |

-| [Zero to HTTP/2 with AWS and Hugo](https://habd.as/zero-to-http-2-aws-hugo/)  | Josh Habdas | 2017-02-16 |

-| [How to Password Protect a Hugo Site](https://www.aerobatic.com/blog/password-protect-a-hugo-site/) | Aerobatic | 2017-02-19 |

-| [Switching from Wordpress to Hugo](http://schnuddelhuddel.de/switching-from-wordpress-to-hugo/) | Mario Martelli | 2017-02-19 | ]

-| [Deploy a Hugo site to Aerobatic with CircleCI ](https://www.aerobatic.com/blog/hugo-github-circleci/) | Aerobatic | 2017-02-14 |

-| [NPM scripts for building and deploying Hugo site](https://www.aerobatic.com/blog/hugo-npm-buildtool-setup/) | Aerobatic | 2017-02-12 |

-| [Getting started with Hugo and the plain-blog theme, on NearlyFreeSpeech.Net](https://www.penwatch.net/cms/get_started_plain_blog/) | Li-aung “Lewis” Yip | 2017-02-12 |

-| [Build a Hugo site using Cloud9 IDE and host on App Engine](https://loyall.ch/lab/2017/01/build-a-static-website-with-cloud9-hugo-and-app-engine/)| Pascal Aubort | 2017-02-05 |

-| [Hugo Continuous Deployment with Bitbucket Pipelines and Aerobatic](https://www.aerobatic.com/blog/hugo-bitbucket-pipelines/) | Aerobatic | 2017-02-04 |

-| [How to use Firebase to host a Hugo site](https://www.m0d3rnc0ad.com/post/static-site-firebase/) | Andrew Cuga | 2017-02-04 |

-| [A publishing workflow for teams using static site generators](https://www.keybits.net/post/publishing-workflow-for-teams-using-static-site-generators/) | Tom Atkins | 2017-01-02 |

-| [How To Dynamically Use Google Fonts In A Hugo Website](https://stoned.io/web-development/hugo/How-To-Dynamically-Use-Google-Fonts-In-A-Hugo-Website/) | Hash Borgir | 2016-10-27 |

-| [Embedding Facebook In A Hugo Template](https://stoned.io/web-development/hugo/Embedding-Facebook-In-A-Hugo-Template/) | Hash Borgir | 2016-10-22 |

-| [通过 Gitlab-cl 将 Hugo blog 自动部署至 GitHub](https://zetaoyang.github.io/post/2016/10/17/gitlab-cl.html) <small>(Chinese, Continious integration)</small> | Zetao Yang | 2016-10-17 |

-| [A Step-by-Step Guide: Hugo on Netlify](https://www.netlify.com/blog/2016/09/21/a-step-by-step-guide-hugo-on-netlify/) | Eli Williamson | 2016-09-21 |

-| [Building our site: From Django & Wordpress to a static generator (Part I)](https://tryolabs.com/blog/2016/09/20/building-our-site-django-wordpress-to-static-part-i/) | Alan Descoins | 2016-09-20 |

-| [Webseitenmaschine - Statische Websites mit Hugo erzeugen](http://www.heise.de/ct/ausgabe/2016-12-Statische-Websites-mit-Hugo-erzeugen-3211704.html) <small>(German, $)</small> | Christian Helmbold | 2016-05-27 |

-| [Cómo hacer sitios web estáticos con Hugo y Go - Platzi](https://www.youtube.com/watch?v=qaXXpdiCHXE) <small>(Video tutorial)</small> | Verónica López  | 2016-04-06 |

-| [CDNOverview: A CDN comparison site made with Hugo](https://www.cloakfusion.com/cdnoverview-cdn-comparison-site-made-hugo/) | Thijs de Zoete | 2016-02-23 |

-| [Hugo: A Modern WebSite Engine That Just Works](https://github.com/shekhargulati/52-technologies-in-2016/blob/master/07-hugo/README.md) | Shekhar Gulati | 2016-02-14 |

-| [Minify Hugo Generated HTML](http://ratson.name/blog/minify-hugo-generated-html/) | Ratson | 2016-02-02 |

-| [<span lang="ja">HugoのデプロイをWerckerからCircle CIに変更した</span> - log](http://log.deprode.net/logs/2016-01-17/) | Deprode | 2016-01-17 |

-| [Static site generators: el futuro de las webs estáticas<br>(Hugo, Jekyll, Flask y otros)](http://sitelabs.es/static-site-generators-futuro-las-webs-estaticas/) | Eneko Sarasola | 2016-01-09 |

-| [Writing a Lambda Function for Hugo](https://blog.jolexa.net/post/writing-a-lambda-function-for-hugo/) | Jeremy Olexa | 2016-01-01 |

-| [Ein Blog mit Hugo erstellen - Tutorial](http://privat.albicker.org/tags/hugo.html) <small>(Deutsch/German)</small> | Bernhard Albicker | 2015-12-30 |

-| [How to host Hugo static website generator on AWS Lambda](http://bezdelev.com/post/hugo-aws-lambda-static-website/) | Ilya Bezdelev | 2015-12-15 |

-| [Migrating from Pelican to Hugo](http://www.softinio.com/post/migrating-from-pelican-to-hugo/) | Salar Rahmanian | 2015-11-29 |

-| [Static Website Generators Reviewed: Jekyll, Middleman, Roots, Hugo](http://www.smashingmagazine.com/2015/11/static-website-generators-jekyll-middleman-roots-hugo-review/) | Mathias Biilmann Christensen | 2015-11-16 |

-| [How To Deploy a Hugo Site to Production with Git Hooks on Ubuntu 14.04](https://www.digitalocean.com/community/tutorials/how-to-deploy-a-hugo-site-to-production-with-git-hooks-on-ubuntu-14-04)        | Justin Ellingwood | 2015-11-12 |

-| [How To Install and Use Hugo, a Static Site Generator, on Ubuntu 14.04](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-hugo-a-static-site-generator-on-ubuntu-14-04) | Justin Ellingwood | 2015-11-09 |

-| [Switching from Wordpress to Hugo](http://justinfx.com/2015/11/08/switching-from-wordpress-to-hugo/) | Justin Israel | 2015-11-08 |

-| [Hands-on Experience with Hugo as a Static Site Generator](http://usersnap.com/blog/hands-on-experience-with-hugo-static-site-generator/) | Thomas Peham | 2015 -10-15 |

-| [Statische Webseites mit Hugo erstellen/Vortrag mit Foliensatz (deutsch)](http://sfd.koelnerlinuxtreffen.de/2015/HaraldWeidner/) | Harald Weidner | 2015-09-19 |

-| [Moving from WordPress to Hugo](http://abhipandey.com/2015/09/moving-to-hugo/) | Abhishek Pandey | 2015-09-15 |

-| [<span lang="zh-CN">通过webhook将Hugo自动部署至GitHub Pages和GitCafe Pages</span> <small>(Automated&nbsp;deployment)</small>](http://blog.coderzh.com/2015/09/13/use-webhook-automated-deploy-hugo/) | CoderZh | 2015-09-13 |

-| [<span lang="zh-CN">使用hugo搭建个人博客站点</span> <small>(Using Hugo to build a personal blog site)</small>](http://blog.coderzh.com/2015/08/29/hugo/) | CoderZh | 2015-08-29 |

-| [Good-Bye Wordpress, Hello Hugo!](http://blog.arminhanisch.de/2015/08/blog-migration-zu-hugo/) <small>(German)</small> | Armin Hanisch | 2015-08-18 |

-| [Générer votre site web statique avec Hugo <small>(Generate your static site with Hugo)<small>](http://www.linux-pratique.com/?p=191) | Benoît Benedetti | 2015-06-26 |

-| [<span lang="ja">Hugo向けの新しいテーマを作った</span> <small>(I created a new theme for Hugo)<small>](https://yet.unresolved.xyz/blog/2016/10/03/how-to-make-of-hugo-theme/) | Daisuke Tsuji | 2015-06-20 |

-| [Hugo - Gerando um site com conteúdo estático. (Portuguese Brazil)](http://blog.ffrizzo.com/posts/hugo/) | Fabiano Frizzo | 2015-06-02 |

-| [An Introduction to Static Site Generators](http://davidwalsh.name/introduction-static-site-generators) | Eduardo Bouças | 2015-05-20 |

-| [Hugo Still Rules](http://cheekycoder.com/2015/05/hugo-still-rules/) | Cheeky Coder | 2015-05-18 |

-| [hugo - Static Site Generator](http://gscacco.github.io/post/hugo/) | G Scaccoio | 2015-05-04 |

-| [<span lang="ja">WindowsでHugoを使う</span>](http://ureta.net/2015/05/hugo-on-windows/) | <span lang="ja">うれ太郎</span> | 2015-05-01 |

-| [<span lang="ja">Hugoのshortcodesを用いてサイトにスライドなどを埋め込む</span>](http://blog.yucchiy.com/2015/04/29/hugo-shortcode/) | Yucchiy | 2015-04-29 |

-| [<span lang="ja">HugoとCircleCIでGitHub PagesにBlogを公開してみたら超簡単だった</span>](http://hori-ryota.github.io/blog/create-blog-with-hugo-and-circleci/) | Hori Ryota | 2015-04-17 |

-| [10 Best Static Site Generators](http://beebom.com/2015/04/best-static-site-generators) | Aniruddha Mysore | 2015-04-06 |

-| [Goodbye WordPress; Hello Hugo](http://willwarren.com/2015/04/05/goodbye-wordpress-hello-hugo/) | Will Warren | 2015-04-05 |

-| [Static Websites with Hugo on Google Cloud Storage](http://www.moxie.io/post/static-websites-with-hugo-on-google-cloud-storage/) | Moxie Input/Output | 2015-04-02 |

-| [De nuevo iniciando un blog](https://alvarolizama.net/) | Alvaro Lizama | 2015-03-29 |

-| [We moved our blog from Posthaven to Hugo after only three posts. Why?](http://blog.hypriot.com/post/moved-from-posthaven-to-hugo/) | Hypriot | 2015-03-27 |

-| [Top Static Site Generators in 2015](http://superdevresources.com/static-site-generators-2015/) | Kanishk Kunal | 2015-03-12 |

-| [Moving to Hugo](http://abiosoft.com/moving-to-hugo/) | Abiola Ibrahim | 2015-03-08 |

-| [Migrating a blog (yes, this one!) from Wordpress to Hugo](http://justindunham.net/migrating-from-wordpress-to-hugo/) | Justin Dunham  |  2015-02-13 |

-| [<span lang="ja">blogをoctopressからHugoに乗り換えたメモ</span>](http://blog.jigyakkuma.org/2015/02/11/hugo/) | jigyakkuma | 2015-02-11 |

-| [<span lang="ja">Hugoでブログをつくった</span>](http://porgy13.github.io/post/new-hugo-blog/) | porgy13 | 2015-02-07 |

-| [<span lang="ja">Hugoにブログを移行した</span>](http://keichi.net/post/first/) | Keichi Takahashi | 2015-02-04 |

-| [<span lang="zh-CN">Hugo静态网站生成器中文教程</span>](http://nanshu.wang/post/2015-01-31/) | Nanshu Wang | 2015-01-31 |

-| [<span lang="ja">Hugo + GitHub Pages + Wercker CI = ¥0（無料）<br>でコマンド 1 発（自動化）でサイト<br>・ブログを公開・運営・分析・収益化</span>](http://qiita.com/yoheimuta/items/8a619cac356bed89a4c9) | Yohei Yoshimuta | 2015-01-31 |

-| [Running Hugo websites on anynines](http://blog.anynines.com/running-hugo-websites-on-anynines/) | Julian Weber | 2015-01-30 |

-| [MiddlemanからHugoへ移行した](http://re-dzine.net/2015/01/hugo/) | Haruki Konishi | 2015-01-21 |

-| [WordPress から Hugo に乗り換えました](http://rakuishi.com/archives/wordpress-to-hugo/)  | rakuishi | 2015-01-20 |

-| [HUGOを使ってサイトを立ち上げる方法](http://qiita.com/syui/items/869538099551f24acbbf) | Syui | 2015-01-17 |

-| [<span lang="ja">Jekyllが許されるのは小学生までだよね</span>](http://t32k.me/mol/log/hugo/) | Ishimoto Koji | 2015-01-16 |

-| [Getting started with Hugo](http://anthonyfok.org/post/getting-started-with-hugo/) | Anthony Fok | 2015-01-12 |

-| [<span lang="zh-CN">把这个博客静态化了</span> <small>(Migrate to Hugo)</small>](http://lich-eng.com/2015/01/03/migrate-to-hugo/)| Li Cheng | 2015-01-03 |

-| [Porting my blog with Hugo](http://blog.srackham.com/posts/porting-my-blog-with-hugo/) | Stuart Rackham | 2014-12-30 |

-| [Hugoを使ってみたときのメモ](http://machortz.github.io/posts/usinghugo/) | Machortz | 2014-12-29 |

-| [OctopressからHugoへ移行した](http://deeeet.com/writing/2014/12/25/hugo/) | Taichi Nakashima | 2014-12-25 |

-| [Migrating to Hugo From Octopress](http://nathanleclaire.com/blog/2014/12/22/migrating-to-hugo-from-octopress/) | Nathan LeClaire | 2014-12-22 |

-| [Dynamic Pages with GoHugo.io](http://cyrillschumacher.com/2014/12/21/dynamic-pages-with-gohugo.io/) | Cyrill Schumacher | 2014-12-21 |

-| [6 Static Blog Generators That Aren’t Jekyll](http://www.sitepoint.com/6-static-blog-generators-arent-jekyll/) | David Turnbull  | 2014-12-08 |

-| [Travel Blogging Setup](http://www.stou.dk/2014/11/travel-blogging-setup/) | Rasmus Stougaard | 2014-11-23 |

-| [Hosting A Hugo Website Behind Nginx](http://www.bigbeeconsultants.co.uk/blog/hosting-hugo-website-behind-nginx) | Rick Beton | 2014-11-20 |

-| [<span lang="zh-CN">使用Hugo搭建免费个人Blog</span> <small>(How to use Hugo)</small>](http://ulricqin.com/post/how-to-use-hugo/) | Ulric Qin <span lang="zh-CN">秦晓辉</span>  | 2014-11-11 |

-| [Built in Speed and Built for Speed by Hugo](http://cheekycoder.com/2014/10/built-for-speed-by-hugo/) | Cheeky Coder | 2014-10-30 |

-| [Hugo para crear sitios web estáticos](http://www.webbizarro.com/noticias/1076/hugo-para-crear-sitios-web-estaticos/) | Web Bizarro | 2014-08-19 |

-| [Going with hugo](http://www.markuseliasson.se/article/going-with-hugo/) | Markus Eliasson  | 2014-08-18 |

-| [Benchmarking Jekyll, Hugo and Wintersmith](http://fredrikloch.me/post/2014-08-12-Jekyll-and-its-alternatives-from-a-site-generation-point-of-view/) | Fredrik Loch | 2014-08-12 |

-| [Goodbye Octopress, Hello Hugo!](http://andreimihu.com/blog/2014/08/11/goodbye-octopress-hello-hugo/) | Andrei Mihu | 2014-08-11 |

-| [Beautiful sites for Open Source projects](http://beautifulopen.com/2014/08/09/hugo/) | Beautiful Open | 2014-08-09 |

-| [Hugo: Beyond the Defaults](http://npf.io/2014/08/hugo-beyond-the-defaults/) | Nate Finch | 2014-08-08 |

-| [First Impressions of Hugo](https://peteraba.com/blog/first-impressions-of-hugo/) | Peter Aba | 2014-06-06 |

-| [New Site Workflow](http://vurt.co.uk/post/new_website/) | Giles Paterson | 2014-08-05 |

-| [How I Learned to Stop Worrying and Love the (Static) Web](http://cognition.ca/post/about-hugo/) | Joshua McKenty | 2014-08-04 |

-| [Hugo - Static Site Generator](http://kenwoo.io/blog/hugo---static-site-generator/) | Kenny Woo | 2014-08-03 |

-| [Hugo Is Friggin' Awesome](http://npf.io/2014/08/hugo-is-awesome/) | Nate Finch | 2014-08-01 |

-| [<span lang="zh-CN">再次搬家</span> <small>(Move from WordPress to Hugo)</small>](http://www.chingli.com/misc/move-from-wordpress-to-hugo/) | <span lang="zh-CN">青砾</span> (chingli) | 2014-07-12 |

-| [Embedding Gists in Hugo](http://danmux.com/posts/embedded_gists/) | Dan Mull | 2014-07-05 |

-| [An Introduction To Hugo](http://www.cirrushosting.com/web-hosting-blog/an-introduction-to-hugo/) | Dan Silber | 2014-07-01 |

-| [Moving to Hugo](http://danmux.com/posts/hugo_based_blog/) | Dan Mull | 2014-05-29 |

-| [<span lang="zh-CN">开源之静态站点生成器排行榜</span><br><small>(Leaderboard of open-source static website generators)</small>](http://code.csdn.net/news/2819909) | CSDN.net | 2014-05-23 |

-| [Finally, a satisfying and effective blog setup](http://michaelwhatcott.com/now-powered-by-hugo/) | Michael Whatcott | 2014-05-20 |

-| [Hugo from scratch](http://zackofalltrades.com/notes/2014/05/hugo-from-scratch/) | Zack Williams | 2014-05-18 |

-| [Why I switched away from Jekyll](http://www.jakejanuzelli.com/why-I-switched-away-from-jekyll/) | Jake Januzelli | 2014-05-10 |

-| [Welcome our new blog](http://blog.ninya.io/posts/welcome-our-new-blog/) | Ninya.io | 2014-04-11 |

-| [Mission Not Accomplished](http://johnsto.co.uk/blog/mission-not-accomplished/) | Dave Johnston | 2014-04-03 |

-| [Hugo - A Static Site Builder in Go](http://deepfriedcode.com/post/hugo/) | Deep Fried Code | 2014-03-30 |

-| [Adventures in Angular Podcast](http://devchat.tv/adventures-in-angular/003-aia-gdes) | Matias Niemela  | 2014-03-28 |

-| [Hugo](http://bra.am/post/hugo/) | bra.am | 2014-03-23 |

-| [Converting Blogger To Markdown](http://trishagee.github.io/project/atom-to-hugo/) | Trisha Gee | 2014-03-20 |

-| [Moving to Hugo Static Web Pages](http://tepid.org/tech/hugo-web/) | Tobias Weingartner | 2014-03-16 |

-| [New Blog Engine: Hugo](https://blog.afoolishmanifesto.com/posts/hugo/) | fREW Schmidt | 2014-03-15 |

-| [Hugo + gulp.js = Huggle](http://ktmud.github.io/huggle/en/intro/) ([English](http://ktmud.github.io/huggle/en/intro/), [<span lang="zh-CN">中文</span>](http://ktmud.github.io/huggle/zh/intro/)) | Jesse Yang <span lang="zh-CN">杨建超</span> | 2014-03-08 |

-| [Powered by Hugo](http://kieranhealy.org/blog/archives/2014/02/24/powered-by-hugo/) | Kieran Healy | 2014-02-24 |

-| [<span lang="ja">静的サイトを素早く構築するために<br>GoLangで作られたジェネレータHugo</span>](http://hamasyou.com/blog/2014/02/21/hugo/)| <div lang="ja" style="line-height: 1.1;">Shogo Hamada<br>濱田章吾</div> | 2014-02-21 |

-| [Latest Roundup of Useful Tools For Developers](http://codegeekz.com/latest-roundup-of-useful-tools-for-developers/) | CodeGeekz | 2014-02-13 |

-| [Hugo: Static Site Generator written in Go](http://www.braveterry.com/2014/02/06/hugo-static-site-generator-written-in-go/) | Brave Terry | 2014-02-06 |

-| [10 Useful HTML5 Tools for Web Designers and Developers](http://designdizzy.com/10-useful-html5-tools-for-web-designers-and-developers/) | Design Dizzy | 2014-02-04 |

-| [Hugo – Fast, Flexible Static Site Generator](http://cube3x.com/hugo-fast-flexible-static-site-generator/) | Joby Joseph | 2014-01-18 |

-| [Hugo: A new way to build static website](http://www.w3update.com/opensource/hugo-a-new-way-to-build-static-website.html) | w3update | 2014-01-17 |

-| [Xaprb now uses Hugo](http://xaprb.com/blog/2014/01/15/using-hugo/) | Baron Schwartz | 2014-01-15 |

-| [New jQuery Plugins And Resources That Web Designers Need](http://www.designyourway.net/blog/resources/new-jquery-plugins-and-resources-that-web-designers-need/) | Design Your Way | 2014-01-01 |

-| [On Blog Construction](http://alexla.sh/post/on-blog-construction/) | Alexander Lash | 2013-12-27 |

-| [Hugo](http://onethingwell.org/post/69070926608/hugo) | One Thing Well | 2013-12-05 |

-| [In Praise Of Hugo](http://sound-guru.com/blog/post/hello-world/) | sound-guru.com | 2013-10-19 |

-| [Hosting a blog on S3 and Cloudfront](http://www.danesparza.net/2013/07/hosting-a-blog-on-s3-and-cloudfront/) | Dan Esparza | 2013-07-24 |

--- /dev/null

+++ b/content/content-management/_index.md

@@ -1,0 +1,20 @@

+---

+title: Content Management

+linktitle: Content Management Overview

+description: Hugo makes managing large static sites easy with support for archetypes, content types, menus, cross references, summaries, and more.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+menu:

+  docs:

+    parent: "content-management"

+    weight: 1

+#tags: [source, organization]

+categories: [content management]

+weight: 01	#rem

+draft: false

+aliases: [/content/,/content/organization]

+toc: false

+---

+A static site generator needs to extend beyond front matter and a couple templates to be both scalable and *manageable*. Hugo was designed with not only developers in mind, but also content managers and authors.

--- /dev/null

+++ b/content/content-management/archetypes.md

@@ -1,0 +1,208 @@

+---

+title: Archetypes

+linktitle: Archetypes

+description: Archetypes allow you to create new instances of content types and set default parameters from the command line.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [archetypes,generators,metadata,front matter]

+categories: ["content management"]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 70

+  quicklinks:

+weight: 70	#rem

+draft: false

+aliases: [/content/archetypes/]

+toc: true

+---

+{{% note %}}

+This section is outdated, see https://github.com/gohugoio/hugoDocs/issues/11

+{{% /note %}}

+{{% todo %}}

+See above

+{{% /todo %}}

+## What are Archetypes?

+**Archetypes** are content files in the [archetypes directory][] of your project that contain preconfigured [front matter][] for your website's [content types][]. Archetypes facilitate consistent metadata across your website content and allow content authors to quickly generate instances of a content type via the `hugo new` command.

+The `hugo new` generator for archetypes assumes your working directory is the content folder at the root of your project. Hugo is able to infer the appropriate archetype by assuming the content type from the content section passed to the CLI command:

+```bash

+hugo new <content-section>/<file-name.md>

+```

+We can use this pattern to create a new `.md` file in the `posts` section:

+{{% code file="archetype-example.sh" %}}

+```bash

+hugo new posts/my-first-post.md

+```

+{{% /code %}}

+{{% note "Override Content Type in a New File" %}}

+To override the content type Hugo infers from `[content-section]`, add the `--kind` flag to the end of the `hugo new` command.

+{{% /note %}}

+Running this command in a new site that does not have default or custom archetypes will create the following file:

+{{% output file="content/posts/my-first-post.md" %}}

+```toml

++++

+date = "2017-02-01T19:20:04-07:00"

+title = "my first post"

+draft = true

++++

+```

+{{% /output %}}

+{{% note %}}

+In this example, if you do not already have a `content/posts` directory, Hugo will create both `content/posts/` and `content/posts/my-first-post.md` for you.

+{{% /note %}}

+The  auto-populated fields are worth examining:

+* `title` is generated from the new content's filename (i.e. in this case, `my-first-post` becomes `"my first post"`)

+* `date` and `title` are the variables that ship with Hugo and are therefore included in *all* content files created with the Hugo CLI. `date` is generated in [RFC 3339 format][] by way of Go's [`now()`][] function, which returns the current time.

+* The third variable, `draft = true`, is *not* inherited by your default or custom archetypes but is included in Hugo's automatically scaffolded `default.md` archetype for convenience.

+Three variables per content file are often not enough for effective content management of larger websites. Luckily, Hugo provides a simple mechanism for extending the number of variables through custom archetypes, as well as default archetypes to keep content creation DRY.

+## Lookup Order for Archetypes

+Similar to the [lookup order for templates][lookup] in your `layouts` directory, Hugo looks for a section- or type-specific archetype, then a default archetype, and finally an internal archetype that ships with Hugo. For example, Hugo will look for an archetype for `content/posts/my-first-post.md` in the following order:

+1. `archetypes/posts.md`

+2. `archetypes/default.md`

+3. `themes/<THEME>/archetypes/posts.md`

+4. `themes/<THEME>/archetypes/default.md` (Auto-generated with `hugo new site`)

+{{% note "Using a Theme Archetype" %}}

+If you wish to use archetypes that ship with a theme, the `theme` field must be specified in your [configuration file](/getting-started/configuration/).

+{{% /note %}}

+## Choose Your Archetype's Front Matter Format

+By default, `hugo new` content files include front matter in the TOML format regardless of the format used in `archetypes/*.md`.

+You can specify a different default format in your site [configuration file][] file using the `metaDataFormat` directive. Possible values are `toml`, `yaml`, and `json`.

+## Default Archetypes

+Default archetypes are convenient if your content's front matter stays consistent across multiple [content sections][sections].

+### Create the Default Archetype

+When you create a new Hugo project using `hugo new site`, you'll notice that Hugo has already scaffolded a file at `archetypes/default.md`.

+The following examples are from a site that's using `tags` and `categories` as [taxonomies][]. If we assume that all content files will require these two key-values, we can create a `default.md` archetype that *extends* Hugo's base archetype. In this example, we are including "golang" and "hugo" as tags and "web development" as a category.

+{{% code file="archetypes/default.md" %}}

+```toml

++++

+tags = ["golang", "hugo"]

+categories = ["web development"]

++++

+```

+{{% /code %}}

+{{% warning "EOL Characters in Text Editors"%}}

+If you get an `EOF error` when using `hugo new`, add a carriage return after the closing `+++` or `---` for your TOML or YAML front matter, respectively. (See the [troubleshooting article on EOF errors](/troubleshooting/eof-error/) for more information.)

+{{% /warning %}}

+### Use the Default Archetype

+With an `archetypes/default.md` in place, we can use the CLI to create a new post in the `posts` content section:

+{{% code file="new-post-from-default.sh" %}}

+```bash

+$ hugo new posts/my-new-post.md

+```

+{{% /code %}}

+Hugo then creates a new markdown file with the following front matter:

+{{% output file="content/posts/my-new-post.md" %}}

+```toml

++++

+categories = ["web development"]

+date = "2017-02-01T19:20:04-07:00"

+tags = ["golang", "hugo"]

+title = "my new post"

++++

+```

+{{% /output %}}

+We see that the `title` and `date` key-values have been added in addition to the `tags` and `categories` key-values from `archetypes/default.md`.

+{{% note "Ordering of Front Matter" %}}

+You may notice that content files created with `hugo new` do not respect the order of the key-values specified in your archetype files. This is a [known issue](https://github.com/gohugoio/hugo/issues/452).

+{{% /note %}}

+## Custom Archetypes

+Suppose your site's `posts` section requires more sophisticated front matter than what has been specified in `archetypes/default.md`. You can create a custom archetype for your posts at `archetypes/posts.md` that includes the full set of front matter to be added to the two default archetypes fields.

+### Create a Custom Archetype

+{{% code file="archetypes/posts.md"%}}

+```toml

++++

+description = ""

+tags = ""

+categories = ""

++++

+```

+{{% /code %}}

+### Use a Custom Archetype

+With an `archetypes/posts.md` in place, you can use the Hugo CLI to create a new post with your preconfigured front matter in the `posts` content section:

+{{% code file="new-post-from-custom.sh" %}}

+```bash

+$ hugo new posts/post-from-custom.md

+```

+{{% /code %}}

+This time, Hugo recognizes our custom `archetypes/posts.md` archetype and uses it instead of `archetypes/default.md`. The generated file will now include the full list of front matter parameters, as well as the base archetype's `title` and `date`:

+{{% output file="content/posts/post-from-custom-archetype.md" %}}

+```toml

++++

+categories = ""

+date = 2017-02-13T17:24:43-08:00

+description = ""

+tags = ""

+title = "post from custom archetype"

++++

+```

+{{% /output %}}

+### Hugo Docs Custom Archetype

+As an example of archetypes in practice, the following is the `functions` archetype from the Hugo docs:

+{{% code file="archetypes/functions.md" %}}

+```yaml

+{{< readfile file="/themes/gohugoioTheme/archetypes/functions.md" >}}

+```

+{{% /code %}}

+{{% note %}}

+The preceding archetype is kept up to date with every Hugo build by using Hugo's [`readFile` function](/functions/readfile/). For similar examples, see [Local File Templates](/templates/files/).

+{{% /note %}}

+[archetypes directory]: /getting-started/directory-structure/

+[`now()`]: http://golang.org/pkg/time/#Now

+[configuration file]: /getting-started/configuration/

+[sections]: /content-management/sections/

+[content types]: /content-management/types/

+[front matter]: /content-management/front-matter/

+[RFC 3339 format]: https://www.ietf.org/rfc/rfc3339.txt

+[taxonomies]: /content-management/taxonomies/

+[lookup]: /templates/lookup/

+[templates]: /templates/

--- /dev/null

+++ b/content/content-management/authors.md

@@ -1,0 +1,193 @@

+---

+title: Authors

+linktitle: Authors

+description:

+date: 2016-08-22

+publishdate: 2017-03-12

+lastmod: 2017-03-12

+#tags: [authors]

+categories: ["content management"]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 55

+weight: 55	#rem

+draft: true

+aliases: [/content/archetypes/]

+toc: true

+comments: Before this page is published, need to also update both site- and page-level variables documentation.

+---

+Larger sites often have multiple content authors. Hugo provides standardized author profiles to organize relationships between content and content creators for sites operating under a distributed authorship model.

+## Author Profiles

+You can create a profile containing metadata for each author on your website. These profiles have to be saved under `data/_authors/`. The filename of the profile will later be used as an identifier. This way Hugo can associate content with one or multiple authors. An author's profile can be defined in the JSON, YAML, or TOML format.

+### Example: Author Profile

+Let's suppose Alice Allison is a blogger. A simple unique identifier would be `alice`. Now, we have to create a file called `alice.toml` in the `data/_authors/` directory. The following example is the standardized template written in TOML:

+{{% code  file="data/_authors/alice.toml" %}}

+```toml

+givenName      = "Alice"   # or firstName as alias

+familyName     = "Allison" # or lastName as alias

+displayName    = "Alice Allison"

+thumbnail      = "static/authors/alice-thumb.jpg"

+image          = "static/authors/alice-full.jpg"

+shortBio       = "My name is Alice and I'm a blogger."

+bio            = "My name is Alice and I'm a blogger... some other stuff"

+email          = "[email protected]"

+weight         = 10

+[social]

+    facebook   = "alice.allison"

+    twitter    = "alice"

+    googleplus = "aliceallison1"

+    website    = "www.example.com"

+[params]

+    random     = "whatever you want"

+```

+{{% /code %}}

+All variables are optional but it's advised to fill all important ones (e.g. names and biography) because themes can vary in their usage.

+You can store files for the `thumbnail` and `image` attributes in the `static` folder. Then add the path to the photos relative to `static`; e.g., `/static/path/to/thumbnail.jpg`.

+`weight` allows you to define the order of an author in an `.Authors` list and can be accessed on list or via the `.Site.Authors` variable.

+The `social` section contains all the links to the social network accounts of an author. Hugo is able to generate the account links for the most popular social networks automatically. This way, you only have to enter your username. You can find a list of all supported social networks [here](#linking-social-network-accounts-automatically). All other variables, like `website` in the example above remain untouched.

+The `params` section can contain arbitrary data much like the same-named section in the config file. What it contains is up to you.

+## Associate Content Through Identifiers

+Earlier it was mentioned that content can be associated with an author through their corresponding identifier. In our case, blogger Alice has the identifier `alice`. In the front matter of a content file, you can create a list of identifiers and assign it to the `authors` variable. Here are examples for `alice` using YAML and TOML, respectively.

+```yaml

+---

+title: Why Hugo is so Awesome

+date: 2016-08-22T14:27:502:00

+authors: ["alice"]

+---

+Nothing to read here. Move along...

+```

+```toml

++++

+title = Why Hugo is so Awesome

+date = "2016-08-22T14:27:502:00"

+authors: ["alice"]

++++

+Nothing to read here. Move along...

+```

+Future authors who might work on this blog post can append their identifiers to the `authors` array in the front matter as well.

+## Work with Templates

+After a successful setup it's time to give some credit to the authors by showing them on the website. Within the templates Hugo provides a list of the author's profiles if they are listed in the `authors` variable within the front matter.

+The list is accessible via the `.Authors` template variable. Printing all authors of a the blog post is straight forward:

+```

+{{ range .Authors }}

+    {{ .DisplayName }}

+{{ end }}

+=> Alice Allison

+```

+Even if there are co-authors you may only want to show the main author. For this case you can use the `.Author` template variable **(note the singular form)**. The template variable contains the profile of the author that is first listed with his identifier in the front matter.

+{{% note %}}

+You can find a list of all template variables to access the profile information in [Author Variables](/variables/authors/).

+{{% /note %}}

+### Link Social Network Accounts

+As aforementioned, Hugo is able to generate links to profiles of the most popular social networks. The following social networks with their corrersponding identifiers are supported:  `github`, `facebook`, `twitter`, `googleplus`, `pinterest`, `instagram`, `youtube` and `linkedin`.

+This is can be done with the `.Social.URL` function. Its only parameter is the name of the social network as they are defined in the profile (e.g. `facebook`, `googleplus`). Custom variables like `website` remain as they are.

+Most articles feature a small section with information about the author at the end. Let's create one containing the author's name, a thumbnail, a (summarized) biography and links to all social networks:

+{{% code file="layouts/partials/author-info.html" download="author-info.html" %}}

+```html

+{{ with .Author }}

+    <h3>{{ .DisplayName }}</h3>

+    <img src="{{ .Thumbnail | absURL }}" alt="{{ .DisplayName }}">

+    <p>{{ .ShortBio }}</p>

+    <ul>

+    {{ range $network, $username := .Social }}

+        <li><a href="{{ $.Author.Social.URL $network }}">{{ $network }}</a></li>

+    {{ end }}

+    </ul>

+{{ end }}

+```

+{{% /code %}}

+## Who Published What?

+That question can be answered with a list of all authors and another list containing all articles that they each have written. Now we have to translate this idea into templates. The [taxonomy][] feature allows us to logically group content based on information that they have in common; e.g. a tag or a category. Well, many articles share the same author, so this should sound familiar, right?

+In order to let Hugo know that we want to group content based on their author, we have to create a new taxonomy called `author` (the name corresponds to the variable in the front matter). Here is the snippet in a `config.yaml` and `config.toml`, respectively:

+```yaml

+taxonomies:

+    author: authors

+```

+```toml

+[taxonomies]

+    author = "authors"

+```

+### List All Authors

+In the next step we can create a template to list all authors of your website. Later, the list can be accessed at `www.example.com/authors/`. Create a new template in the `layouts/taxonomy/` directory called `authors.term.html`. This template will be exclusively used for this taxonomy.

+{{% code file="layouts/taxonomy/author.term.html" download="author.term.html" %}}

+```html

+<ul>

+{{ range $author, $v := .Data.Terms }}

+    {{ $profile := $.Authors.Get $author }}

+    <li>

+        <a href="{{ printf "%s/%s/" $.Data.Plural $author | absURL }}">

+            {{ $profile.DisplayName }} - {{ $profile.ShortBio }}

+        </a>

+    </li>

+{{ end }}

+</ul>

+```

+{{% /code %}}

+`.Data.Terms` contains the identifiers of all authors and we can range over it to create a list with all author names. The `$profile` variable gives us access to the profile of the current author. This allows you to generate a nice info box with a thumbnail, a biography and social media links, like at the [end of a blog post](#linking-social-network-accounts-automatically).

+### List Each Author's Publications

+Last but not least, we have to create the second list that contains all publications of an author. Each list will be shown in its own page and can be accessed at `www.example.com/authors/<IDENTIFIER>`. Replace `<IDENTIFIER>` with a valid author identifier like `alice`.

+The layout for this page can be defined in the template `layouts/taxonomy/author.html`.

+{{% code file="layouts/taxonomy/author.html" download="author.html" %}}

+```html

+{{ range .Data.Pages }}

+    <h2><a href="{{ .Permalink }}">{{ .Title }}</a></h2>

+    <span>written by {{ .Author.DisplayName }}</span>

+    {{ .Summary }}

+{{ end }}

+```

+{{% /code %}}

+The example above generates a simple list of all posts written by a single author. Inside the loop you've access to the complete set of [page variables][pagevars]. Therefore, you can add additional information about the current posts like the publishing date or the tags.

+With a lot of content this list can quickly become very long. Consider to use the [pagination][] feature. It splits the list into smaller chunks and spreads them over multiple pages.

+[pagevars]: /variables/page/

+[pagination]: /templates/pagination/

--- /dev/null

+++ b/content/content-management/comments.md

@@ -1,0 +1,84 @@

+---

+title: Comments

+linktitle: Comments

+description: Hugo ships with an internal Disqus template, but this isn't the only commenting system that will work with your new Hugo website.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-09

+#tags: [sections,content,organization]

+categories: [project organization, fundamentals]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 140

+weight: 140	#rem

+draft: false

+aliases: [/extras/comments/]

+toc: true

+---

+Hugo ships with support for [Disqus](https://disqus.com/), a third-party service that provides comment and community capabilities to websites via JavaScript.

+Your theme may already support Disqus, but if not, it is easy to add to your templates via [Hugo's built-in Disqus partial][disquspartial].

+## Add Disqus

+Hugo comes with all the code you need to load Disqus into your templates. Before adding Disqus to your site, you'll need to [set up an account][disqussetup].

+### Configure Disqus

+Disqus comments require you set a single value in your [site's configuration file][configuration]. The following show the configuration variable in a `config.toml` and `config.yml`, respectively:

+```toml

+disqusShortname = "yourdiscussshortname"

+```

+```yaml

+disqusShortname: "yourdiscussshortname"

+```

+For many websites, this is enough configuration. However, you also have the option to set the following in the [front matter][] of a single content file:

+* `disqus_identifier`

+* `disqus_title`

+* `disqus_url`

+### Render Hugo's Built-in Disqus Partial Template

+See [Partial Templates][partials] to learn how to add the Disqus partial to your Hugo website's templates.

+## Comments Alternatives

+There are a few alternatives to commenting on static sites for those who do not want to use Disqus:

+* [Static Man](https://staticman.net/)

+* [txtpen](https://txtpen.com)

+* [IntenseDebate](http://intensedebate.com/)

+* [Graph Comment][]

+* [Muut](http://muut.com/)

+* [isso](http://posativ.org/isso/) (Self-hosted, Python)

+    * [Tutorial on Implementing Isso with Hugo][issotutorial]

+<!-- I don't think this is worth including in the documentation since it seems that Steve is no longer supporting or developing this project. rdwatters - 2017-02-29.-->

+<!-- * [Kaiju](https://github.com/spf13/kaiju) -->

+<!-- ## Kaiju

+[Kaiju](https://github.com/spf13/kaiju) is an open-source project started by [spf13](http://spf13.com/) (Hugo’s author) to bring easy and fast real time discussions to the web.

+Written using Go, Socket.io, and [MongoDB][], Kaiju is very fast and easy to deploy.

+It is in early development but shows promise. If you have interest, please help by contributing via pull request, [opening an issue in the Kaiju GitHub repository][kaijuissue], or [Tweeting about it][tweet]. Every bit helps. -->

+[configuration]: /getting-started/configuration/

+[disquspartial]: /templates/partials/#disqus

+[disqussetup]: https://disqus.com/profile/signup/

+[forum]: https://discourse.gohugo.io

+[front matter]: /content-management/front-matter/

+[Graph Comment]: https://graphcomment.com/

+[kaijuissue]: https://github.com/spf13/kaiju/issues/new

+[issotutorial]: https://stiobhart.net/2017-02-24-isso-comments/

+[partials]: /templates/partials/

+[MongoDB]: https://www.mongodb.com/

+[tweet]: https://twitter.com/spf13

--- /dev/null

+++ b/content/content-management/cross-references.md

@@ -1,0 +1,125 @@

+---

+title: Cross References

+description: Hugo makes it easy to link documents together.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-31

+categories: [content management]

+#tags: ["cross references","references", "anchors", "urls"]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 100

+weight: 100	#rem

+aliases: [/extras/crossreferences/]

+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.

+## Use `ref` and `relref`

+```md

+{{</* ref "document" */>}}

+{{</* ref "#anchor" */>}}

+{{</* ref "document#anchor" */>}}

+{{</* relref "document" */>}}

+{{</* relref "#anchor" */>}}

+{{</* relref "document#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.

+### Document Names

+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:

+```md

+{{</* relref "blog/post.md" */>}} => `/blog/post/`

+{{</* relref "post.md" */>}} => `/blog/post/`

+```

+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:

+```bash

+.

+└── content

+    ├── events

+    │   └── my-birthday.md

+    ├── galleries

+    │   └── my-birthday.md

+    ├── meta

+    │   └── my-article.md

+    └── posts

+        └── my-birthday.md

+```

+To be sure to get the correct reference in this case, use the full path:

+{{% code file="content/meta/my-article.md" copy="false" %}}

+```md

+{{</* relref "events/my-birthday.md" */>}} => /events/my-birthday/

+```

+{{% /code %}}

+{{< todo >}}Remove this warning when https://github.com/gohugoio/hugo/issues/3703 is released.{{< /todo >}}

+A relative document name must *not* begin with a slash (`/`).

+```md

+{{</* relref "/events/my-birthday.md" */>}} => ""

+```

+### 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" */>}})

+```

+### 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:

+```md

+{{</* 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

+```md

+{{</* relref "#who" */>}} => #who:9decaf7

+{{</* 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" */>}}` => `http://yoursite.com/blog/post/`

+* `{{</* ref "post.md#tldr" */>}}` => `http://yoursite.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`

+## Hugo Heading Anchors

+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.

+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`.

+`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.)

+```md

+{{</* relref "content-management/cross-references.md#hugo-heading-anchors" */>}}

+/content-management/cross-references/#hugo-heading-anchors:77cd9ea530577debf4ce0f28c8dca242

+```

+[built-in Hugo shortcodes]: /content-management/shortcodes/#using-the-built-in-shortcodes

+[lists]: /templates/lists/

+[output formats]: /templates/output-formats/

+[shortcode]: /content-management/shortcodes/

\ No newline at end of file

--- /dev/null

+++ b/content/content-management/formats.md

@@ -1,0 +1,249 @@

+---

+title: Supported Content Formats

+linktitle: Supported Content Formats

+description: Markdown and Emacs Org-Mode have native support, and additional formats (e.g. Asciidoc) come via external helpers.

+date: 2017-01-10

+publishdate: 2017-01-10

+lastmod: 2017-04-06

+categories: [content management]

+#tags: [markdown,asciidoc,mmark,content format]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 20

+weight: 20	#rem

+draft: false

+aliases: [/content/markdown-extras/,/content/supported-formats/,/doc/supported-formats/,/tutorials/mathjax/]

+toc: true

+---

+**Markdown is the main content format** and comes in two flavours:  The excellent [Blackfriday project][blackfriday] (name your files `*.md` or set `markup = "markdown"` in front matter) or its fork [Mmark][mmark] (name your files `*.mmark` or set `markup = "mmark"` in front matter), both very fast markdown engines written in Go.

+For Emacs users, [goorgeous](https://github.com/chaseadamsio/goorgeous) provides built-in native support for Org-mode  (name your files `*.org` or set `markup = "org"` in front matter)

+{{% note "Deeply Nested Lists" %}}

+Before you begin writing your content in markdown, Blackfriday has a known issue [(#329)](https://github.com/russross/blackfriday/issues/329) with handling deeply nested lists. Luckily, there is an easy workaround. Use 4-spaces (i.e., <kbd>tab</kbd>) rather than 2-space indentations.

+{{% /note %}}

+## Configure BlackFriday Markdown Rendering

+You can configure multiple aspects of Blackfriday as show in the following list. See the docs on [Configuration][config] for the full list of explicit directions you can give to Hugo when rendering your site.

+{{< readfile file="/content/readfiles/bfconfig.md" markdown="true" >}}

+## Extend Markdown

+Hugo provides some convenient methods for extending markdown.

+### Task Lists

+Hugo supports [GitHub-styled task lists (i.e., TODO lists)][gfmtasks] for the Blackfriday markdown renderer. If you do not want to use this feature, you can disable it in your configuration.

+#### Example Task List Input

+{{% code file="content/my-to-do-list.md" %}}

+```markdown

+- [ ] a task list item

+- [ ] list syntax required

+- [ ] incomplete

+- [x] completed

+```

+{{% /code %}}

+#### Example Task List Output

+The preceding markdown produces the following HTML in your rendered website:

+```html

+<ul class="task-list">

+    <li><input type="checkbox" disabled="" class="task-list-item"> a task list item</li>

+    <li><input type="checkbox" disabled="" class="task-list-item"> list syntax required</li>

+    <li><input type="checkbox" disabled="" class="task-list-item"> incomplete</li>

+    <li><input type="checkbox" checked="" disabled="" class="task-list-item"> completed</li>

+</ul>

+```

+#### Example Task List Display

+The following shows how the example task list will look to the end users of your website. Note that visual styling of lists is up to you. This list has been styled according to [the Hugo Docs stylesheet][hugocss].

+- [ ] a task list item

+- [ ] list syntax required

+- [ ] incomplete

+- [x] completed

+### Emojis

+To add emojis directly to content, set `enableEmoji` to `true` in your [site configuration][config]. To use emojis in templates or shortcodes, see [`emojify` function][].

+For a full list of emojis, see the [Emoji cheat sheet][emojis].

+### Shortcodes

+If you write in Markdown and find yourself frequently embedding your content with raw HTML, Hugo provides built-in shortcodes functionality. This is one of the most powerful features in Hugo and allows you to create your own Markdown extensions very quickly.

+See [Shortcodes][sc] for usage, particularly for the built-in shortcodes that ship with Hugo, and [Shortcode Templating][sct] to learn how to build your own.

+### Code Blocks

+Hugo supports GitHub-flavored markdown's use of triple back ticks, as well as provides a special [`highlight` nested shortcode][hlsc] to render syntax highlighting via [Pygments][]. For usage examples and a complete explanation, see the [syntax highlighting documentation][hl] in [developer tools][].

+## Mmark

+Mmark is a [fork of BlackFriday][mmark] and markdown superset that is well suited for writing [IETF documentation][ietf]. You can see examples of the syntax in the [Mmark GitHub repository][mmarkgh] or the full syntax on [Miek Gieben's website][].

+### Use Mmark

+As Hugo ships with Mmark, using the syntax is as easy as changing the extension of your content files from `.md` to `.mmark`.

+In the event that you want to only use Mmark in specific files, you can also define the Mmark syntax in your content's front matter:

+```yaml

+---

+title: My Post

+date: 2017-04-01

+markdown: mmark

+---

+```

+{{% warning %}}

+Thare are some features not available in Mmark; one example being that shortcodes are not translated when used in an included `.mmark` file ([#3131](https://github.com/gohugoio/hugo/issues/3137)), and `EXTENSION_ABBREVIATION` ([#1970](https://github.com/gohugoio/hugo/issues/1970)) and the aforementioned GFM todo lists ([#2270](https://github.com/gohugoio/hugo/issues/2270)) are not fully supported. Contributions are welcome.

+{{% /warning %}}

+## MathJax with Hugo

+[MathJax](http://www.mathjax.org/) is a JavaScript library that allows the display of mathematical expressions described via a LaTeX-style syntax in the HTML (or Markdown) source of a web page. As it is a pure a JavaScript library, getting it to work within Hugo is fairly straightforward, but does have some oddities that will be discussed here.

+This is not an introduction into actually using MathJax to render typeset mathematics on your website. Instead, this page is a collection of tips and hints for one way to get MathJax working on a website built with Hugo.

+### Enable MathJax

+The first step is to enable MathJax on pages that you would like to have typeset math. There are multiple ways to do this (adventurous readers can consult the [Loading and Configuring](http://docs.mathjax.org/en/latest/configuration.html) section of the MathJax documentation for additional methods of including MathJax), but the easiest way is to use the secure MathJax CDN by include a `<script>` tag for the officially recommended secure CDN ([cdn.js.com](https://cdnjs.com)):

+{{% code file="add-mathjax-to-page.html" %}}

+```html

+<script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-AMS-MML_HTMLorMML">

+</script>

+```

+{{% /code %}}

+One way to ensure that this code is included in all pages is to put it in one of the templates that live in the `layouts/partials/` directory. For example, I have included this in the bottom of my template `footer.html` because I know that the footer will be included in every page of my website.

+### Options and Features

+MathJax is a stable open-source library with many features. I encourage the interested reader to view the [MathJax Documentation](http://docs.mathjax.org/en/latest/index.html), specifically the sections on [Basic Usage](http://docs.mathjax.org/en/latest/index.html#basic-usage) and [MathJax Configuration Options](http://docs.mathjax.org/en/latest/index.html#mathjax-configuration-options).

+### Issues with Markdown

+{{% note %}}

+The following issues with Markdown assume you are using `.md` for content and BlackFriday for parsing. Using [Mmark](#mmark) as your content format will obviate the need for the following workarounds.

+When using Mmark with MathJax, use `displayMath: [['$$','$$'], ['\\[','\\]']]`. See the [Mmark `README.md`](https://github.com/miekg/mmark/wiki/Syntax#math-blocks) for more information. In addition to MathJax, Mmark has been shown to work well with [KaTeX](https://github.com/Khan/KaTeX). See this [related blog post from a Hugo user](http://nosubstance.me/post/a-great-toolset-for-static-blogging/).

+{{% /note %}}

+After enabling MathJax, any math entered between proper markers (see the [MathJax documentation][mathjaxdocs]) will be processed and typeset in the web page. One issue that comes up, however, with Markdown is that the underscore character (`_`) is interpreted by Markdown as a way to wrap text in `emph` blocks while LaTeX (MathJax) interprets the underscore as a way to create a subscript. This "double speak" of the underscore can result in some unexpected and unwanted behavior.

+### Solution

+There are multiple ways to remedy this problem. One solution is to simply escape each underscore in your math code by entering `\_` instead of `_`. This can become quite tedious if the equations you are entering are full of subscripts.

+Another option is to tell Markdown to treat the MathJax code as verbatim code and not process it. One way to do this is to wrap the math expression inside a `<div>` `</div>` block. Markdown would ignore these sections and they would get passed directly on to MathJax and processed correctly. This works great for display style mathematics, but for inline math expressions the line break induced by the `<div>` is not acceptable. The syntax for instructing Markdown to treat inline text as verbatim is by wrapping it in backticks (`` ` ``). You might have noticed, however, that the text included in between backticks is rendered differently than standard text (on this site these are items highlighted in red). To get around this problem, we could create a new CSS entry that would apply standard styling to all inline verbatim text that includes MathJax code. Below I will show the HTML and CSS source that would accomplish this (note this solution was adapted from [this blog post](http://doswa.com/2011/07/20/mathjax-in-markdown.html)---all credit goes to the original author).

+{{% code file="mathjax-markdown-solution.html" %}}

+```js

+<script type="text/x-mathjax-config">

+MathJax.Hub.Config({

+  tex2jax: {

+    inlineMath: [['$','$'], ['\\(','\\)']],

+    displayMath: [['$$','$$'], ['\[','\]']],

+    processEscapes: true,

+    processEnvironments: true,

+    skipTags: ['script', 'noscript', 'style', 'textarea', 'pre'],

+    TeX: { equationNumbers: { autoNumber: "AMS" },

+         extensions: ["AMSmath.js", "AMSsymbols.js"] }

+  }

+});

+</script>

+<script type="text/x-mathjax-config">

+  MathJax.Hub.Queue(function() {

+    // Fix <code> tags after MathJax finishes running. This is a

+    // hack to overcome a shortcoming of Markdown. Discussion at

+    // https://github.com/mojombo/jekyll/issues/199

+    var all = MathJax.Hub.getAllJax(), i;

+    for(i = 0; i < all.length; i += 1) {

+        all[i].SourceElement().parentNode.className += ' has-jax';

+    }

+});

+</script>

+```

+{{% /code %}}

+As before, this content should be included in the HTML source of each page that will be using MathJax. The next code snippet contains the CSS that is used to have verbatim MathJax blocks render with the same font style as the body of the page.

+{{% code file="mathjax-style.css" %}}

+```css

+code.has-jax {

+    font: inherit;

+    font-size: 100%;

+    background: inherit;

+    border: inherit;

+    color: #515151;

+}

+```

+{{% /code %}}

+In the CSS snippet, notice the line `color: #515151;`. `#515151` is the value assigned to the `color` attribute of the `body` class in my CSS. In order for the equations to fit in with the body of a web page, this value should be the same as the color of the body.

+### Usage

+With this setup, everything is in place for a natural usage of MathJax on pages generated using Hugo. In order to include inline mathematics, just put LaTeX code in between `` `$ TeX Code $` `` or `` `\( TeX Code \)` ``. To include display style mathematics, just put LaTeX code in between `<div>$$TeX Code$$</div>`. All the math will be properly typeset and displayed within your Hugo generated web page!

+## Additional Formats Through External Helpers

+Hugo has new concept called _external helpers_. It means that you can write your content using [Asciidoc][ascii], [reStructuredText][rest]. If you have files with associated extensions, Hugo will call external commands to generate the content. ([See the Hugo source code for external helpers][helperssource].)

+For example, for Asciidoc files, Hugo will try to call the `asciidoctor` or `asciidoc` command. This means that you will have to install the associated tool on your machine to be able to use these formats. ([See the Asciidoctor docs for installation instructions](http://asciidoctor.org/docs/install-toolchain/)).

+To use these formats, just use the standard extension and the front matter exactly as you would do with natively supported `.md` files.

+{{% warning "Performance of External Helpers" %}}

+Because additional formats are external commands generation performance will rely heavily on the performance of the external tool you are using. As this feature is still in its infancy, feedback is welcome.

+{{% /warning %}}

+## Learn Markdown

+Markdown syntax is simple enough to learn in a single sitting. The following are excellent resources to get you up and running:

+* [Daring Fireball: Markdown, John Gruber (Creator of Markdown)][fireball]

+* [Markdown Cheatsheet, Adam Pritchard][mdcheatsheet]

+* [Markdown Tutorial (Interactive), Garen Torikian][mdtutorial]

+[`emojify` function]: /functions/emojify/

+[ascii]: http://asciidoc.org/

+[bfconfig]: /getting-started/configuration/#configuring-blackfriday-rendering

+[blackfriday]: https://github.com/russross/blackfriday

+[mmark]: https://github.com/miekg/mmark

+[config]: /getting-started/configuration/

+[developer tools]: /tools/

+[emojis]: https://www.webpagefx.com/tools/emoji-cheat-sheet/

+[fireball]: https://daringfireball.net/projects/markdown/

+[gfmtasks]: https://guides.github.com/features/mastering-markdown/#syntax

+[helperssource]: https://github.com/gohugoio/hugo/blob/77c60a3440806067109347d04eb5368b65ea0fe8/helpers/general.go#L65

+[hl]: /tools/syntax-highlighting/

+[hlsc]: /content-management/shortcodes/#highlight

+[hugocss]: /css/style.css

+[ietf]: https://tools.ietf.org/html/

+[mathjaxdocs]: https://docs.mathjax.org/en/latest/

+[mdcheatsheet]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

+[mdtutorial]: http://www.markdowntutorial.com/

+[Miek Gieben's website]: https://miek.nl/2016/March/05/mmark-syntax-document/

+[mmark]: https://github.com/miekg/mmark

+[mmarkgh]: https://github.com/miekg/mmark/wiki/Syntax

+[org]: http://orgmode.org/

+[Pygments]: http://pygments.org/

+[rest]: http://docutils.sourceforge.net/rst.html

+[sc]: /content-management/shortcodes/

+[sct]: /templates/shortcode-templates/

--- /dev/null

+++ b/content/content-management/front-matter.md

@@ -1,0 +1,198 @@

+---

+title: Front Matter

+linktitle:

+description: Hugo allows you to add front matter in yaml, toml, or json to your content files.

+date: 2017-01-09

+publishdate: 2017-01-09

+lastmod: 2017-02-24

+categories: [content management]

+#tags: ["front matter", "yaml", "toml", "json", "metadata", "archetypes"]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 30

+weight: 30	#rem

+draft: false

+aliases: [/content/front-matter/]

+toc: true

+---

+**Front matter** allows you to keep metadata attached to an instance of a [content type][]---i.e., embedded inside a content file---and is one of the many features that gives Hugo its strength.

+## Front Matter Formats

+Hugo supports three formats for front matter, each with their own identifying tokens.

+TOML

+: identified by opening and closing `+++`.

+YAML

+: identified by opening and closing `---`.

+JSON

+: a single JSON object surrounded by '`{`' and '`}`', followed by a new line.

+### TOML Example

+```toml

++++

+title = "spf13-vim 3.0 release and new website"

+description = "spf13-vim is a cross platform distribution of vim plugins and resources for Vim."

+tags = [ ".vimrc", "plugins", "spf13-vim", "vim" ]

+date = "2012-04-06"

+categories = [

+  "Development",

+  "VIM"

+]

+slug = "spf13-vim-3-0-release-and-new-website"

++++

+```

+### YAML Example

+```yaml

+---

+title: "spf13-vim 3.0 release and new website"

+description: "spf13-vim is a cross platform distribution of vim plugins and resources for Vim."

+#tags: [ ".vimrc", "plugins", "spf13-vim", "vim" ]

+lastmod: 2015-12-23

+date: "2012-04-06"

+categories:

+  - "Development"

+  - "VIM"

+slug: "spf13-vim-3-0-release-and-new-website"

+---

+```

+### JSON Example

+```json

+{

+    "title": "spf13-vim 3.0 release and new website",

+    "description": "spf13-vim is a cross platform distribution of vim plugins and resources for Vim.",

+    "tags": [ ".vimrc", "plugins", "spf13-vim", "vim" ],

+    "date": "2012-04-06",

+    "categories": [

+        "Development",

+        "VIM"

+    ],

+    "slug": "spf13-vim-3-0-release-and-new-website"

+}

+```

+## Front Matter Variables

+### Predefined

+There are a few predefined variables that Hugo is aware of. See [Page Variables][pagevars] for how to call many of these predefined variables in your templates.

+`aliases`

+: an array of one or more aliases (e.g., old published paths of renamed content) that will be created in the output directory structure . See [Aliases][aliases] for details.

+`date`

+: the datetime at which the content was created; note this value is auto-populated according to Hugo's built-in [archetype][].

+`description`

+: the description for the content.

+`draft`

+: if `true`, the content will not be rendered unless the `--buildDrafts` flag is passed to the `hugo` command.

+`expiryDate`

+: the datetime at which the content should no longer be published by Hugo; expired content will not be rendered unless the `--buildExpired` flag is passed to the `hugo` command.

+`isCJKLanguage`

+: if `true`, Hugo will explicitly treat the content as a CJK language; both `.Summary` and `.WordCount` work properly in CJK languages.

+`keywords`

+: the meta keywords for the content.

+`layout`

+: the layout Hugo should select from the [lookup order][lookup] when rendering the content. If a `type` is not specified in the front matter, Hugo will look for the layout of the same name in the layout directory that corresponds with a content's section. See ["Defining a Content Type"][definetype]

+`lastmod`

+: the datetime at which the content was last modified.

+`linkTitle`

+: used for creating links to content; if set, Hugo defaults to using the `linktitle` before the `title`. Hugo can also [order lists of content by `linktitle`][bylinktitle].

+`markup`

+: **experimental**; specify `"rst"` for reStructuredText (requires`rst2html`) or `"md"` (default) for Markdown.

+`outputs`

+: allows you to specify output formats specific to the content. See [output formats][outputs].

+`publishDate`

+: if in the future, content will not be rendered unless the `--buildFuture` flag is passed to `hugo`.

+`slug`

+: appears as the tail of the output URL. A value specified in front matter will override the segment of the URL based on the filename.

+`taxonomies`

+: these will use the field name of the plural form of the index; see the `tags` and `categories` in the above front matter examples.

+`title`

+: the title for the content.

+`type`

+: the type of the content; this value will be automatically derived from the directory (i.e., the [section][]) if not specified in front matter.

+`url`

+: the full path to the content from the web root. It makes no assumptions about the path of the content file. It also ignores any language prefixes of

+the multilingual feature.

+`weight`

+: used for [ordering your content in lists][ordering].

+{{% note "Hugo's Default URL Destinations" %}}

+If neither `slug` nor `url` is present and [permalinks are not configured otherwise in your site `config` file](/content-management/urls/#permalinks), Hugo will use the filename of your content to create the output URL. See [Content Organization](/content-management/organization) for an explanation of paths in Hugo and [URL Management](/content-management/urls/) for ways to customize Hugo's default behaviors.

+{{% /note %}}

+### User-Defined

+You can add fields to your front matter arbitrarily to meet your needs. These user-defined key-values are placed into a single `.Params` variable for use in your templates.

+The following fields can be accessed via `.Params.include_toc` and `.Params.show_comments`, respectively. The [Variables][] section provides more information on using Hugo's page- and site-level variables in your templates.

+```yaml

+include_toc: true

+show_comments: false

+```

+These two user-defined fields can then be accessed via `.Params.include_toc` and `.Params.show_comments`, respectively. The [Variables][variables] section provides more information on using Hugo's page- and site-level variables in your templates.

+## Order Content Through Front Matter

+You can assign content-specific `weight` in the front matter of your content. These values are especially useful for [ordering][ordering] in list views. You can use `weight` for ordering of content and the convention of [`<TAXONOMY>_weight`][taxweight] for ordering content within a taxonomy. See [Ordering and Grouping Hugo Lists][lists] to see how `weight` can be used to organize your content in list views.

+## Override Global Markdown Configuration

+It's possible to set some options for Markdown rendering in a content's front matter as an override to the [BlackFriday rendering options set in your project configuration][config].

+## Front Matter Format Specs

+* [TOML Spec][toml]

+* [YAML Spec][yaml]

+* [JSON Spec][json]

+[variables]: /variables/

+[aliases]: /content-management/urls/#aliases/

+[archetype]: /content-management/archetypes/

+[bylinktitle]: /templates/lists/#by-link-title

+[config]: /getting-started/configuration/ "Hugo documentation for site configuration"

+[content type]: /content-management/types/

+[contentorg]: /content-management/organization/

+[definetype]: /content-management/types/#defining-a-content-type "Learn how to specify a type and a layout in a content's front matter"

+[json]: /documents/ecma-404-json-spec.pdf "Specification for JSON, JavaScript Object Notation"

+[lists]: /templates/lists/#ordering-content "See how to order content in list pages; for example, templates that look to specific _index.md for content and front matter."

+[lookup]: /templates/lookup-order/ "Hugo traverses your templates in a specific order when rendering content to allow for DRYer templating."

+[ordering]: /templates/lists/ "Hugo provides multiple ways to sort and order your content in list templates"

+[outputs]: /templates/output-formats/ "With the release of v22, you can output your content to any text format using Hugo's familiar templating"

+[pagevars]: /variables/page/

+[section]: /content-management/sections/

+[taxweight]: /content-management/taxonomies/

+[toml]: https://github.com/toml-lang/toml "Specification for TOML, Tom's Obvious Minimal Language"

+[urls]: /content-management/urls/

+[variables]: /variables/

+[yaml]: http://yaml.org/spec/ "Specification for YAML, YAML Ain't Markup Language"

--- /dev/null

+++ b/content/content-management/menus.md

@@ -1,0 +1,183 @@

+---

+title: Menus

+linktitle: Menus

+description: Hugo has a simple yet powerful menu system.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-31

+categories: [content management]

+#tags: [menus]

+draft: false

+menu:

+  docs:

+    parent: "content-management"

+    weight: 120

+weight: 120	#rem

+aliases: [/extras/menus/]

+toc: true

+---

+{{% note "Lazy Blogger"%}}

+If all you want is a simple menu for your sections, see the ["Section Menu for Lazy Bloggers" in Menu Templates](/templates/menu-templates/#section-menu-for-lazy-blogger).

+{{% /note %}}

+You can do this:

+* Place content in one or many menus

+* Handle nested menus with unlimited depth

+* Create menu entries without being attached to any content

+* Distinguish active element (and active branch)

+## What is a Menu in Hugo?

+A **menu** is a named array of menu entries accessible by name via the [`.Site.Menus` site variable][sitevars]. For example, you can access your site's `main` menu via `.Site.Menus.main`.

+{{% note "Menus on Multilingual Sites" %}}

+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

+## Add content to menus

+Hugo allows you to add content to a menu via the content's [front matter](/content-management/front-matter/).

+### Simple

+If all you need to do is add an entry to a menu, the simple form works well.

+#### A Single Menu

+```yaml

+---

+menu: "main"

+---

+```

+#### Multiple Menus

+```yaml

+---

+menu: ["main", "footer"]

+---

+```

+#### Advanced

+```yaml

+---

+menu:

+  docs:

+    parent: 'extras'

+    weight: 20

+---

+```

+## Add Non-content Entries to a Menu

+You can also add entries to menus that aren’t attached to a piece of content. This takes place in your Hugo project's [`config` file][config].

+Here’s an example snippet pulled from a `config.toml`:

+{{% code file="config.toml" %}}

+```toml

+[[menu.main]]

+    name = "about hugo"

+    pre = "<i class='fa fa-heart'></i>"

+    weight = -110

+    identifier = "about"

+    url = "/about/"

+[[menu.main]]

+    name = "getting started"

+    pre = "<i class='fa fa-road'></i>"

+    weight = -100

+    url = "/getting-started/"

+```

+{{% /code %}}

+Here's the equivalent snippet in a `config.yaml`:

+{{% code file="config.yml" %}}

+```yaml

+---

+menu:

+  docs:

+      - Name: "about hugo"

+        Pre: "<i class='fa fa-heart'></i>"

+        Weight: -110

+        Identifier: "about"

+        URL: "/about/"

+      - Name: "getting started"

+        Pre: "<i class='fa fa-road'></i>"

+        Weight: -100

+        URL: "/getting-started/"

+---

+```

+{{% /code %}}

+{{% note %}}

+The URLs must be relative to the context root. If the `baseURL` is `http://example.com/mysite/`, then the URLs in the menu must not include the context root `mysite`. Using an absolute URL will overide the baseURL. If the value used for `URL` in the above example is `http://subdomain.example.com/`, the output will be `http://subdomain.example.com`.

+{{% /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).

+The following order is used to determine an Identifier:

+`.Name > .LinkTitle > .Title`

+This means that `.Title` will be used unless `.LinkTitle` is present, etc. In practice, `.Name` and `.Identifier` are only used to structure relationships and therefore never displayed.

+In this example, the top level of the menu is defined in your [site `config` file][config]). All content entries are attached to one of these entries via the `.Parent` field.

+## Render Menus

+See [Menu Templates](/templates/menu-templates/) for information on how to render your site menus within your templates.

+[config]: /getting-started/configuration/

+[multilingual]: /content-management/multilingual/

+[sitevars]: /variables/

--- /dev/null

+++ b/content/content-management/multilingual.md

@@ -1,0 +1,300 @@

+---

+title: Multilingual Mode

+linktitle: Multilingual and i18n

+description: Hugo supports the creation of websites with multiple languages side by side.

+date: 2017-01-10

+publishdate: 2017-01-10

+lastmod: 2017-01-10

+categories: [content management]

+#tags: [multilingual,i18n, internationalization]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 150

+weight: 150	#rem

+draft: false

+aliases: [/content/multilingual/,/content-management/multilingual/]

+toc: true

+---

+You should define the available languages in a `Languages` section in your site configuration.

+## Configure Languages

+The following is an example of a TOML site configuration for a multilingual Hugo project:

+{{% code file="config.toml" download="config.toml" %}}

+```toml

+DefaultContentLanguage = "en"

+copyright = "Everything is mine"

+[params.navigation]

+help  = "Help"

+[Languages]

+[Languages.en]

+title = "My blog"

+weight = 1

+[Languages.en.params]

+linkedin = "english-link"

+[Languages.fr]

+copyright = "Tout est à moi"

+title = "Mon blog"

+weight = 2

+[Languages.fr.params]

+linkedin = "lien-francais"

+[Languages.fr.navigation]

+help  = "Aide"

+```

+{{% /code %}}

+Anything not defined in a `[Languages]` block will fall back to the global

+value for that key (e.g., `copyright` for the English [`en`] language).

+With the configuration above, all content, sitemap, RSS feeds, paginations,

+and taxonomy pages will be rendered below `/` in English (your default content language) and then below `/fr` in French.

+When working with front matter `Params` in [single page templates][singles], omit the `params` in the key for the translation.

+If you want all of the languages to be put below their respective language code, enable `defaultContentLanguageInSubdir: true`.

+Only the obvious non-global options can be overridden per language. Examples of global options are `baseURL`, `buildDrafts`, etc.

+## Taxonomies and Blackfriday

+Taxonomies and [Blackfriday configuration][config] can also be set per language:

+{{% code file="bf-config.toml" %}}

+```toml

+[Taxonomies]

+tag = "tags"

+[blackfriday]

+angledQuotes = true

+hrefTargetBlank = true

+[Languages]

+[Languages.en]

+weight = 1

+title = "English"

+[Languages.en.blackfriday]

+angledQuotes = false

+[Languages.fr]

+weight = 2

+title = "Français"

+[Languages.fr.Taxonomies]

+plaque = "plaques"

+```

+{{% /code %}}

+## Translate Your Content

+Translated articles are identified by the name of the content file.

+### Examples of Translated Articles

+1. `/content/about.en.md`

+2. `/content/about.fr.md`

+In this eample, the `about.md` will be assigned the configured `defaultContentLanguage`.

+1. `/content/about.md`

+2. `/content/about.fr.md`

+This way, you can slowly start to translate your current content without having to rename everything. If left unspecified, the default value for `defaultContentLanguage` is `en`.

+By having the same *base filename*, the content pieces are linked together as translated pieces.

+If you need distinct URLs per language, you can set the slug in the non-default language file. For example, you can define a custom slug for a French translation in the front matter of `content/about.fr.md` as follows:

+```yaml

+slug: "a-propos"

+```

+At render, Hugo will build both `/about/` and `/a-propos/` as properly linked translated pages.

+{{%note %}}

+Hugo currently uses the base filename as the translation key, which can be an issue with identical filenames in different sections.

+We will fix this in https://github.com/gohugoio/hugo/issues/2699

+{{% /note %}}

+{{< todo >}}Rewrite/remove the above one issue is fixed.{{< /todo >}}

+## Link to Translated Content

+To create a list of links to translated content, use a template similar to the following:

+{{% code file="layouts/partials/i18nlist.html" %}}

+```html

+{{ if .IsTranslated }}

+<h4>{{ i18n "translations" }}</h4>

+<ul>

+    {{ range .Translations }}

+    <li>

+        <a href="{{ .Permalink }}">{{ .Lang }}: {{ .Title }}{{ if .IsPage }} ({{ i18n "wordCount" . }}){{ end }}</a>

+    </li>

+    {{ end}}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+The above can be put in a `partial` (i.e., inside `layouts/partials/`) and included in any template, be it for a [single content page][contenttemplate] or the [homepage][]. It will not print anything if there are no translations for a given page, or if there are translations---in the case of the homepage, section listing, etc.---a site with only render one language.

+The above also uses the [`i18n` function][i18func] described in the next section.

+## Translation of Strings

+Hugo uses [go-i18n][] to support string translations. [See the project's source repository][go-i18n-source] to find tools that will help you manage your translation workflows.

+Translations are collected from the `themes/<THEME>/i18n/` folder (built into the theme), as well as translations present in `i18n/` at the root of your project. In the `i18n`, the translations will be merged and take precedence over what is in the theme folder. Language files should be named according to [RFC 5646][] with names such as `en-US.toml`, `fr.toml`, etc.

+From within your templates, use the `i18n` function like this:

+```

+{{ i18n "home" }}

+```

+This uses a definition like this one in `i18n/en-US.toml`:

+```

+[home]

+other = "Home"

+```

+Often you will want to use to the page variables in the translations strings. To do that, pass on the "." context when calling `i18n`:

+```

+{{ i18n "wordCount" . }}

+```

+This uses a definition like this one in `i18n/en-US.toml`:

+```

+[wordCount]

+other = "This article has {{ .WordCount }} words."

+```

+An example of singular and plural form:

+```

+[readingTime]

+one = "One minute read"

+other = "{{.Count}} minutes read"

+```

+And then in the template:

+```

+{{ i18n "readingTime" .ReadingTime }}

+```

+To track down missing translation strings, run Hugo with the `--i18n-warnings` flag:

+```bash

+ hugo --i18n-warnings | grep i18n

+i18n|MISSING_TRANSLATION|en|wordCount

+```

+## Customize Dates

+At the time of this writing, Golang does not yet have support for internationalized locales, but if you do some work, you can simulate it. For example, if you want to use French month names, you can add a data file like ``data/mois.yaml`` with this content:

+~~~yaml

+1: "janvier"

+2: "février"

+3: "mars"

+4: "avril"

+5: "mai"

+6: "juin"

+7: "juillet"

+8: "août"

+9: "septembre"

+10: "octobre"

+11: "novembre"

+12: "décembre"

+~~~

+... then index the non-English date names in your templates like so:

+~~~html

+<time class="post-date" datetime="{{ .Date.Format "2006-01-02T15:04:05Z07:00" | safeHTML }}">

+  Article publié le {{ .Date.Day }} {{ index $.Site.Data.mois (printf "%d" .Date.Month) }} {{ .Date.Year }} (dernière modification le {{ .Lastmod.Day }} {{ index $.Site.Data.mois (printf "%d" .Lastmod.Month) }} {{ .Lastmod.Year }})

+</time>

+~~~

+This technique extracts the day, month and year by specifying ``.Date.Day``, ``.Date.Month``, and ``.Date.Year``, and uses the month number as a key, when indexing the month name data file.

+## Menus

+You can define your menus for each language independently. The [creation of a menu][menus] works analogous to earlier versions of Hugo, except that they have to be defined in their language-specific block in the configuration file:

+```toml

+defaultContentLanguage = "en"

+[languages.en]

+weight = 0

+languageName = "English"

+[[languages.en.menu.main]]

+url    = "/"

+name   = "Home"

+weight = 0

+[languages.de]

+weight = 10

+languageName = "Deutsch"

+[[languages.de.menu.main]]

+url    = "/"

+name   = "Startseite"

+weight = 0

+```

+The rendering of the main navigation works as usual. `.Site.Menus` will just contain the menu of the current language. Pay attention to the generation of the menu links. `absLangURL` takes care that you link to the correct locale of your website. Otherwise, both menu entries would link to the English version as the default content language that resides in the root directory.

+```html

+<ul>

+    {{- $currentPage := . -}}

+    {{ range .Site.Menus.main -}}

+    <li class="{{ if $currentPage.IsMenuCurrent "main" . }}active{{ end }}">

+        <a href="{{ .URL | absLangURL }}">{{ .Name }}</a>

+    </li>

+    {{- end }}

+</ul>

+```

+## Missing translations

+If a string does not have a translation for the current language, Hugo will use the value from the default language. If no default value is set, an empty string will be shown.

+While translating a Hugo website, it can be handy to have a visual indicator of missing translations. The [`enableMissingTranslationPlaceholders` configuration option][config] will flag all untranslated strings with the placeholder `[i18n] identifier`, where `identifier` is the id of the missing translation.

+{{% note %}}

+Hugo will generate your website with these missing translation placeholders. It might not be suited for production environments.

+{{% /note %}}

+## Multilingual Themes support

+To support Multilingual mode in your themes, some considerations must be taken for the URLs in the templates. If there is more than one language, URLs must meet the following criteria:

+* Come from the built-in `.Permalink` or `.URL`

+* Be constructed with

+    * The [`relLangURL` template function][rellangurl] or the [`absLangURL` template function][abslangurl] **OR**

+    * Prefixed with `{{ .LanguagePrefix }}`

+If there is more than one language defined, the `LanguagePrefix` variable will equal `/en` (or whatever your `CurrentLanguage` is). If not enabled, it will be an empty string and is therefore harmless for single-language Hugo websites.

+[abslangurl]: /functions/abslangurl

+[config]: /getting-started/configuration/

+[contenttemplate]: /templates/single-page-templates/

+[go-i18n-source]: https://github.com/nicksnyder/go-i18n

+[go-i18n]: https://github.com/nicksnyder/go-i18n

+[homepage]: /templates/homepage/

+[i18func]: /functions/i18n/

+[menus]: /content-management/menus/

+[rellangurl]: /functions/rellangurl

+[RFC 5646]: https://tools.ietf.org/html/rfc5646

+[singles]: /templates/single-page-templates/

--- /dev/null

+++ b/content/content-management/organization.md

@@ -1,0 +1,247 @@

+---

+title: Content Organization

+linktitle: Organization

+description: Hugo assumes that the same structure that works to organize your source content is used to organize the rendered site.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [content management,fundamentals]

+#tags: [sections,content,organization]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 10

+weight: 10	#rem

+draft: false

+aliases: [/content/sections/]

+toc: true

+---

+{{% note %}}

+This section is not updated with the new nested sections support in Hugo 0.24, see https://github.com/gohugoio/hugoDocs/issues/36

+{{% /note %}}

+{{% todo %}}

+See above

+{{% /todo %}}

+## Organization of Content Source

+In Hugo, your content should be organized in a manner that reflects the rendered website.

+While Hugo supports content nested at any level, the top levels (i.e. `content/<DIRECTORIES>`) are special in Hugo and are considered the content [sections][]. Without any additional configuration, the following will just work:

+```

+.

+└── content

+    └── about

+    |   └── _index.md  // <- http://yoursite.com/about/

+    ├── post

+    |   ├── firstpost.md   // <- http://yoursite.com/post/firstpost/

+    |   ├── happy

+    |   |   └── ness.md  // <- http://yoursite.com/post/happy/ness/

+    |   └── secondpost.md  // <- http://yoursite.com/post/secondpost/

+    └── quote

+        ├── first.md       // <- http://yoursite.com/quote/first/

+        └── second.md      // <- http://yoursite.com/quote/second/

+```

+## Path Breakdown in Hugo

+The following demonstrates the relationships between your content organization and the output URL structure for your Hugo website when it renders. These examples assume you are [using pretty URLs][pretty], which is the default behavior for Hugo. The examples also assume a key-value of `baseurl = "http://yoursite.com"` in your [site's configuration file][config].

+### Index Pages: `_index.md`

+`_index.md` has a special role in Hugo. It allows you to add front matter and content to your [list templates][lists] as of v0.18. These templates include those for [section templates][], [taxonomy templates][], [taxonomy terms templates][], and your [homepage template][]. In your templates, you can grab information from `_index.md` using the [`.Site.GetPage` function][getpage].

+You can keep one `_index.md` for your homepage and one in each of your content sections, taxonomies, and taxonomy terms. The following shows typical placement of an `_index.md` that would contain content and front matter for a `posts` section list page on a Hugo website:

+```bash

+.         url

+.       ⊢--^-⊣

+.        path    slug

+.       ⊢--^-⊣⊢---^---⊣

+.           filepath

+.       ⊢------^------⊣

+content/posts/_index.md

+```

+At build, this will output to the following destination with the associated values:

+```bash

+                     url ("/posts/")

+                    ⊢-^-⊣

+       baseurl      section ("posts")

+⊢--------^---------⊣⊢-^-⊣

+        permalink

+⊢----------^-------------⊣

+http://yoursite.com/posts/index.html

+```

+### Single Pages in Sections

+Single content files in each of your sections are going to be rendered as [single page templates][singles]. Here is an example of a single `post` within `posts`:

+```bash

+                   path ("posts/my-first-hugo-post.md")

+.       ⊢-----------^------------⊣

+.      section        slug

+.       ⊢-^-⊣⊢--------^----------⊣

+content/posts/my-first-hugo-post.md

+```

+At the time Hugo builds your site, the content will be output to the following destination:

+```bash

+                               url ("/posts/my-first-hugo-post/")

+                   ⊢------------^----------⊣

+       baseurl     section     slug

+⊢--------^--------⊣⊢-^--⊣⊢-------^---------⊣

+                 permalink

+⊢--------------------^---------------------⊣

+http://yoursite.com/posts/my-first-hugo-post/index.html

+```

+### Section with Nested Directories

+To continue the example, the following demonstrates destination paths for a file located at `content/events/chicago/lollapalooza.md` in the same site:

+```bash

+                    section

+                    ⊢--^--⊣

+                               url

+                    ⊢-------------^------------⊣

+      baseURL             path        slug

+⊢--------^--------⊣ ⊢------^-----⊣⊢----^------⊣

+                  permalink

+⊢----------------------^-----------------------⊣

+http://yoursite.com/events/chicago/lollapalooza/

+```

+{{% note %}}

+As of v0.20, Hugo does not recognize nested sections. While you can nest as many content *directories* as you'd like, any child directory of a section will still be considered the same section as that of its parents. Therefore, in the above example, `{{.Section}}` for `lollapalooza.md` is `events` and *not* `chicago`. See the [related issue on GitHub](https://github.com/gohugoio/hugo/issues/465).

+{{% /note %}}

+## Paths Explained

+The following concepts will provide more insight into the relationship between your project's organization and the default behaviors of Hugo when building the output website.

+### `section`

+A default content type is determined by a piece of content's section. `section` is determined by the location within the project's `content` directory. `section` *cannot* be specified or overridden in front matter.

+### `slug`

+A content's `slug` is either `name.extension` or `name/`. The value for `slug` is determined by

+* the name of the content file (e.g., `lollapalooza.md`) OR

+* front matter overrides

+### `path`

+A content's `path` is determined by the section's path to the file. The file `path`

+* is based on the path to the content's location AND

+* does not include the slug

+### `url`

+The `url` is the relative URL for the piece of content. The `url`

+* is based on the content's location within the directory structure OR

+* is defined in front matter and *overrides all the above*

+## Override Destination Paths via Front Matter

+Hugo believes that you organize your content with a purpose. The same structure that works to organize your source content is used to organize the rendered site. As displayed above, the organization of the source content will be mirrored in the destination.

+There are times where you may need more control over your content. In these cases, there are fields that can be specified in the front matter to determine the destination of a specific piece of content.

+The following items are defined in this order for a specific reason: items explained further down in the list will override earlier items, and not all of these items can be defined in front matter:

+### `filename`

+This isn't in the front matter, but is the actual name of the file minus the extension. This will be the name of the file in the destination (e.g., `content/posts/my-post.md` becomes `yoursite.com/posts/my-post/`).

+### `slug`

+When defined in the front matter, the `slug` can take the place of the filename for the destination.

+{{% code file="content/posts/old-post.md" %}}

+```yaml

+---

+title: New Post

+slug: "new-post"

+---

+```

+{{% /code %}}

+This will render to the following destination according to Hugo's default behavior:

+```

+yoursite.com/posts/new-post/

+```

+### `section`

+`section` is determined by a content's location on disk and *cannot* be specified in the front matter. See [sections][] for more information.

+### `type`

+A content's `type` is also determined by its location on disk but, unlike `section`, it *can* be specified in the front matter. See [types][]. This can come in especially handy when you want a piece of content to render using a different layout. In the following example, you can create a layout at `layouts/new/mylayout.html` that Hugo will use to render this piece of content, even in the midst of many other posts.

+{{% code file="content/posts/my-post.md" %}}

+```yaml

+---

+title: My Post

+type: new

+layout: mylayout

+---

+```

+{{% /code %}}

+<!-- See https://discourse.gohugo.io/t/path-not-works/6387 -->

+<!-- ### `path`

+`path` can be provided in the front matter. This will replace the actual path to the file on disk. Destination will create the destination with the same path, including the section. -->

+### `url`

+A complete URL can be provided. This will override all the above as it pertains to the end destination. This must be the path from the baseURL (starting with a `/`). `url` will be used exactly as it provided in the front matter and will ignore the `--uglyURLs` setting in your site configuration:

+{{% code file="content/posts/old-url.md" %}}

+```yaml

+---

+title: Old URL

+url: /blog/new-url/

+---

+```

+{{% /code %}}

+Assuming your `baseURL` is [configured][config] to `https://yoursite.com`, the addition of `url` to the front matter will make `old-url.md` render to the following destination:

+```

+https://yoursite.com/blog/new-url/

+```

+You can see more information on how to control output paths in [URL Management][urls].

+[config]: /getting-started/configuration/

+[formats]: /content-management/formats/

+[front matter]: /content-management/front-matter/

+[getpage]: /functions/getpage/

+[homepage template]: /templates/homepage/

+[homepage]: /templates/homepage/

+[lists]: /templates/lists/

+[pretty]: /content-management/urls/#pretty-urls

+[section templates]: /templates/section-templates/

+[sections]: /content-management/sections/

+[singles]: /templates/single-page-templates/

+[taxonomy templates]: /templates/taxonomy-templates/

+[taxonomy terms templates]: /templates/taxonomy-templates/

+[types]: /content-management/types/

+[urls]: /content-management/urls/

--- /dev/null

+++ b/content/content-management/sections.md

@@ -1,0 +1,73 @@

+---

+title: Content Sections

+linktitle: Sections

+description: Hugo supports content sections, which according to Hugo's default behavior, will reflect the structure of the rendered website.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [content management]

+#tags: [lists,sections,content types,organization]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 50

+weight: 50	#rem

+draft: false

+aliases: [/content/sections/]

+toc: true

+---

+{{% note %}}

+This section is not updated with the new nested sections support in Hugo 0.24, see https://github.com/gohugoio/hugoDocs/issues/36

+{{% /note %}}

+{{% todo %}}

+See above

+{{% /todo %}}

+Hugo believes that you organize your content with a purpose. The same structure that works to organize your source content is used to organize the rendered site (see [directory structure][]).

+Following this pattern, Hugo uses the top level of your content organization as the content **section**.

+The following example shows a content directory structure for a website that has three sections: "authors," "events," and "posts":

+```bash

+.

+└── content

+    ├── authors

+    |   ├── _index.md     // <- yoursite.com/authors/

+    |   ├── john-doe.md   // <- yoursite.com/authors/john-doe/

+    |   └── jane-doe.md   // <- yoursite.com/authors/jane-doe/

+    └── events

+    |   ├── _index.md     // <- yoursite.com/events/

+    |   ├── event-1.md    // <- yoursite.com/events/event-1/

+    |   ├── event-2.md    // <- yoursite.com/events/event-2/

+    |   └── event-3.md    // <- yoursite.com/events/event-3/

+    └── posts

+    |   ├── _index.md     // <- yoursite.com/posts/

+    |   ├── event-1.md    // <- yoursite.com/posts/event-1/

+    |   ├── event-2.md    // <- yoursite.com/posts/event-2/

+    |   ├── event-3.md    // <- yoursite.com/posts/event-3/

+    |   ├── event-4.md    // <- yoursite.com/posts/event-4/

+    |   └── event-5.md    // <- yoursite.com/posts/event-5/

+```

+## Content Section Lists

+Hugo will automatically create pages for each section root that list all of the content in that section. See the documentation on [section templates][] for details on customizing the way these pages are rendered.

+As of Hugo v0.18, section pages can also have a content file and front matter. These section content files must be placed in their corresponding section folder and named `_index.md` in order for Hugo to correctly render the front matter and content.

+{{% warning "`index.md` vs `_index.md`" %}}

+Hugo themes developed before v0.18 often used an `index.md`(i.e., without the leading underscore [`_`]) in a content section as a hack to emulate the behavior of `_index.md`. The hack may work...*sometimes*; however, the order of page rendering can be unpredictable in Hugo. What works now may fail to render appropriately as your site grows. It is **strongly advised** to use `_index.md` as content for your section index pages. **Note:** `_index.md`'s layout, as representative of a section, is a [list page template](/templates/section-templates/) and *not* a [single page template](/templates/single-page-templates/). If you want to alter the new default behavior for `_index.md`, configure `disableKinds` accordingly in your [site's configuration](/getting-started/configuration/).

+{{% /warning %}}

+## Content *Section* vs Content *Type*

+By default, everything created within a section will use the [content type][] that matches the section name. For example, Hugo will assume that `posts/post-1.md` has a `posts` content type. If you are using an [archetype][] for your posts section, Hugo will generate front matter according to what it finds in `archetypes/posts.md`.

+[archetype]: /content-management/archetypes/

+[content type]: /content-management/types/

+[directory structure]: /getting-started/directory-structure/

+[section templates]: /templates/section-templates/

--- /dev/null

+++ b/content/content-management/shortcodes.md

@@ -1,0 +1,431 @@

+---

+title: Shortcodes

+linktitle:

+description: Shortcodes are simple snippets inside your content files calling built-in or custom templates.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-31

+menu:

+  docs:

+    parent: "content-management"

+    weight: 35

+weight: 35	#rem

+categories: [content management]

+#tags: [markdown,content,shortcodes]

+draft: false

+aliases: [/extras/shortcodes/]

+toc: true

+---

+## What a Shortcode is

+Hugo loves Markdown because of its simple content format, but there are times when Markdown falls short. Often, content authors are forced to add raw HTML (e.g., video `<iframes>`) to Markdown content. We think this contradicts the beautiful simplicity of Markdown's syntax.

+Hugo created **shortcodes** to circumvent these limitations.

+A shortcode is a simple snippet inside a content file that Hugo will render using a predefined template. Note that shortcodes will not work in template files. If you need the type of drop-in functionality that shortcodes provide but in a template, you most likely want a [partial template][partials] instead.

+In addition to cleaner Markdown, shortcodes can be updated any time to reflect new classes, techniques, or standards. At the point of site generation, Hugo shortcodes will easily merge in your changes. You avoid a possibly complicated search and replace operation.

+## Use Shortcodes

+In your content files, a shortcode can be called by calling `{{%/* shortcodename parameters */%}}`. Shortcode parameters are space delimited, and parameters with internal spaces can be quoted.

+The first word in the shortcode declaration is always the name of the shortcode. Parameters follow the name. Depending upon how the shortcode is defined, the parameters may be named, positional, or both, although you can't mix parameter types in a single call. The format for named parameters models that of HTML with the format `name="value"`.

+Some shortcodes use or require closing shortcodes. Again like HTML, the opening and closing shortcodes match (name only) with the closing declaration, which is prepended with a slash.

+Here are two examples of paired shortcodes:

+```md

+{{%/* mdshortcode */%}}Stuff to `process` in the *center*.{{%/* /mdshortcode */%}}

+```

+```md

+{{</* highlight go */>}} A bunch of code here {{</* /highlight */>}}

+```

+The examples above use two different delimiters, the difference being the `%` character in the first and the `<>` characters in the second.

+### Shortcodes with Markdown

+The `%` character indicates that the shortcode's inner content---called in the [shortcode template][sctemps] with the [`.Inner` variable][scvars]---needs further processing by the page's rendering processor (i.e. markdown via Blackfriday). In the following example, Blackfriday would convert `**World**` to `<strong>World</strong>`:

+```md

+{{%/* myshortcode */%}}Hello **World!**{{%/* /myshortcode */%}}

+```

+### Shortcodes Without Markdown

+The `<` character indicates that the shortcode's inner content does *not* need further rendering. Often shortcodes without markdown include internal HTML:

+```md

+{{</* myshortcode */>}}<p>Hello <strong>World!</strong></p>{{</* /myshortcode */>}}

+```

+### Nested Shortcodes

+You can call shortcodes within other shortcodes by creating your own templates that leverage the `.Parent` variable. `.Parent` allows you to check the context in which the shortcode is being called. See [Shortcode templates][sctemps].

+## Use Hugo's Built-in Shortcodes

+Hugo ships with a set of predefined shortcodes that represent very common usage. These shortcodes are provided for author convenience and to keep your markdown content clean.

+### `figure`

+`figure` is an extension of the image syntax in markdown, which does not provide a shorthand for the more semantic [HTML5 `<figure>` element][figureelement].

+The `figure` shortcode can use the following named parameters:

+* `src`

+* `link`

+* `title`

+* `caption`

+* `class`

+* `attr` (i.e., attribution)

+* `attrlink`

+* `alt`

+#### Example `figure` Input

+{{% code file="figure-input-example.md" %}}

+```markdown

+{{</* figure src="/media/spf13.jpg" title="Steve Francia" */>}}

+```

+{{% /code %}}

+#### Example `figure` Output

+{{% output file="figure-output-example.html" %}}

+```html

+<figure>

+  <img src="/media/spf13.jpg"  />

+  <figcaption>

+      <h4>Steve Francia</h4>

+  </figcaption>

+</figure>

+```

+{{% /output %}}

+### `gist`

+Bloggers often want to include GitHub gists when writing posts. Let's suppose we want to use the [gist at the following url][examplegist]:

+```html

+https://gist.github.com/spf13/7896402

+```

+We can embed the gist in our content via username and gist ID pulled from the URL:

+```md

+{{</* gist spf13 7896402 */>}}

+```

+#### Example `gist` Input

+If the gist contains several files and you want to quote just one of them, you can pass the filename (quoted) as an optional third argument:

+{{% code file="gist-input.md" %}}

+```md

+{{</* gist spf13 7896402 "img.html" */>}}

+```

+{{% /code %}}

+#### Example `gist` Output

+{{% output file="gist-output.html" %}}

+```html

+{{< gist spf13 7896402 >}}

+```

+{{% /output %}}

+#### Example `gist` Display

+To demonstrate the remarkably efficiency of Hugo's shortcode feature, we have embedded the `spf13` `gist` example in this page. The following simulates the experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.

+{{< gist spf13 7896402 >}}

+### `highlight`

+This shortcode will convert the source code provided into syntax-highlighted HTML. Read more on [highlighting](/tools/syntax-highlighting/). `highlight` takes exactly one required `language` parameter and requires a closing shortcode.

+#### Example `highlight` Input

+{{% code file="content/tutorials/learn-html.md" %}}

+```html

+{{</* highlight html */>}}

+<section id="main">

+  <div>

+   <h1 id="title">{{ .Title }}</h1>

+    {{ range .Data.Pages }}

+        {{ .Render "summary"}}

+    {{ end }}

+  </div>

+</section>

+{{</* /highlight */>}}

+```

+{{% /code %}}

+#### Example `highlight` Output

+The `highlight` shortcode example above would produce the following HTML when the site is rendered:

+{{% output file="tutorials/learn-html/index.html" %}}

+```html

+<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 }}

+        {{ .Render &quot;summary&quot;}}

+    {{ end }}

+  <span style="color: #f92672">&lt;/div&gt;</span>

+<span style="color: #f92672">&lt;/section&gt;</span>

+```

+{{% /output %}}

+{{% note "More on Syntax Highlighting" %}}

+To see even more options for adding syntax-highlighted code blocks to your website, see [Syntax Highlighting in Developer Tools](/tools/syntax-highlighting/).

+{{% /note %}}

+### `instagram`

+If you'd like to embed a photo from [Instagram][], you only need the photo's ID. You can discern an Instagram photo ID from the URL:

+```html

+https://www.instagram.com/p/BWNjjyYFxVx/

+```

+#### Example `instagram` Input

+{{% code file="instagram-input.md" %}}

+```md

+{{</* instagram BWNjjyYFxVx */>}}

+```

+{{% /code %}}

+You also have the option to hide the caption:

+{{% code file="instagram-input-hide-caption.md" %}}

+```md

+{{</* instagram BWNjjyYFxVx hidecaption */>}}

+```

+{{% /code %}}

+#### Example `instagram` Output

+By adding the preceding `hidecaption` example, the following HTML will be added to your rendered website's markup:

+{{% output file="instagram-hide-caption-output.html" %}}

+```html

+{{< instagram BWNjjyYFxVx hidecaption >}}

+```

+{{% /output %}}

+#### Example `instagram` Display

+Using the preceding `instagram` with hidecaption` example above, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.

+{{< instagram BWNjjyYFxVx hidecaption >}}

+### `ref` and `relref`

+These shortcodes will look up the pages by their relative path (e.g., `blog/post.md`) or their logical name (`post.md`) and return the permalink (`ref`) or relative permalink (`relref`) for the found page.

+`ref` and `relref` also make it possible to make fragmentary links that work for the header links generated by Hugo.

+{{% note "More on Cross References" %}}

+Read a more extensive description of `ref` and `relref` in the [cross references](/content-management/cross-references/) documentation.

+{{% /note %}}

+`ref` and `relref` take exactly one required parameter of _reference_, quoted and in position `0`.

+#### Example `ref` and `relref` Input

+```md

+[Neat]({{</* ref "blog/neat.md" */>}})

+[Who]({{</* relref "about.md#who" */>}})

+```

+#### Example `ref` and `relref` Output

+Assuming that standard Hugo pretty URLs are turned on.

+```html

+<a href="/blog/neat">Neat</a>

+<a href="/about/#who:c28654c202e73453784cfd2c5ab356c0">Who</a>

+```

+### `speakerdeck`

+To embed slides from [Speaker Deck][], click on "&lt;&#8239;/&gt;&nbsp;Embed" (under Share right next to the template on Speaker Deck) and copy the URL:

+```html

+<script async class="speakerdeck-embed" data-id="4e8126e72d853c0060001f97" data-ratio="1.33333333333333" src="//speakerdeck.com/assets/embed.js"></script>

+```

+#### `speakerdeck` Example Input

+Extract the value from the field `data-id` and pass it to the shortcode:

+{{% code file="speakerdeck-example-input.md" %}}

+```md

+{{</* speakerdeck 4e8126e72d853c0060001f97 */>}}

+```

+{{% /code %}}

+#### `speakerdeck` Example Output

+{{% output file="speakerdeck-example-input.md" %}}

+```html

+{{< speakerdeck 4e8126e72d853c0060001f97 >}}

+```

+{{% /output %}}

+#### `speakerdeck` Example Display

+For the preceding `speakerdeck` example, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.

+{{< speakerdeck 4e8126e72d853c0060001f97 >}}

+### `tweet`

+You want to include a single tweet into your blog post? Everything you need is the URL of the tweet:

+```

+https://twitter.com/spf13/status/877500564405444608

+```

+#### Example `tweet` Input

+Pass the tweet's ID from the URL as a parameter to the `tweet` shortcode:

+{{% code file="example-tweet-input.md" %}}

+```md

+{{</* tweet 877500564405444608 */>}}

+```

+{{% /code %}}

+#### Example `tweet` Output

+Using the preceding `tweet` example, the following HTML will be added to your rendered website's markup:

+{{% output file="example-tweet-output.html" %}}

+```html

+{{< tweet 877500564405444608 >}}

+```

+{{% /output %}}

+#### Example `tweet` Display

+Using the preceding `tweet` example, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.

+{{< tweet 877500564405444608 >}}

+### `vimeo`

+Adding a video from [Vimeo][] is equivalent to the YouTube shortcode above.

+```

+https://vimeo.com/channels/staffpicks/146022717

+```

+#### Example `vimeo` Input

+Extract the ID from the video's URL and pass it to the `vimeo` shortcode:

+{{% code file="example-vimeo-input.md" %}}

+```md

+{{</* vimeo 146022717 */>}}

+```

+{{% /code %}}

+#### Example `vimeo` Output

+Using the preceding `vimeo` example, the following HTML will be added to your rendered website's markup:

+{{% output file="example-vimeo-output.html" %}}

+```html

+{{< vimeo 146022717 >}}

+```

+{{% /output %}}

+{{% tip %}}

+If you want to further customize the visual styling of the YouTube or Vimeo output, add a `class` named parameter when calling the shortcode. The new `class` will be added to the `<div>` that wraps the `<iframe>` *and* will remove the inline styles. Note that you will need to call the `id` as a named parameter as well.

+```md

+{{</* vimeo id="146022717" class="my-vimeo-wrapper-class" */>}}

+```

+{{% /tip %}}

+#### Example `vimeo` Display

+Using the preceding `vimeo` example, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.

+{{< vimeo 146022717 >}}

+### `youtube`

+The `youtube` shortcode embeds a responsive video player for [YouTube videos][]. Only the ID of the video is required, e.g.:

+```

+https://www.youtube.com/watch?v=w7Ft2ymGmfc

+```

+#### Example `youtube` Input

+Copy the YouTube video ID that follows `v=` in the video's URL and pass it to the `youtube` shortcode:

+{{% code file="example-youtube-input.md" %}}

+```md

+{{</* youtube w7Ft2ymGmfc */>}}

+```

+{{% /code %}}

+Furthermore, you can automatically start playback of the embedded video by setting the `autoplay` parameter to `true`. Remember that you can't mix named an unnamed parameters, so you'll need to assign the yet unnamed video id to the parameter `id`:

+{{% code file="example-youtube-input-with-autoplay.md" %}}

+```md

+{{</* youtube id="w7Ft2ymGmfc" autoplay="true" */>}}

+```

+{{% /code %}}

+#### Example `youtube` Output

+Using the preceding `youtube` example, the following HTML will be added to your rendered website's markup:

+{{% code file="example-youtube-output.html" %}}

+```html

+{{< youtube id="w7Ft2ymGmfc" autoplay="true" >}}

+```

+{{% /code %}}

+#### Example `youtube` Display

+Using the preceding `youtube` example (without `autoplay="true"`), the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup. The video is also include in the [Quick Start of the Hugo documentation][quickstart].

+{{< youtube w7Ft2ymGmfc >}}

+## Create Custom Shortcodes

+To learn more about creating custom shortcodes, see the [shortcode template documentation][].

+[`figure` shortcode]: #figure

+[contentmanagementsection]: /content-management/formats/

+[examplegist]: https://gist.github.com/spf13/7896402

+[figureelement]: http://html5doctor.com/the-figure-figcaption-elements/ "An article from HTML5 doctor discussing the fig and figcaption elements."

+[Instagram]: https://www.instagram.com/

+[pagevariables]: /variables/page/

+[partials]: /templates/partials/

+[Pygments]: http://pygments.org/

+[quickstart]: /getting-started/quick-start/

+[sctemps]: /templates/shortcode-templates/

+[scvars]: /variables/shortcodes/

+[shortcode template documentation]: /templates/shortcode-templates/

+[Speaker Deck]: https://speakerdeck.com/

+[templatessection]: /templates/

+[Vimeo]: https://vimeo.com/

+[YouTube Videos]: https://www.youtube.com/

--- /dev/null

+++ b/content/content-management/summaries.md

@@ -1,0 +1,83 @@

+---

+title: Content Summaries

+linktitle: Summaries

+description: Hugo generates summaries of your content.

+date: 2017-01-10

+publishdate: 2017-01-10

+lastmod: 2017-01-10

+categories: [content management]

+#tags: [summaries,abstracts,read more]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 90

+weight: 90	#rem

+draft: false

+aliases: [/content/summaries/,/content-management/content-summaries/]

+toc: true

+---

+With the use of the `.Summary` [page variable][pagevariables], Hugo generates summaries of content to use as a short version in summary views.

+## Summary Splitting Options

+* Hugo-defined Summary Split

+* User-defined Summary Split

+It is natural to accompany the summary with links to the original content, and a common design pattern is to see this link in the form of a "Read More ..." button. See the `.RelPermalink`, `.Permalink`, and `.Truncated` [page variables][pagevariables].

+### Hugo-defined: Automatic Summary Splitting

+By default, Hugo automatically takes the first 70 words of your content as its summary and stores it into the `.Summary` page variable for use in your templates. Taking the Hugo-defined approach to summaries may save time, but it has pros and cons:

+* **Pros:** Automatic, no additional work on your part.

+* **Cons:** All HTML tags are stripped from the summary, and the first 70 words, whether they belong to a heading or to different paragraphs, are all put into one paragraph.

+{{% note %}}

+The Hugo-defined summaries are set to use word count calculated by splitting the text by one or more consecutive white space characters. If you are creating content in a `CJK` language and want to use Hugo's automatic summary splitting, set `hasCJKLanguage` to `true` in you [site configuration](/getting-started/configuration/).

+{{% /note %}}

+### User-defined: Manual Summary Splitting

+Alternatively, you may add the <code>&#60;&#33;&#45;&#45;more&#45;&#45;&#62;</code> summary divider where you want to split the article. For [org content][org], use `# more` where you want to split the article. Content that comes before the summary divider will be used as that content's summary and stored in the `.Summary` page variable with all HTML formatting intact.

+{{% note "Summary Divider"%}}

+The concept of a *summary divider* is not unique to Hugo. It is also called the "more tag" or "excerpt separator" in other literature.

+{{% /note %}}

+* Pros: Freedom, precision, and improved rendering.  All HTML tags and formatting are preserved.

+* Cons: Extra work for content authors, since they need to remember to type <code>&#60;&#33;&#45;&#45;more&#45;&#45;&#62;</code> (or `# more` for [org content][org]) in each content file. This can be automated by adding the summary divider below the front matter of an [archetype](/content-management/archetypes/).

+{{% warning "Be Precise with the Summary Divider" %}}

+Be careful to enter <code>&#60;&#33;&#45;&#45;more&#45;&#45;&#62;</code> exactly; i.e., all lowercase and with no whitespace.

+{{% /warning %}}

+## Example: First 10 Articles with Summaries

+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" %}}

+```html

+{{ range first 10 .Data.Pages }}

+    <article>

+      <!-- this <div> includes the title summary -->

+      <div>

+        <h2><a href="{{ .RelPermalink }}">{{ .Title }}</a></h2>

+        {{ .Summary }}

+      </div>

+      {{ if .Truncated }}

+      <!-- This <div> includes a read more link, but only if the summary is truncated... -->

+      <div>

+        <a href="{{ .RelPermalink }}">Read More…</a>

+      </div>

+      {{ end }}

+    </article>

+{{ end }}

+```

+{{% /code %}}

+Note how the `.Truncated` boolean valuable may be used to hide the "Read More..." link when the content is not truncated; i.e., when the summary contains the entire article.

+[org]: /content-management/formats/

+[pagevariables]: /variables/page/

+[section template]: /templates/section-templates/

\ No newline at end of file

--- /dev/null

+++ b/content/content-management/taxonomies.md

@@ -1,0 +1,238 @@

+---

+title: Taxonomies

+linktitle:

+description: Hugo includes support for user-defined taxonomies to help you  demonstrate logical relationships between content for the end users of your website.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [taxonomies,metadata,front matter,terms]

+categories: [content management]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 80

+weight: 80	#rem

+draft: false

+aliases: [/taxonomies/overview/,/taxonomies/usage/,/indexes/overview/,/doc/indexes/,/extras/indexes]

+toc: true

+---

+## What is a Taxonomy?

+Hugo includes support for user-defined groupings of content called **taxonomies**. Taxonomies are classifications of logical relationships between content.

+### Definitions

+Taxonomy

+: a categorization that can be used to classify content

+Term

+: a key within the taxonomy

+Value

+: a piece of content assigned to a term

+## Example Taxonomy: Movie Website

+Let's assume you are making a website about movies. You may want to include the following taxonomies:

+* Actors

+* Directors

+* Studios

+* Genre

+* Year

+* Awards

+Then, in each of the movies, you would specify terms for each of these taxonomies (i.e., in the [front matter][] of each of your movie content files). From these terms, Hugo would automatically create pages for each Actor, Director, Studio, Genre, Year, and Award, with each listing all of the Movies that matched that specific Actor, Director, Studio, Genre, Year, and Award.

+### Movie Taxonomy Organization

+To continue with the example of a movie site, the following demonstrates content relationships from the perspective of the taxonomy:

+```

+Actor                    <- Taxonomy

+    Bruce Willis         <- Term

+        The Six Sense    <- Content

+        Unbreakable      <- Content

+        Moonrise Kingdom <- Content

+    Samuel L. Jackson    <- Term

+        Unbreakable      <- Content

+        The Avengers     <- Content

+        xXx              <- Content

+```

+From the perspective of the content, the relationships would appear differently, although the data and labels used are the same:

+```

+Unbreakable                 <- Content

+    Actors                  <- Taxonomy

+        Bruce Willis        <- Term

+        Samuel L. Jackson   <- Term

+    Director                <- Taxonomy

+        M. Night Shyamalan  <- Term

+    ...

+Moonrise Kingdom            <- Content

+    Actors                  <- Taxonomy

+        Bruce Willis        <- Term

+        Bill Murray         <- Term

+    Director                <- Taxonomy

+        Wes Anderson        <- Term

+    ...

+```

+## Hugo Taxonomy Defaults

+Hugo natively supports taxonomies.

+Without adding a single line to your site's configuration file, Hugo will automatically create taxonomies for `tags` and `categories`. If you do not want Hugo to create any taxonomies, set `disableKinds` in your site's configuration to the following:

+```toml

+disableKinds = ["taxonomy","taxonomyTerm"]

+```

+### Default Destinations

+When taxonomies are used---and [taxonomy templates][] are provided---Hugo will automatically create both a page listing all the taxonomy's terms and individual pages with lists of content associated with each term. For example, a `categories` taxonomy declared in your your configuration and used in your content front matter will create the following pages:

+* A single page at `yoursite.com/categories/` that lists all the [terms within the taxonomy][]

+* [Individual taxonomy list pages][taxonomy templates] (e.g., `/categories/development/`) for each of the terms that shows a listing of all pages marked as part of that taxonomy within any content file's [front matter][]

+## Configure Taxonomies

+Taxonomies must be defined in your [website configuration][config] before they can be used throughout the site. You need to provide both the plural and singular labels for each taxonomy. For example, `singular key = "plural value"` for TOML and `singular key: "plural value"` for YAML.

+### Example: TOML Taxonomy Configuration

+```toml

+[taxonomies]

+  tag = "tags"

+  category = "categories"

+  series = "series"

+```

+### Example: YAML Taxonomy Configuration

+```yaml

+taxonomies:

+  tag: "tags"

+  category: "categories"

+  series: "series"

+```

+### Preserve Taxonomy Values

+By default, taxonomy names are normalized.

+Therefore, if you want to have a taxonomy term with special characters such as `Gérard Depardieu` instead of `Gerard Depardieu`, set the value for `preserveTaxonomyNames` to `true` in your [site configuration][config]. Hugo will then preserve special characters in taxonomy values but will still title-ize the values for titles and normalize them in URLs.

+Note that if you use `preserveTaxonomyNames` and intend to manually construct URLs to the archive pages, you will need to pass the taxonomy values through the [`urlize` template function][].

+{{% note %}}

+You can add content and front matter to your taxonomy list and taxonomy terms pages. See [Content Organization](/content-management/organization/) for more information on how to add an `_index.md` for this purpose.

+Note also that taxonomy [permalinks](/content-management/urls/) are *not* configurable.

+{{% /note %}}

+## Add Taxonomies to Content

+Once a taxonomy is defined at the site level, any piece of content can be assigned to it, regardless of [content type][] or [content section][].

+Assigning content to a taxonomy is done in the [front matter][]. Simply create a variable with the *plural* name of the taxonomy and assign all terms you want to apply to the instance of the content type.

+{{% note %}}

+If you would like the ability to quickly generate content files with preconfigured taxonomies or terms, read the docs on [Hugo archetypes](/content-management/archetypes/).

+{{% /note %}}

+### Example: TOML Front Matter with Taxonomies

+```toml

++++

+title = "Hugo: A fast and flexible static site generator"

+tags = [ "Development", "Go", "fast", "Blogging" ]

+categories = [ "Development" ]

+series = [ "Go Web Dev" ]

+slug = "hugo"

+project_url = "https://github.com/gohugoio/hugo"

++++

+```

+### Example: YAML Front Matter with Taxonomies

+```yaml

+---

+title: "Hugo: A fast and flexible static site generator"

+#tags: ["Development", "Go", "fast", "Blogging"]

+categories: ["Development"]

+categories: ["Go Web Dev"]

+slug: "hugo"

+project_url: "https://github.com/gohugoio/hugo"

+---

+```

+### Example: JSON Front Matter with Taxonomies

+```json

+{

+    "title": "Hugo: A fast and flexible static site generator",

+    "tags": [

+        "Development",

+        "Go",

+        "fast",

+        "Blogging"

+    ],

+    "categories" : [

+        "Development"

+    ],

+    "series" : [

+        "Go Web Dev"

+    ],

+    "slug": "hugo",

+    "project_url": "https://github.com/gohugoio/hugo"

+}

+```

+## Order Taxonomies

+A content file can assign weight for each of its associate taxonomies. Taxonomic weight can be used for sorting or ordering content in [taxonomy list templates][] and is declared in a content file's [front matter][]. The convention for declaring taxonomic weight is `taxonomyname_weight`.

+The following TOML and YAML examples show a piece of content that has a weight of 22, which can be used for ordering purposes when rendering the pages assigned to the "a", "b" and "c" values of the `tags` taxonomy. It has also been assigned the weight of 44 when rendering the "d" category page.

+### Example: TOML Taxonomic `weight`

+```toml

++++

+title = "foo"

+tags = [ "a", "b", "c" ]

+tags_weight = 22

+categories = ["d"]

+categories_weight = 44

++++

+```

+### Example: YAML Taxonomic `weight`

+```yaml

+---

+title: foo

+#tags: [ "a", "b", "c" ]

+tags_weight: 22

+categories: ["d"]

+categories_weight: 44

+---

+```

+By using taxonomic weight, the same piece of content can appear in different positions in different taxonomies.

+{{% note "Limits to Ordering Taxonomies" %}}

+Currently taxonomies only support the [default `weight => date` ordering of list content](/templates/lists/#default-weight-date). For more information, see the documentation on [taxonomy templates](/templates/taxonomy-templates/).

+{{% /note %}}

+[`urlize` template function]: /functions/urlize/

+[content section]: /content-management/sections/

+[content type]: /content-management/types/

+[documentation on archetypes]: /content-management/archetypes/

+[front matter]: /content-management/front-matter/

+[taxonomy list templates]: /templates/taxonomy-templates/#taxonomy-page-templates

+[taxonomy templates]: /templates/taxonomy-templates/

+[terms within the taxonomy]: /templates/taxonomy-templates/#taxonomy-terms-templates "See how to order terms associated with a taxonomy"

+[config]: /getting-started/configuration/

--- /dev/null

+++ b/content/content-management/toc.md

@@ -1,0 +1,95 @@

+---

+title: Table of Contents

+linktitle:

+description: Hugo can automatically parse Markdown content and create a Table of Contents you can use in your templates.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [content management]

+#tags: [table of contents, toc]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 130

+weight: 130	#rem

+draft: false

+aliases: [/extras/toc/,/content-management/toc/]

+toc: true

+---

+{{% note "TOC Heading Levels are Fixed" %}}

+Currently, the `{{.TableOfContents}}` [page variable](/variables/page/) does not allow you to specify which heading levels you want the TOC to render. [See the related GitHub discussion (#1778)](https://github.com/gohugoio/hugo/issues/1778). As such, the resulting `<nav id="TableOfContents"><ul></ul></nav>` is going to start at `<h1>` when pulling from `{{.Content}}`.

+{{% /note %}}

+## Usage

+Create your markdown the way you normally would with the appropriate headings. Here is some example content:

+```md

+<!-- Your front matter up here -->

+## Introduction

+One morning, when Gregor Samsa woke from troubled dreams, he found himself transformed in his bed into a horrible vermin.

+## My Heading

+He lay on his armour-like back, and if he lifted his head a little he could see his brown belly, slightly domed and divided by arches into stiff sections. The bedding was hardly able to cover it and seemed ready to slide off any moment.

+### My Subheading

+A collection of textile samples lay spread out on the table - Samsa was a travelling salesman - and above it there hung a picture that he had recently cut out of an illustrated magazine and housed in a nice, gilded frame. It showed a lady fitted out with a fur hat and fur boa who sat upright, raising a heavy fur muff that covered the whole of her lower arm towards the viewer. Gregor then turned to look out the window at the dull weather. Drops

+```

+Hugo will take this Markdown and create a table of contents from `## Introduction`, `## My Heading`, and `### My Subheading` and then store it in the [page variable][pagevars]`.TableOfContents`.

+The built-in `.TableOfContents` variables outputs a `<nav id="TableOfContents">` element with a child `<ul>`, whose child `<li>` elements begin with any `<h1>`'s (i.e., `#` in markdown) inside your content.'

+## Template Example: Basic TOC

+The following is an example of a very basic [single page template][]:

+{{% code file="layout/_default/single.html" download="single.html" %}}

+```html

+{{ define "main" }}

+<main>

+    <article>

+    <header>

+        <h1>{{ .Title }}</h1>

+    </header>

+        {{ .Content }}

+    </article>

+    <aside>

+        {{ .TableOfContents }}

+    </aside>

+</main>

+{{ end }}

+```

+{{% /code %}}

+## Template Example: TOC Partial

+The following is a [partial template][partials] that adds slightly more logic for page-level control over your table of contents. It assumes you are using a `toc` field in your content's [front matter][] that, unless specifically set to `false`, will add a TOC to any page with a `.WordCount` (see [Page Variables][pagevars]) greater than 400. This example also demonstrates how to use [conditionals][] in your templating:

+{{% code file="layouts/partials/toc.html" download="toc.html" %}}

+```html

+{{ if and (gt .WordCount 400 ) (ne .Params.toc "false") }}

+<aside>

+    <header>

+    <h2>{{.Title}}</h2>

+    </header>

+    {{.TableOfContents}}

+</aside>

+{{ end }}

+```

+{{% /code %}}

+{{% note %}}

+With the preceding example, even pages with > 400 words *and* `toc` not set to `false` will not render a table of contents if there are no headings in the page for the `{{.TableOfContents}}` variable to pull from.

+{{% /note %}}

+[conditionals]: /templates/introduction/#conditionals

+[front matter]: /content-management/table-of-contents/

+[pagevars]: /variables/page/

+[partials]: /templates/partials/

+[single page template]: /templates/single-page-templates/

\ No newline at end of file

--- /dev/null

+++ b/content/content-management/types.md

@@ -1,0 +1,101 @@

+---

+title: Content Types

+linktitle: Types

+description: Hugo supports sites with multiple content types and assumes your site will be organized into sections, where each section represents the corresponding type.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [content management]

+#tags: [lists,sections,content types,types,organization]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 60

+weight: 60	#rem

+draft: false

+aliases: [/content/types]

+toc: true

+---

+A **content type** can have a unique set of metadata (i.e., [front matter][]) or customized [template][] and can be created by the `hugo new` command via [archetypes][].

+## What is a Content Type

+[Tumblr][] is a good example of a website with multiple content types. A piece of "content" could be a photo, quote, or a post, each with different sets of metadata and different visual rendering.

+## Assign a Content Type

+Hugo assumes that your site will be organized into [sections][] and each section represents a corresponding type. This is to reduce the amount of configuration necessary for new Hugo projects.

+If you are taking advantage of this default behavior, each new piece of content you place into a section will automatically inherit the type. Therefore a new file created at `content/posts/new-post.md` will automatically be assigned the type `posts`. Alternatively, you can set the content type in a content file's [front matter][] in the field "`type`".

+## Create New Content of a Specific Type

+You can manually add files to your content directories, but Hugo can create and populate a new content file with preconfigured front matter via [archetypes][].

+## Define a Content Type

+Creating a new content type is easy. You simply define the templates and archetype unique to your new content type, or Hugo will use defaults.

+{{% note "Declaring Content Types" %}}

+Remember, all of the following are *optional*. If you do not specifically declare content types in your front matter or develop specific layouts for content types, Hugo is smart enough to assume the content type from the file path and section. (See [Content Sections](/content-management/sections/) for more information.)

+{{% /note %}}

+The following examples take you stepwise through creating a new type layout for a content file that contains the following front matter:

+{{% code file="content/events/my-first-event.md" copy="false" %}}

+```toml

++++

+title = My First Event

+date = "2016-06-24T19:20:04-07:00"

+description = "Today is my 36th birthday. How time flies."

+type = "event"

+layout = "birthday"

++++

+```

+{{% /code %}}

+By default, Hugo assumes `*.md` under `events` is of the `events` content type. However, we have specified that this particular file at `content/events/ my-first-event.md` is of type `event` and should render using the `birthday` layout.

+### Create a Type Layout Directory

+Create a directory with the name of the type in `/layouts`. For creating these custom layouts, **type is always singular**; e.g., `events => event` and `posts => post`.

+For this example, you need to create `layouts/event/birthday.html`.

+{{% note %}}

+If you have multiple content files in your `events` directory that are of the `special` type and you don't want to define the `layout` specifically for each piece of content, you can create a layout at `layouts/special/single.html` to observe the [single page template lookup order](/templates/single-page-templates/).

+{{% /note %}}

+{{% warning %}}

+With the "everything is a page" data model introduced in v0.18 (see [Content Organization](/content-management/organization/)), you can use `_index.md` in content directories to add both content and front matter to [list pages](/templates/lists/). However, `type` and `layout` declared in the front matter of `_index.md` are *not* currently respected at build time as of v0.19. This is a known issue [(#3005)](https://github.com/gohugoio/hugo/issues/3005).

+{{% /warning %}}

+### Create Views

+Many sites support rendering content in a few different ways; e.g., a single page view and a summary view to be used when displaying a [list of section contents][sectiontemplates].

+Hugo limits assumptions about how you want to display your content to an intuitive set of sane defaults and will support as many different views of a content type as your site requires. All that is required for these additional views is that a template exists in each `/layouts/<TYPE>` directory with the same name.

+### Custom Content Type Template Lookup Order

+The lookup order for the `content/events/my-first-event.md` templates would be as follows:

+* `layouts/event/birthday.html`

+* `layouts/event/single.html`

+* `layouts/events/single.html`

+* `layouts/_default/single.html`

+### Create a Corresponding Archetype

+We can then create a custom archetype with preconfigured front matter at `event.md` in the `/archetypes` directory; i.e. `archetypes/event.md`.

+Read [Archetypes][archetypes] for more information on archetype usage with `hugo new`.

+[archetypes]: /content-management/archetypes/

+[front matter]: /content-management/front-matter/

+[sectiontemplates]: /templates/section-templates/

+[sections]: /content-management/sections/

+[template]: /templates/

+[Tumblr]: https://www.tumblr.com/

\ No newline at end of file

--- /dev/null

+++ b/content/content-management/urls.md

@@ -1,0 +1,285 @@

+---

+title: URL Management

+linktitle: URL Management

+description: Hugo supports permalinks, aliases, link canonicalization, and multiple options for handling relative vs absolute URLs.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-09

+#tags: [aliases,redirects,permalinks,urls]

+categories: [content management]

+menu:

+  docs:

+    parent: "content-management"

+    weight: 110

+weight: 110	#rem

+draft: false

+aliases: [/extras/permalinks/,/extras/aliases/,/extras/urls/,/doc/redirects/,/doc/alias/,/doc/aliases/]

+toc: true

+---

+## Permalinks

+The default Hugo target directory for your built website is `public/`. However, you can change this value by specifying a different `publishDir` in your [site configuration][config]. The directories created at build time for a section reflect the position of the content's directory within the `content` folder and namespace matching its layout within the `contentdir` hierarchy.

+The `permalinks` option in your [site configuration][config] allows you to adjust the directory paths (i.e., the URLs) on a per-section basis. This will change where the files are written to and will change the page's internal "canonical" location, such that template references to `.RelPermalink` will honor the adjustments made as a result of the mappings in this option.

+{{% note "Default Publish and Content Folders" %}}

+These examples use the default values for `publishDir` and `contentDir`; i.e., `publish` and `content`, respectively. You can override the default values in your [site's `config` file](/getting-started/configuration/).

+{{% /note %}}

+For example, if one of your [sections][] is called `post` and you want to adjust the canonical path to be hierarchical based on the year, month, and post title, you could set up the following configurations in YAML and TOML, respectively.

+### YAML Permalinks Configuration Example

+{{% code file="config.yml" copy="false" %}}

+```yaml

+permalinks:

+  post: /:year/:month/:title/

+```

+{{% /code %}}

+### TOML Permalinks Configuration Example

+{{% code file="config.toml" copy="false" %}}

+```toml

+[permalinks]

+  post = "/:year/:month/:title/"

+```

+{{% /code %}}

+Only the content under `post/` will have the new URL structure. For example, the file `content/post/sample-entry.md` with `date: 2017-02-27T19:20:00-05:00` in its front matter will render to `public/2017/02/sample-entry/index.html` at build time and therefore be reachable at `http://yoursite.com/2013/11/sample-entry/`.

+### Permalink Configuration Values

+The following is a list of values that can be used in a `permalink` definition in your site `config` file. All references to time are dependent on the content's date.

+`:year`

+: the 4-digit year

+`:month`

+: the 2-digit month

+`:monthname`

+: the name of the month

+`:day`

+: the 2-digit day

+`:weekday`

+: the 1-digit day of the week (Sunday = 0)

+`:weekdayname`

+: the name of the day of the week

+`:yearday`

+: the 1- to 3-digit day of the year

+`:section`

+: the content's section

+`:title`

+: the content's title

+`:slug`

+: the content's slug (or title if no slug is provided in the front matter)

+`:filename`

+: the content's filename (without extension)

+## Aliases

+For people migrating existing published content to Hugo, there's a good chance you need a mechanism to handle redirecting old URLs.

+Luckily, redirects can be handled easily with **aliases** in Hugo.

+### Example: Aliases

+Let's assume you create a new piece of content at `content/posts/my-awesome-blog-post.md`. The content is a revision of your previous post at `content/posts/my-original-url.md`. You can create an `aliases` field in the front matter of your new `my-awesome-blog-post.md` where you can add previous paths. The following examples show how to create this filed in TOML and YAML front matter, respectively.

+#### TOML Front Matter

+{{% code file="content/posts/my-awesome-post.md" copy="false" %}}

+```toml

++++

+aliases = [

+    "/posts/my-original-url/",

+    "/2010/01/01/even-earlier-url.html"

+]

++++

+```

+{{% /code %}}

+#### YAML Front Matter

+{{% code file="content/posts/my-awesome-post.md" copy="false" %}}

+```yaml

+---

+aliases:

+    - /posts/my-original-url/

+    - /2010/01/01/even-earlier-url.html

+---

+```

+{{% /code %}}

+Now when you visit any of the locations specified in aliases---i.e., *assuming the same site domain*---you'll be redirected to the page they are specified on. For example, a visitor to `yoursite.com/posts/my-original-url/` will be immediately redirected to `yoursite.com/posts/my-awesome-blog-post/`.

+### Example: Aliases in Multilingual

+On [multilingual sites][multilingual], each translation of a post can have unique aliases. To use the same alias across multiple languages, prefix it with the language code.

+In `/posts/my-new-post.es.md`:

+```yaml

+---

+aliases:

+    - /es/posts/my-original-post/

+---

+```

+### How Hugo Aliases Work

+When aliases are specified, Hugo creates a directory to match the alias entry. Inside the directory, Hugo creates an `.html` file specifying the canonical URL for the page and the new redirect target.

+For example, a content file at `posts/my-intended-url.md` with the following in the front matter:

+```yaml

+---

+title: My New post

+aliases: [/posts/my-old-url/]

+---

+```

+Assuming a `baseURL` of `yoursite.com`, the contents of the auto-generated alias `.html` found at `https://yoursite.com/posts/my-old-url/ will contain the following:`

+```html

+<!DOCTYPE html>

+<html>

+  <head>

+    <title>http://yoursite.com/posts/my-intended-url</title>

+    <link rel="canonical" href="http://yoursite.com/posts/my-intended-url"/>

+    <meta name=\"robots\" content=\"noindex\">

+    <meta http-equiv="content-type" content="text/html; charset=utf-8"/>

+    <meta http-equiv="refresh" content="0; url=http://yoursite.com/posts/my-intended-url"/>

+  </head>

+</html>

+```

+The `http-equiv="refresh"` line is what performs the redirect, in 0 seconds in this case. If an end user of your website goes to `https://yoursite.com/posts/my-old-url`, they will now be automatically redirected to the newer, correct URL. The addition of `<meta name=\"robots\" content=\"noindex\">` lets search engine bots know they they should not crawl and index your new alias page.

+### Customize

+You may customize this alias page by creating an `alias.html` template in the

+layouts folder of your site (i.e., `layouts/alias.html`). In this case, the data passed to the template is

+`Permalink`

+: the link to the page being aliased

+`Page`

+: the Page data for the page being aliased

+### Important Behaviors of Aliases

+1. Hugo makes no assumptions about aliases. They also do not change based

+on your UglyURLs setting. You need to provide absolute paths to your web root

+and the complete filename or directory.

+2. Aliases are rendered *before* any content are rendered and therefore will be overwritten by any content with the same location.

+## Pretty URLs

+Hugo's default behavior is to render your content with "pretty" URLs. No non-standard server-side configuration is required for these pretty URLs to work.

+The following demonstrates the concept:

+```bash

+content/posts/_index.md

+=> yoursite.com/posts/index.html

+content/posts/post-1.md

+=> yoursite.com/posts/post-1/

+```

+## Ugly URLs

+If you would like to have are often referred to as "ugly URLs" (e.g., yoursite.com/urls.html), set `uglyurls = true` or `uglyurls: true` in your site's `config.toml` or `config.yaml`, respectively. You can also use the `--uglyURLs=true` [flag from the command line][usage] with `hugo` or `hugo server`..

+If you want a specific piece of content to have an exact URL, you can specify this in the [front matter][] under the `url` key. The following are examples of the same content directory and what the eventual URL structure will be when Hugo runs with its default behavior.

+See [Content Organization][contentorg] for more details on paths.

+```bash

+.

+└── content

+    └── about

+    |   └── _index.md  // <- http://yoursite.com/about/

+    ├── post

+    |   ├── firstpost.md   // <- http://yoursite.com/post/firstpost/

+    |   ├── happy

+    |   |   └── ness.md  // <- http://yoursite.com/post/happy/ness/

+    |   └── secondpost.md  // <- http://yoursite.com/post/secondpost/

+    └── quote

+        ├── first.md       // <- http://yoursite.com/quote/first/

+        └── second.md      // <- http://yoursite.com/quote/second/

+```

+Here's the same organization run with `hugo --uglyURLs`:

+```bash

+.

+└── content

+    └── about

+    |   └── _index.md  // <- http://yoursite.com/about/index.html

+    ├── post

+    |   ├── firstpost.md   // <- http://yoursite.com/post/firstpost.html

+    |   ├── happy

+    |   |   └── ness.md    // <- http://yoursite.com/post/happy/ness.html

+    |   └── secondpost.md  // <- http://yoursite.com/post/secondpost.html

+    └── quote

+        ├── first.md       // <- http://yoursite.com/quote/first.html

+        └── second.md      // <- http://yoursite.com/quote/second.html

+```

+## Canonicalization

+By default, all relative URLs encountered in the input are left unmodified, e.g. `/css/foo.css` would stay as `/css/foo.css`. The `canonifyURLs` field in your site `config` has a default value of `false`.

+By setting `canonifyURLs` to `true`, all relative URLs would instead be *canonicalized* using `baseURL`.  For example, assuming you have `baseURL = https://yoursite.com/`, the relative URL `/css/foo.css` would be turned into the absolute URL `http://yoursite.com/css/foo.css`.

+Benefits of canonicalization include fixing all URLs to be absolute, which may aid with some parsing tasks. Note, however, that all modern browsers handle this on the client without issue.

+Benefits of non-canonicalization include being able to have scheme-relative resource inclusion; e.g., so that `http` vs `https` can be decided according to how the page was retrieved.

+{{% note "`canonifyURLs` default change" %}}

+In the May 2014 release of Hugo v0.11, the default value of `canonifyURLs` was switched from `true` to `false`, which we think is the better default and should continue to be the case going forward. Please verify and adjust your website accordingly if you are upgrading from v0.10 or older versions.

+{{% /note %}}

+To find out the current value of `canonifyURLs` for your website, you may use the handy `hugo config` command added in v0.13.

+```bash

+hugo config | grep -i canon

+```

+Or, if you are on Windows and do not have `grep` installed:

+```

+hugo config | FINDSTR /I canon

+```

+## Override URLS with Front Matter

+In addition to specifying permalink values in your site configuration for different content sections, Hugo provides even more granular control for individual pieces of content.

+Both `slug` and `url` can be defined in individual front matter. For more information on content destinations at build time, see [Content Organization][contentorg].

+## Relative URLs

+By default, all relative URLs are left unchanged by Hugo, which can be problematic when you want to make your site browsable from a local file system.

+Setting `relativeURLs` to `true` in your [site configuration][config] will cause Hugo to rewrite all relative URLs to be relative to the current content.

+For example, if your `/post/first/` page contains a link to `/about/`, Hugo will rewrite the URL to `../../about/`.

+[config]: /getting-started/configuration/

+[contentorg]: /content-management/organization/

+[front matter]: /content-management/front-matter/

+[multilingual]: /content-management/multilingual/

+[sections]: /content-management/sections/

+[usage]: /getting-started/usage/

--- a/content/content/archetypes.md

+++ /dev/null

@@ -1,330 +1,0 @@

----

-lastmod: 2016-10-01

-date: 2014-05-14T02:13:50Z

-menu:

-  main:

-    parent: content

-next: /content/ordering

-prev: /content/types

-title: Archetypes

-weight: 50

-toc: true

----

-Typically, each piece of content you create within a Hugo project will have [front matter](/content/front-matter/) that follows a consistent structure. If you write blog posts, for instance, you might use the following front matter for the vast majority of those posts:

-```toml

-+++

-title = ""

-date = ""

-slug = ""

-tags = [

-  ""

-]

-categories = [

-  ""

-]

-draft = true

-+++

-```

-You can always add non-typical front matter to any piece of content, but since it takes extra work to develop a theme that handles unique metadata, consistency is simpler.

-With this in mind, Hugo has a convenient feature known as *archetypes* that allows users to define default front matter for new pieces of content.

-By using archetypes, we can:

-1. **Save time**. Stop writing the same front matter over and over again.

-2. **Avoid errors**. Reduce the odds of typos, improperly formatted syntax, and other simple mistakes.

-3. **Focus on more important things**. Avoid having to remember all of the fields that need to be associated with each piece of content. (This is particularly important for larger projects with complex front matter and a variety of content types.)

-Let's explore how they work.

-## Built-in Archetypes

-If you've been using Hugo for a while, there's a decent chance you've come across archetypes without even realizing it. This is because Hugo includes a basic, built-in archetype that is used by default whenever it generates a content file.

-To see this in action, open the command line, navigate into your project's directory, and run the following command:

-```bash

-hugo new hello-world.md

-```

-This `hugo new` command creates a new content file inside the project's `content` directory — in this case, a file named `hello-world.md` — and if you open this file, you'll notice it contains the following front matter:

-```toml

-+++

-date = "2017-05-31T15:18:11+10:00"

-draft = true

-title = "hello world"

-+++

-```

-Here, we can see that three fields have been added to the document: a `title` field that is based on the file name we defined, a `draft` field that ensures this content won't be published by default, and a `date` field that is auto-populated with the current date and time in the [RFC 3339](https://stackoverflow.com/questions/522251/whats-the-difference-between-iso-8601-and-rfc-3339-date-formats) format.

-This, in its most basic form, is an example of an archetype. To understand how useful they can be though, it's best if we create our own.

-## Creating Archetypes

-In this section, we're going to create an archetype that will override the built-in archetype, allowing us to define custom front matter that will be included in any content files that we generate with the `hugo new` command.

-To achieve this, create a file named `default.md` inside the `archetypes` folder of a Hugo project. (If the folder doesn't exist, create it.)

-Then, inside this file, define the following front matter:

-```toml

-+++

-slug = ""

-tags = []

-categories = []

-draft = true

-+++

-```

-You'll notice that we haven't defined a `title` or `date` field. This is because Hugo will automatically add these fields to the beginning of the front matter. We do, however, need to define the `draft` field if we want it to exist in our front matter.

-You'll also notice that we're writing the front matter in the TOML format. It's possible to define archetype front matter in other formats, but a setting needs to be changed in the configuration file for this to be possible. See the "[Archetype Formats](#archetype-formats)" section of this article for more details.

-Next, run the following command:

-```bash

-hugo new my-archetype-example.md

-```

-This command will generate a file named `my-archetype-example.md` inside the `content` directory, and this file will contain the following output:

-```toml

-+++

-categories = []

-date = "2017-05-31T15:21:13+10:00"

-draft = true

-slug = ""

-tags = []

-title = "my archetype example"

-+++

-```

-As we can see, the file contains the `title` and `date` property that Hugo created for us, along with the front matter that we defined in the `archetypes/default.md` file.

-You'll also notice that the fields have been sorted into alphabetical order. This is an unintentional side-effect that stems from the underlying code libraries that Hugo relies upon. It is, however, [a known issue that is actively being discussed](https://github.com/gohugoio/hugo/issues/452).

-## Section Archetypes

-By creating the `archetypes/default.md` file, we've created a default archetype that is more useful than the built-in archetype, but since Hugo encourages us to [organize our content into sections](/content/sections/), each of which will likely have different front matter requirements, a "one-size-fits-all" archetype isn't necessarily the best approach.

-To accommodate for this, Hugo allows us to create archetypes for each section of our project. This means, whenever we generate content for a certain section, the appropriate front matter for that section will be automatically included in the generated file.

-To see this in action, create a "photo" section by creating a directory named "photo" inside the `content` directory.

-Then create a file named `photo.md` inside the `archetypes` directory and include the following front matter inside this file:

-```toml

-+++

-image_url = ""

-camera = ""

-lens = ""

-aperture = ""

-iso = ""

-draft = true

-+++

-```

-Here, the critical detail is that the `photo.md` file in the `archetypes` directory is named after the `photo` section that we just created. By sharing a name, Hugo can understand that there's a relationship between them.

-Next, run the following command:

-```bash

-hugo new photo/my-pretty-cat.md

-```

-This command will generate a file named `my-pretty-cat.md` inside the `content/photo` directory, and this file will contain the following output:

-```toml

-+++

-aperture = ""

-camera = ""

-date = "2017-05-31T15:25:18+10:00"

-draft = true

-image_url = ""

-iso = ""

-lens = ""

-title = "my pretty cat"

-+++

-```

-As we can see, the `title` and `date` fields are still included by Hugo, but the rest of the front matter is being generated from the `photo.md` archetype instead of the `default.md` archetype.

-### Tip: Default Values

-To make archetypes more useful, define default values for any fields that will always be set to a range of limited options. In the case of the `photo.md` archetype, for instance, you could include lists of the various cameras and lenses that you own:

-```toml

-+++

-image_url = ""

-camera = [

-  "Sony RX100 Mark IV",

-  "Canon 5D Mark III",

-  "iPhone 6S"

-]

-lens = [

-  "Canon EF 50mm f/1.8",

-  "Rokinon 14mm f/2.8"

-]

-aperture = ""

-iso = ""

-draft = true

-+++

-```

-Then, after generating a content file, simply remove the values that aren't relevant. This saves you from typing out the same options over and over again while ensuring consistency in how they're written.

-## Scaffolding Content

-Archetypes aren't limited to defining default front matter. They can also be used to define a default structure for the body of Markdown documents.

-For example, imagine creating a `review.md` archetype for the purpose of writing camera reviews. This is what the front matter for such an archetype might look like:

-```toml

-+++

-manufacturer = ""

-model = ""

-price = ""

-releaseDate = ""

-rating = ""

-+++

-```

-But reviews tend to follow strict formats and need to answer specific questions, and it's with these expectations of precise structure that archetypes can prove to be even more useful.

-For the sake of writing reviews, for instance, we could define the structure of a review beneath the front matter of the `review.md` file:

-```markdown

-+++

-manufacturer = ""

-model = ""

-price = ""

-releaseDate = ""

-rating = ""

-+++

-## Introduction

-## Sample Photos

-## Conclusion

-```

-Then, whenever we use the `hugo new` command to create a new review, not only will the default front matter be copied into the newly created Markdown document, but the body of the `review.md` archetype will also be copied.

-To take this further though — and to ensure authors on multi-author websites are on the same page about how content should be written — we could include notes and reminders within the archetype:

-```markdown

-+++

-manufacturer = ""

-model = ""

-price = ""

-releaseDate = ""

-rating = ""

-+++

-## Introduction

-<!--

-  What is the selling point of the camera?

-  What has changed since last year's model?

-  Include a bullet-point list of key features.

--->

-## Sample Photos

-<!-- TODO: Take at least 12 photos in a variety of situations. -->

-## Conclusion

-<!--

-  Is this camera worth the money?

-  Does it accomplish what it set out to achieve?

-  Are there any specific groups of people who should/shouldn't buy it?

-  Would you recommend it to a friend?

-  Are there alternatives on the horizon?

--->

-```

-That way, each time we generate a new content file, we have a series of handy notes to push us closer to a piece of writing that's suitable for publishing.

-(If you're wondering why the notes are wrapped in the HTML comment syntax, it's to ensure they won't appear inside the preview window of whatever Markdown editor the author happens to be using. They're not strictly necessary though.)

-This is still a fairly simple example, but if your content usually contains a variety of components — headings, bullet-points, images, [short-codes](/extras/shortcodes/), etc — it's not hard to see the time-saving benefits of placing these components in the body of an archetype file.

-## Theme Archetypes

-Whenever you generate a content file with the `hugo new` command, Hugo will start by searching for archetypes in the `archetypes` directory, initially looking for an archetype that matches the content's section and falling-back on the `default.md` archetype (if one is present). If no archetypes are found in this directory, Hugo will continue its search in the `archetypes` directory of the currently active theme. In other words, it's possible for themes to come packaged with their own archetypes, ensuring that users of that theme format their content files with correctly structured front matter.

-To allow Hugo to use archetypes from a theme, [that theme must be activated via the project's configuration file](/themes/usage/):

-```toml

-theme = "ThemeNameGoesHere"

-```

-If an archetype doesn't exist in the `archetypes` directory at the top-level of a project or inside the `archetypes` directory of an active theme, the built-in archetype will be used.

-{{< figure src="/img/content/archetypes/archetype-hierarchy.png" alt="How Hugo Decides Which Archetype To Use" >}}

-## Archetype Formats

-By default, the `hugo new` command will generate front matter in the TOML format. This means, even if we define the front matter in our archetype files as YAML or JSON, it will be converted to the TOML format before it ends up in our content files.

-Fortunately, this functionality can be overwritten.

-Inside the project's configuration file, simply define a `metaDataFormat` property:

-```toml

-metaDataFormat = ""

-```

-Then set this property to any of the following values:

-* toml

-* yaml

-* json

-By defining this option, any front matter will be generated in your preferred format.

-It's worth noting, however, that when generating front matter in the TOML format, you might encounter the following error:

-```bash

-Error: cannot convert type <nil> to TomlTree

-```

-This is because, to generate TOML, all of the fields in the front matter need to have a default value, even if that default value is just an empty string.

-For example, this YAML would *not* successfully compile into the TOML format:

-```yaml

----

-slug:

-tags:

-categories:

-draft:

----

-```

-But this YAML *would* successfully compile:

-```yaml

----

-slug: ""

-tags:

-  -

-categories:

-  -

-draft: true

----

-```

-It's a subtle yet important detail to remember.

-## Notes

-* Prior to Hugo v0.13, some users received [an "EOF" error when using archetypes](https://github.com/gohugoio/hugo/issues/776), related to what text editor they used to create the archetype. As of Hugo v0.13, this error has been [resolved](https://github.com/gohugoio/hugo/pull/785).

--- a/content/content/example.md

+++ /dev/null

@@ -1,91 +1,0 @@

----

-aliases:

-- /doc/example/

-lastmod: 2015-12-23

-date: 2013-07-01

-linktitle: Example

-menu:

-  main:

-    parent: content

-prev: /content/multilingual

-next: /content/using-index-md

-notoc: true

-title: Example Content File

-weight: 70

----

-Some things are better shown than explained. The following is a very basic example of a content file written in [Markdown](https://help.github.com/articles/github-flavored-markdown/):

-**mysite/content/project/nitro.md → http://mysite.com/project/nitro.html**

-With TOML front matter:

-<pre><code class="language-toml">+++

-date        = "2013-06-21T11:27:27-04:00"

-title       = "Nitro: A quick and simple profiler for Go"

-description = "Nitro is a simple profiler for your Golang applications"

-tags        = [ "Development", "Go", "profiling" ]

-topics      = [ "Development", "Go" ]

-slug        = "nitro"

-project_url = "https://github.com/spf13/nitro"

-+++

-</code><code class="language-markdown"># Nitro

-Quick and easy performance analyzer library for [Go](http://golang.org/).

-## Overview

-Nitro is a quick and easy performance analyzer library for Go.

-It is useful for comparing A/B against different drafts of functions

-or different functions.

-## Implementing Nitro

-Using Nitro is simple. First, use `go get` to install the latest version

-of the library.

-    $ go get github.com/spf13/nitro

-Next, include nitro in your application.

-</code></pre>

-You may also use the equivalent YAML front matter:

-```yaml

----

-lastmod: 2015-12-23

-date:        "2013-06-21T11:27:27-04:00"

-title:       "Nitro: A quick and simple profiler for Go"

-description: "Nitro is a simple profiler for your Go lang applications"

-tags:        [ "Development", "Go", "profiling" ]

-topics:      [ "Development", "Go" ]

-slug:        "nitro"

-project_url: "https://github.com/spf13/nitro"

----

-```

-`nitro.md` would be rendered as follows:

-> # Nitro

->

-> Quick and easy performance analyzer library for [Go](http://golang.org/).

->

-> ## Overview

->

-> Nitro is a quick and easy performance analyzer library for Go.

-> It is useful for comparing A/B against different drafts of functions

-> or different functions.

->

-> ## Implementing Nitro

->

-> Using Nitro is simple. First, use `go get` to install the latest version

-> of the library.

->

->     $ go get github.com/spf13/nitro

->

-> Next, include nitro in your application.

-The source `nitro.md` file is converted to HTML by the excellent

-[Blackfriday](https://github.com/russross/blackfriday) Markdown processor,

-which supports extended features found in the popular

-[GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/).

--- a/content/content/front-matter.md

+++ /dev/null

@@ -1,119 +1,0 @@

----

-aliases:

-- /doc/front-matter/

-lastmod: 2015-12-23

-date: 2013-07-01

-menu:

-  main:

-    parent: content

-next: /content/sections

-prev: /content/organization

-title: Front Matter

-weight: 20

-toc: true

----

-The **front matter** is one of the features that gives Hugo its strength. It enables

-you to include the meta data of the content right with it. Hugo supports a few

-different formats, each with their own identifying tokens.

-Supported formats:

-  * **[TOML][]**, identified by '`+++`'.

-  * **[YAML][]**, identified by '`---`'.

-  * **[JSON][]**, a single JSON object which is surrounded by '`{`' and '`}`', followed by a newline.

-[TOML]: https://github.com/toml-lang/toml "Tom's Obvious, Minimal Language"

-[YAML]: http://www.yaml.org/ "YAML Ain't Markup Language"

-[JSON]: http://www.json.org/ "JavaScript Object Notation"

-## TOML Example

-<pre><code class="language-toml">+++

-title = "spf13-vim 3.0 release and new website"

-description = "spf13-vim is a cross platform distribution of vim plugins and resources for Vim."

-tags = [ ".vimrc", "plugins", "spf13-vim", "vim" ]

-date = "2012-04-06"

-categories = [

-  "Development",

-  "VIM"

-]

-slug = "spf13-vim-3-0-release-and-new-website"

-+++

-</code><code class="language-markdown">Content of the file goes Here

-</code></pre>

-## YAML Example

-```yaml

----

-title: "spf13-vim 3.0 release and new website"

-description: "spf13-vim is a cross platform distribution of vim plugins and resources for Vim."

-tags: [ ".vimrc", "plugins", "spf13-vim", "vim" ]

-lastmod: 2015-12-23

-date: "2012-04-06"

-categories:

-  - "Development"

-  - "VIM"

-slug: "spf13-vim-3-0-release-and-new-website"

----

-Content of the file goes Here

-```

-## JSON Example

-```json

-{

-    "title": "spf13-vim 3.0 release and new website",

-    "description": "spf13-vim is a cross platform distribution of vim plugins and resources for Vim.",

-    "tags": [ ".vimrc", "plugins", "spf13-vim", "vim" ],

-    "date": "2012-04-06",

-    "categories": [

-        "Development",

-        "VIM"

-    ],

-    "slug": "spf13-vim-3-0-release-and-new-website"

-}

-Content of the file goes Here

-```

-## Variables

-There are a few predefined variables that Hugo is aware of and utilizes. The user can also create

-any variable they want. These will be placed into the `.Params` variable available to the templates.

-Field names are always normalized to lowercase (e.g. `camelCase: true` is available as `.Params.camelcase`).

-### Required variables

-* **title** The title for the content

-* **description** The description for the content

-* **date** The date the content will be sorted by

-* **taxonomies** These will use the field name of the plural form of the index (see tags and categories above)

-### Optional variables

-* **aliases** An array of one or more aliases

-              (e.g. old published path of a renamed content)

-              that would be created to redirect to this content.

-              See [Aliases]({{< relref "extras/aliases.md" >}}) for details.

-* **draft** If true, the content will not be rendered unless `hugo` is called with `--buildDrafts`

-* **publishdate** If in the future, content will not be rendered unless `hugo` is called with `--buildFuture`

-* **expirydate** Content already expired will not be rendered unless `hugo` is called with `--buildExpired`

-* **type** The type of the content (will be derived from the directory automatically if unset)

-* **isCJKLanguage** If true, explicitly treat the content as CJKLanguage (`.Summary` and `.WordCount` can work properly in CJKLanguage)

-* **weight** Used for sorting

-* **markup** *(Experimental)* Specify `"rst"` for reStructuredText (requires

-            `rst2html`) or `"md"` (default) for Markdown

-* **slug** appears as tail of the url. It can be used to change the part of the url that is based on the filename.

-* **url** The full path to the content from the web root. It makes no assumptions about the path of the content file. It also ignores any language prefixes of the multilingual feature.

-*If neither `slug` or `url` is present, the filename will be used.*

-## Configure Blackfriday rendering

-It's possible to set some options for Markdown rendering in the page's front matter as an override to the site wide configuration.

-See [Configuration]({{< ref "overview/configuration.md#configure-blackfriday-rendering" >}}) for more.

--- a/content/content/markdown-extras.md

+++ /dev/null

@@ -1,49 +1,0 @@

----

-aliases:

-- /doc/supported-formats/

-lastmod: 2016-07-22

-date: 2016-07-22

-menu:

-  main:

-    parent: content

-prev: /content/summaries

-next: /content/multilingual

-title: Markdown Extras

-weight: 66

-toc: false

----

-Hugo provides some convenient markdown extensions.

-## Task lists

-Hugo supports GitHub styled task lists (TODO lists) for the Blackfriday renderer (md-files). See [Blackfriday config](/overview/configuration/#configure-blackfriday-rendering) for how to turn it off.

-Example:

-```markdown

-- [ ] a task list item

-- [ ] list syntax required

-- [ ] incomplete

-- [x] completed

-```

-Renders as:

-- [ ] a task list item

-- [ ] list syntax required

-- [ ] incomplete

-- [x] completed

-And produces this HTML:

-```html

-<ul class="task-list">

-<li><input type="checkbox" disabled="" class="task-list-item"> a task list item</li>

-<li><input type="checkbox" disabled="" class="task-list-item"> list syntax required</li>

-<li><input type="checkbox" disabled="" class="task-list-item"> incomplete</li>

-<li><input type="checkbox" checked="" disabled="" class="task-list-item"> completed</li>

-</ul>

-```

--- a/content/content/multilingual.md

+++ /dev/null

@@ -1,232 +1,0 @@

----

-date: 2016-01-02T21:21:00Z

-menu:

-  main:

-    parent: content

-prev: /content/markdown-extras

-next: /content/example

-title: Multilingual Mode

-weight: 68

-toc: true

----

-Hugo supports multiple languages side-by-side (added in `Hugo 0.17`). Define the available languages in a `Languages` section in your top-level `config.toml` (or equivalent).

-Example:

-```

-DefaultContentLanguage = "en"

-copyright = "Everything is mine"

-[params.navigation]

-help  = "Help"

-[Languages]

-[Languages.en]

-title = "My blog"

-weight = 1

-[Languages.en.params]

-linkedin = "english-link"

-[Languages.fr]

-copyright = "Tout est à moi"

-title = "Mon blog"

-weight = 2

-[Languages.fr.params]

-linkedin = "lien-francais"

-[Languages.fr.navigation]

-help  = "Aide"

-```

-Anything not defined in a `[Languages]` block will fall back to the global

-value for that key (like `copyright` for the English (`en`) language in this example).

-With the config above, all content, sitemap, RSS feeds, paginations

-and taxonomy pages will be rendered below `/` in English (your default content language), and below `/fr` in French.

-When working with params in frontmatter pages, omit the `params` in the key for the translation.

-If you want all of the languages to be put below their respective language code, enable `defaultContentLanguageInSubdir: true` in your configuration.

-Only the obvious non-global options can be overridden per language. Examples of global options are `BaseURL`, `BuildDrafts`, etc.

-Taxonomies and Blackfriday configuration can also be set per language, example:

-```

-[Taxonomies]

-tag = "tags"

-[blackfriday]

-angledQuotes = true

-hrefTargetBlank = true

-[Languages]

-[Languages.en]

-weight = 1

-title = "English"

-[Languages.en.blackfriday]

-angledQuotes = false

-[Languages.fr]

-weight = 2

-title = "Français"

-[Languages.fr.Taxonomies]

-plaque = "plaques"

-```

-### Translating your content

-Translated articles are identified by the name of the content file.

-Example of translated articles:

-1. `/content/about.en.md`

-2. `/content/about.fr.md`

-You can also have:

-1. `/content/about.md`

-2. `/content/about.fr.md`

-In which case the config variable `defaultContentLanguage` will be used to affect the default language `about.md`.  This way, you can

-slowly start to translate your current content without having to rename everything.

-If left unspecified, the value for `defaultContentLanguage` defaults to `en`.

-By having the same _base file name_, the content pieces are linked together as translated pieces.

-If you need distinct URLs per language you can set the slug in the non-default language file. Just define the custom slug for the french translation in your `/content/about.fr.md` file:

-```

----

-slug: "a-propos"

----

-```

-You will get both `/about/` and `/a-propos/` URLs in your build, properly linked as translated pieces.

-### Link to translated content

-To create a list of links to translated content, use a template similar to this:

-```

-{{ if .IsTranslated }}

-<h4>{{ i18n "translations" }}</h4>

-<ul>

-    {{ range .Translations }}

-    <li>

-        <a href="{{ .Permalink }}">{{ .Lang }}: {{ .Title }}{{ if .IsPage }} ({{ i18n "wordCount" . }}){{ end }}</a>

-    </li>

-    {{ end}}

-</ul>

-{{ end }}

-```

-The above can be put in a `partial` and included in any template, be it for a content page or the home page.  It will not print anything if there are no translations for a given page, or if it is -- in the case of the home page, section listing etc. -- a site with only one language.

-The above also uses the `i18n` func, see [Translation of strings](#translation-of-strings).

-### Translation of strings

-Hugo uses [go-i18n](https://github.com/nicksnyder/go-i18n) to support string translations. Follow the link to find tools to manage your translation workflows.

-Translations are collected from the `themes/[name]/i18n/` folder (built into the theme), as well as translations present in `i18n/` at the root of your project.  In the `i18n`, the translations will be merged and take precedence over what is in the theme folder.  Language files should be named according to RFC 5646  with names such as `en-US.toml`, `fr.toml`, etc.

-From within your templates, use the `i18n` function like this:

-```

-{{ i18n "home" }}

-```

-This uses a definition like this one in `i18n/en-US.toml`:

-```

-[home]

-other = "Home"

-```

-Often you will want to use to the page variables in the translations strings. To do that, pass on the "." context when calling `i18n`:

-```

-{{ i18n "wordCount" . }}

-```

-This uses a definition like this one in `i18n/en-US.toml`:

-```

-[wordCount]

-other = "This article has {{ .WordCount }} words."

-```

-An example of singular and plural form:

-```

-[readingTime]

-one = "One minute read"

-other = "{{.Count}} minutes read"

-```

-And then in the template:

-```

-{{ i18n "readingTime" .ReadingTime }}

-```

-To track down missing translation strings, run Hugo with the `--i18n-warnings` flag:

-```bash

- hugo --i18n-warnings | grep i18n

-i18n|MISSING_TRANSLATION|en|wordCount

-```

-### Menus

-You can define your menus for each language independently. The [creation of a menu]({{< relref "extras/menus.md" >}}) works analogous to earlier versions of Hugo, except that they have to be defined in their language-specific block in the configuration file:

-```toml

-defaultContentLanguage = "en"

-[languages.en]

-weight = 0

-languageName = "English"

-[[languages.en.menu.main]]

-url    = "/"

-name   = "Home"

-weight = 0

-[languages.de]

-weight = 10

-languageName = "Deutsch"

-[[languages.de.menu.main]]

-url    = "/"

-name   = "Startseite"

-weight = 0

-```

-The rendering of the main navigation works as usual. `.Site.Menus` will just contain the menu of the current language. Pay attention to the generation of the menu links. `absLangURL` takes care that you link to the correct locale of your website. Otherwise, both menu entries would link to the English version because it's the default content language that resides in the root directory.

-```html

-<ul>

-    {{- $currentPage := . -}}

-    {{ range .Site.Menus.main -}}

-    <li class="{{ if $currentPage.IsMenuCurrent "main" . }}active{{ end }}">

-        <a href="{{ .URL | absLangURL }}">{{ .Name }}</a>

-    </li>

-    {{- end }}

-</ul>

-```

-### Missing translations

-If a string does not have a translation for the current language, Hugo will use the value from the default language. If no default value is set, an empty string will be shown.

-While translating a Hugo site, it can be handy to have a visual indicator of missing translations. The `EnableMissingTranslationPlaceholders` config option will flag all untranslated strings with the placeholder `[i18n] identifier`, where `identifier` is the id of the missing translation.

-**Remember: Hugo will generate your website with these placeholders. It might not be suited for production environments.**

-### Multilingual Themes support

-To support Multilingual mode in your themes, some considerations must be taken for the URLs in the templates. If there are more than one language, URLs  must either  come from the built-in `.Permalink` or `.URL`, be constructed with `relLangURL` or `absLangURL` template funcs -- or prefixed with `{{.LanguagePrefix }}`.

-If there are more than one language defined, the`LanguagePrefix` variable will equal `"/en"` (or whatever your `CurrentLanguage` is). If not enabled, it will be an empty string, so it is harmless for single-language sites.

--- a/content/content/ordering.md

+++ /dev/null

@@ -1,41 +1,0 @@

----

-lastmod: 2015-12-23

-date: 2014-03-06

-linktitle: Ordering

-menu:

-  main:

-    parent: content

-next: /content/summaries

-prev: /content/archetypes

-title: Ordering Content

-weight: 60

----

-Hugo provides you with all the flexibility you need to organize how your content is ordered.

-By default, content is ordered by weight, then by date with the most

-recent date first, but alternative sorting (by `title` and `linktitle`) is

-also available. The order the content would appear is specified in

-the [list template](/templates/list/).

-_Both the `date` and `weight` fields are optional._

-Unweighted pages appear at the end of the list. If no weights are provided (or

-if weights are the same), `date` will be used to sort. If neither is provided,

-content will be ordered based on how it's read off the disk, and no order is

-guaranteed.

-## Assigning weight to content

-```toml

-+++

-weight = 4

-title = "Three"

-date = "2012-04-06"

-+++

-Front Matter with Ordered Pages 3

-```

-## Ordering Content Within Taxonomies

-Please see the [Taxonomy Ordering Documentation](/taxonomies/ordering/).

--- a/content/content/organization.md

+++ /dev/null

@@ -1,175 +1,0 @@

----

-aliases:

-- /doc/organization/

-lastmod: 2015-09-27

-date: 2013-07-01

-linktitle: Organization

-menu:

-  main:

-    parent: content

-next: /content/supported-formats

-prev: /overview/source-directory

-title: Content Organization

-weight: 10

-toc: true

----

-Hugo uses files (see [supported formats](/content/supported-formats/)) with headers commonly called the *front matter*. Hugo

-respects the organization that you provide for your content to minimize any

-extra configuration, though this can be overridden by additional configuration

-in the front matter.

-## Organization

-In Hugo, the content should be arranged in the same way they are intended for

-the rendered website. Without any additional configuration, the following will

-just work. Hugo supports content nested at any level. The top level is special

-in Hugo and is used as the [section](/content/sections/).

-    .

-    └── content

-        └── about

-        |   └── _index.md  // <- http://1.com/about/

-        ├── post

-        |   ├── firstpost.md   // <- http://1.com/post/firstpost/

-        |   ├── happy

-        |   |   └── ness.md  // <- http://1.com/post/happy/ness/

-        |   └── secondpost.md  // <- http://1.com/post/secondpost/

-        └── quote

-            ├── first.md       // <- http://1.com/quote/first/

-            └── second.md      // <- http://1.com/quote/second/

-**Here's the same organization run with `hugo --uglyURLs`**

-    .

-    └── content

-        └── about

-        |   └── _index.md  // <- http://1.com/about/

-        ├── post

-        |   ├── firstpost.md   // <- http://1.com/post/firstpost.html

-        |   ├── happy

-        |   |   └── ness.md    // <- http://1.com/post/happy/ness.html

-        |   └── secondpost.md  // <- http://1.com/post/secondpost.html

-        └── quote

-            ├── first.md       // <- http://1.com/quote/first.html

-            └── second.md      // <- http://1.com/quote/second.html

-## Destinations

-Hugo believes that you organize your content with a purpose. The same structure

-that works to organize your source content is used to organize the rendered

-site. As displayed above, the organization of the source content will be

-mirrored in the destination.

-Notice that the first level `about/` page URL was created using a directory

-named "about" with a single `_index.md` file inside. Find out more about `_index.md` specifically in [content for the homepage and other list pages](https://gohugo.io/overview/source-directory#content-for-home-page-and-other-list-pages).

-There are times when one would need more control over their content. In these

-cases, there are a variety of things that can be specified in the front matter

-to determine the destination of a specific piece of content.

-The following items are defined in order; latter items in the list will override

-earlier settings.

-### filename

-This isn't in the front matter, but is the actual name of the file minus the

-extension. This will be the name of the file in the destination.

-### slug

-Defined in the front matter, the `slug` can take the place of the filename for the

-destination.

-### filepath

-The actual path to the file on disk. Destination will create the destination

-with the same path. Includes [section](/content/sections/).

-### section

-`section` is determined by its location on disk and *cannot* be specified in the front matter. See [section](/content/sections/).

-### type

-`type` is also determined by its location on disk but, unlike `section`, it *can* be specified in the front matter. See [type](/content/types/).

-### path

-`path` can be provided in the front matter. This will replace the actual

-path to the file on disk. Destination will create the destination with the same

-path. Includes [section](/content/sections/).

-### url

-A complete URL can be provided. This will override all the above as it pertains

-to the end destination. This must be the path from the baseURL (starting with a "/").

-When a `url` is provided, it will be used exactly. Using `url` will ignore the

-`--uglyURLs` setting.

-## Path breakdown in Hugo

-### Content

-    .             path           slug

-    .       ⊢-------^----⊣ ⊢------^-------⊣

-    content/extras/indexes/category-example/index.html

-    .       section              slug

-    .       ⊢--^--⊣        ⊢------^-------⊣

-    content/extras/indexes/category-example/index.html

-    .       section  slug

-    .       ⊢--^--⊣⊢--^--⊣

-    content/extras/indexes/index.html

-### Destination

-               permalink

-    ⊢--------------^-------------⊣

-    http://spf13.com/projects/hugo

-       baseURL       section  slug

-    ⊢-----^--------⊣ ⊢--^---⊣ ⊢-^⊣

-    http://spf13.com/projects/hugo

-       baseURL       section          slug

-    ⊢-----^--------⊣ ⊢--^--⊣        ⊢--^--⊣

-    http://spf13.com/extras/indexes/example

-       baseURL            path       slug

-    ⊢-----^--------⊣ ⊢------^-----⊣ ⊢--^--⊣

-    http://spf13.com/extras/indexes/example

-       baseURL            url

-    ⊢-----^--------⊣ ⊢-----^-----⊣

-    http://spf13.com/projects/hugo

-       baseURL               url

-    ⊢-----^--------⊣ ⊢--------^-----------⊣

-    http://spf13.com/extras/indexes/example

-**section** = which type the content is by default

-* based on content location

-* front matter overrides

-**slug** = name.ext or name/

-* based on content-name.md

-* front matter overrides

-**path** = section + path to file excluding slug

-* based on path to content location

-**url** = relative URL

-* defined in front matter

-* overrides all the above

--- a/content/content/sections.md

+++ /dev/null

@@ -1,54 +1,0 @@

----

-lastmod: 2015-12-23

-date: 2013-07-01

-menu:

-  main:

-    parent: content

-next: /content/types

-notoc: true

-prev: /content/front-matter

-title: Sections

-weight: 30

----

-Hugo believes that you organize your content with a purpose. The same structure

-that works to organize your source content is used to organize the rendered

-site (see [Organization](/content/organization/)). Following this pattern Hugo

-uses the top level of your content organization as **the Section**.

-The following example site uses two sections, "post" and "quote".

-{{< nohighlight >}}.

-└── content

-    ├── post

-    |   ├── firstpost.md       // <- http://1.com/post/firstpost/

-    |   ├── happy

-    |   |   └── ness.md        // <- http://1.com/post/happy/ness/

-    |   └── secondpost.md      // <- http://1.com/post/secondpost/

-    └── quote

-        ├── first.md           // <- http://1.com/quote/first/

-        └── second.md          // <- http://1.com/quote/second/

-{{< /nohighlight >}}

-## Section Lists

-Hugo will automatically create pages for each section root that list all

-of the content in that section. See [List Templates](/templates/list/)

-for details on customizing the way they appear.

-Section pages can also have a content file and frontmatter, see [Source Organization]({{< relref "overview/source-directory.md#content-for-home-page-and-other-list-pages" >}}).

-## Sections and Types

-By default everything created within a section will use the content type

-that matches the section name.

-Section defined in the front matter have the same impact.

-To change the type of a given piece of content, simply define the type

-in the front matter.

-If a layout for a given type hasn't been provided, a default type template will

-be used instead provided it exists.

--- a/content/content/summaries.md

+++ /dev/null

@@ -1,54 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2013-07-01

-menu:

-  main:

-    parent: content

-notoc: true

-prev: /content/ordering

-next: /content/markdown-extras

-title: Summaries

-weight: 65

----

-With the use of the `.Summary` [page variable](/templates/variables/), Hugo can generate summaries of content to show snippets in summary views. The summary view snippets are automatically generated by Hugo. Where a piece of content is split for the content summary depends on whether the split is Hugo-defined or user-defined.

-Content summaries may also provide links to the original content, usually in the form of a "Read More..." link, with the help of the `.RelPermalink` or `.Permalink` variable, as well as the `.Truncated` boolean variable to determine whether such "Read More..." link is necessary.

-## Hugo-defined: automatic summary split

-By default, Hugo automatically takes the first 70 words of your content as its summary and stores it into the `.Summary` variable, which you may use in your templates.

-* Pros: Automatic, no additional work on your part.

-* Cons: All HTML tags are stripped from the summary, and the first 70 words, whether they belong to a heading or to different paragraphs, are all lumped into one paragraph.  Some people like it, but some people don't.

-## User-defined: manual summary split:

-Alternatively, you may add the <code>&#60;&#33;&#45;&#45;more&#45;&#45;&#62;</code> summary divider[^1] (for org content, use <code># more</code>) where you want to split the article.  Content prior to the summary divider will be used as that content's summary, and stored into the `.Summary` variable with all HTML formatting intact.

-[^1]: The **summary divider** is also called "more tag", "excerpt separator", etc. in other literature.

-* Pros: Freedom, precision, and improved rendering.  All formatting is preserved.

-* Cons: Need to remember to type <code>&#60;&#33;&#45;&#45;more&#45;&#45;&#62;</code> (or <code># more</code> for org content) in your content file.  :-)

-Be careful to enter <code>&#60;&#33;&#45;&#45;more&#45;&#45;&#62;</code> (or <code># more</code> for org content) exactly, i.e. all lowercase with no whitespace, otherwise it would be treated as regular comment and ignored.

-If there is nothing but spaces and newlines after the summary divider then `.Truncated` will be false.

-## Showing Summaries

-You can show content summaries with the following code. You could do this, for example, on a [list](/templates/list/) page.

-    {{ range first 10 .Data.Pages }}

-      <div class="summary">

-        <h4><a href="{{ .RelPermalink }}">{{ .Title }}</a></h4>

-        {{ .Summary }}

-      </div>

-      {{ if .Truncated }}

-      <div class="read-more-link">

-        <a href="{{ .RelPermalink }}">Read More…</a>

-      </div>

-      {{ end }}

-    {{ end }}

-Note how the `.Truncated` boolean valuable may be used to hide the "Read More..." link when the content is not truncated, i.e. when the summary contains the entire article.

--- a/content/content/supported-formats.md

+++ /dev/null

@@ -1,27 +1,0 @@

----

-aliases:

-- /doc/supported-formats/

-lastmod: 2015-08-01

-date: 2015-08-01

-menu:

-  main:

-    parent: content

-next: /content/front-matter

-prev: /content/organization

-title: Supported Formats

-weight: 15

-toc: true

----

-  Since 0.14, Hugo has defined a new concept called _external helpers_. It means that you can write your content using Asciidoc[tor], reStructuredText or Org-Mode. If you have files with associated extensions ([details](https://github.com/gohugoio/hugo/blob/77c60a3440806067109347d04eb5368b65ea0fe8/helpers/general.go#L65)), then Hugo will call external commands to generate the content (the exception being Org-Mode content, which is parsed natively).

-  This means that you will have to install the associated tool on your machine to be able to use those formats.

-  For example, for Asciidoc files, Hugo will try to call __asciidoctor__ or __asciidoc__ command.

-  To use those formats, just use the standard extension and the front matter exactly as you would do with natively supported _.md_ files.

-  Notes:

-  * as these are external commands, generation performance for that content will heavily depend on the performance of those external tools.

-  * this feature is still in early stage, hence feedback is even more welcome.

--- a/content/content/types.md

+++ /dev/null

@@ -1,80 +1,0 @@

----

-lastmod: 2015-09-28

-date: 2013-07-01

-linktitle: Types

-menu:

-  main:

-    parent: content

-next: /content/archetypes

-prev: /content/sections

-title: Content Types

-weight: 40

-toc: true

----

-Hugo has full support for different types of content. A content type can have a

-unique set of meta data, template and can be automatically created by the `hugo new`

-command through using content [archetypes](/content/archetypes/).

-A good example of when multiple types are needed is to look at [Tumblr](https://www.tumblr.com/). A piece

-of content could be a photo, quote or post, each with different meta data and

-rendered differently.

-## Assigning a content type

-Hugo assumes that your site will be organized into [sections](/content/sections/)

-and each section will use the corresponding type. If you are taking advantage of

-this, then each new piece of content you place into a section will automatically

-inherit the type.

-Alternatively, you can set the type in the meta data under the key "`type`".

-## Creating new content of a specific type

-Hugo has the ability to create a new content file and populate the front matter

-with the data set corresponding to that type. Hugo does this by utilizing

-[archetypes](/content/archetypes/).

-To create a new piece of content, use:

-    hugo new relative/path/to/content.md

-For example, if I wanted to create a new post inside the post section, I would type:

-    hugo new post/my-newest-post.md

-## Defining a content type

-Creating a new content type is easy in Hugo. You simply provide the templates and archetype

-that the new type will use. You only need to define the templates, archetypes and/or views

-unique to that content type. Hugo will fall back to using the general templates and default archetype

-whenever a specific file is not present.

-*Remember, all of the following are optional:*

-### Create Type Directory

-Create a directory with the name of the type in `/layouts`. Type is always singular.  *E.g. `/layouts/post`*.

-### Create single template

-Create a file called `single.html` inside your directory. *E.g. `/layouts/post/single.html`*.

-### Create list template

-Create a file called `post.html` inside the section lists template directory, `/layouts/section`. *E.g. `/layouts/section/post.html`*.

-### Create views

-Many sites support rendering content in a few different ways, for

-instance, a single page view and a summary view to be used when

-displaying a [list of contents on a single page](/templates/list).

-Hugo makes no assumptions here about how you want to display your

-content, and will support as many different views of a content type

-as your site requires. All that is required for these additional

-views is that a template exists in each `/layouts/TYPE` directory

-with the same name.

-### Create a corresponding archetype

-Create a file called <code><em>type</em>.md</code> in the `/archetypes` directory. *E.g. `/archetypes/post.md`*.

-More details about archetypes can be found at the [archetypes docs](/content/archetypes/).

--- a/content/content/using-index-md.md

+++ /dev/null

@@ -1,118 +1,0 @@

----

-aliases:

-- /doc/using-index-md/

-lastmod: 2017-02-22

-date: 2017-02-22

-linktitle: Using _index.md

-menu:

-  main:

-    parent: content

-prev: /content/example

-next: /themes/overview

-notoc: true

-title: Using _index.md

-weight: 70

----

-# \_index.md and 'Everything is a Page'

-As of version v0.18 Hugo now treats '[everything as a page](http://bepsays.com/en/2016/12/19/hugo-018/)'. This allows you to add content and frontmatter to any page - including List pages like [Sections](/content/sections/), [Taxonomies](/taxonomies/overview/), [Taxonomy Terms pages](/templates/terms/) and even to potential 'special case' pages like the [Home page](/templates/homepage/).

-In order to take advantage of this behaviour you need to do a few things.

-1. Create an \_index.md file that contains the frontmatter and content you would like to apply.

-2. Place the \_index.md file in the correct place in the directory structure.

-3. Ensure that the respective template is configured to display `{{ .Content }}` if you wish for the content of the \_index.md file to be rendered on the respective page.

-## How \_index.md pages work

-Before continuing it's important to know that this page must reference certain templates to describe how the \_index.md page will be rendered. Hugo has a multitude of possible templates that can be used and placed in various places (think theme templates for instance). For simplicity/brevity the default/top level template location will be used to refer to the entire range of places the template can be placed.

-If this is confusing or you are unfamiliar with Hugo's template hierarchy, visit the various template pages listed below. You may need to find the 'active' template responsible for any particular page on your own site by going through the template hierarchy and matching it to your particular setup/theme you are using.

-- [Home page template](/templates/homepage/)

-- [Content List templates](/templates/list/)

-- [Single Content templates](/templates/content/)

-- [Taxonomy Terms templates](/templates/terms/)

-Now that you've got a handle on templates lets recap some Hugo basics to understand how to use an \_index.md file with a List page.

-1. Sections and Taxonomies are 'List' pages, NOT single pages.

-2. List pages are rendered using the template hierarchy found in the [Content - List Template](/templates/list/) docs.

-3. The Home page, though technically a List page, can have [its own template](/templates/homepage/) at layouts/index.html rather than \_default/list.html. Many themes exploit this behaviour so you are likely to encounter this specific use case.

-4. Taxonomy terms pages are 'lists of metadata' not lists of content, so [have their own templates](/templates/terms/).

-Let's put all this information together:

-> **\_index.md files used in List pages, Terms pages or the Home page are NOT rendered as single pages or with Single Content templates.**

-> **All pages, including List pages, can have frontmatter and frontmatter can have markdown content - meaning \_index.md files are the way to _provide_ frontmatter and content to the respective List/Terms/Home page.**

-Here are a couple of examples to make it clearer...

-| \_index.md location                 | Page affected             | Rendered by                   |

-| -------------------                 | ------------              | -----------                   |

-| /content/post/\_index.md            | site.com/post/            | /layouts/section/post.html    |

-| /content/categories/hugo/\_index.md | site.com/categories/hugo/ | /layouts/taxonomy/hugo.html   |

-## Why \_index.md files are used

-With a Single page such as a post it's possible to add the frontmatter and content directly into the .md page itself. With List/Terms/Home pages this is not possible so \_index.md files can be used to provide that frontmatter/content to them.

-## How to display content from \_index.md files

-From the information above it should follow that content within an \_index.md file won't be rendered in its own Single Page, instead it'll be made available to the respective List/Terms/Home page.

-To **_actually render that content_** you need to ensure that the relevant template responsible for rendering the List/Terms/Home page contains (at least) `{{ .Content }}`.

-This is the way to actually display the content within the \_index.md file on the List/Terms/Home page.

-A very simple/naive example of this would be:

-```html

-{{ partial "header.html" . }}

-	<main>

-        {{ .Content }}

-        {{ range .Paginator.Pages }}

-			{{ partial "summary.html" . }}

-		{{ end }}

-		{{ partial "pagination.html" . }}

-	</main>

-{{ partial "sidebar.html" . }}

-{{ partial "footer.html" . }}

-```

-You can see `{{ .Content }}` just after the `<main>` element. For this particular example, the content of the \_index.md file will show before the main list of summaries.

-## Where to organise an \_index.md file

-To add content and frontmatter to the home page, a section, a taxonomy or a taxonomy terms listing, add a markdown file with the base name \_index on the relevant place on the file system.

-```bash

-└── content

-    ├── _index.md

-    ├── categories

-    │   ├── _index.md

-    │   └── photo

-    │       └── _index.md

-    ├── post

-    │   ├── _index.md

-    │   └── firstpost.md

-    └── tags

-        ├── _index.md

-        └── hugo

-            └── _index.md

-```

-In the above example \_index.md pages have been added to each section/taxonomy.

-An \_index.md file has also been added in the top level 'content' directory.

-### Where to place \_index.md for the Home page

-Hugo themes are designed to use the 'content' directory as the root of the website, so adding an \_index.md file here (like has been done in the example above) is how you would add frontmatter/content to the home page.

--- /dev/null

+++ b/content/contribute/_index.md

@@ -1,0 +1,23 @@

+---

+title: Contributing to the Hugo Project

+linktitle: Contributing to Hugo

+description: Contribute to Hugo development and documentation.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [contribute]

+#tags: []

+menu:

+  docs:

+    parent: "contribute"

+    weight: 01

+weight: 01	#rem

+draft: false

+slug:

+aliases: [/tutorials/how-to-contribute-to-hugo/,/community/contributing/]

+toc: false

+---

+Hugo relies heavily on the enthusiasm and participation of the open-source community. We need your support in both its development and documentation.

+Hugo's contribution guidelines are [detailed in a `CONTRIBUTING.md`](https://github.com/gohugoio/hugo/blob/master/CONTRIBUTING.md) in the Hugo source repository on GitHub.

--- /dev/null

+++ b/content/contribute/development.md

@@ -1,0 +1,412 @@

+---

+title: Contribute to Hugo Development

+linktitle: Development

+description: Hugo relies heavily on contributions from the open source community.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [contribute]

+#tags: [dev,open source]

+authors: [digitalcraftsman]

+menu:

+  docs:

+    parent: "contribute"

+    weight: 10

+weight: 10

+sections_weight: 10

+draft: false

+aliases: [/contribute/development/]

+toc: true

+---

+## Introduction

+Hugo is an open-source project and lives by the work of its [contributors][]. There are plenty of [open issues][issues], and we need your help to make Hugo even more awesome. You don't need to be a Go guru to contribute to the project's development.

+## Assumptions

+This contribution guide takes a step-by-step approach in hopes of helping newcomers. Therefore, we only assume the following:

+* You are new to Git or open-source projects in general

+* You are a fan of Hugo and enthusiastic about contributing to the project

+{{% note "Additional Questions?" %}}

+If you're struggling at any point in this contribution guide, reach out to the Hugo community in [Hugo's Discussion forum](https://discourse.gohugo.io).

+{{% /note %}}

+## Install Go

+The installation of Go should take only a few minutes. You have more than one option to get Go up and running on your machine.

+If you are having trouble following the installation guides for go, check out [Go Bootcamp, which contains setups for every platform][gobootcamp] or reach out to the Hugo community in the [Hugo Discussion Forums][forums].

+### Install Go From Source

+[Download the latest stable version of Go][godl] and follow the official [Golang installation guide][goinstall].

+Once you're finished installing Go, let's confirm everything is working correctly. Open a terminal---or command line under Windows--and type the following:

+```bash

+go version

+```

+You should see something similar to the following written to the console. Note that the version here reflects the most recent version of Go as of the last update for this page:

+```bash

+go version go1.8 darwin/amd64

+```

+Next, make sure that you set up your `GOPATH` [as described in the installation guide][setupgopath].

+You can print the `GOPATH` with `echo $GOPATH`. You should see a non-empty string containing a valid path to your Go workspace; .e.g.:

+```bash

+/Users/<yourusername>/Code/go

+```

+### Install Go with Homebrew

+If you are a macOS user and have [Homebrew](https://brew.sh/) installed on your machine, installing Go is as simple as the following command:

+{{% code file="install-go.sh" %}}

+```bash

+brew install go

+```

+{{% /code %}}

+### Install Go via GVM

+More experienced users can use the [Go Version Manager][gvm] (GVM). GVM allows you to switch between different Go versions *on the same machine*. If you're a beginner, you probably don't need this feature. However, GVM makes it easy to upgrade to a new released Go version with just a few commands.

+GVM comes in especially handy if you follow the development of Hugo over a longer period of time. Future versions of Hugo will usually be compiled with the latest version of Go. Sooner or later, you will have to upgrade if you want to keep up.

+## Create a GitHub Account

+If you're going to contribute code, you'll need to have an account on GitHub. Go to [www.github.com/join](https://github.com/join) and set up a personal account.

+## Install Git on Your System

+You will need to have Git installed on your computer to contribute to Hugo development. Teaching git is outside the scope of the Hugo docs, but if you're looking for an excellent reference to learn the basics of Git, we recommend the [Git book][gitbook] if you are not sure where to begin. The used terminology will be explained with annotations.

+Git is a [version control system](https://en.wikipedia.org/wiki/Version_control) to track the changes of source code. Hugo depends on smaller third-party packages that are used to extend the functionality. We use them because we don't want to reinvent the wheel.

+Go ships with a sub-command called `get` that will download these packages for us when we setup our working environment. The source code of the packages is tracked with Git. `get` will interact with the Git servers of the package hosters in order to fetch all dependencies.

+Move back to the terminal and check if Git is already installed. Type in `git version` and press enter. You can skip the rest of this section if the command returned a version number. Otherwise [download](https://git-scm.com/downloads) the lastest version of Git and follow this [installation guide](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).

+Finally, check again with `git version` if Git was installed successfully.

+### Git Graphical Front Ends

+There are several [GUI clients](https://git-scm.com/downloads/guis) that help you to operate Git. Not all are available for all operating systems and maybe differ in their usage. Thus, so we will use the command line since the commands are everywhere the same.

+### Install Hub on Your System (Optional)

+Hub is a great tool for working with GitHub. The main site for it is [www.hub.github.com](https://hub.github.com/). Feel free to install this little Git wrapper.

+On a Mac, you can install [Hub](https://github.com/github/hub) using [Homebrew](https://brew.sh):

+```sh

+brew install hub

+```

+Now we'll create an [alias in Bash](http://tldp.org/LDP/abs/html/aliases.html) so that typing `git` actually runs `Hub`:

+```sh

+echo "alias git='hub'" >> ~/.bash_profile

+```

+Confirm the installation:

+```sh

+git version 2.6.3

+hub version 2.2.2

+```

+## Set up your working copy

+The working copy is set up locally on your computer. It's what you'll edit, compile, and end up pushing back to GitHub. The main steps are cloning the repository and creating your fork as a remote.

+### Clone the repository

+We assume that you've set up your `GOPATH` (see the section above if you're unsure about this). You should now copy the Hugo repository down to your computer. You'll hear this called "clone the repo". GitHub's [help pages](https://help.github.com/articles/cloning-a-repository/) give us a short explanation:

+> When you create a repository on GitHub, it exists as a remote repository. You can create a local clone of your repository on your computer and sync between the two locations.

+We're going to clone the [master Hugo repository](https://github.com/gohugoio/hugo). That seems counter-intuitive, since you won't have commit rights on it. But it's required for the Go workflow. You'll work on a copy of the master and push your changes to your own repository on GitHub.

+So, let's clone that master repository:

+```sh

+go get -v -u github.com/gohugoio/hugo

+```

+### Fork the repository

+If you're not fimiliar with this term, GitHub's [help pages](https://help.github.com/articles/fork-a-repo/) provide again a simple explanation:

+> A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.

+#### Fork by hand

+Open the [Hugo repository](https://github.com/gohugoio/hugo) on GitHub and click on the "Fork" button in the top right.

+![Fork button](/images/contribute/development/forking-a-repository.png)

+Now open your fork repository on GitHub and copy the remote url of your fork. You can choose between HTTPS and SSH as protocol that Git should use for the following operations. HTTPS works always [if you're not sure](https://help.github.com/articles/which-remote-url-should-i-use/).

+![Copy remote url](/images/contribute/development/copy-remote-url.png)

+Switch back to the terminal and move into the directory of the cloned master repository from the last step.

+```sh

+cd $GOPATH/src/github.com/gohugoio/hugo

+```

+Now Git needs to know that our fork exists by adding the copied remote url:

+```sh

+git remote add <YOUR-GITHUB-USERNAME> <COPIED REMOTE-URL>

+```

+#### Fork with Hub

+Alternatively, you can use the Git wrapper Hub. Hub makes forking a repository easy:

+```sh

+git fork

+```

+That command will log in to GitHub using your account, create a fork of the repository that you're currently working in, and add it as a remote to your working copy.

+#### Trust, but verify

+Let's check if everything went right by listing all known remotes:

+```sh

+git remote -v

+```

+The output should look similar:

+```sh

+digitalcraftsman    [email protected]:digitalcraftsman/hugo.git (fetch)

+digitalcraftsman    [email protected]:digitalcraftsman/hugo.git (push)

+origin  https://github.com/gohugoio/hugo (fetch)

+origin  https://github.com/gohugoio/hugo (push)

+```

+## The Hugo Git Contribution Workflow

+### Create a new branch

+You should never develop against the "master" branch. The development team will not accept a pull request against that branch. Instead, create a descriptive named branch and work on it.

+First, you should always pull the latest changes from the master repository:

+```sh

+git checkout master

+git pull

+```

+Now we can create a new branch for your additions:

+```sh

+git checkout -b <BRANCH-NAME>

+```

+You can check on which branch your are with `git branch`. You should see a list of all local branches. The current branch is indicated with a little asterisk.

+### Contribute to Documentation

+Perhaps you want to start contributing to the Hugo docs. If so, you can ignore most of the following steps and focus on the `/docs` directory within your newly cloned repository. You can change directories into the Hugo docs using `cd docs`.

+You can start Hugo's built-in server via `hugo server`. Browse the documentation by entering [http://localhost:1313](http://localhost:1313) in the address bar of your browser. The server automatically updates the page whenever you change content.

+We have developed a [separate Hugo documentation contribution guide][docscontrib] for more information on how the Hugo docs are built, organized, and improved by the generosity of people like you.

+### Build Hugo

+While making changes in the codebase it's a good idea to build the binary to test them:

+```sh

+go build -o hugo main.go

+```

+### Test

+Sometimes changes on the codebase can cause unintended side effects. Or they don't work as expected. Most functions have their own test cases. You can find them in files ending with `_test.go`.

+Make sure the commands `go test ./...` passes, and `go build` completes.

+### Formatting

+The Go code styleguide maybe is opiniated but it ensures that the codebase looks the same, regardless who wrote the code. Go comes with its own formatting tool. Let's apply the styleguide to our addtions:

+```sh

+go fmt ./...

+```

+Once you made your additions commit your changes. Make sure that you follow our [code contribution guidelines](https://github.com/gohugoio/hugo/blob/master/CONTRIBUTING.md):

+```sh

+# Add all changed files

+git add --all

+git commit --message "YOUR COMMIT MESSAGE"

+```

+The commit message should describe what the commit does (e.g. add feature XYZ), not how it is done.

+### Modify commits

+You noticed some commit messages don't fulfill the code contribution guidelines or you just forget something to add some files? No problem. Git provides the necessary tools to fix such problems. The next two methods cover all common cases.

+If you are unsure what a command does leave the commit as it is. We can fix your commits later in the pull request.

+#### Modify the last commit

+Let's say you want to modify the last commit message. Run the following command and replace the current message:

+```sh

+git commit --amend -m"YOUR NEW COMMIT MESSAGE"

+```

+Take a look at the commit log to see the change:

+```sh

+git log

+# Exit with q

+```

+After making the last commit you may forgot something. There is no need to create a new commit. Just add the latest changes and merge them into the intended commit:

+```sh

+git add --all

+git commit --amend

+```

+#### Modify multiple commits

+{{% warning "Be Careful Modifying Multiple Commits"%}}

+Modifications such as those described in this section can have serious unintended consequences. Skip this section if you're not sure!

+{{% /warning %}}

+This is a bit more advanced. Git allows you to [rebase](https://git-scm.com/docs/git-rebase) commits interactively. In other words: it allows you to rewrite the commit history.

+```sh

+git rebase --interactive @~6

+```

+The `6` at the end of the command represents the number of commits that should be modified. An editor should open and present a list of last six commit messages:

+```sh

+pick 80d02a1 tpl: Add hasPrefix to the template funcs' "smoke test"

+pick aaee038 tpl: Sort the smoke tests

+pick f0dbf2c tpl: Add the other test case for hasPrefix

+pick 911c35b Add "How to contribute to Hugo" tutorial

+pick 33c8973 Begin workflow

+pick 3502f2e Refactoring and typo fixes

+```

+In the case above we should merge the last to commits in the commit of this tutorial (`Add "How to contribute to Hugo" tutorial`). You can "squash" commits, i.e. merge two or more commits into a single one.

+All operations are written before the commit message. Replace "pick" with an operation. In this case `squash` or `s` for short:

+```sh

+pick 80d02a1 tpl: Add hasPrefix to the template funcs' "smoke test"

+pick aaee038 tpl: Sort the smoke tests

+pick f0dbf2c tpl: Add the other test case for hasPrefix

+pick 911c35b Add "How to contribute to Hugo" tutorial

+squash 33c8973 Begin workflow

+squash 3502f2e Refactoring and typo fixes

+```

+We also want to rewrite the commits message of the third last commit. We forgot "docs:" as prefix according to the code contribution guidelines. The operation to rewrite a commit is called `reword` (or `r` as shortcut).

+You should end up with a similar setup:

+```sh

+pick 80d02a1 tpl: Add hasPrefix to the template funcs' "smoke test"

+pick aaee038 tpl: Sort the smoke tests

+pick f0dbf2c tpl: Add the other test case for hasPrefix

+reword 911c35b Add "How to contribute to Hugo" tutorial

+squash 33c8973 Begin workflow

+squash 3502f2e Refactoring and typo fixes

+```

+Close the editor. It should open again with a new tab. A text is instructing you to define a new commit message for the last two commits that should be merged (aka "squashed"). Save the file with <kbd>CTRL</kbd>+<kbd>S</kbd> and close the editor again.

+A last time a new tab opens. Enter a new commit message and save again. Your terminal should contain a status message. Hopefully this one:

+```sh

+Successfully rebased and updated refs/heads/<BRANCHNAME>.

+```

+Check the commit log if everything looks as expected. Should an error occur you can abort this rebase with `git rebase --abort`.

+### Push commits

+To push our commits to the fork on GitHub we need to speficy a destination. A destination is defined by the remote and a branch name. Earlier, the defined that the remote url of our fork is the same as our GitHub handle, in my case `digitalcraftsman`. The branch should have the same as our local one. This makes it easy to identify corresponding branches.

+```sh

+git push --set-upstream <YOUR-GITHUB-USERNAME> <BRANCHNAME>

+```

+Now Git knows the destination. Next time when you to push commits you just need to enter `git push`.

+If you modified your commit history in the last step GitHub will reject your try to push. This is a safety-feature because the commit history isn't the same and new commits can't be appended as usual. You can enforce this push explicitly with `git push --force`.

+## Open a pull request

+We made a lot of progress. Good work. In this step we finally open a pull request to submit our additions. Open the [Hugo master repository](https://github.com/gohugoio/hugo/) on GitHub in your browser.

+You should find a green button labeld with "New pull request". But GitHub is clever and probably suggests you a pull request like in the beige box below:

+![Open a pull request](/images/contribute/development/open-pull-request.png)

+The new page summaries the most important information of your pull request. Scroll down and you find the additions of all your commits. Make sure everything looks as expected and click on "Create pull request".

+### Accept the contributor license agreement

+Last but not least you should accept the contributor license agreement (CLA). A new comment should be added automatically to your pull request. Click on the yellow badge, accept the agreement and authenticate yourself with your GitHub account. It just takes a few clicks and only needs to be done once.

+![Accept the CLA](/images/contribute/development/accept-cla.png)

+### Automatic builds

+We use the [Travis CI loop](https://travis-ci.org/gohugoio/hugo) (Linux and OS&nbsp;X) and [AppVeyor](https://ci.appveyor.com/project/gohugoio/hugo/branch/master) (Windows) to compile Hugo with your additions. This should ensure that everything works as expected before merging your pull request. This in most cases only relevant if you made changes to the codebase of Hugo.

+![Automic builds and their status](/images/contribute/development/ci-errors.png)

+Above you can see that Travis wasn't able to compile the changes in this pull request. Click on "Details" and try to investigate why the build failed. But it doesn't have to be your fault. Mostly, the `master` branch that we used as foundation for your pull request should build without problems.

+If you have questions, leave a comment in the pull request. We are willing to assist you.

+## Where to start?

+Thank you for reading through this contribution guide. Hopefully, we will see you again soon on GitHub. There are plenty of [open issues][issues] for you to help with.

+Feel free to [open an issue][newissue] if you think you found a bug or you have a new idea to improve Hugo. We are happy to hear from you.

+## Additional References for Learning Git and Golang

+* [Codecademy's Free "Learn Git" Course][codecademy] (Free)

+* [Code School and GitHub's "Try Git" Tutorial][trygit] (Free)

+* [The Git Book][gitbook] (Free)

+* [Go Bootcamp][gobootcamp]

+* [GitHub Pull Request Tutorial, Thinkful][thinkful]

+[codecademy]: https://www.codecademy.com/learn/learn-git

+[contributors]: https://github.com/gohugoio/hugo/graphs/contributors

+[docscontrib]: /contribute/documentation/

+[forums]: https://discourse.gohugo.io

+[gitbook]: https://git-scm.com/

+[gobootcamp]: http://www.golangbootcamp.com/book/get_setup

+[godl]: https://golang.org/dl/

+[goinstall]: https://golang.org/doc/install

+[gvm]: https://github.com/moovweb/gvm

+[issues]: https://github.com/gohugoio/hugo/issues

+[newissue]: https://github.com/gohugoio/hugo/issues/new

+[releases]: /getting-started/

+[setupgopath]: https://golang.org/doc/code.html#Workspaces

+[thinkful]: https://www.thinkful.com/learn/github-pull-request-tutorial/

+[trygit]: https://try.github.io/levels/1/challenges/1

--- /dev/null

+++ b/content/contribute/documentation.md

@@ -1,0 +1,376 @@

+---

+title: Contribute to the Hugo Docs

+linktitle: Documentation

+description: Documentation is an integral part of any open source project. The Hugo docs are as much a work in progress as the source it attempts to cover.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [contribute]

+#tags: [docs,documentation,community, contribute]

+menu:

+  docs:

+    parent: "contribute"

+    weight: 20

+weight: 20

+sections_weight: 20

+draft: false

+aliases: [/contribute/docs/]

+toc: true

+---

+## Create Your Fork

+It's best to make changes to the Hugo docs on your local machine to check for consistent visual styling. Make sure you've created a fork of [hugoDocs](https://github.com/gohugoio/hugoDocs) on GitHub and cloned the repository locally on your machine. For more information, you can see [GitHub's documentation on "forking"][ghforking] or follow along with [Hugo's development contribution guide][hugodev].

+You can then create a separate branch for your additions. Be sure to choose a descriptive branch name that best fits the type of content. The following is an example of a branch name you might use for adding a new website to the showcase:

+```git

+git checkout -b jon-doe-showcase-addition

+```

+## Add New Content

+The Hugo docs make heavy use of Hugo's [archetypes][] feature. All content sections in Hugo documentation have an assigned archetype.

+Adding new content to the Hugo docs follows the same pattern, regardless of the content section:

+```

+hugo new <DOCS-SECTION>/<new-content-lowercase>.md

+```

+{{% note "`title:`, `date:`, and Field Order" %}}

+`title` and `date` fields are added automatically when using archetypes via `hugo new`. Do not be worried if the order of the new file's front matter fields on your local machine is different than that of the examples provided in the Hugo docs. This is a known issue [(#452)](https://github.com/gohugoio/hugo/issues/452).

+{{% /note %}}

+### Add a New Function

+Once you have cloned the Hugo repository, you can create a new function via the following command. Keep the file name lowercase.

+```

+hugo new functions/newfunction.md

+```

+The archetype for `functions` according to the Hugo theme is as follows:

+{{% code file="archetypes/functions.md" %}}

+```yaml

+{{< readfile file="/themes/gohugoioTheme/archetypes/functions.md">}}

+```

+{{% /code %}}

+#### New Function Required Fields

+Here is a review of the front matter fields automatically generated for you using `hugo new functions/*`:

+***`title`***

+: this will be auto-populated in all lowercase when you use `hugo new` generator.

+***`linktitle`***

+: the function's actual casing (e.g., `replaceRE` rather than `replacere`).

+***`description`***

+: a brief description used to populate the [Functions Quick Reference](/functions/).

+`categories`

+: currently auto-populated with 'functions` for future-proofing and portability reasons only; ignore this field.

+`tags`

+: only if you think it will help end users find other related functions

+`signature`

+: this is a signature/syntax definition for calling the function (e.g., `apply SEQUENCE FUNCTION [PARAM...]`).

+`workson`

+: acceptable values include `lists`,`taxonomies`, `terms`, `groups`, and `files`.

+`hugoversion`

+: the version of Hugo that will ship with this new function.

+`relatedfuncs`

+: other [templating functions][] you feel are related to your new function to help fellow Hugo users.

+`{{.Content}}`

+: an extended description of the new function; examples are not only welcomed but encouraged.

+In the body of your function, expand the short description used in the front matter. Include as many examples as possible, and leverage the Hugo docs [`code` shortcode](#adding-code-blocks). If you are unable to add examples but would like to solicit help from the Hugo community, add `needsexample: true` to your front matter.

+### Add a New Tutorial

+Once you have cloned the Hugo repository, you can create a new tutorial via the following command. Name the markdown file accordingly:

+```

+hugo new tutorials/my-new-tutorial.md

+```

+The archetype for the `tutorials` content type is as follows:

+{{% code file="archetypes/tutorials.md" %}}

+```yaml

+{{< readfile file="/themes/gohugoioTheme/archetypes/tutorials.md">}}

+```

+{{% /code %}}

+## Add Code Blocks

+Code blocks are crucial for providing examples of Hugo's new features to end users of the Hugo docs. Whenever possible, create examples that you think Hugo users will be able to implement in their own projects.

+### Standard Syntax

+Across all pages on the Hugo docs, the typical triple-back-tick markdown syntax is used. If you do not want to take the extra time to implement the following code block shortcodes, please use standard GitHub-flavored markdown. The Hugo docs use a version of [highlight.js](https://highlightjs.org/) with a specific set of languages.

+Your options for languages are `xml`/`html`, `go`/`golang`, `md`/`markdown`/`mkd`, `handlebars`, `apache`, `toml`, `yaml`, `json`, `css`, `asciidoc`, `ruby`, `powershell`/`ps`, `scss`, `sh`/`zsh`/`bash`/`git`, `http`/`https`, and `javascript`/`js`.

+````html

+```html

+<h1>Hello world!</h1>

+```

+````

+### Code Block Shortcode

+The Hugo documentation comes with a very robust shortcode for adding interactive code blocks.

+{{% note %}}

+With the `code` shortcodes, *you must include triple back ticks and a language declaration*. This was done by design so that the shortcode wrappers were easily added to legacy documentation and will be that much easier to remove if needed in future versions of the Hugo docs.

+{{% /note %}}

+### `code`

+`code` is the Hugo docs shortcode you'll use most often. `code` requires has only one named parameter: `file`. Here is the pattern:

+````markdown

+{{%/* code file="smart/file/name/with/path.html" download="download.html" copy="true" */%}}

+```language

+A whole bunch of coding going on up in here!

+```

+{{%/* /code */%}}

+````

+The following are the arguments passed into `code`:

+***`file`***

+: the only *required* argument. `file` is needed for styling but also plays an important role in helping users create a mental model around Hugo's directory structure. Visually, this will be displayed as text in the top left of the code block.

+`download`

+: if omitted, this will have no effect on the rendered shortcode. When a value is added to `download`, it's used as the filename for a downloadable version of the code block.

+`copy`

+: a copy button is added automatically to all `code` shortcodes. If you want to keep the filename and styling of `code` but don't want to encourage readers to copy the code (e.g., a "Do not do" snippet in a tutorial), use `copy="false"`.

+#### Example `code` Input

+This example HTML code block tells Hugo users the following:

+1. This file *could* live in `layouts/_default`, as demonstrated by `layouts/_default/single.html` as the value for `file`.

+2. This snippet is complete enough to be downloaded and implemented in a Hugo project, as demonstrated by `download="single.html"`.

+````md

+{{%/* code file="layouts/_default/single.html" download="single.html" */%}}

+```html

+{{ define "main" }}

+<main>

+    <article>

+        <header>

+            <h1>{{.Title}}</h1>

+            {{with .Params.subtitle}}

+            <span>{{.}}</span>

+        </header>

+        <div>

+            {{.Content}}

+        </div>

+        <aside>

+            {{.TableOfContents}}

+        </aside>

+    </article>

+</main>

+{{ end }}

+```

+{{%/* /code */%}}

+````

+##### Example 'code' Display

+The output of this example will render to the Hugo docs as follows:

+{{% code file="layouts/_default/single.html" download="single.html" %}}

+```html

+{{ define "main" }}

+<main>

+    <article>

+        <header>

+            <h1>{{.Title}}</h1>

+            {{with .Params.subtitle}}

+            <span>{{.}}</span>

+        </header>

+        <div>

+            {{.Content}}

+        </div>

+        <aside>

+            {{.TableOfContents}}

+        </aside>

+    </article>

+</main>

+{{ end }}

+```

+{{% /code %}}

+<!-- #### Output Code Block

+The `output` shortcode is almost identical to the `code` shortcode but only takes and requires `file`. The purpose of `output` is to show *rendered* HTML and therefore almost always follows another basic code block *or* and instance of the `code` shortcode:

+````html

+{{%/* output file="post/my-first-post/index.html" */%}}

+```html

+<h1>This is my First Hugo Blog Post</h1>

+<p>I am excited to be using Hugo.</p>

+```

+{{%/* /output */%}}

+````

+The preceding `output` example will render as follows to the Hugo docs:

+{{% output file="post/my-first-post/index.html" %}}

+```html

+<h1>This is my First Hugo Blog Post</h1>

+<p>I am excited to be using Hugo.</p>

+```

+{{% /output %}} -->

+## Blockquotes

+Blockquotes can be added to the Hugo documentation using [typical Markdown blockquote syntax][bqsyntax]:

+```markdown

+> Without the threat of punishment, there is no joy in flight.

+```

+The preceding blockquote will render as follows in the Hugo docs:

+> Without the threat of punishment, there is no joy in flight.

+However, you can add a quick and easy `<cite>` element (added on the client via JavaScript) by separating your main blockquote and the citation with a hyphen with a single space on each side:

+```markdown

+> Without the threat of punishment, there is no joy in flight. - [Kobo Abe](https://en.wikipedia.org/wiki/Kobo_Abe)

+```

+Which will render as follows in the Hugo docs:

+> Without the threat of punishment, there is no joy in flight. - [Kobo Abe][abe]

+{{% note "Blockquotes `!=` Admonitions" %}}

+Previous versions of Hugo documentation used blockquotes to draw attention to text. This is *not* the [intended semantic use of `<blockquote>`](http://html5doctor.com/cite-and-blockquote-reloaded/). Use blockquotes when quoting. To note or warn your user of specific information, use the admonition shortcodes that follow.

+{{% /note %}}

+## Admonitions

+**Admonitions** are common in technical documentation. The most popular is that seen in [reStructuredText Directives][sourceforge]. From the SourceForge documentation:

+> Admonitions are specially marked "topics" that can appear anywhere an ordinary body element can. They contain arbitrary body elements. Typically, an admonition is rendered as an offset block in a document, sometimes outlined or shaded, with a title matching the admonition type. - [SourceForge][sourceforge]

+The Hugo docs contain three admonitions: `note`, `tip`, and `warning`.

+### `note` Admonition

+Use the `note` shortcode when you want to draw attention to information subtly. `note` is intended to be less of an interruption in content than is `warning`.

+#### Example `note` Input

+{{% code file="note-with-heading.md" %}}

+```markdown

+{{%/* note */%}}

+Here is a piece of information I would like to draw your **attention** to.

+{{%/* /note */%}}

+```

+{{% /code %}}

+#### Example `note` Output

+{{% output file="note-with-heading.html" %}}

+```html

+{{% note %}}

+Here is a piece of information I would like to draw your **attention** to.

+{{% /note %}}

+```

+{{% /output %}}

+#### Example `note` Display

+{{% note %}}

+Here is a piece of information I would like to draw your **attention** to.

+{{% /note %}}

+### `tip` Admonition

+Use the `tip` shortcode when you want to give the reader advice. `tip`, like `note`, is intended to be less of an interruption in content than is `warning`.

+#### Example `tip` Input

+{{% code file="using-tip.md" %}}

+```markdown

+{{%/* tip */%}}

+Here's a bit of advice to improve your productivity with Hugo.

+{{%/* /tip */%}}

+```

+{{% /code %}}

+#### Example `tip` Output

+{{% output file="tip-output.html" %}}

+```html

+{{% tip %}}

+Here's a bit of advice to improve your productivity with Hugo.

+{{% /tip %}}

+```

+{{% /output %}}

+#### Example `tip` Display

+{{% tip %}}

+Here's a bit of advice to improve your productivity with Hugo.

+{{% /tip %}}

+### `warning` Admonition

+Use the `warning` shortcode when you want to draw the user's attention to something important. A good usage example is for articulating breaking changes in Hugo versions, known bugs, or templating "gotchas."

+#### Example `warning` Input

+{{% code file="warning-admonition-input.md" %}}

+```markdown

+{{%/* warning */%}}

+This is a warning, which should be reserved for *important* information like breaking changes.

+{{%/* /warning */%}}

+```

+{{% /code %}}

+#### Example `warning` Output

+{{% output file="warning-admonition-output.html" %}}

+```html

+{{% warning %}}

+This is a warning, which should be reserved for *important* information like breaking changes.

+{{% /warning %}}

+```

+{{% /output %}}

+#### Example `warning` Display

+{{% warning %}}

+This is a warning, which should be reserved for *important* information like breaking changes.

+{{% /warning %}}

+{{% note "Pull Requests and Branches" %}}

+Similar to [contributing to Hugo development](/contribute/development/), the Hugo team expects you to create a separate branch/fork when you make your contributions to the Hugo docs.

+{{% /note %}}

+[abe]: https://en.wikipedia.org/wiki/Kobo_Abe

+[archetypes]: /content-management/archetypes/

+[bqsyntax]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#blockquotes

+[charcount]: http://www.lettercount.com/

+[`docs/static/images/showcase/`]: https://github.com/gohugoio/hugo/tree/master/docs/static/images/showcase/

+[ghforking]: https://help.github.com/articles/fork-a-repo/

+[hugodev]: /contribute/development/

+[shortcodeparams]: content-management/shortcodes/#shortcodes-without-markdown

+[sourceforge]: http://docutils.sourceforge.net/docs/ref/rst/directives.html#admonitions

+[templating function]: /functions/

--- /dev/null

+++ b/content/contribute/themes.md

@@ -1,0 +1,154 @@

+---

+title: Add Your Hugo Theme to the Showcase

+linktitle: Themes

+description: If you've built a Hugo theme and want to contribute back to the Hugo Community, add your theme to the Hugo Showcase.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-27

+categories: [contribute]

+#tags: [contribute,themes,design]

+authors: [digitalcraftsman]

+menu:

+  docs:

+    parent: "contribute"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+aliases: [/contribute/theme/]

+wip: true

+toc: true

+---

+A collection of all themes created by the Hugo community, including screenshots and demos, can be found at <https://themes.gohugo.io>. Every theme in this list will automatically be added to the theme site. Theme updates aren't scheduled but usually happen at least once a week.

+## tl;dr

+1. Create your theme using `hugo new theme <THEMENAME>`;

+2. Test your theme against <https://github.com/spf13/HugoBasicExample> \*

+3. Add a `theme.toml` file to the root of the theme with all required metadata

+4. Add a descriptive `README.md` to the root of the theme source

+5. Add `/images/screenshot.png` and `/images/tn.png`

+\* If your theme doesn't fit into the `Hugo Basic Example` site, we encourage theme authors to supply a self-contained Hugo site in `/exampleSite`.

+{{% note %}}

+The folder name here---`exampleSite`---is important, as this folder will be picked up and used by the script that generates the Hugo Theme Site. It mirrors the root directory of a Hugo website and allows you to add custom content, assets, and a `config` file with preset values.

+{{% /note %}}

+See the [Hugo Artist theme's exampleSite][artistexample] for a good example.

+{{% note %}}

+Please make your example site's content is as neutral as possible. We hope this goes without saying.

+{{% /note %}}

+## Theme Requirements

+In order to add your theme to the Hugo Themes Showcase, the following requirements need to be met:

+1. `theme.toml` with all required fields

+2. Images for thumbnail and screenshot

+3. A good README file instructions for users

+4. Addition to the hugoThemes GitHub repository

+### Add Your Theme to the Repo

+The easiest way to add your theme is to [open up a new issue in the theme repository][themeissuenew] with a link to the theme's repository on GitHub.

+### Create a `theme.toml` File

+`theme.toml` contains metadata about the theme and its creator and should be created automatically when running the `hugo new theme`. The auto-generated file is provided here as well for easy downloading:

+{{% code file="theme.toml" download="theme.toml" %}}

+```toml

+name = ""

+license = "MIT"

+licenselink = "https://github.com/<YOURNAME>/<YOURTHEME>/blob/master/LICENSE.md"

+description = ""

+homepage = "http://yoursite.com/"

+tags = []

+features = []

+min_version = 0.19

+[author]

+  name = ""

+  homepage = ""

+# If porting an existing theme

+[original]

+  name = ""

+  homepage = ""

+  repo = ""

+```

+{{% /code %}}

+The following fields are required:

+```toml

+name = "Hyde"

+license = "MIT"

+licenselink = "https://github.com/spf13/hyde/blob/master/LICENSE.md"

+description = "An elegant open source and mobile first theme"

+homepage = "http://siteforthistheme.com/"

+tags = ["blog", "company"]

+features = ["blog"]

+min_version = 0.13

+[author]

+    name = "spf13"

+    homepage = "http://spf13.com/"

+# If porting an existing theme

+[original]

+    author = "mdo"

+    homepage = "http://hyde.getpoole.com/"

+    repo = "https://www.github.com/mdo/hyde"

+```

+{{% note %}}

+1. This is different from the `theme.toml` file created by `hugo new theme` in Hugo versions before v0.14.

+2. Only `theme.toml` is accepted; ie. not `theme.yaml` andnot `theme.json`.

+{{% /note %}}

+### Images

+Screenshots are used for previews in the Hugo Theme Gallery. Make sure that they have the right dimensions:

+* Thumbnail should be 900px × 600px

+* Screenshot should be 1500px × 1000px

+* Media must be located in

+    * <THEMEDIR>/images/screenshot.png</code>

+    * <THEMEDIR>/images/tn.png</code>

+Additional media may be provided in the same directory.

+### Create a README File

+Your theme's README file should be written in markdown and saved at the root of your theme's directory structure. Your `README.md` serves as

+1. Content for your theme's details page at <https://themes.gohugo.io>

+2. General information about the theme in your GitHub repository (i.e., it's usual purpose)

+#### Example `README.md`

+You can download the following `README.md` as an outline:

+{{% code file="README.md" download="README.md" %}}

+```markdown

+# Theme Title

+**Need input from @digitalcraftsman on what could be added to this file.**

+```

+{{% /code %}}

+{{% note "Screenshots in your `README.md`"%}}

+If you add screenshots to the README, please make use of absolute file paths instead of relative ones like `/images/screenshot.png`. Relative paths work great on GitHub but they don't correspond to the directory structure of [themes.gohugo.io](http://themes.gohugo.io/). Therefore, browsers will not be able to display screenshots on the theme site under the given (relative) path.

+{{% /note %}}

+[artistexample]: https://github.com/digitalcraftsman/hugo-artists-theme/tree/master/exampleSite

+[themeissuenew]: https://github.com/gohugoio/hugoThemes/issues/new

\ No newline at end of file

--- /dev/null

+++ b/content/documentation.md

@@ -1,0 +1,19 @@

+---

+title: Hugo Documentation

+linktitle: Hugo

+description: Hugo is the world's fastest static website engine. It's written in Go (aka Golang) and developed by bep, spf13 and friends.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+menu:

+  main:

+    parent: "section name"

+    weight: 01

+weight: 01	#rem

+draft: false

+slug:

+aliases: []

+toc: false

+layout: documentation-home

+---

+Hugo is the **world's fastest static website engine.** It's written in Go (aka Golang) and developed by [bep](https://github.com/bep), [spf13](https://github.com/spf13) and [friends](https://github.com/gohugoio/hugo/graphs/contributors). Below you will find some of the most common and helpful pages from our documentation.

--- a/content/extras/aliases.md

+++ /dev/null

@@ -1,103 +1,0 @@

----

-aliases:

-- /doc/redirects/

-- /doc/alias/

-- /doc/aliases/

-lastmod: 2015-12-23

-date: 2013-07-09

-menu:

-  main:

-    parent: extras

-next: /extras/analytics

-prev: /taxonomies/methods

-title: Aliases

----

-For people migrating existing published content to Hugo, there's a good chance you need a mechanism to handle redirecting old URLs.

-Luckily, redirects can be handled easily with _aliases_ in Hugo.

-## Example

-Given a post on your current Hugo site, with a path of:

-``content/posts/my-awesome-blog-post.md``

-... you create an "aliases" section in the frontmatter of your post, and add previous paths to that.

-### TOML frontmatter

-```toml

-+++

-        ...

-aliases = [

-    "/posts/my-original-url/",

-    "/2010/01/01/even-earlier-url.html"

-]

-        ...

-+++

-```

-### YAML frontmatter

-```yaml

----

-        ...

-aliases:

-    - /posts/my-original-url/

-    - /2010/01/01/even-earlier-url.html

-        ...

----

-```

-Now when you visit any of the locations specified in aliases, _assuming the same site domain_, you'll be redirected to the page they are specified on.

-## Important Behaviors

-1. *Hugo makes no assumptions about aliases. They also don't change based

-on your UglyURLs setting. You need to provide absolute path to your webroot

-and the complete filename or directory.*

-2. *Aliases are rendered prior to any content and will be overwritten by

-any content with the same location.*

-## Multilingual example

-On [multilingual sites]({{< relref "content/multilingual.md" >}}), each translation of a post can have unique aliases. To use the same alias across multiple languages, prefix it with the language code.

-In `/posts/my-new-post.es.md`:

-```yaml

----

-aliases:

-    - /es/posts/my-original-post/

----

-```

-## How Hugo Aliases Work

-When aliases are specified, Hugo creates a physical folder structure to match the alias entry, and, an html file specifying the canonical URL for the page, and a redirect target.

-Assuming a baseURL of `mysite.tld`, the contents of the html file will look something like:

-```html

-<!DOCTYPE html>

-<html>

-  <head>

-    <title>http://mysite.tld/posts/my-original-url</title>

-    <link rel="canonical" href="http://mysite.tld/posts/my-original-url"/>

-    <meta http-equiv="content-type" content="text/html; charset=utf-8"/>

-    <meta http-equiv="refresh" content="0; url=http://mysite.tld/posts/my-original-url"/>

-  </head>

-</html>

-```

-The `http-equiv="refresh"` line is what performs the redirect, in 0 seconds in this case.

-## Customizing

-You may customize this alias page by creating an alias.html template in the

-layouts folder of your site.  In this case, the data passed to the template is

-* Permalink - the link to the page being aliased

-* Page - the Page data for the page being aliased

--- a/content/extras/analytics.md

+++ /dev/null

@@ -1,28 +1,0 @@

----

-date: 2016-02-06

-linktitle: Analytics

-menu:

-  main:

-    parent: extras

-next: /extras/builders

-prev: /extras/aliases

-title: Analytics in Hugo

----

-Hugo ships with prebuilt internal templates for Google Analytics tracking, including both synchronous and asynchronous tracking codes.

-## Configuring Google Analytics

-Provide your tracking id in your configuration file, e.g. config.yaml.

-    googleAnalytics = "UA-123-45"

-## Example

-Include the internal template in your templates like so:

-    {{ template "_internal/google_analytics.html" . }}

-For async include the async template:

-    {{ template "_internal/google_analytics_async.html" . }}

--- a/content/extras/builders.md

+++ /dev/null

@@ -1,56 +1,0 @@

----

-lastmod: 2015-12-24

-date: 2014-05-26

-linktitle: Builders

-menu:

-  main:

-    parent: extras

-next: /extras/comments

-prev: /extras/analytics

-title: Hugo Builders

----

-Hugo provides the functionality to quickly get a site, theme or page

-started.

-## New Site

-Want to get a site built quickly?

-{{< nohighlight >}}$ hugo new site <i>path/to/site</i>

-{{< /nohighlight >}}

-Hugo will create all the needed directories and files to get started

-quickly.

-Hugo will only touch the files and create the directories (in the right

-places), [configuration](/overview/configuration/) and content are up to

-you... but luckily we have builders for content (see below).

-## New Theme

-Want to design a new theme?

-    $ hugo new theme THEME_NAME

-Run from your working directory, this will create a new theme with all

-the needed files in your themes directory. Hugo will provide you with a

-license and theme.toml file with most of the work done for you.

-Follow the [Theme Creation Guide](/themes/creation/) once the builder is

-done.

-## New Content

-You will use this builder the most of all. Every time you want to create

-a new piece of content, the content builder will get you started right.

-Leveraging [content archetypes](/content/archetypes/) the content builder

-will not only insert the current date and appropriate metadata, but it

-will pre-populate values based on the content type.

-    $ hugo new relative/path/to/content

-This assumes it is being run from your working directory and the content

-path starts from your content directory. Now, Hugo watches your content directory by default and rebuilds your entire website if any change occurs.

--- a/content/extras/comments.md

+++ /dev/null

@@ -1,99 +1,0 @@

----

-lastmod: 2015-08-04

-date: 2014-05-26

-linktitle: Comments

-menu:

-  main:

-    parent: extras

-next: /extras/crossreferences

-prev: /extras/builders

-title: Comments in Hugo

----

-As Hugo is a static site generator, the content produced is static and doesn’t interact with the users. The most common interaction people ask for is comment capability.

-Hugo ships with support for [Disqus](https://disqus.com/), a third-party service that provides comment and community capabilities to website via JavaScript.

-Your theme may already support Disqus, but even it if doesn’t, it is easy to add.

-# Disqus Support

-## Adding Disqus to a template

-Hugo comes with all the code you would need to include load Disqus. Simply include the following line where you want your comments to appear:

-    {{ template "_internal/disqus.html" . }}

-## Configuring Disqus

-That template requires you to set a single value in your site config file, e.g. config.yaml.

-    disqusShortname = "XYW"

-Additionally, you can optionally set the following in the front matter

-for a given piece of content:

- * **disqus_identifier**

- * **disqus_title**

- * **disqus_url**

-## Conditional Loading of Disqus Comments

-Users have noticed that enabling Disqus comments when running the Hugo web server on localhost causes the creation of unwanted discussions on the associated Disqus account. In order to prevent this, a slightly tweaked partial template is required. So, rather than using the built-in `"_internal/disqus.html"` template referenced above, create a template in your `partials` folder that looks like this:

-```html

-<div id="disqus_thread"></div>

-<script type="text/javascript">

-(function() {

-    // Don't ever inject Disqus on localhost--it creates unwanted

-    // discussions from 'localhost:1313' on your Disqus account...

-    if (window.location.hostname == "localhost")

-        return;

-    var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;

-    var disqus_shortname = '{{ .Site.DisqusShortname }}';

-    dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';

-    (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);

-})();

-</script>

-<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>

-<a href="http://disqus.com/" class="dsq-brlink">comments powered by <span class="logo-disqus">Disqus</span></a>

-```

-Notice that there is a simple `if` statement that detects when you are running on localhost and skips the initialization of the Disqus comment injection.

-Now, reference the partial template from your page template:

-    {{ partial "disqus.html" . }}

-# Alternatives

-A few alternatives exist to [Disqus](https://disqus.com/):

-* [txtpen](https://txtpen.com)

-* [Discourse](http://www.discourse.org)

-* [IntenseDebate](http://intensedebate.com/)

-* [Livefyre](http://www.adobe.com/marketing-cloud/enterprise-content-management/ugc-content-platform.html)

-* [Muut](http://muut.com/)

-* [多说](http://duoshuo.com/) ([Duoshuo](http://duoshuo.com/), popular in China)

-* [isso](http://posativ.org/isso/) (Self-hosted, Python)

-* [Kaiju](https://github.com/spf13/kaiju)

-## Kaiju

-[Kaiju](https://github.com/spf13/kaiju) is an open-source project started by [spf13](http://spf13.com/) (Hugo’s author) to bring easy and fast real time discussions to the web.

-Written using Go, Socket.io and MongoDB, it is very fast and easy to deploy.

-It is in early development but shows promise. If you have interest, please help by contributing whether via a pull request, an issue or even just a tweet. Everything helps.

-## txtpen

-[txtpen](https://txtpen.com) adds highlighting an in-line commenting similar to Medium to your Hugo blog.

-## Discourse

-Additionally, you may recognize [Discourse](http://www.discourse.org) as the system that powers the [Hugo Discussion Forum](https://discourse.gohugo.io).

--- a/content/extras/crossreferences.md

+++ /dev/null

@@ -1,153 +1,0 @@

----

-lastmod: 2015-12-23

-date: 2014-11-25

-menu:

-  main:

-    parent: extras

-next: /extras/robots-txt

-prev: /extras/comments

-title: Cross-References

-toc: true

----

-Hugo makes it easy to link documents together with the `ref` and `relref` shortcodes. These shortcodes are also used to safely 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/`).

-## Using `ref` and `relref`

-```django

-{{</* ref "document" */>}}

-{{</* ref "#anchor" */>}}

-{{</* ref "document#anchor" */>}}

-{{</* relref "document" */>}}

-{{</* relref "#anchor" */>}}

-{{</* relref "document#anchor" */>}}

-```

-The single parameter to `ref` is a string with a content _document name_ (`about.md`), an in-document _anchor_ (`#who`), or both (`about.md#who`).

-### Document Names

-The _document name_ 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.

-    {{</* relref "blog/post.md" */>}} ⇒ `/blog/post/`

-    {{</* relref "post.md" */>}} ⇒ `/blog/post/`

-If you have multiple sections with the same filename, you should only use the relative path format, because the behaviour is _undefined_. So, if I also have a document `link/post.md`, the output of `ref` is unknown for `post.md`.

-    {{</* relref "blog/post.md" */>}} ⇒ `/blog/post/`

-    {{</* relref "post.md" */>}} ⇒ `/blog/post/` (maybe)

-    {{</* relref "post.md" */>}} ⇒ `/link/post/` (maybe)

-    {{</* relref "link/post.md" */>}} ⇒ `/link/post/`

-A relative document name must *not* begin with a slash (`/`).

-    {{</* relref "/blog/post.md" */>}} ⇒ `""`

-### Anchors

-When an _anchor_ is provided by itself, the current page’s unique identifier will be appended; when an _anchor_ is provided with a document name, the found page's unique identifier will be appended.

-    {{</* relref "#who" */>}} ⇒ `#who:9decaf7`

-    {{</* 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" */>}}` ⇒ `http://1.com/blog/post/`

-* `{{</* ref "post.md#tldr" */>}}` ⇒ `http://1.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`

-## Hugo Heading Anchors

-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.

-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`.

-`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 "extras/crossreferences.md#hugo-heading-anchors" */>}}

-    /extras/crossreferences/#hugo-heading-anchors:77cd9ea530577debf4ce0f28c8dca242

-> What follows is a deeper discussion of *why* and *how* Hugo generates heading anchors. It is not necessary to know this to use `ref` and `relref`, but it may be useful in understanding how some anchors may not match your expectations.

-### How to Generate a Heading Anchor

-Convert the text of the heading to lowercase.

-    Hugo: A Fast & Modern Static Web Engine

-    hugo: a fast & modern static web engine

-Replace anything that isn't an ASCII letter (`a-z`) or number (`0-9`) with a dash (`-`).

-    hugo: a fast & modern static web engine

-    hugo--a-fast---modern-static-web-engine

-Get rid of extra dashes.

-    hugo--a-fast---modern-static-web-engine

-    hugo-a-fast-modern-static-web-engine

-You have just converting the text of a heading to a suitable anchor. If your document has unique heading text, all of the anchors will be unique, too.

-#### Specifying Heading Anchors

-You can also tell Hugo to use a particular heading anchor.

-    # Hugo: A Fast & Modern Static Web Engine {#hugo-main}

-Hugo will use `hugo-main` as the heading anchor.

-### What About Duplicate Heading Anchors?

-The technique outlined above works well enough, but some documents have headings with identical text, like the [shortcodes](/extras/shortcodes/) page—there are three headings with the text "Example". You can specify heading anchors manually:

-    ### Example {#example-1}

-    ### Example {#example-2}

-    ### Example {#example-3}

-It’s easy to forget to do that all the time, and Hugo is smart enough to do it for you. It just adds `-x` to the end of each heading it has already seen.

-* `### Example` ⇒ `example`

-* `### Example` ⇒ `example-1`

-* `### Example` ⇒ `example-2`

-Sometimes it's a little harder, but Hugo can recover from those, too, by adding more suffixes:

-* `# Heading` ⇒ `heading`

-* `# Heading 1` ⇒ `heading-1`

-* `# Heading` ⇒ `heading-1-1`

-* `# Heading` ⇒ `heading-1-2`

-* `# Heading 1` ⇒ `heading-2`

-This can even affect specified heading anchors that come after a generated heading anchor.

-* `# My Heading` ⇒ `my-heading`

-* `# My Heading {#my-heading}` ⇒ `my-heading-1`

-> This particular collision and override is unfortunate, but unavoidable because Hugo processes each heading for collision detection as it sees it during conversion.

-This technique works well for documents rendered on individual pages, like blog posts. What about on Hugo list pages?

-### Unique Heading Anchors in Lists

-Hugo converts each document from Markdown independently. it doesn’t know that `blog/post.md` has an "Example" heading that will collide with the "Example" heading in `blog/post2.md`. Even if it did know this, the addition of `blog/post3.md` should not cause the anchors for the headings in the other blog posts to change.

-Enter the document’s unique identifier. To prevent this sort of collision on

-list pages, Hugo always appends the document's to a generated heading anchor.

-So, the "Example" heading in `blog/post.md` actually turns into

-`#example:81df004…`, and the "Example" heading in `blog/post2.md` actually

-turns into `#example:8cf1599…`. All you have to know is the heading anchor that

-was generated, not the document identifier; `ref` and `relref` take care of the

-rest for you.

-    <a href='{{</* relref "blog/post.md#example" */>}}'>Post Example</a>

-    <a href='/blog/post.md#81df004…'>Post Example</a>

-    [Post Two Example]({{</* relref "blog/post2.md#example" */>}})

-    <a href='/blog/post2.md#8cf1599…'>Post Two Example</a>

-Now you know.

--- a/content/extras/datadrivencontent.md

+++ /dev/null

@@ -1,142 +1,0 @@

----

-aliases:

-- /doc/datadrivencontent/

-lastmod: 2016-03-03

-date: 2015-02-14

-menu:

-  main:

-    parent: extras

-next: /extras/gitinfo

-prev: /extras/datafiles

-title: Data-driven Content

-toc: true

----

-Data-driven content with a static site generator? Yes, it is possible!

-In addition to the [data files](/extras/datafiles/) feature, we have also

-implemented the feature "Data-driven Content", which lets you load

-any [JSON](http://www.json.org/) or

-[CSV](http://en.wikipedia.org/wiki/Comma-separated_values) file

-from nearly any resource.

-"Data-driven Content" currently consists of two functions, `getJSON`

-and `getCSV`, which are available in **all template files**.

-## Implementation details

-### Calling the functions with an URL

-In any HTML template or Markdown document, call the functions like this:

-	{{ $dataJ := getJSON "url" }}

-	{{ $dataC := getCSV "separator" "url" }}

-or, if you use a prefix or postfix for the URL, the functions

-accept [variadic arguments](http://en.wikipedia.org/wiki/Variadic_function):

-	{{ $dataJ := getJSON "url prefix" "arg1" "arg2" "arg n" }}

-	{{ $dataC := getCSV  "separator" "url prefix" "arg1" "arg2" "arg n" }}

-The separator for `getCSV` must be put in the first position and can only

-be one character long.

-All passed arguments will be joined to the final URL; for example:

-	{{ $urlPre := "https://api.github.com" }}

-	{{ $gistJ := getJSON $urlPre "/users/GITHUB_USERNAME/gists" }}

-will resolve internally to:

-	{{ $gistJ := getJSON "https://api.github.com/users/GITHUB_USERNAME/gists" }}

-Finally, you can range over an array. This example will output the

-first 5 gists for a GitHub user:

-	<ul>

-	  {{ $urlPre := "https://api.github.com" }}

-	  {{ $gistJ := getJSON $urlPre "/users/GITHUB_USERNAME/gists" }}

-	  {{ range first 5 $gistJ }}

-	    {{ if .public }}

-	      <li><a href="{{ .html_url }}" target="_blank">{{ .description }}</a></li>

-	    {{ end }}

-	  {{ end }}

-	</ul>

-### Example for CSV files

-For `getCSV`, the one-character long separator must be placed in the

-first position followed by the URL.

-	<table>

-	  <thead>

-	    <tr>

-		<th>Name</th>

-		<th>Position</th>

-		<th>Salary</th>

-	    </tr>

-	  </thead>

-	  <tbody>

-	  {{ $url := "http://a-big-corp.com/finance/employee-salaries.csv" }}

-	  {{ $sep := "," }}

-	  {{ range $i, $r := getCSV $sep $url }}

-	    <tr>

-	      <td>{{ index $r 0 }}</td>

-	      <td>{{ index $r 1 }}</td>

-	      <td>{{ index $r 2 }}</td>

-	    </tr>

-	  {{ end }}

-	  </tbody>

-	</table>

-The expression `{{index $r number}}` must be used to output the nth-column from

-the current row.

-### Caching of URLs

-Each downloaded URL will be cached in the default folder `$TMPDIR/hugo_cache/`.

-The variable `$TMPDIR` will be resolved to your system-dependent

-temporary directory.

-With the command-line flag `--cacheDir`, you can specify any folder on

-your system as a caching directory.

-You can also set `cacheDir` in the main configuration file.

-If you don't like caching at all, you can fully disable caching with the

-command line flag `--ignoreCache`.

-### Authentication when using REST URLs

-Currently, you can only use those authentication methods that can

-be put into an URL. [OAuth](http://en.wikipedia.org/wiki/OAuth) or

-other authentication methods are not implemented.

-### Loading local files

-To load local files with the two functions `getJSON` and `getCSV`, the

-source files must reside within Hugo's working directory. The file

-extension does not matter but the content does.

-It applies the same output logic as in the topic: *Calling the functions with an URL*.

-## LiveReload

-There is no chance to trigger a [LiveReload](/extras/livereload/) when

-the content of an URL changes. However, when a local JSON/CSV file changes,

-then a LiveReload will be triggered of course. Symlinks are not supported.

-**URLs and LiveReload**: If you change any local file and the LiveReload

-is triggered, Hugo will either read the URL content from the cache or, if

-you have disabled the cache, Hugo will re-download the content.

-This can create huge traffic and you may also reach API limits quickly.

-As downloading of content takes a while, Hugo stops processing

-your Markdown files until the content has been downloaded.

-## Examples

-- Photo gallery JSON powered: [https://github.com/pcdummy/hugo-lightslider-example](https://github.com/pcdummy/hugo-lightslider-example)

-- GitHub Starred Repositories [in a posts](https://github.com/SchumacherFM/blog-cs/blob/master/content%2Fposts%2Fgithub-starred.md) with the related [short code](https://github.com/SchumacherFM/blog-cs/blob/master/layouts%2Fshortcodes%2FghStarred.html).

-- More?  Please tell us!

--- a/content/extras/datafiles.md

+++ /dev/null

@@ -1,106 +1,0 @@

----

-aliases:

-- /doc/datafiles/

-lastmod: 2015-08-04

-date: 2015-01-22

-menu:

-  main:

-    parent: extras

-next: /extras/datadrivencontent

-prev: /extras/robots-txt

-title: Data Files

----

-In addition to the [built-in variables](/templates/variables/) available from Hugo, you can specify your own custom data that can be accessed via templates or shortcodes.

-Hugo supports loading data from [YAML](http://yaml.org/), [JSON](http://www.json.org/), and [TOML](https://github.com/toml-lang/toml) files located in the `data` directory.

-**It even works with [LiveReload](/extras/livereload/).**

-Data Files can also be used in [themes](/themes/overview/), but note: If the same `key` is used in both the main data folder and in the theme's data folder, the main one will win. So, for theme authors,  for theme specific data items that shouldn't be overridden, it can be wise to prefix the folder structure with a namespace, e.g. `mytheme/data/mytheme/somekey/...`. To check if any such duplicate exists, run hugo with the `-v` flag, e.g. `hugo -v`.

-## The Data Folder

-The `data` folder is where you can store additional data for Hugo to use when generating your site. Data files aren't used to generate standalone pages - rather they're meant to supplement the content files. This feature can extend the content in case your frontmatter would grow immensely. Or perhaps you want to show a larger dataset in a template (see example below). In both cases it's a good idea to outsource the data in their own file.

-These files must be YAML, JSON or TOML files (using either the `.yml`, `.yaml`, `.json` or `toml` extension) and the data will be accessible as a `map` in `.Site.Data`.

-**The keys in this map will be a dot chained set of _path_, _filename_ and _key_ in file (if applicable).**

-This is best explained with an example:

-## Example: Jaco Pastorius' Solo Discography

-[Jaco Pastorius](http://en.wikipedia.org/wiki/Jaco_Pastorius_discography) was a great bass player, but his solo discography is short enough to use as an example. [John Patitucci](http://en.wikipedia.org/wiki/John_Patitucci) is another bass giant.

-The example below is a bit constructed, but it illustrates the flexibility of Data Files. It uses TOML as file format.

-Given the files:

-* `data/jazz/bass/jacopastorius.toml`

-* `data/jazz/bass/johnpatitucci.toml`

-`jacopastorius.toml` contains the content below, `johnpatitucci.toml` contains a similar list:

-```

-discography = [

-"1974 – Modern American Music … Period! The Criteria Sessions",

-"1974 – Jaco",

-"1976 - Jaco Pastorius",

-"1981 - Word of Mouth",

-"1981 - The Birthday Concert (released in 1995)",

-"1982 - Twins I & II (released in 1999)",

-"1983 - Invitation",

-"1986 - Broadway Blues (released in 1998)",

-"1986 - Honestly Solo Live (released in 1990)",

-"1986 - Live In Italy (released in 1991)",

-"1986 - Heavy'n Jazz (released in 1992)",

-"1991 - Live In New York City, Volumes 1-7.",

-"1999 - Rare Collection (compilation)",

-"2003 - Punk Jazz: The Jaco Pastorius Anthology (compilation)",

-"2007 - The Essential Jaco Pastorius (compilation)"

-]

-```

-The list of bass players can be accessed via `.Site.Data.jazz.bass`, a single bass player by adding the filename without the suffix, e.g. `.Site.Data.jazz.bass.jacopastorius`.

-You can now render the list of recordings for all the bass players in a template:

-```

-{{ range $.Site.Data.jazz.bass }}

-   {{ partial "artist.html" . }}

-{{ end }}

-```

-And then in `partial/artist.html`:

-```

-<ul>

-{{ range .discography }}

-  <li>{{ . }}</li>

-{{ end }}

-</ul>

-```

-Discover a new favourite bass player? Just add another TOML-file.

-## Example: Accessing named values in a Data File

-Assuming you have the following YAML structure to your `User0123.yml` Data File located directly in `data/`

-```

-Name: User0123

-"Short Description": "He is a **jolly good** fellow."

-Achievements:

-  - "Can create a Key, Value list from Data File"

-  - "Learns Hugo"

-  - "Reads documentation"

-```

-To render the `Short Description` in your `layout` File following code is required.

-```

-<div>Short Description of {{.Site.Data.User0123.Name}}: <p>{{ index .Site.Data.User0123 "Short Description" | markdownify }}</p></div>

-```

-Note the use of the `markdownify` template function. This will send the description through the Blackfriday Markdown rendering engine.

--- a/content/extras/gitinfo.md

+++ /dev/null

@@ -1,54 +1,0 @@

----

-aliases:

-- /doc/gitinfo/

-lastmod: 2016-12-11

-date: 2016-12-11

-menu:

-  main:

-    parent: extras

-next: /extras/livereload

-prev: /extras/datadrivencontent

-title: GitInfo

----

-Hugo provides a way to integrate Git data into your site.

-## Prerequisites

-1. The Hugo site must be in a Git-enabled directory.

-1. The Git executable must be installed and in your system `PATH`.

-1. Enable the GitInfo feature in Hugo by using `--enableGitInfo` on the command

-   line or by setting `enableGitInfo` to `true` in your site configuration.

-## The GitInfo Object

-The `GitInfo` object contains the following fields:

-AbbreviatedHash

-: abbreviated commit hash, e.g. `866cbcc`

-AuthorName

-: author name, respecting `.mailmap`

-AuthorEmail

-: author email address, respecting `.mailmap`

-AuthorDate

-: the author date

-Hash

-: commit hash, e.g. `866cbccdab588b9908887ffd3b4f2667e94090c3`

-Subject

-: commit message subject, e.g. `tpl: Add custom index function`

-## Other Considerations

-The Git integrations should be fairly performant, but it does add some time to the build, which depends somewhat on the Git history size.

-The accuracy of data depends on the underlying local git respository.  If the local repository is a *shallow clone*, then any file that hasn't been modified in the truncated history will default to data in the oldest commit.  In particular, if the respository has been cloned using `--depth=1` then every file will the exact same `GitInfo` data -- that of the only commit in the repository.

-In particular, many CI/CD systems such as [travis-ci.org](https://travis-ci.org) default to a clone depth of 50 which is unlikely to be deep enough.  You can explicitly add back the missing history using using `git fetch --unshallow` or [make the initial checkout deeper](https://docs.travis-ci.com/user/customizing-the-build#Git-Clone-Depth).

--- a/content/extras/highlighting.md

+++ /dev/null

@@ -1,197 +1,0 @@

----

-aliases:

-- /extras/highlight/

-lastmod: 2015-10-27

-date: 2013-07-01

-menu:

-  main:

-    parent: extras

-next: /extras/toc

-prev: /extras/shortcodes

-title: Syntax Highlighting

-toc: true

----

-Hugo provides the ability for you to highlight source code in _two different ways_ &mdash; either pre-processed server side from your content, or to defer the processing to the client side, using a JavaScript library.

-**The advantage of server side** is that it doesn’t depend on a JavaScript library and consequently works very well when read from an RSS feed.

-**The advantage of client side** is that it doesn’t cost anything when building your site and some of the highlighting scripts available cover more languages than Pygments does.

-## Server-side

-For the pre-processed approach, highlighting is performed by an external Python-based program called [Pygments](http://pygments.org/) and is triggered via an embedded Hugo shortcode (see example below). If Pygments is absent from the path, it will silently simply pass the content along unhighlighted.

-### Pygments

-If you have never worked with Pygments before, here is a brief primer:

-+ Install Python from [python.org](https://www.python.org/downloads/). Version 2.7.x is already sufficient.

-+ Run `pip install Pygments` in order to install Pygments. Once installed, Pygments gives you a command `pygmentize`. Make sure it sits in your PATH, otherwise Hugo cannot find it.

-On Debian and Ubuntu systems, you may also install Pygments by running `sudo apt-get install python3-pygments`.

-Hugo gives you two options that you can set with the variable `pygmentsuseclasses` (default `false`) in `config.toml` (or `config.yaml`).

-1. Color-codes for highlighting keywords are directly inserted if `pygmentsuseclasses = false` (default). See in the example below. The color-codes depend on your choice of the `pygmentsstyle` (default `"monokai"`). You can explore the different color styles on [pygments.org](http://pygments.org/) after inserting some example code.

-2. If you choose `pygmentsuseclasses = true`, Hugo includes class names in your code instead of color-codes. For class-names to be meaningful, you need to include a `.css`-file in your website representing your color-scheme. You can either generate this `.css`-files according to this [description](http://pygments.org/docs/cmdline/) or download the standard ones from the [GitHub pygments-css repository](https://github.com/richleland/pygments-css).

-### Usage

-Highlighting is carried out via the in-built shortcode `highlight`. `highlight` takes exactly one required parameter of language, and requires a closing shortcode. Note that `highlight` is _not_ used for client-side javascript highlighting.

-### Example

-```

-{{</* highlight html */>}}

-<section id="main">

-  <div>

-    <h1 id="title">{{ .Title }}</h1>

-    {{ range .Data.Pages }}

-      {{ .Render "summary"}}

-    {{ end }}

-  </div>

-</section>

-{{</* /highlight */>}}

-```

-### Example Output

-```

-<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 }}

-      {{ .Render &quot;summary&quot;}}

-    {{ end }}

-  <span style="color: #f92672">&lt;/div&gt;</span>

-<span style="color: #f92672">&lt;/section&gt;</span>

-```

-### Options

-Options to control highlighting can be added as a quoted, comma separated key-value list as the second argument in the shortcode. The example below will highlight as language `go` with inline line numbers, with line number 2 and 3 highlighted.

-```

-{{</* highlight go "linenos=inline,hl_lines=2 3" */>}}

-var a string

-var b string

-var c string

-var d string

-{{</* / highlight */>}}

-```

-Supported keywords:  `style`, `encoding`, `noclasses`, `hl_lines`, `linenos`. Note that `style` and `noclasses` will override the similar setting in the global config.

-The keywords are the same you would using with Pygments from the command line, see the [Pygments doc](http://pygments.org/docs/) for more info.

-### Code fences

-It is also possible to add syntax highlighting with GitHub flavoured code fences. To enable this, set the `PygmentsCodeFences` to `true` in Hugo's configuration file.

-````

-``` html

-<section id="main">

-  <div>

-    <h1 id="title">{{ .Title }}</h1>

-    {{ range .Data.Pages }}

-      {{ .Render "summary"}}

-    {{ end }}

-  </div>

-</section>

-```

-````

-### Disclaimers

- * Pygments is relatively slow and _causes a performance hit when building your site_, but Hugo has been designed to cache the results to disk.

- * The caching can be turned off by setting the `--ignoreCache` flag to `true`.

- * Languages available depends on your Pygments installation.

-## Client-side

-Alternatively, code highlighting can be done in client-side JavaScript.

-Client-side syntax highlighting is very simple to add. You'll need to pick

-a library and a corresponding theme. Some popular libraries are:

-- [Highlight.js]

-- [Prism]

-- [Rainbow]

-- [Syntax Highlighter]

-- [Google Prettify]

-### Highlight.js example

-This example uses the popular [Highlight.js] library, hosted by [Yandex], a popular Russian search engine.

-In your `./layouts/partials/` (or `./layouts/chrome/`) folder, depending on your specific theme, there will be a snippet that will be included in every generated HTML page, such as `header.html` or `header.includes.html`. Simply add the css and js to initialize [Highlight.js]:

-~~~

-<link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.6.0/styles/default.min.css">

-<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.6.0/highlight.min.js"></script>

-<script>hljs.initHighlightingOnLoad();</script>

-~~~

-### Prism example

-Prism is another popular highlighter library, used on some major sites. Similar to Highlight.js, you simply load `prism.css` in your `<head>` via whatever Hugo partial template is creating that part of your pages, like so:

-```html

-...

-<link href="/css/prism.css" rel="stylesheet" />

-...

-```

-... and add `prism.js` near the bottom of your `<body>` tag, again in whatever Hugo partial template is appropriate for your site or theme.

-```html

-...

-<script src="/js/prism.js"></script>

-...

-</body>

-```

-In this example, the local paths indicate that your own copy of these files are being added to the site, typically under `./static/`.

-### Using Client-side highlighting

-To use client-side highlighting, most of these javascript libraries expect your code to be wrapped in semantically correct `<code>` tags, with the language expressed in a class attribute on the `<code>` tag, such as `class="language-abc"`, where the `abc` is the code the highlighter script uses to represent that language.

-The script would be looking for classes like `language-go`, `language-html`, or `language-css`. If you look at the page's source, it would be marked up like so:

-~~~html

-<pre>

-<code class="language-css">

-body {

-  font-family: "Noto Sans", sans-serif;

-}

-</code>

-</pre>

-~~~

-The markup in your content pages (e.g. `my-css-tutorial.md`) needs to look like the following, with the name of the language to be highlighted entered directly after the first "fence", in a fenced code block:

-<pre><code class="language-css">&#126;&#126;&#126;css

-body {

-  font-family: "Noto Sans", sans-serif;

-}

-&#126;&#126;&#126;</code></pre>

-When passed through the highlighter script, it would yield something like this output when viewed on your rendered page:

-~~~css

-body {

-  font-family: "Noto Sans", sans-serif;

-}

-~~~

-Please see individual libraries' documentation for how to implement each of the JavaScript-based libraries.

-[Prism]: http://prismjs.com

-[Highlight.js]: http://highlightjs.org/

-[Rainbow]: http://craig.is/making/rainbows

-[Syntax Highlighter]: http://alexgorbatchev.com/SyntaxHighlighter/

-[Google Prettify]: https://github.com/google/code-prettify

-[Yandex]: http://yandex.ru/

--- a/content/extras/livereload.md

+++ /dev/null

@@ -1,74 +1,0 @@

----

-lastmod: 2016-08-09

-date: 2014-05-26

-menu:

-  main:

-    parent: extras

-next: /extras/menus

-prev: /extras/gitinfo

-title: LiveReload

----

-Hugo may not be the first static site generator to utilize LiveReload

-technology, but it’s the first to do it right.

-The combination of Hugo’s insane build speed and LiveReload make

-crafting your content pure joy. Virtually instantly after you hit save

-your rebuilt content will appear in your browser.

-## Using LiveReload

-Hugo comes with LiveReload built in. There are no additional packages to

-install. A common way to use Hugo while developing a site is to have

-Hugo run a server and watch for changes:

-{{< nohighlight >}}$ hugo server

-{{< /nohighlight >}}

-This will run a full functioning web server while simultaneously

-watching your file system for additions, deletions or changes within

-your:

- * static files

- * content

- * data files

- * layouts

- * current theme

- * configuration files

-Whenever anything changes, Hugo will rebuild the site while continuing to serve

-the content. As soon as the build is finished, it will tell the

-browser and silently reload the page. Because most Hugo builds are so

-fast they are barely noticeable, you merely need to glance at your open

-browser and you will see the change, already there.

-This means that keeping the site open on a second monitor (or another

-half of your current monitor) allows you to see exactly what your

-content looks like, without even leaving your text editor.

-## Disabling Watch

-If for some reason you don't want the Hugo server's watch functionality,

-just do:

-{{< nohighlight >}}$ hugo server --watch=false

-{{< /nohighlight >}}

-## Disabling LiveReload

-LiveReload works by injecting JavaScript into the pages Hugo generates,

-which creates a connection from the browser web socket client to the

-Hugo web socket server.

-Awesome for development, but not something you would want to do in

-production. Since many people use `hugo server` in production to

-instantly display any updated content, we’ve made it easy to disable the

-LiveReload functionality:

-{{< nohighlight >}}$ hugo server --disableLiveReload

-{{< /nohighlight >}}

-## Notes

-You must have a closing `</body>` tag for LiveReload to work.

-Hugo injects the LiveReload `<script>` before this tag.

--- a/content/extras/localfiles.md

+++ /dev/null

@@ -1,57 +1,0 @@

----

-aliases:

-- /doc/localfiles/

-lastmod: 2016-09-12

-date: 2015-06-12

-menu:

-  main:

-    parent: extras

-next: /extras/urls

-notoc: true

-prev: /extras/toc

-title: Traversing Local Files

----

-## Traversing Local Files

-Using Hugo's function `readDir`,

-you can traverse your web site's files on your server.

-## Using _readDir_

-The `readDir` function returns an array

-of [`os.FileInfo`](https://golang.org/pkg/os/#FileInfo).

-It takes a single, string argument: a path.

-This path can be to any directory of your web site

-(as found on your server's filesystem).

-Whether the path is absolute or relative makes no difference,

-because&mdash;at least for `readDir`&mdash;the root of your web site (typically `./public/`)

-in effect becomes both:

-1. The filesystem root; and

-1. The current working directory.

-## New Shortcode

-So, let's create a new shortcode using `readDir`:

-**layouts/shortcodes/directoryindex.html**

-```html

-{{< readfile "layouts/shortcodes/directoryindex.html" >}}

-```

-For the files in any given directory,

-this shortcode usefully lists their basenames and sizes,

-while providing links to them.

-Already&mdash;actually&mdash;this shortcode

-has been included in this very web site.

-So, let's list some of its CSS files.

-(If you click on their names, you can reveal the contents.)

-{{<   directoryindex path="/static/css" pathURL="/css"   >}}

-<br />

-This is the call that rendered the above output:

-```html

-{{</* directoryindex path="/static/css" pathURL="/css" */>}}

-```

-By the way,

-regarding the pathURL argument, the initial slash `/` is important.

-Otherwise, it becomes relative to the current web page.

--- a/content/extras/menus.md

+++ /dev/null

@@ -1,393 +1,0 @@

----

-lastmod: 2015-08-04

-date: 2014-05-14T02:36:37Z

-toc: true

-menu:

-  main:

-    parent: extras

-next: /extras/pagination

-prev: /extras/livereload

-title: Menus

----

-Hugo has a simple yet powerful menu system that permits content to be

-placed in menus with a good degree of control without a lot of work.

-*TIP:* If all you want is a simple menu for your sections, see [Section Menu for "the Lazy Blogger"]({{< relref "#section-menu-for-the-lazy-blogger" >}}).

-Some of the features of Hugo Menus:

-* Place content in one or many menus

-* Handle nested menus with unlimited depth

-* Create menu entries without being attached to any content

-* Distinguish active element (and active branch)

-## What is a menu?

-A menu is a named array of menu entries accessible on the site under

-`.Site.Menus` by name. For example, if I have a menu called `main`, I would

-access it via `.Site.Menus.main`.

-If you make use of the [multilingual feature]({{< relref "content/multilingual.md#menus">}}) you can define menus language independent.

-A menu entry has the following properties:

-* `URL        string`

-* `Name       string`

-* `Menu       string`

-* `Identifier string`

-* `Pre        template.HTML`

-* `Post       template.HTML`

-* `Weight     int`

-* `Parent     string`

-* `Children   Menu`

-And the following functions:

-* `HasChildren() bool`

-Additionally, the `Page` object has two functions, which can be used when rendering menus:

-* `IsMenuCurrent (menu string, menuEntry *MenuEntry ) bool`

-* `HasMenuCurrent** (menu string, menuEntry *MenuEntry) bool`

-See [Menu Functions](#menu-functions) for explanations of these functions, and [Rendering Nested Menus](#rendering-nested-menus) for an example of their use.

-## Adding content to menus

-Hugo supports a couple of different methods of adding a piece of content

-to the front matter.

-### Simple

-If all you need to do is add an entry to a menu, the simple form works

-well.

-**A single menu:**

-    ---

-    menu: "main"

-    ---

-**Multiple menus:**

-    ---

-    menu: ["main", "footer"]

-    ---

-### Advanced

-If more control is required, then the advanced approach gives you the

-control you want. All of the menu entry properties listed above are

-available.

-    ---

-    menu:

-      main:

-        parent: 'extras'

-        weight: 20

-    ---

-## Adding (non-content) entries to a menu

-You can also add entries to menus that aren’t attached to a piece of

-content. This takes place in the sitewide [config file](/overview/configuration/).

-Here’s an example `config.toml`:

-    [[menu.main]]

-        name = "about hugo"

-        pre = "<i class='fa fa-heart'></i>"

-        weight = -110

-        identifier = "about"

-        url = "/about/"

-    [[menu.main]]

-        name = "getting started"

-        pre = "<i class='fa fa-road'></i>"

-        weight = -100

-        url = "/getting-started/"

-And the equivalent example `config.yaml`:

-    ---

-    menu:

-      main:

-          - Name: "about hugo"

-            Pre: "<i class='fa fa-heart'></i>"

-            Weight: -110

-            Identifier: "about"

-            URL: "/about/"

-          - Name: "getting started"

-            Pre: "<i class='fa fa-road'></i>"

-            Weight: -100

-            URL: "/getting-started/"

-    ---

-**NOTE:** The URLs must be relative to the context root. If the `baseURL` is `http://example.com/mysite/`, then the URLs in the menu must not include the context root `mysite`. Using an absolute URL will overide the baseURL. If the `URL` is `http://subdomain.example.com/`, the output will be `http://subdomain.example.com`.

-## Nesting

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

-The parent of an entry should be the identifier of another entry.

-Identifier should be unique (within a menu).

-The following order is used to determine an Identifier:

-> Name > LinkTitle > Title.

-This means that the title will be used unless

-linktitle is present, etc. In practice Name and Identifier are never

-displayed and only used to structure relationships.

-In this example, the top level of the menu is defined in the config file

-and all content entries are attached to one of these entries via the

-`parent` field.

-## Rendering menus

-Hugo makes no assumptions about how your rendered HTML will be

-structured. Instead, it provides all of the functions you will need to be

-able to build your menu however you want.

-The following is an example:

-    <!--sidebar start-->

-    <aside>

-        <div id="sidebar" class="nav-collapse">

-            <!-- sidebar menu start-->

-            <ul class="sidebar-menu">

-              {{ $currentPage := . }}

-              {{ range .Site.Menus.main }}

-                  {{ if .HasChildren }}

-                <li class="sub-menu{{if $currentPage.HasMenuCurrent "main" . }} active{{end}}">

-                <a href="javascript:;" class="">

-                    {{ .Pre }}

-                    <span>{{ .Name }}</span>

-                    <span class="menu-arrow arrow_carrot-right"></span>

-                </a>

-                <ul class="sub">

-                    {{ range .Children }}

-                    <li{{if $currentPage.IsMenuCurrent "main" . }} class="active"{{end}}><a href="{{.URL}}"> {{ .Name }} </a> </li>

-                    {{ end }}

-                </ul>

-              {{else}}

-                <li>

-                <a href="{{.URL}}">

-                    {{ .Pre }}

-                    <span>{{ .Name }}</span>

-                </a>

-              {{end}}

-              </li>

-              {{end}}

-                <li> <a href="https://github.com/gohugoio/hugo/issues" target="blank">Questions and Issues</a> </li>

-                <li> <a href="#" target="blank">Edit this Page</a> </li>

-            </ul>

-            <!-- sidebar menu end-->

-        </div>

-    </aside>

-    <!--sidebar end-->

-> **Note**: use the `absLangURL` or `relLangURL` if your theme makes use of the [multilingual feature]({{< relref "content/multilingual.md" >}}). In contrast to `absURL` and `relURL` it adds the correct language prefix to the url. [Read more]({{< relref "templates/functions.md#urls" >}}).

-## Section Menu for "the Lazy Blogger"

-To enable this menu, add this to your site config, i.e. `config.toml`:

-```

-SectionPagesMenu = "main"

-```

-The menu name can be anything, but take a note of what it is.

-This will create a menu with all the sections as menu items and all the sections' pages as "shadow-members". The _shadow_ implies that the pages isn't represented by a menu-item themselves, but this enables you to create a top-level menu like this:

-```

-  <nav class="sidebar-nav">

-        {{ $currentPage := . }}

-        {{ range .Site.Menus.main }}

-        <a class="sidebar-nav-item{{if or ($currentPage.IsMenuCurrent "main" .) ($currentPage.HasMenuCurrent "main" .) }} active{{end}}" href="{{.URL}}">{{ .Name }}</a>

-        {{ end }}

-    </nav>

-```

-In the above, the menu item is marked as active if on the current section's list page or on a page in that section.

-The above is all that's needed. But if you want custom menu items, e.g. changing weight or name, you can define them manually in the site config, i.e. `config.toml`:

-```

- [[menu.main]]

-        name = "This is the blog section"

-        weight = -110

-        identifier = "blog"

-        url = "/blog/"

-```

-**Note** that the `identifier` must match the section name.

-## Menu Functions

-Suppose you have the menu structure shown below.

-```

-    [menu.main]

-    │

-    ├───colour

-    │   │

-    │   ├───warm

-    │   │   ├───orange

-    │   │   ├───red

-    │   │   └───yellow

-    │   │

-    │   └───cool

-    │       ├───blue

-    │       ├───green

-    │       └───purple

-    │

-    └───tool

-        ├───hammer

-        ├───shovel

-        └───saw

-```

-For each menu item, you can determine:

-* If the menu item has any children: `.HasChildren()`

-* If the menu item is a parent of the page you are currently rendering: `.Page.HasMenuCurrent()`

-* If the menu item **is** the page you are currently rendering: `.Page.IsMenuCurrent()`

-For example, if you are currently rendering the page `/colour/warm`, the values of `.HasChildren`, `HasMenuCurrent`, and `IsMenuCurrent` would be as shown below:

-```

-    [menu.main]           |                |               |             |

-    │                     |                |               |             |

-    ├───colour            | HasMenuCurrent |               | HasChildren |

-    │   ├───<< WARM >>    |                | IsMenuCurrent | HasChildren |

-    │   │   ├───orange    |                |               |             |

-    │   │   ├───red       |                |               |             |

-    │   │   └───yellow    |                |               |             |

-    │   └───cool          |                |               | HasChildren |

-    │       ├───blue      |                |               |             |

-    │       ├───green     |                |               |             |

-    │       └───purple    |                |               |             |

-    └───tool              |                |               | HasChildren |

-        ├───hammer        |                |               |             |

-        ├───shovel        |                |               |             |

-        └───saw           |                |               |             |

-```

-## Rendering nested menus

-Hugo supports nested menus with as many levels as you like.

-Nested menus can be rendered using a recursive partial template, such as the example below.

-```

-<!-- layouts/index.html, layouts/_default/single.html, ... -->

-<h1>{{ .Title }}</h1>

-<!-- Put this line in your main template, at the place where you want to

-     render the menu. -->

-{{ partial "menu_include.html" . }}

-```

-```

-<!-- layouts/partials/menu_include.html -->

-{{ partial "menu_recursive.html" (dict "menu" .Site.Menus.main "page" . "site" .Site) }}

-```

-```

-<!-- layouts/partials/menu_recursive.html -->

-{{ $page := .page }}

-{{ $site := .site }}

-<ul>

-{{ range .menu }}

-  {{ $is := $page.IsMenuCurrent "main" . }}

-  {{ $has := $page.HasMenuCurrent "main" . }}

-  {{ if .HasChildren }}

-    <li>

-      <a href="{{ .URL }}">

-        {{ .Name }}

-        {{ if $is }}[Is]{{ end }}

-        {{ if $has }}[Has]{{ end }}

-        {{ if .HasChildren }}[Children]{{ end }}

-      </a>

-        <!-- If the menu item has children, include this partial template again (recursively) -->

-        {{ partial "menu_recursive.html" (dict "menu" .Children "page" $page "site" $site) }}

-    </li>

-  {{ else }}

-    <li>

-      <a href="{{ .URL }}">

-        {{ .Name }}

-        {{ if $is }}[Is]{{ end }}

-        {{ if $has }}[Has]{{ end }}

-        {{ if .HasChildren }}[Children]{{ end }}

-      </a>

-    </li>

-  {{ end }}

-{{ end }}

-</ul>

-```

-This example code renders the words `[Is]`, `[Has]`, and `[Children]` to demonstrate how the `IsMenuCurrent()`, `HasMenuCurrent()`, and `HasChildren()` functions work.

-You can customise this example to implement features such as:

-* Highlight the current item, by applying a CSS style:

-        <a href="{{ .URL }}"{{ if $is }} class="active"{{ end }}>

-                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-* Highlight parents of the current item, by applying a CSS style:

-        <a href="{{ .URL }}"{{ if $has }} class="parent-active"{{ end }}>

-                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-* Only render sub-menus for parents of the current menu item, and the current menu item itself:

-        {{ if or $is $has }}

-            {{ partial "menu_recursive.html" (dict "menu" .Children "page" $page "site" $site) }}

-        {{ end }}

-A working example, implementing these features, is shown below.

-```

-<!-- layouts/partials/menu_recursive.html -->

-{{ $page := .page }}

-{{ $site := .site }}

-<ul>

-<!-- Menu items sorted alphabetically by name -->

-{{ range .menu.ByName }}

-  {{ $is := $page.IsMenuCurrent "main" . }}

-  {{ $has := $page.HasMenuCurrent "main" . }}

-  {{ if .HasChildren }}

-    <li>

-      <a href="{{ .URL }}" class="{{ if $is }} active{{ end }}{{ if $has }} parent-active{{ end }}">

-        {{ .Name }}

-        <!-- Show a » symbol if there is a sub-menu we haven't rendered -->

-        {{ if not (or $is $has) }}»{{ end }}

-      </a>

-      <!-- Only render sub-menu for parent items and the current item -->

-      {{ if or $is $has }}

-        {{ partial "menu_recursive.html" (dict "menu" .Children "page" $page "site" $site) }}

-      {{ end }}

-    </li>

-  {{ else }}

-    <li>

-      <a href="{{ .URL }}" class="{{ if $is }}active{{end}}">{{ .Name }}</a>

-    </li>

-  {{ end }}

-{{ end }}

-</ul>

-```

--- a/content/extras/output-formats.md

+++ /dev/null

@@ -1,185 +1,0 @@

----

-aliases:

-- /doc/output-formats/

-- /doc/custom-output/

-date: 2017-03-22T08:20:13+01:00

-menu:

-  main:

-    parent: extras

-title: Output Formats

-weight: 5

-toc: true

----

-Hugo `0.20` introduced the powerful feature **Custom Output Formats**; Hugo isn't just that "static HTML with an added RSS feed" anymore. _Say hello_ to calendars, e-book formats, Google AMP, and JSON search indexes, to name a few.

-This page describes how to properly configure your site with the media types and output formats you need.

-## Media Types

-A [media type](https://en.wikipedia.org/wiki/Media_type) (also known as MIME type and content type) is a two-part identifier for file formats and format contents transmitted on the Internet.

-This is the full set of built-in media types in Hugo:

-{{< datatable "media" "types" "Type" "Suffix" >}}

-**Note:**

-* It is possible to add custom media types or change the defaults (if you, say, want to change the suffix to `asp` for `text/html`).

-* The `Suffix` is the value that will be used for URLs and filenames for that media type in Hugo.

-* The `Type` is the identifier that must be used when defining new `Output Formats` (see below).

-* The `Delimiter` defaults to ".", but can be changed or even blanked out to support, as an example, Netlify's `_redirect` files.

-* The full set of media types will be registered in Hugo's built-in development server to make sure they are recognized by the browser.

-To add or modify a media type, define it in a `mediaTypes` section in your site config (either for all sites or for a given language).

-Example in `config.toml`:

-```toml

-[mediaTypes]

-[mediaTypes."text/enriched"]

-suffix = "enr"

-[mediaTypes."text/html"]

-suffix = "asp"

-```

-The above example adds one new media type, `text/enriched`, and changes the suffix for the built-in `text/html` media type.

-## Output Formats

-Given a media type and some additional configuration, you get an `Output Format`.

-This is the full set of built-in output formats in Hugo:

-{{< datatable "output" "formats" "Name" "MediaType" "Path" "BaseName" "Rel" "Protocol" "IsPlainText" "IsHTML" "NoUgly" "NotAlternative">}}

-**Note:**

-* A page can be output in as many output formats as you want, and you can have an infinite amount of output formats defined, as long as _they resolve to a unique path on the file system_. In the table above, the best example of this is `AMP` vs. `HTML`: We have given `AMP` a value for `Path` so it doesn't overwrite the `HTML` version, i.e. we can now have both `/index.html` and `/amp/index.html`.

-* The `MediaType` must match the `Type` of an already defined media type (see above).

-* You can define new or redefine built-in output formats (if you, as an example, want to put `AMP` pages in a different path).

-To add or modify a media type, define it in a `outputFormats` section in your site config (either for all sites or for a given language).

-Example in `config.toml`:

-```toml

-[outputFormats.MyEnrichedFormat]

-mediaType = "text/enriched"

-baseName = "myindex"

-isPlainText = true

-protocol = "bep://"

-```

-The above example is fictional, but if used for the home page on a site with `baseURL` `http://example.org`, it will produce a plain text home page with the URL `bep://example.org/myindex.enr`.

-All the available configuration options for output formats and their default values:

-Field | Description

---- | ---

-**Name** | The output format identifier. This is used to define what output format(s) you want for your pages.

-**MediaType**|This must match the `Type` of a defined media type. |

-**Path** | Sub path to save the output files.

-**BaseName** | The base filename for the list filenames (home page etc.). **Default:** _index_.

-**Rel** | Can be used to create `rel` values in `link` tags. **Default:** _alternate_.

-**Protocol** | Will replace the "http://" or "https://" in your `baseURL` for this output format.

-**IsPlainText** | Use Go's plain text templates parser for the templates. **Default:** _false_.

-**IsHTML** | Used in situations only relevant for `HTML` type of formats, page aliases being one example.|

-**NoUgly** | If `uglyURLs` is enabled globally, this can be used to turn it off for a given output format. **Default:** _false_.

-**NotAlternative** |  Enable if it doesn't make sense to include this format in an the `.AlternativeOutputFormats` format listing on `Page`, `CSS` being one good example. Note that we use the term "alternative" and not "alternate" here, as it does not necessarily replace the other format, it is an alternative representation.  **Default:** _false_.

-## Output Formats for your pages

-A `Page` in Hugo can be rendered to multiple representations on the file system: In its default configuration all will get an `HTML` page and some of them will get an `RSS` page (home page, sections etc.).

-This can be changed by defining an `outputs` list of output formats in either the `Page` front matter or in the site configuration (either for all sites or per language).

-Example from site config in `config.toml`:

-```toml

- [outputs]

- home = [ "HTML", "AMP", "RSS"]

- page = [ "HTML"]

- ```

- Note:

- * The output definition is per `Page` `Kind`(`page`, `home`, `section`, `taxonomy`, `taxonomyTerm`).

- * The names used must match the `Name` of a defined `Output Format`.

- * Any `Kind` without a definition will get `HTML`.

- * These can be overriden per `Page` in front matter (see below).

- * When `outputs` is specified, only the formats defined in outputs will be rendered

-A `Page` with `YAML` front matter defining some output formats for that `Page`:

-```yaml

----

- date: "2016-03-19"

- outputs:

- - html

- - amp

- - json

- ---

- ```

- Note:

- * The names used for the output formats are case insensitive.

- * The first output format in the list will act as the default.

- * The default output format is used when generating links to other pages in menus, etc.

-## Link to Output Formats

- `Page` has both  `.OutputFormats` (all formats including the current) and `.AlternativeOutputFormats`, the latter useful for creating a `link rel` list in your `head` section:

- ```

- {{ range .AlternativeOutputFormats -}}

- <link rel="{{ .Rel }}" type="{{ .MediaType.Type }}" href="{{ .Permalink | safeURL }}">

- {{ end -}}

-  ```

-Note that `.Permalink` on `RelPermalink` on `Page` will return the first output format defined for that page (usually `HTML` if nothing else is defined).

-This is how you link to a given output format:

-```

-{{ with  .OutputFormats.Get "json" -}}

-<a href="{{ .Permalink }}">{{ .Name }}</a>

-{{- end }}

-```

-From content files, you can use the `ref` or `relref` shortcodes:

-```

-[Neat]({{</* ref "blog/neat.md" "amp" */>}})

-[Who]({{</* relref "about.md#who" "amp" */>}})

-```

-## Templates for your Output Formats

-Of course, for a new Output Format to render anything useful, we need a template for it.

-**The fundamental thing to understand about this is that we in `Hugo 0.20` now also look at Output Format´s `Name` and MediaType´s `Suffix` when we choose the templates to use to render a given `Page`.**

-And with so many possible variations, this is best explained with some examples:

-{{< datatable "output" "layouts" "Example" "OutputFormat" "Suffix" "Template Lookup Order" >}}

-**Note:**

-* All of the above examples can use a base template, see [Blocks]({{< relref "templates/blocks.md" >}}).

-* All of the above examples can also include partials.

-Hugo will now also detect the media type and output format of partials, if possible, and use that information to decide if the partial should be parsed as a plain text template or not.

-Hugo will look for the name given, so you can name it whatever you want. But if you want it treated as plain text, you should use the file suffix and, if needed, the name of the Output Format (`[partial name].[OutputFormat].[suffix])`.

-The partial below is a plain text template (Output Format is `CSV`, and since this is the only output format with the suffix `csv`, we don't need to include the Output Format's `Name`):

-```

-{{ partial "mytextpartial.csv" . }}

-```

-Also note that plain text partials can currently only be included in plain text templates, and vice versa. See [this issue](https://github.com/gohugoio/hugo/issues/3273) for some background.

--- a/content/extras/pagination.md

+++ /dev/null

@@ -1,106 +1,0 @@

----

-aliases:

-- /doc/pagination/

-lastmod: 2015-07-16

-date: 2014-01-01

-menu:

-  main:

-    parent: extras

-next: /extras/permalinks

-prev: /extras/menus

-title: Pagination

----

-Hugo supports pagination for the home page, sections and taxonomies. It's built to be easy use, but with loads of flexibility when needed. The real power shines when you combine it with [`where`](/templates/functions/), with its SQL-like operators, `first` and others --- you can even [order the content](/templates/list/) the way you've become used to with Hugo.

-## Configuration

-Pagination can be configured in the site configuration (e.g. `config.toml`):

-* `Paginate` (default `10`) (this setting can be overridden in the template)

-* `PaginatePath` (default `page`)

-Setting `Paginate` to a positive value will split the list pages for the home page, sections and taxonomies into chunks of that size. But note that the generation of the pagination pages for sections, taxonomies and home page is *lazy* --- the pages will not be created if not referenced by a `.Paginator` (see below).

-`PaginatePath` is used to adapt the `URL` to the pages in the paginator (the default setting will produce URLs on the form `/page/1/`.

-## List the pages

-**A `.Paginator` is provided to help building a pager menu. This is currently only relevant for the templates for the home page and the list pages (sections and taxonomies).**

-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 sub-set 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 }}`.

-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 }}`

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

-```

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

-```

-## Build the navigation

-The `.Paginator` contains enough information to build a paginator interface.

-The easiest way to add this to your pages is to include the built-in template (with `Bootstrap`-compatible styles):

-```

-{{ template "_internal/pagination.html" . }}

-```

-**Note:** If you use any filters or ordering functions to create your `.Paginator` **and** you want the navigation buttons to be shown before the page listing, you must create the `.Paginator` before it's used:

-```

-{{ $paginator := .Paginate (where .Data.Pages "Type" "post") }}

-{{ template "_internal/pagination.html" . }}

-{{ range $paginator.Pages }}

-   {{ .Title }}

-{{ end }}

-```

-Without the where-filter, the above is simpler:

-```

-{{ template "_internal/pagination.html" . }}

-{{ range .Paginator.Pages }}

-   {{ .Title }}

-{{ end }}

-```

-If you want to build custom navigation, you can do so using the `.Paginator` object:

-* `PageNumber`: The current page's number in the pager sequence

-* `URL`: The relative URL to the current pager

-* `Pages`: The pages in the current pager

-* `NumberOfElements`: The number of elements on this page

-* `HasPrev`: Whether there are page(s) before the current

-* `Prev`: The pager for the previous page

-* `HasNext`: Whether there are page(s) after the current

-* `Next`: The pager for the next page

-* `First`: The pager for the first page

-* `Last`: The pager for the last page

-* `Pagers`: A list of pagers that can be used to build a pagination menu

-* `PageSize`: Size of each pager

-* `TotalPages`: The number of pages in the paginator

-* `TotalNumberOfElements`: The number of elements on all pages in this paginator

-## Additional information

-The pages are built on the following form (`BLANK` means no value):

-```

-[SECTION/TAXONOMY/BLANK]/index.html

-[SECTION/TAXONOMY/BLANK]/page/1/index.html => redirect to  [SECTION/TAXONOMY/BLANK]/index.html

-[SECTION/TAXONOMY/BLANK]/page/2/index.html

-....

-```

binary files a/content/extras/permalinks.md /dev/null differ

--- a/content/extras/robots-txt.md

+++ /dev/null

@@ -1,36 +1,0 @@

----

-lastmod: 2016-01-06

-date: 2015-12-08

-menu:

-  main:

-    parent: extras

-next: /extras/datafiles

-prev: /extras/crossreferences

-title: Custom robots.txt

----

-Hugo can generate a customized [robots.txt](http://www.robotstxt.org/) in the

-[same way as any other templates]({{< ref "templates/go-templates.md" >}}).

-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:

-```http

-User-agent: *

-```

-Hugo will use the template `robots.txt` according to the following list in descending precedence:

-* /layouts/robots.txt

-* /themes/`THEME`/layout/robots.txt

-An example of a robots.txt layout is:

-```http

-User-agent: *

-{{range .Data.Pages}}

-Disallow: {{.RelPermalink}}{{end}}

-```

-This template disallows and all the pages of the site creating one `Disallow` entry for each one.

--- a/content/extras/scratch.md

+++ /dev/null

@@ -1,63 +1,0 @@

----

-aliases:

-- /doc/scratch/

-lastmod: 2015-08-02

-date: 2015-01-22

-menu:

-  main:

-    parent: extras

-next: /extras/shortcodes

-prev: /extras/permalinks

-title: Scratch

----

-`Scratch` -- a "scratchpad" for your page-scoped variables. In most cases you can do well without `Scratch`, but there are some use cases that aren't solvable with Go's templates without `Scratch`'s help, due to scoping issues.

-`Scratch` is added to both `Page` and `Shortcode` -- with following methods:

-* `Set` and `Add` takes a `key` and the `value` to add.

-* `Get` returns the `value` for the `key` given.

-* `SetInMap` takes a `key`, `mapKey` and `value`

-* `GetSortedMapValues` returns array of values from `key` sorted by `mapKey`

-`Set` and `SetInMap` can store values of any type.

-For single values, `Add` accepts values that support Go's `+` operator. If the first `Add` for a key is an array or slice, the following adds will be appended to that list.

-The scope of the backing data is global for the given `Page` or `Shortcode`, and spans partial and shortcode includes.

-Note that `.Scratch` from a shortcode will return the shortcode's `Scratch`, which in most cases is what you want. If you want to store it in the page scroped Scratch, then use `.Page.Scratch`.

-## Sample usage

-The usage is best illustrated with some samples:

-```

-{{ $.Scratch.Add "a1" 12 }}

-{{ $.Scratch.Get "a1" }} {{/* => 12 */}}

-{{ $.Scratch.Add "a1" 1 }}

-{{ $.Scratch.Get "a1" }} // {{/* => 13 */}}

-{{ $.Scratch.Add "a2" "AB" }}

-{{ $.Scratch.Get "a2" }} {{/* => AB */}}

-{{ $.Scratch.Add "a2" "CD" }}

-{{ $.Scratch.Get "a2" }} {{/* => ABCD */}}

-{{ $.Scratch.Add "l1" (slice "A" "B") }}

-{{ $.Scratch.Get "l1" }} {{/* => [A B]  */}}

-{{ $.Scratch.Add "l1" (slice "C" "D") }}

-{{ $.Scratch.Get "l1" }} {{/* => [A B C D] */}}

-{{ $.Scratch.Set "v1" 123 }}

-{{ $.Scratch.Get "v1" }}  {{/* => 123 */}}

-{{ $.Scratch.SetInMap "a3" "b" "XX" }}

-{{ $.Scratch.SetInMap "a3" "a" "AA" }}

-{{ $.Scratch.SetInMap "a3" "c" "CC" }}

-{{ $.Scratch.SetInMap "a3" "b" "BB" }}

-{{ $.Scratch.GetSortedMapValues "a3" }} {{/* => []interface {}{"AA", "BB", "CC"} */}}

-```

-**Note:** The examples above uses the special `$` variable, which refers to the top-level node. This is the behavior you most likely want, and will help remove some confusion when using `Scratch` inside page range loops -- and you start inadvertently calling the wrong `Scratch`. But there may be use cases for `{{ .Scratch.Add "key" "some value" }}`.

--- a/content/extras/shortcodes.md

+++ /dev/null

@@ -1,413 +1,0 @@

----

-aliases:

-- /doc/shortcodes/

-lastmod: 2016-02-03

-date: 2013-07-01

-menu:

-  main:

-    parent: extras

-next: /extras/highlighting

-prev: /extras/scratch

-title: Shortcodes

-toc: true

----

-Hugo uses Markdown for its simple content format. However, there are a lot

-of things that Markdown doesn’t support well.

-We are unwilling to accept being constrained by our simple format. Also

-unacceptable is writing raw HTML in our Markdown every time we want to include

-unsupported content such as a video. To do so is in complete opposition to the

-intent of using a bare-bones format for our content and utilizing templates to

-apply styling for display.

-To avoid both of these limitations, Hugo created shortcodes.

-A shortcode is a simple snippet inside a content file that Hugo will render

-using a predefined template. Note that shortcodes will not work in template

-files---if you need a functionality like that in a template, you most likely

-want a [partial template](/templates/partials/) instead.

-Another benefit is, you can update your shortcode with any related new classes or

-techniques, and upon generation, Hugo will easily merge in your changes. You

-avoid a possibly complicated search and replace operation.

-## Using a shortcode

-In your content files, a shortcode can be called by using the `{{%/* name parameters

-*/%}}` form. Shortcode parameters are space delimited.  Parameters with spaces

-can be quoted.

-The first word is always the name of the shortcode. Parameters follow the name.

-Depending upon how the shortcode is defined, the parameters may be named,

-positional or both (although you can't mix parameter types in a single call).

-The format for named parameters models that of HTML with the format

-`name="value"`.

-Some shortcodes use or require closing shortcodes. Like HTML, the opening and closing

-shortcodes match (name only), the closing being prepended with a slash.

-Example of a paired shortcode:

-    {{</* highlight go */>}} A bunch of code here {{</* /highlight */>}}

-The examples above use two different delimiters, the difference being the `%` and the `<` character:

-### Shortcodes with Markdown

-The `%` characters indicates that the shortcode's inner content needs further processing by the page's rendering processor (i.e. Markdown), needed to get the **bold** text in the example below:

-    {{%/* myshortcode */%}}Hello **World!**{{%/* /myshortcode */%}}

-### Shortcodes without Markdown

-The `<` character indicates that the shortcode's inner content doesn't need any further rendering, this will typically be pure HTML:

-    {{</* myshortcode */>}}<p>Hello <strong>World!</strong></p>{{</* /myshortcode */>}}

-## Built-in Shortcodes

-Hugo ships with a set of predefined shortcodes.

-### highlight

-This shortcode will convert the source code provided into syntax highlighted

-HTML. Read more on [highlighting](/extras/highlighting/).

-#### Usage

-`highlight` takes exactly one required parameter of _language_ and requires a

-closing shortcode.

-#### Example

-    {{</* highlight html */>}}

-    <section id="main">

-      <div>

-       <h1 id="title">{{ .Title }}</h1>

-        {{ range .Data.Pages }}

-            {{ .Render "summary"}}

-        {{ end }}

-      </div>

-    </section>

-    {{</* /highlight */>}}

-#### Example Output

-    <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 }}

-            {{ .Render &quot;summary&quot;}}

-        {{ end }}

-      <span style="color: #f92672">&lt;/div&gt;</span>

-    <span style="color: #f92672">&lt;/section&gt;</span>

-### figure

-`figure` is simply an extension of the image capabilities present with Markdown.

-`figure` provides the ability to add captions, CSS classes, alt text, links etc.

-#### Usage

-`figure` can use the following named parameters:

- * src

- * link

- * title

- * caption

- * class

- * attr (attribution)

- * attrlink

- * alt

-#### Example

-    {{</* figure src="/media/spf13.jpg" title="Steve Francia" */>}}

-#### Example output

-    <figure>

-        <img src="/media/spf13.jpg"  />

-        <figcaption>

-            <h4>Steve Francia</h4>

-        </figcaption>

-    </figure>

-### ref, relref

-These shortcodes will look up the pages by their relative path (e.g.,

-`blog/post.md`) or their logical name (`post.md`) and return the permalink

-(`ref`) or relative permalink (`relref`) for the found page.

-`ref` and `relref` also make it possible to make fragmentary links that work

-for the header links generated by Hugo.

-Read more on [cross-references]({{% ref "extras/crossreferences.md" %}}).

-#### Usage

-`ref` and `relref` take exactly one required parameter of _reference_.

-#### Example

-    [Neat]({{</* ref "blog/neat.md" */>}})

-    [Who]({{</* relref "about.md#who" */>}})

-If the page exists in multiple [output formats]({{< relref "extras/output-formats.md" >}}),  `ref` or `relref` can be used with a output format name:

-     [Neat]({{</* ref "blog/neat.md" "amp" */>}})

-#### Example Output

-Assuming that standard Hugo pretty URLs are turned on.

-    <a href="/blog/neat">Neat</a>

-    <a href="/about/#who:c28654c202e73453784cfd2c5ab356c0">Who</a>

-### Twitter

-You want to include a single tweet into your blog post? Everything you need is the URL of the tweet, e.g.:

-* https://twitter.com/spf13/status/666616452582129664

-Pass the tweet's ID from the URL as parameter to the shortcode as shown below:

-    {{</* tweet 666616452582129664 */>}}

-### YouTube

-This shortcode embeds a responsive video player for [YouTube](https://www.youtube.com/) videos. Only the ID of the video is required, e.g.:

-* https://www.youtube.com/watch?v=w7Ft2ymGmfc

-Copy the ID from behind `v=` and pass it to the shortcode:

-    {{</* youtube w7Ft2ymGmfc */>}}

-Furthermore, you can autoplay the embedded video by setting the `autoplay` parameter to true. Remember that you can't mix named and unnamed parameters. Assign the yet unnamed video id to the parameter `id` like below too.

-     {{</* youtube id="w7Ft2ymGmfc" autoplay="true" */>}}

-### Vimeo

-Adding a video from [Vimeo](https://vimeo.com/) is equivalent to the YouTube shortcode above. Extract the ID from the URL, e.g.:

-* https://vimeo.com/channels/staffpicks/146022717

-and pass it to the shortcode:

-    {{</* vimeo 146022717 */>}}

-### GitHub gists

-Including code snippets with GitHub gists while writing a tutorial is common situation bloggers face. With a given URL of the gist, e.g.:

-* https://gist.github.com/spf13/7896402

-pass the owner and the ID of the gist to the shortcode:

-    {{</* gist spf13 7896402 */>}}

-If the gist contains several files and you want to quote just one of them, you can pass the filename (quoted) as an optional third argument:

-    {{</* gist spf13 7896402 "img.html" */>}}

-### Speaker Deck

-To embed slides from [Speaker Deck](https://speakerdeck.com/), click on "&lt;&#8239;/&gt;&nbsp;Embed" (under Share right next to the template on Speaker Deck) and copy the URL, e.g.:

-    <script async class="speakerdeck-embed" data-id="4e8126e72d853c0060001f97" data-ratio="1.33333333333333" src="//speakerdeck.com/assets/embed.js"></script>

-Extract the value from the field `data-id` and pass it to the shortcode:

-    {{</* speakerdeck 4e8126e72d853c0060001f97 */>}}

-### Instagram

-If you'd like to embed photo from [Instagram](https://www.instagram.com/), all you need is photo ID from the URL, e. g.:

-* https://www.instagram.com/p/BMokmydjG-M/

-Pass it to the shortcode:

-    {{</* instagram BMokmydjG-M */>}}

-Optionally, hide caption:

-    {{</* instagram BMokmydjG-M hidecaption */>}}

-## Creating your own shortcodes

-To create a shortcode, place a template in the layouts/shortcodes directory. The

-template name will be the name of the shortcode.

-In creating a shortcode, you can choose if the shortcode will use _positional

-parameters_, or _named parameters_, or _both_. A good rule of thumb is that if a

-shortcode has a single required value in the case of the `youtube` example below,

-then positional works very well. For more complex layouts with optional

-parameters, named parameters work best.  Allowing both types of parameters is

-useful for complex layouts where you want to set default values that can be

-overridden.

-**Inside the template**

-To access a parameter by position, the `.Get` method can be used:

-    {{ .Get 0 }}

-To access a parameter by name, the `.Get` method should be utilized:

-    {{ .Get "class" }}

-`with` is great when the output depends on a parameter being set:

-    {{ with .Get "class"}} class="{{.}}"{{ end }}

-`.Get` can also be used to check if a parameter has been provided. This is

-most helpful when the condition depends on either one value or another...

-or both:

-    {{ or .Get "title" | .Get "alt" | if }} alt="{{ with .Get "alt"}}{{.}}{{else}}{{.Get "title"}}{{end}}"{{ end }}

-If a closing shortcode is used, the variable `.Inner` will be populated with all

-of the content between the opening and closing shortcodes. If a closing

-shortcode is required, you can check the length of `.Inner` and provide a warning

-to the user.

-A shortcode with `.Inner` content can be used without the inline content, and without the closing shortcode, by using the self-closing syntax:

-    {{</* innershortcode /*/>}}

-The variable `.Params` contains the list of parameters in case you need to do

-more complicated things than `.Get`.  It is sometimes useful to provide a

-flexible shortcode that can take named or positional parameters.  To meet this

-need, Hugo shortcodes have a `.IsNamedParams` boolean available that can be used

-such as `{{ if .IsNamedParams }}...{{ else }}...{{ end }}`.  See the

-`Single Flexible Example` below for an example.

-You can also use the variable `.Page` to access all the normal [Page Variables](/templates/variables/).

-A shortcodes can be nested. In a nested shortcode you can access the parent shortcode context with `.Parent`. This can be very useful for inheritance of common shortcode parameters from the root.

-## Single Positional Example: youtube

-    {{</* youtube 09jf3ow9jfw */>}}

-Would load the template /layouts/shortcodes/youtube.html

-    <div class="embed video-player">

-    <iframe class="youtube-player" type="text/html" width="640" height="385" src="http://www.youtube.com/embed/{{ index .Params 0 }}" allowfullscreen frameborder="0">

-    </iframe>

-    </div>

-This would be rendered as:

-    <div class="embed video-player">

-    <iframe class="youtube-player" type="text/html"

-        width="640" height="385"

-        src="http://www.youtube.com/embed/09jf3ow9jfw"

-        allowfullscreen frameborder="0">

-    </iframe>

-    </div>

-## Single Named Example: image with caption

-    {{</* img src="/media/spf13.jpg" title="Steve Francia" */>}}

-Would load the template /layouts/shortcodes/img.html

-    <!-- image -->

-    <figure {{ with .Get "class" }}class="{{.}}"{{ end }}>

-        {{ with .Get "link"}}<a href="{{.}}">{{ end }}

-            <img src="{{ .Get "src" }}" {{ if or (.Get "alt") (.Get "caption") }}alt="{{ with .Get "alt"}}{{.}}{{else}}{{ .Get "caption" }}{{ end }}"{{ end }} />

-        {{ if .Get "link"}}</a>{{ end }}

-        {{ if or (or (.Get "title") (.Get "caption")) (.Get "attr")}}

-        <figcaption>{{ if isset .Params "title" }}

-            <h4>{{ .Get "title" }}</h4>{{ end }}

-            {{ if or (.Get "caption") (.Get "attr")}}<p>

-            {{ .Get "caption" }}

-            {{ with .Get "attrlink"}}<a href="{{.}}"> {{ end }}

-                {{ .Get "attr" }}

-            {{ if .Get "attrlink"}}</a> {{ end }}

-            </p> {{ end }}

-        </figcaption>

-        {{ end }}

-    </figure>

-    <!-- image -->

-Would be rendered as:

-    <figure >

-        <img src="/media/spf13.jpg"  />

-        <figcaption>

-            <h4>Steve Francia</h4>

-        </figcaption>

-    </figure>

-## Single Flexible Example: vimeo with defaults

-    {{</* vimeo 49718712 */>}}

-    {{</* vimeo id="49718712" class="flex-video" */>}}

-Would load the template /layouts/shortcodes/vimeo.html

-    {{ if .IsNamedParams }}

-      <div class="{{ if .Get "class" }}{{ .Get "class" }}{{ else }}vimeo-container{{ end }}">

-        <iframe src="//player.vimeo.com/video/{{ .Get "id" }}" allowfullscreen></iframe>

-      </div>

-    {{ else }}

-      <div class="{{ if len .Params | eq 2 }}{{ .Get 1 }}{{ else }}vimeo-container{{ end }}">

-        <iframe src="//player.vimeo.com/video/{{ .Get 0 }}" allowfullscreen></iframe>

-      </div>

-    {{ end }}

-Would be rendered as:

-    <div class="vimeo-container">

-      <iframe src="//player.vimeo.com/video/49718712" allowfullscreen></iframe>

-    </div>

-    <div class="flex-video">

-      <iframe src="//player.vimeo.com/video/49718712" allowfullscreen></iframe>

-    </div>

-## Paired Example: Highlight

-*Hugo already ships with the `highlight` shortcode*

-    {{</* highlight html */>}}

-    <html>

-        <body> This HTML </body>

-    </html>

-    {{</* /highlight */>}}

-The template for this utilizes the following code (already included in Hugo)

-    {{ .Get 0 | highlight .Inner  }}

-And will be rendered as:

-    <div class="highlight" style="background: #272822"><pre style="line-height: 125%"><span style="color: #f92672">&lt;html&gt;</span>

-        <span style="color: #f92672">&lt;body&gt;</span> This HTML <span style="color: #f92672">&lt;/body&gt;</span>

-    <span style="color: #f92672">&lt;/html&gt;</span>

-    </pre></div>

-Please notice that this template makes use of a Hugo-specific template function

-called `highlight` which uses Pygments to add the highlighting code.

-## Simple Single-word Example: Year

-Let's assume you would like to have a shortcode to be replaced by the current year in your Markdown content files, for a license or copyright statement. Calling a shortcode like this:

-    {{</* year */>}}

-... would load your one-line template ``/layouts/shortcodes/year.html``, which contains:

-    {{ .Page.Now.Year }}

-More shortcode examples can be found at [spf13.com](https://github.com/spf13/spf13.com/tree/master/layouts/shortcodes).

--- a/content/extras/toc.md

+++ /dev/null

@@ -1,37 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2013-07-09

-menu:

-  main:

-    parent: extras

-next: /extras/localfiles

-prev: /extras/highlighting

-title: Table of Contents

----

-Hugo will automatically parse the Markdown for your content and create

-a Table of Contents you can use to guide readers to the sections within

-your content.

-## Usage

-Simply create content like you normally would with the appropriate

-headers.

-Hugo will take this Markdown and create a table of contents stored in the

-[content variable](/layout/variables/) `.TableOfContents`

-## Template Example

-This is example code of a [single.html template](/layout/content/).

-    {{ partial "header.html" . }}

-        <div id="toc" class="well col-md-4 col-sm-6">

-        {{ .TableOfContents }}

-        </div>

-        <h1>{{ .Title }}</h1>

-        {{ .Content }}

-    {{ partial "footer.html" . }}

--- a/content/extras/urls.md

+++ /dev/null

@@ -1,70 +1,0 @@

----

-aliases:

-- /doc/urls/

-lastmod: 2016-05-07

-date: 2014-01-03

-menu:

-  main:

-    parent: extras

-next: /community/mailing-list

-notoc: true

-prev: /extras/localfiles

-title: URLs

----

-## Pretty URLs

-By default, Hugo creates content with 'pretty' URLs. For example,

-content created at `/content/extras/urls.md` will be rendered at

-`/public/extras/urls/index.html`, thus accessible from the browser

-at http://example.com/extras/urls/.  No non-standard server-side

-configuration is required for these pretty URLs to work.

-If you would like to have what we call "ugly URLs",

-e.g.&nbsp;http://example.com/extras/urls.html, you are in luck.

-Hugo supports the ability to create your entire site with ugly URLs.

-Simply add `uglyurls = true` to your site-wide `config.toml`,

-or use the `--uglyURLs=true` flag on the command line.

-If you want a specific piece of content to have an exact URL, you can

-specify this in the front matter under the `url` key. See [Content

-Organization](/content/organization/) for more details.

-## Canonicalization

-By default, all relative URLs encountered in the input are left unmodified,

-e.g. `/css/foo.css` would stay as `/css/foo.css`,

-i.e. `canonifyURLs` defaults to `false`.

-By setting `canonifyURLs` to `true`, all relative URLs would instead

-be *canonicalized* using `baseURL`.  For example, assuming you have

-`baseURL = http://yoursite.example.com/` defined in the site-wide

-`config.toml`, the relative URL `/css/foo.css` would be turned into

-the absolute URL `http://yoursite.example.com/css/foo.css`.

-Benefits of canonicalization include fixing all URLs to be absolute, which may

-aid with some parsing tasks.  Note though that all real browsers handle this

-client-side without issues.

-Benefits of non-canonicalization include being able to have resource inclusion

-be scheme-relative, so that http vs https can be decided based on how this

-page was retrieved.

-> Note: In the May 2014 release of Hugo v0.11, the default value of `canonifyURLs` was switched from `true` to `false`, which we think is the better default and should continue to be the case going forward. So, please verify and adjust your website accordingly if you are upgrading from v0.10 or older versions.

-To find out the current value of `canonifyURLs` for your website, you may use the handy `hugo config` command added in v0.13:

-    hugo config | grep -i canon

-Or, if you are on Windows and do not have `grep` installed:

-    hugo config | FINDSTR /I canon

-## Relative URLs

-By default, all relative URLs are left unchanged by Hugo,

-which can be problematic when you want to make your site browsable from a local file system.

-Setting `relativeURLs` to `true` in the site configuration will cause Hugo to rewrite all relative URLs to be relative to the current content.

-For example, if the `/post/first/` page contained a link with a relative URL of `/about/`, Hugo would rewrite that URL to `../../about/`.

--- /dev/null

+++ b/content/functions/GetPage.md

@@ -1,0 +1,67 @@

+---

+title: .GetPage

+description: "Gets a `Page` of a given `Kind` and `path`."

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [sections,lists,indexes]

+signature: [".GetPage TYPE PATH"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+Every `Page` has a `Kind` attribute 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` looks up a page of a given `Kind` and `path`.

+```

+{{ with .Site.GetPage "section" "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 isn't found.

+For a regular page:

+```

+{{ with .Site.GetPage "page" "blog" "my-post.md" }}{{ .Title }}{{ end }}

+```

+Note that the path can also be supplied like this:

+```

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

+```

+The valid page kinds are: *page, home, section, taxonomy and taxonomyTerm.*

+## `.GetPage` Example

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

+1. Grab the index object of your `tags` [taxonomy][].

+2. Assign this object to a variable, `$t`

+3. Sort the terms associated with the taxonomy by popularity.

+4. Grab the top two most popular terms in the taxonomy (i.e., the two most popular tags assigned to content.

+{{% code file="grab-top-two-tags.html" %}}

+```html

+<ul class="most-popular-tags">

+{{ $t := $.Site.GetPage "taxonomyTerm" "tags" }}

+{{ range first 2 $t.Data.Terms.ByCount }}

+    <li>{{.}}</li>

+{{ end }}

+</ul>

+```

+{{% /code %}}

+[partials]: /templates/partials/

+[taxonomy]: /content-management/taxonomies/

--- /dev/null

+++ b/content/functions/NumFmt.md

@@ -1,0 +1,34 @@

+---

+title: lang.NumFmt

+description: "Formats a number with a given precision using the requested `decimal`, `grouping`, and `negative` characters."

+godocref: ""

+workson: []

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+#tags: [numbers]

+menu:

+  docs:

+    parent: "functions"

+toc: false

+signature: ["lang.NumFmt <decimal> <grouping> <negative> <precision> <number>"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+comments:

+---

+The default options value is `- . ,`.

+Numbers greater than or equal to 5 are rounded up. For example, if precision is set to `0`, `1.5` becomes `2`, and `1.4` becomes `1`.

+```

+{{ lang.NumFmt "," "." "-" 2 12345.6789 }} → 12.345,68

+{{ lang.NumFmt "." "" "-" 6 -12345.6789 }} → -12345.678900

+{{ lang.NumFmt "." "," "-" 0 -12345.6789 }} → -12,346

+{{ -98765.4321 | lang.NumFmt "." "," "-" 2 }} → -98,765.43

+```

--- /dev/null

+++ b/content/functions/_index.md

@@ -1,0 +1,20 @@

+---

+title: Functions Quick Reference

+linktitle: Functions Quick Reference

+description: Comprehensive list of Hugo templating functions, including basic and advanced usage examples.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: []

+menu:

+  docs:

+    parent: "functions"

+weight: 01	#rem

+draft: false

+aliases: [/layout/functions/,/templates/functions]

+---

+Go templates are lightweight but extensible. Go itself supplies built-in functions, including comparison operators and other basic tools. These are listed in the [Go template documentation][gofuncs]. Hugo has added additional functions to the basic template logic.

+[gofuncs]: http://golang.org/pkg/text/template/#hdr-Functions

--- /dev/null

+++ b/content/functions/abslangurl.md

@@ -1,0 +1,28 @@

+---

+title: absLangURL

+description: Adds the absolute URL with correct language prefix according to site configuration for multilingual.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [multilingual,i18n,urls]

+signature: ["absLangURL INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [relLangURL]

+deprecated: false

+aliases: []

+---

+Both `absLangURL` and [`relLangURL`](/functions/rellangurl/) are similar to their [`absURL`](/functions/absurl/) and [`relURL`](/functions/relurl) relatives but will add the correct language prefix when the site is configured with more than one language.

+So for a site  `baseURL` set to `http://yoursite.com/hugo/` and the current language is `en`:

+```golang

+{{ "blog/" | absLangURL }} → "http://yoursite.com/hugo/en/blog/"

+{{ "blog/" | relLangURL }} → "/hugo/en/blog/"

+```

--- /dev/null

+++ b/content/functions/absurl.md

@@ -1,0 +1,53 @@

+---

+title: absURL

+description: Creates an absolute URL based on the configured baseURL.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [urls]

+signature: ["absURL INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [relURL]

+deprecated: false

+aliases: []

+---

+Both `absURL` and `relURL` consider the configured value of `baseURL` in your site's [`config` file][configuration]. Given a `baseURL` set to `http://yoursite.com/hugo/`:

+```golang

+{{ "mystyle.css" | absURL }} → "http://yoursite.com/hugo/mystyle.css"

+{{ "mystyle.css" | relURL }} → "/hugo/mystyle.css"

+{{ "http://gohugo.io/" | relURL }} →  "http://gohugo.io/"

+{{ "http://gohugo.io/" | absURL }} →  "http://gohugo.io/"

+```

+The last two examples may look strange but can be very useful. For example, the following shows how to use `absURL` in [JSON-LD structured data (SEO)][jsonld], where some of your images for a piece of content may or may not be hosted locally:

+{{% code file="layouts/partials/schemaorg-metadata.html" download="schemaorg-metadata.html" %}}

+```html

+<script type="application/ld+json">

+{

+    "@context" : "http://schema.org",

+    "@type" : "BlogPosting",

+    "image" : {{ apply .Params.images "absURL" "." }}

+}

+</script>

+```

+{{% /code %}}

+The above uses the [apply function][] and also exposes how the Go template parser JSON-encodes objects inside `<script>` tags. See [the safeJS template function][safejs] for examples of how to tell Hugo not to escape strings inside of such tags.

+{{% note "Ending Slash" %}}

+`absURL` and `relURL` are smart about missing slashes, but they will *not* add a closing slash to a URL if it is not present.

+{{% /note %}}

+[apply function]: /functions/apply/

+[configuration]: /getting-started/configuration/

+[jsonld]: https://developers.google.com/search/docs/guides/intro-structured-data

+[safejs]: /functions/safejs

--- /dev/null

+++ b/content/functions/adddate.md

@@ -1,0 +1,54 @@

+---

+title: .AddDate

+description: Returns the time corresponding to adding the given number of years, months, and days passed to the function.

+godocref: https://golang.org/pkg/time/#Time.AddDate

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [dates,time]

+signature: [".AddDate YEARS MONTHS DAYS"]

+workson: [times]

+hugoversion:

+relatedfuncs: [now]

+deprecated: false

+aliases: []

+---

+The `AddDate` function takes three arguments in logical order of `years`, `months`, and `days`.

+## Example: Randomized Tweets from the Last 2 Years

+Let's assume you have a file at `data/tweets.toml` that contains a list of Tweets to display on your site's homepage. The file is filled with `[[tweet]]` blocks; e.g.---

+```toml

+[[tweet]]

+name = "Steve Francia"

+twitter_handle = "@spf13"

+quote = "I'm creator of Hugo. #metadocreference"

+link = "https://twitter.com/spf13"

+date = "2017-01-07T00:00:00Z"

+```

+Let's assume you want to grab Tweets from the last two years and present them in a random order. In conjunction with the [`where`](/functions/where/) and [`now`](/functions/now/) functions, you can limit our range to the last two years via `now.AddDate -2 0 0`, which represents a point in time 2 years, 0 days, and 0 hours before the time of your last site build.

+{{% code file="partials/templates/random-tweets.html" download="tweets.html" %}}

+```html

+{{ range where $.Site.Data.tweets.tweet "date" "ge" (now.AddDate -2 0 0) | shuffle }}

+    <div class="item">

+        <blockquote>

+            <p>

+            {{ .quote | safeHTML }}

+            </p>

+            &mdash; {{ .name }} ({{ .twitter_handle }}) <a href="{{ .link }}">

+                {{ dateFormat "January 2, 2006" .date }}

+            </a>

+        </blockquote>

+    </div>

+{{ end }}

+```

+{{% /code %}}

--- /dev/null

+++ b/content/functions/after.md

@@ -1,0 +1,68 @@

+---

+title: after

+description: "`after` slices an array to only the items after the <em>N</em>th item."

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [iteration]

+signature: ["after INDEX COLLECTION"]

+workson: []

+hugoversion:

+relatedfuncs: [last,first,seq]

+deprecated: false

+aliases: []

+---

+The following shows `after` being used in conjunction with the [`slice` function][slice]:

+```html

+{{ $data := slice "one" "two" "three" "four" }}

+{{ range after 2 $data }}

+    {{ . }}

+{{ end }}

+→ ["three", "four"]

+```

+## Example of `after` with `first`: 2nd&ndash;4th Most Recent Articles

+You can use `after` in combination with the [`first` function][] and Hugo's [powerful sorting methods][lists]. Let's assume you have a list page at `yoursite.com/articles`. You have 10 articles, but you want your templating for the [list/section page][] to show only two rows:

+1. The top row is titled "Featured" and shows only the most recently published article (i.e. by `publishdate` in the content files' front matter).

+2. The second row is titled "Recent Articles" and shows only the 2nd- to 4th-most recently published articles.

+{{% code file="layouts/section/articles.html" download="articles.html" %}}

+```html

+{{ define "main" }}

+<section class="row featured-article">

+    <h2>Featured Article</h2>

+    {{ range first 1 .Data.Pages.ByPublishDate.Reverse }}

+     <header>

+        <h3><a href="{{.Permalink}}">{{.Title}}</a></h3>

+    </header>

+    <p>{{.Description}}</p>

+    {{ end }}

+</section>

+<div class="row recent-articles">

+    <h2>Recent Articles</h2>

+    {{ range first 3 (after 1 .Data.Pages.ByPublishDate.Reverse) }}

+        <section class="recent-article">

+            <header>

+                <h3><a href="{{.Permalink}}">{{.Title}}</a></h3>

+            </header>

+            <p>{{.Description}}</p>

+        </section>

+    {{ end }}

+</div>

+{{ end }}

+```

+{{% /code %}}

+[`first` function]: /functions/first/

+[list/section page]: /templates/section-templates/

+[lists]: /lists/

+[slice]: /functions/slice/

--- /dev/null

+++ b/content/functions/apply.md

@@ -1,0 +1,125 @@

+---

+title: apply

+description: Given a map, array, or slice, `apply` returns a new slice with a function applied over it.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [advanced]

+signature: ["apply COLLETION FUNCTION [PARAM...]"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+{{< todo >}}

+<!-- POTENTIAL NEW CONTENT: see apply/sequence discussion: https://discourse.gohugo.io/t/apply-printf-on-a-sequence/5722; -->

+{{< /todo >}}

+`apply` expects at least three parameters, depending on the function being applied.

+1. The first parameter is the sequence to operate on

+2. The second parameter is the name of the function as a string, which must be the name of a valid [Hugo function][functions].

+3. After that, the parameters to the applied function are provided, with the string `"."` standing in for each element of the sequence the function is to be applied against.

+Here is an example of a content file with `name:` as a front matter field:

+```toml

++++

+names: [ "Derek Perkins", "Joe Bergevin", "Tanner Linsley" ]

++++

+```

+You can then use `apply` as follows:

+```golang

+{{ apply .Params.names "urlize" "." }}

+```

+Which will result as follows:

+```

+"derek-perkins", "joe-bergevin", "tanner-linsley"

+```

+This is *roughly* equivalent to using the following with [range][]

+```golang

+{{ range .Params.names }}{{ . | urlize }}{{ end }}

+```

+However, it isn’t possible to provide the output of a range to the [`delimit` function][delimit], so you need to `apply` it.

+If you have `post-tag-list.html` and `post-tag-link.html` as [partials][], you *could* use the following snippets, respectively:

+{{% code file="layouts/partial/post-tag-list.html" copy="false" %}}

+```html

+{{ with .Params.tags }}

+<div class="tags-list">

+  Tags:

+  {{ $len := len . }}

+  {{ if eq $len 1 }}

+    {{ partial "post/tag/link" (index . 0) }}

+  {{ else }}

+    {{ $last := sub $len 1 }}

+    {{ range first $last . }}

+      {{ partial "post/tag/link" . }},

+    {{ end }}

+    {{ partial "post/tag/link" (index . $last) }}

+  {{ end }}

+</div>

+{{ end }}

+```

+{{% /code %}}

+{{% code file="layouts/partial/post-tag-link.html" copy="false" %}}

+```html

+<a class="post-tag post-tag-{{ . | urlize }}" href="/tags/{{ . | urlize }}">{{ . }}</a>

+```

+{{% /code %}}

+This works, but the complexity of `post-tag-list.html` is fairly high. The Hugo template needs to perform special behavior for the case where there’s only one tag, and it has to treat the last tag as special. Additionally, the tag list will be rendered something like `Tags: tag1 , tag2 , tag3` because of the way that the HTML is generated and then interpreted by a browser.

+This first version of `layouts/partials/post-tag-list.html` separates all of the operations for ease of reading. The combined and DRYer version is shown next:

+```html

+{{ with .Params.tags }}

+    <div class="tags-list">

+      Tags:

+      {{ $sort := sort . }}

+      {{ $links := apply $sort "partial" "post-tag-link" "." }}

+      {{ $clean := apply $links "chomp" "." }}

+      {{ delimit $clean ", " }}

+    </div>

+{{ end }}

+```

+Now in the completed version, you can sort the tags, convert the tags to links with `layouts/partials/post-tag-link.html`, [chomp][] off stray newlines, and join the tags together in a delimited list for presentation. Here is an even DRYer version of the preceding example:

+{{% code file="layouts/partials/post-tag-list.html" download="post-tag-list.html" %}}

+```html

+    {{ with .Params.tags }}

+    <div class="tags-list">

+      Tags:

+      {{ delimit (apply (apply (sort .) "partial" "post-tag-link" ".") "chomp" ".") ", " }}

+    </div>

+    {{ end }}

+```

+{{% /code %}}

+{{% note %}}

+`apply` does not work when receiving the sequence as an argument through a pipeline.

+{{% /note %}}

+[chomp]: /functions/chomp/ "See documentation for the chomp function"

+[delimit]: /functions/delimit/ "See documentation for the delimit function"

+[functions]: /functions/ "See the full list of Hugo functions to see what can be passed as an argument to the apply function."

+[partials]: /templates/partials/

+[range]: /functions/range/ "Learn the importance of the range function, a fundamental keyword in both Hugo templates and the Go programming language."

--- /dev/null

+++ b/content/functions/base64.md

@@ -1,0 +1,55 @@

+---

+title: base64

+description: "`base64Encode` and `base64Decode` let you easily decode content with a base64 encoding and vice versa through pipes."

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+relatedfuncs: []

+signature: ["base64Decode INPUT", "base64Encode INPUT"]

+workson: []

+hugoversion:

+deprecated: false

+draft: false

+aliases: []

+---

+An example:

+{{% code file="base64-input.html" %}}

+```html

+<p>Hello world = {{ "Hello world" | base64Encode }}</p>

+<p>SGVsbG8gd29ybGQ = {{ "SGVsbG8gd29ybGQ=" | base64Decode }}</p>

+```

+{{% /code %}}

+{{% output file="base-64-output.html" %}}

+```html

+<p>Hello world = SGVsbG8gd29ybGQ=</p>

+<p>SGVsbG8gd29ybGQ = Hello world</p>

+```

+{{% /output %}}

+You can also pass other data types as arguments to the template function which tries to convert them. The following will convert *42* from an integer to a string because both `base64Encode` and `base64Decode` always return a string.

+```

+{{ 42 | base64Encode | base64Decode }}

+=> "42" rather than 42

+```

+## `base64` with APIs

+Using base64 to decode and encode becomes really powerful if we have to handle

+responses from APIs.

+```golang

+{{ $resp := getJSON "https://api.github.com/repos/gohugoio/hugo/readme"  }}

+{{ $resp.content | base64Decode | markdownify }}

+```

+The response of the GitHub API contains the base64-encoded version of the [README.md](https://github.com/gohugoio/hugo/blob/master/README.md) in the Hugo repository. Now we can decode it and parse the Markdown. The final output will look similar to the rendered version on GitHub.

--- /dev/null

+++ b/content/functions/chomp.md

@@ -1,0 +1,24 @@

+---

+title: chomp

+description: Removes any trailing newline characters.

+godocref: Removes any trailing newline characters.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [trim]

+signature: ["chomp INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [truncate]

+deprecated: false

+---

+Useful in a pipeline to remove newlines added by other processing (e.g., [`markdownify`](/functions/markdownify/)).

+```golang

+{{chomp "<p>Blockhead</p>\n"}} → "<p>Blockhead</p>"

+```

--- /dev/null

+++ b/content/functions/countrunes.md

@@ -1,0 +1,28 @@

+---

+title: countrunes

+description: Determines the number of runes in a string excluding any whitespace.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [counting, word count]

+signature: ["countrunes INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: [/functions/countrunes/,/functions/countwords/]

+---

+In contrast with `countwords` function, which counts every word in a string, the `countrunes` function determines the number of runes in the content and excludes any whitespace. This has specific utility if you are dealing with CJK-like languages.

+```html

+{{ "Hello, 世界" | countrunes }}

+<!-- outputs a content length of 8 runes. -->

+```

+[pagevars]: /variables/page/

--- /dev/null

+++ b/content/functions/countwords.md

@@ -1,0 +1,29 @@

+---

+title: countwords

+description: Counts the number of words in a string.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [counting, word count]

+signature: ["countwords INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [countrunes]

+deprecated: false

+aliases: [/functions/countrunes/,/functions/countwords/]

+---

+The template function works similar to the [.WordCount page variable][pagevars].

+```html

+{{ "Hugo is a static site generator." | countwords }}

+<!-- outputs a content length of 6 words.  -->

+```

+[pagevars]: /variables/page/

--- /dev/null

+++ b/content/functions/dateformat.md

@@ -1,0 +1,31 @@

+---

+title: dateFormat

+description: Converts the textual representation of the `datetime` into the specified format.

+godocref: https://golang.org/pkg/time/

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [dates,time,strings]

+signature: ["dateFormat LAYOUT INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [Format,now,Unix,time]

+deprecated: false

+---

+`dateFormat` converts the textual representation of the `datetime` into the specified format or returns it as a Go `time.Time` type value. These are formatted with the layout string.

+```

+{{ dateFormat "Monday, Jan 2, 2006" "2015-01-21" }} → "Wednesday, Jan 21, 2015"

+```

+{{% warning %}}

+As of v0.19 of Hugo, the `dateFormat` function is *not* supported as part of Hugo's [multilingual feature](/content-management/multilingual/).

+{{% /warning %}}

+See the [`Format` function](/functions/format/) for a more complete list of date formatting options in your templates.

--- /dev/null

+++ b/content/functions/default.md

@@ -1,0 +1,105 @@

+---

+title: default

+description: Allows setting a default value that can be returned if a first value is not set.

+qref: "Returns a default value if a value is not set when checked."

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [defaults]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+toc:

+signature: ["default DEFAULT INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: [/functions/default/]

+needsexamples: false

+---

+`default` checks whether a given value is set and returns a default value if it is not. *Set* in this context means different things depending on date type:

+* non-zero for numeric types and times

+* non-zero length for strings, arrays, slices, and maps

+* any boolean or struct value

+* non-nil for any other types

+`default` function examples reference the following content page:

+{{% code file="content/posts/default-function-example.md" %}}

+```yaml

+---

+title: Sane Defaults

+seo_title:

+date: 2017-02-18

+font:

+oldparam: The default function helps make your templating DRYer.

+newparam:

+---

+```

+{{% /code %}}

+`default` can be written in more than one way:

+```golang

+{{ index .Params "font" | default "Roboto" }}

+{{ default "Roboto" (index .Params "font") }}

+```

+Both of the above `default` function calls return `Roboto`.

+A `default` value, however, does not need to be hard coded like the previous example. The `default` value can be a variable or pulled directly from the front matter using dot notation:

+{{% code file="variable-as-default-value.html" nocopy="true" %}}

+```golang

+{{$old := .Params.oldparam }}

+<p>{{ .Params.newparam | default $old }}</p>

+```

+{{% /code %}}

+Which would return:

+```

+<p>The default function helps make your templating DRYer.</p>

+```

+And then using dot notation

+{{% code file="dot-notation-default-value.html" %}}

+```golang

+<title>{{ .Params.seo_title | default .Title }}</title>

+```

+{{% /code %}}

+Which would return

+{{% output file="dot-notation-default-return-value.html" %}}

+```html

+<title>Sane Defaults</title>

+```

+{{% /output %}}

+The following have equivalent return values but are far less terse. This demonstrates the utility of `default`:

+Using `if`:

+{{% code file="if-instead-of-default.html" nocopy="true" %}}

+```golang

+<title>{{if .Params.seo_title}}{{.Params.seo_title}}{{else}}{{.Title}}{{end}}</title>

+=> Sane Defaults

+```

+{{% /code %}}

+Using `with`:

+{{% code file="with-instead-of-default.html" nocopy="true" %}}

+```golang

+<title>{{with .Params.seo_title}}{{.}}{{else}}{{.Title}}{{end}}</title>

+=> Sane Defaults

+```

+{{% /code %}}

--- /dev/null

+++ b/content/functions/delimit.md

@@ -1,0 +1,74 @@

+---

+title: delimit

+description: Loops through any array, slice, or map and returns a string of all the values separated by a delimiter.

+godocref:

+workson: []

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [iteration]

+toc: false

+signature: ["delimit COLLECTION DELIMIT LAST"]

+workson: [lists,taxonomies,terms]

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+`delimit` called in your template takes the form of

+```

+{{ delimit array/slice/map delimiter optionallastdelimiter}}

+```

+`delimit` loops through any array, slice, or map and returns a string of all the values separated by a delimiter, the second argument in the function call. There is an optional third parameter that lets you choose a different delimiter to go between the last two values in the loop.

+To maintain a consistent output order, maps will be sorted by keys and only a slice of the values will be returned.

+The examples of `delimit` that follow all use the same front matter:

+{{% code file="delimit-example-front-matter.toml" nocopy="true" %}}

+```toml

++++

+title: I love Delimit

+#tags: [ "tag1", "tag2", "tag3" ]

++++

+```

+{{% /code %}}

+{{% code file="delimit-page-tags-input.html" %}}

+```html

+<p>Tags: {{ delimit .Params.tags ", " }}</p>

+```

+{{% /code %}}

+{{% output file="delimit-page-tags-output.html" %}}

+```html

+<p>Tags: tag1, tag2, tag3</p>

+```

+{{% /output %}}

+Here is the same example but with the optional "last" delimiter:

+{{% code file="delimit-page-tags-final-and-input.html" %}}

+```golang

+Tags: {{ delimit .Params.tags ", " ", and " }}

+```

+{{% /code %}}

+{{% output file="delimit-page-tags-final-and-output.html" %}}

+```html

+<p>Tags: tag1, tag2, and tag3</p>

+```

+{{% /output %}}

+[lists]: /templates/lists/

+[taxonomies]: /templates/taxonomy-templates/#taxonomy-list-templates

+[terms]: /templates/taxonomy-templates/#terms-list-templates

--- /dev/null

+++ b/content/functions/dict.md

@@ -1,0 +1,47 @@

+---

+title: dict

+description: Creates a dictionary from a list of key and value pairs.

+godocref:

+workson: []

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-26

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [dictionary]

+signature: ["dict KEY VALUE [KEY VALUE]..."]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+`dict` is especially useful for passing more than one value to a partial template.

+## Example: `dict` with Embedded SVGs

+The partial below creates a SVG and expects `fill` `height` and `width` from the caller:

+{{% code file="layouts/partials/svgs/external-links.svg" download="external-links.svg" %}}

+```xml

+<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" fill="{{ .fill }}" width="{{ .size }}" height="{{ .size }}" viewBox="0 0 32 32" aria-label="External Link">

+<path d="M25.152 16.576v5.696q0 2.144-1.504 3.648t-3.648 1.504h-14.848q-2.144 0-3.648-1.504t-1.504-3.648v-14.848q0-2.112 1.504-3.616t3.648-1.536h12.576q0.224 0 0.384 0.16t0.16 0.416v1.152q0 0.256-0.16 0.416t-0.384 0.16h-12.576q-1.184 0-2.016 0.832t-0.864 2.016v14.848q0 1.184 0.864 2.016t2.016 0.864h14.848q1.184 0 2.016-0.864t0.832-2.016v-5.696q0-0.256 0.16-0.416t0.416-0.16h1.152q0.256 0 0.416 0.16t0.16 0.416zM32 1.152v9.12q0 0.48-0.352 0.8t-0.8 0.352-0.8-0.352l-3.136-3.136-11.648 11.648q-0.16 0.192-0.416 0.192t-0.384-0.192l-2.048-2.048q-0.192-0.16-0.192-0.384t0.192-0.416l11.648-11.648-3.136-3.136q-0.352-0.352-0.352-0.8t0.352-0.8 0.8-0.352h9.12q0.48 0 0.8 0.352t0.352 0.8z"></path>

+</svg>

+```

+{{% /code %}}

+These values can be stored in one object with `dict` and passed to the partial:

+{{% code file="layouts/_default/list.html" %}}

+```html

+{{ partial "svg/link-ext.svg" (dict "fill" "#01589B" "size" 10 "width" 20 ) }}

+```

+{{% /code %}}

+[partials]: /templates/partials/

--- /dev/null

+++ b/content/functions/echoparam.md

@@ -1,0 +1,25 @@

+---

+title: echoParam

+description: Prints a parameter if it is set.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["echoParam DICTIONARY KEY"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+```

+{{ echoParam .Params "project_url" }}

+```

--- /dev/null

+++ b/content/functions/emojify.md

@@ -1,0 +1,32 @@

+---

+title: emojify

+description: Runs a string through the Emoji emoticons processor.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings,emojis]

+signature: ["emojify INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+`emoji` runs a passed string through the Emoji emoticons processor.

+See the [Emoji cheat sheet][emojis] for available emoticons.

+The `emojify` function can be called in your templates but not directly in your content files by default. For emojis in content files, set `enableEmoji` to `true` in your site's [configuration][config]. Then you can write emoji shorthand directly into your content files; e.g. <code>I :</code><code>heart</code><code>: Hugo!</code>:

+I :heart: Hugo!

+[config]: /getting-started/configuration/

+[emojis]: http://www.emoji-cheat-sheet.com/

+[sc]: /templates/shortcode-templates/

+[scsource]: https://github.com/gohugoio/hugo/tree/master/docs/layouts/shortcodes

--- /dev/null

+++ b/content/functions/eq.md

@@ -1,0 +1,25 @@

+---

+title: eq

+linktitle: eq

+description: Returns true if the parameters are equal.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [operators,logic]

+signature: ["eq ARG1 ARG2"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```

+{{ if eq .Section "blog" }}current{{ end }}

+```

--- /dev/null

+++ b/content/functions/findRe.md

@@ -1,0 +1,47 @@

+---

+title: findRE

+description: Returns a list of strings that match the regular expression.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [regex]

+signature: ["findRE PATTERN INPUT [LIMIT]"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+By default all matches will be included. The number of matches can be limitted with an optional third parameter.

+The example below returns a list of all second level headers (`<h2>`) in the content:

+```

+{{ findRE "<h2.*?>(.|\n)*?</h2>" .Content }}

+```

+You can limit the number of matches in the list with a third parameter. The following example shows how to limit the returned value to just one match (or none, if there are no matched substrings):

+```golang

+{{ findRE "<h2.*?>(.|\n)*?</h2>" .Content 1 }}

+    <!-- returns ["<h2 id="#foo">Foo</h2>"] -->

+```

+{{% note %}}

+Hugo uses Golang's [Regular Expression package](https://golang.org/pkg/regexp/), which is the same general syntax used by Perl, Python, and other languages but with a few minor differences for those coming from a background in PCRE. For a full syntax listing, see the [GitHub wiki for re2](https://github.com/google/re2/wiki/Syntax).

+If you are just learning RegEx, or at least Golang's flavor, you can practice pattern matching in the browser at <https://regex101.com/>.

+{{% /note %}}

+[partials]: /templates/partials/

+[`plainify`]: /functions/plainify/

+[toc]: /content-management/toc/

+[`urlize`]: /functions/urlize

--- /dev/null

+++ b/content/functions/first.md

@@ -1,0 +1,28 @@

+---

+title: first

+linktitle: first

+description: "Slices an array to only the first _N_ elements."

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [iteration]

+signature: ["first LIMIT COLLECTION"]

+workson: [lists,taxonomies,terms,groups]

+hugoversion:

+relatedfuncs: [after,last]

+deprecated: false

+aliases: []

+---

+```golang

+{{ range first 10 .Data.Pages }}

+    {{ .Render "summary" }}

+{{ end }}

+```

--- /dev/null

+++ b/content/functions/format.md

@@ -1,0 +1,126 @@

+---

+title: .Format

+description: Formats built-in Hugo dates---`.Date`, `.PublishDate`, and `.LastMod`---according to Go's layout string.

+godocref: https://golang.org/pkg/time/#example_Time_Format

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [dates,time]

+signature: [".Format FORMAT"]

+workson: [times]

+hugoversion:

+relatedfuncs: [dateFormat,now,Unix,time]

+deprecated: false

+aliases: []

+toc: true

+---

+`.Format` will format date values defined in your front matter and can be used as a property on the following [page variables][pagevars]:

+* `.PublishDate`

+* `.Date`

+* `.LastMod`

+Assuming a key-value of `date: 2017-03-03` in a content file's front matter, your can run the date through `.Format` followed by a layout string for your desired output at build time:

+```golang

+{{ .PublishDate.Format "January 2, 2006" }} => March 3, 2017

+```

+For formatting *any* string representations of dates defined in your front matter, see the [`dateFormat` function][dateFormat], which will still leverage the Golang layout string explained below but uses a slightly different syntax.

+## Go's Layout String

+Hugo templates [format your dates][time] via layout strings that point to a specific reference time:

+```

+Mon Jan 2 15:04:05 MST 2006

+```

+While this may seem arbitrary, the numerical value of `MST` is `07`, thus making the layout string a sequence of numbers.

+Here is a visual explanation [taken directly from the Go docs][gdex]:

+```

+ Jan 2 15:04:05 2006 MST

+=> 1 2  3  4  5    6  -7

+```

+### Hugo Date and Time Templating Reference

+The following examples show the layout string followed by the rendered output.

+The examples were rendered and tested in [CST][] and all point to the same field in a content file's front matter:

+```

+date: 2017-03-03T14:15:59-06:00

+```

+`.Date` (i.e. called via [page variable][pagevars])

+: **Returns**: `2017-03-03 14:15:59 -0600 CST`

+`"Monday, January 2, 2006"`

+: **Returns**: `Friday, March 3, 2017`

+`"Mon Jan 2 2006"`

+: **Returns**: `Fri Mar 3 2017`

+`"January 2nd"`

+: **Returns**: `March 3rd`

+`"January 2006"`

+: **Returns**: `March 2017`

+`"2006-01-02"`

+: **Returns**: `2017-03-03`

+`"Monday"`

+: **Returns**: `Friday`

+`"02 Jan 06 15:04 MST"` (RFC822)

+: **Returns**: `03 Mar 17 14:15 CST`

+`"02 Jan 06 15:04 -0700"` (RFC822Z)

+: **Returns**: `03 Mar 17 14:15 -0600`

+`"Mon, 02 Jan 2006 15:04:05 MST"` (RFC1123)

+: **Returns**: `Fri, 03 Mar 2017 14:15:59 CST`

+`"Mon, 02 Jan 2006 15:04:05 -0700"` (RFC339)

+: **Returns**: `Fri, 03 Mar 2017 14:15:59 -0600`

+### Cardinal Numbers and Ordinal Abbreviations

+Spelled-out cardinal numbers (e.g. "one", "two", and "three") and ordinal abbreviations (i.e., with shorted suffixes like "1st", "2nd", and "3rd") are not currently supported:

+```

+{{.Date.Format "Jan 2nd 2006"}}

+```

+Hugo assumes you want to append `nd` as a string to the day of the month and outputs the following:

+```

+Mar 3nd 2017

+```

+<!-- Content idea: see https://discourse.gohugo.io/t/formatting-a-date-with-suffix-2nd/5701 -->

+### Use `.Local` and `.UTC`

+In conjunction with the [`dateFormat` function][dateFormat], you can also convert your dates to `UTC` or to local timezones:

+`{{ dateFormat "02 Jan 06 15:04 MST" .Date.UTC }}`

+: **Returns**: `03 Mar 17 20:15 UTC`

+`{{ dateFormat "02 Jan 06 15:04 MST" .Date.Local }}`

+: **Returns**: `03 Mar 17 14:15 CST`

+[CST]: https://en.wikipedia.org/wiki/Central_Time_Zone

+[dateFormat]: /functions/dateformat/

+[gdex]: https://golang.org/pkg/time/#example_Time_Format

+[pagevars]: /variables/page/

+[time]: https://golang.org/pkg/time/

--- /dev/null

+++ b/content/functions/get.md

@@ -1,0 +1,32 @@

+---

+title: .Get

+description: Accesses positional and ordered parameters in shortcode declaration.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [shortcodes]

+signature: ["Get INDEX", "Get KEY"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+needsexample: true

+---

+`.Get` is specifically used when creating your own [shortcode template][sc].

+[sc]: /templates/shortcode-templates/

--- /dev/null

+++ b/content/functions/getenv.md

@@ -1,0 +1,31 @@

+---

+title: getenv

+description: Returns the value of an environment variable.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["getenv VARIABLE"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+Takes a string containing the name of the variable as input. Returns

+an empty string if the variable is not set, otherwise returns the

+value of the variable.

+```

+{{ getenv "HOME" }}

+```

+{{% note %}}

+In Unix-like environments, the variable must also be exported in order to be seen by `hugo`.

+{{% /note %}}

--- /dev/null

+++ b/content/functions/hasPrefix.md

@@ -1,0 +1,22 @@

+---

+title: hasprefix

+linktitle: hasPrefix

+description: Tests whether a string begins with prefix.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["hasPrefix STRING PREFIX"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+* `{{ hasPrefix "Hugo" "Hu" }}` → true

--- /dev/null

+++ b/content/functions/haschildren.md

@@ -1,0 +1,23 @@

+---

+title: .HasChildren

+description:

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [menus]

+toc:

+signature: ["HasChildren"]

+workson: [menus]

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: true

+aliases: []

+---

+Used in [menu templates](/templates/menu-templates/).

--- /dev/null

+++ b/content/functions/hasmenucurrent.md

@@ -1,0 +1,23 @@

+---

+title: .HasMenuCurrent

+description:

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [menus]

+signature: ["HasMenuCurrent"]

+workson: [menus]

+hugoversion:

+relatedfuncs: []

+deprecated: false

+toc: false

+draft: true

+aliases: []

+---

+Used in [menu templates](/templates/menu-templates/).

--- /dev/null

+++ b/content/functions/highlight.md

@@ -1,0 +1,28 @@

+---

+title: highlight

+linktitle: highlight

+description: Takes a string of code and language declaration and uses Pygments to return syntax-highlighted HTML with inline-styles.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [highlighting,pygments,code blocks,syntax]

+signature: ["highlight INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+[`highlight` is used in Hugo's built-in `highlight` shortcode][highlight].

+See [Installing Hugo][installpygments] for more information on Pygments or [Syntax Highlighting][syntax] for more options on how to add syntax highlighting to your code blocks with Hugo.

+[highlight]: /content-management/shortcodes/#highlight

+[installpygments]: /getting-started/installing/#installing-pygments-optional

+[syntax]: /tools/syntax-highlighting/

--- /dev/null

+++ b/content/functions/htmlEscape.md

@@ -1,0 +1,26 @@

+---

+title: htmlEscape

+linktitle:

+description: Returns the given string with the reserved HTML codes escaped.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings, html]

+signature: ["htmlEscape INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [htmlUnescape]

+deprecated: false

+aliases: []

+---

+In the result `&` becomes `&amp;` and so on. It escapes only: `<`, `>`, `&`, `'` and `"`.

+```

+{{ htmlEscape "Hugo & Caddy > Wordpress & Apache" }} → "Hugo &amp; Caddy &gt; Wordpress &amp; Apache"

+```

--- /dev/null

+++ b/content/functions/htmlUnescape.md

@@ -1,0 +1,28 @@

+---

+title: htmlUnescape

+linktitle: htmlUnescape

+description: Returns the given string with HTML escape codes un-escaped.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["htmlUnescape INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [htmlEscape]

+deprecated: false

+aliases: []

+---

+`htmlUnescape` returns the given string with HTML escape codes un-escaped.

+Remember to pass the output of this to `safeHTML` if fully un-escaped characters are desired. Otherwise, the output will be escaped again as normal.

+```

+{{ htmlUnescape "Hugo &amp; Caddy &gt; Wordpress &amp; Apache" }} → "Hugo & Caddy > Wordpress & Apache"

+```

--- /dev/null

+++ b/content/functions/humanize.md

@@ -1,0 +1,31 @@

+---

+title: humanize

+linktitle:

+description: Returns the humanized version of an argument with the first letter capitalized.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings,casing]

+signature: ["humanize INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+If the input is either an int64 value or the string representation of an integer, humanize returns the number with the proper ordinal appended.

+```

+{{humanize "my-first-post"}} → "My first post"

+{{humanize "myCamelPost"}} → "My camel post"

+{{humanize "52"}} → "52nd"

+{{humanize 103}} → "103rd"

+```

--- /dev/null

+++ b/content/functions/i18n.md

@@ -1,0 +1,34 @@

+---

+title: i18n

+linktitle: i18n

+description: Translates a piece of content based on your i18n configuration files.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [internationalization,i18n,multilingual]

+signature: ["i18n KEY", "T KEY"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+This translates a piece of content based on your `i18n/en-US.yaml` (and similar) files. You can use the [go-i18n](https://github.com/nicksnyder/go-i18n) tools to manage your translations. The translations can exist in both the theme and at the root of your repository.

+```golang

+{{ i18n "translation_id" }}

+```

+{{% note "Alias `T`" %}}

+`T` is an alias to `i18n`. E.g. `{{ T "translation_id" }}`.

+{{% /note %}}

+For more information about string translations, see [Translation of Strings in Multilingual Mode][multistrings].

+[multistrings]: /content-management/multilingual/#translation-of-strings

--- /dev/null

+++ b/content/functions/imageConfig.md

@@ -1,0 +1,24 @@

+---

+linktitle: imageConfig

+description: Parses the image and returns the height, width, and color model.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [images]

+signature: ["imageConfig PATH"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+```golang

+{{ with (imageConfig "favicon.ico") }}

+favicon.ico: {{.Width}} x {{.Height}}

+{{ end }}

+```

--- /dev/null

+++ b/content/functions/in.md

@@ -1,0 +1,33 @@

+---

+title: in

+linktitle:

+description: Checks if an element is in an array or slice--or a substring in a string---and returns a boolean.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["in SET ITEM"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+The elements supported are strings, integers and floats, although only float64 will match as expected.

+In addition, `in` can also check if a substring exists in a string.

+```

+{{ if in .Params.tags "Git" }}Follow me on GitHub!{{ end }}

+```

+```

+{{ if in "this string contains a substring" "substring" }}Substring found!{{ end }}

+```

--- /dev/null

+++ b/content/functions/index-function.md

@@ -1,0 +1,84 @@

+---

+title: index

+linktitle: index

+description: Looks up the index(es) or key(s) of the data structure passed into it.

+godocref: https://golang.org/pkg/text/template/#hdr-Functions

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["index COLLECTION INDEX", "index COLLECTION KEY"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: [/functions/index/]

+needsexample: true

+---

+From the Godocs:

+> Returns the result of indexing its first argument by the following arguments. Thus "index x 1 2 3" is, in Go syntax, x[1][2][3]. Each indexed item must be a map, slice, or array.

+In Go templates, you can't access array, slice, or map elements directly the same way you would in Go. For example, `$.Site.Data.authors[.Params.authorkey]` isn't supported syntax.

+Instead, you have to use `index`, a function that handles the lookup for you.

+## Example: Load Data from a Path Based on Front Matter Params

+Assume you want to add a `location = ""` field to your front matter for every article written in `content/vacations/`. You want to use this field to populate information about the location at the bottom of the article in your `single.html` template. You also have a directory in `data/locations/` that looks like the following:

+```

+.

+└── data

+    └── locations

+        ├── abilene.toml

+        ├── chicago.toml

+        ├── oslo.toml

+        └── provo.toml

+```

+Here is an example of the data inside `data/locations/oslo.toml`:

+```toml

+website = "https://www.oslo.kommune.no"

+pop_city = 658390

+pop_metro = 1717900

+```

+The example we will use will be an article on Oslo, which front matter should set to exactly the same name as the corresponding file name in `data/locations/`:

+```toml

+title = "My Norwegian Vacation"

+location = "oslo"

+```

+The content of `oslo.toml` can be accessed from your template using the following node path: `.Site.Data.locations.oslo`. However, the specific file you need is going to change according to the front matter.

+This is where the `index` function is needed. `index` takes 2 parameters in this use case:

+1. The node path

+2. A string corresponding to the desired data; e.g.&mdash;

+```

+{{ index .Site.Data.locations “oslo” }}

+```

+The variable for `.Params.location` is a string and can therefore replace `oslo` in the example above:

+```golang

+{{ index .Site.Data.authors .Params.author }}

+=> map[website:https://www.oslo.kommune.no pop_city:658390 pop_metro:1717900]

+```

+Now the call will return the specific file according to the location specified in the content's front matter, but you will likely want to write specific properties to the template. You can do this by continuing down the node path via dot notation (`.`):

+```golang

+{{ (index .Site.Data.locations .Params.location).pop_city }}

+=> 658390

+```

--- /dev/null

+++ b/content/functions/int.md

@@ -1,0 +1,26 @@

+---

+title: int

+linktitle: int

+description: Creates an `int` from the argument passed into the function.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings,integers]

+signature: ["int INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+Useful for turning strings into numbers.

+```

+{{ int "123" }} → 123

+```

--- /dev/null

+++ b/content/functions/intersect.md

@@ -1,0 +1,58 @@

+---

+title: intersect

+linktitle: intersect

+description: Returns the common elements of two arrays or slices.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["intersect SET1 SET2"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+The elements supported are strings, integers, and floats (only float64).

+A useful example of `intersect` functionality is a "related posts" block. `isset` allows us to create a list of links to other posts that have tags that intersect with the tags in the current post.

+The following is an example of a "related posts" [partial template][partials] that could be added to a [single page template][single]:

+{{% code file="layouts/partials/related-posts.html" download="related-posts.html" %}}

+```html

+<ul>

+{{ $page_link := .Permalink }}

+{{ $tags := .Params.tags }}

+{{ range .Site.Pages }}

+    {{ $page := . }}

+    {{ $has_common_tags := intersect $tags .Params.tags | len | lt 0 }}

+    {{ if and $has_common_tags (ne $page_link $page.Permalink) }}

+        <li><a href="{{ $page.Permalink }}">{{ $page.Title }}</a></li>

+    {{ end }}

+{{ end }}

+</ul>

+```

+{{% /code %}}

+This is also very useful to use as `AND` filters when combined with where:

+```html

+{{ $pages := where .Site.RegularPages "Type" "not in" (slice "page" "about") }}

+{{ $pages := $pages | union (where .Site.RegularPages "Params.pinned" true) }}

+{{ $pages := $pages | intersect (where .Site.RegularPages "Params.images" "!=" nil) }}

+```

+The above fetches regular pages not of `page` or `about` type unless they are pinned. And finally, we exclude all pages with no `images` set in Page params.

+See [union](/functions/union) for `OR`.

+[partials]: /templates/partials/

+[single]: /templates/single-page-templates/

--- /dev/null

+++ b/content/functions/ismenucurrent.md

@@ -1,0 +1,23 @@

+---

+title: .IsMenuCurrent

+description:

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [menus]

+signature: ["IsMenuCurrent"]

+workson: [menus]

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: true

+aliases: []

+needsexample: true

+---

+Used in [menu templates](/templates/menu-templates/).

--- /dev/null

+++ b/content/functions/isset.md

@@ -1,0 +1,31 @@

+---

+title: isset

+linktitle: isset

+description: Returns true if the parameter is set.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["isset COLLECTION INDEX", "isset COLLECTION KEY"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+Takes either a slice, array, or channel and an index or a map and a key as input.

+```

+{{ if isset .Params "project_url" }} {{ index .Params "project_url" }}{{ end }}

+```

+{{% warning %}}

+All site-level configuration keys are stored as lower case. Therefore, a `myParam` key-value set in your [site configuration file](/getting-started/configuration/) needs to be accessed with `{{if isset .Site.Params "myparam"}}` and *not* with `{{if isset .Site.Params "myParam"}}`. Note that you can still access the same config key with `.Site.Params.myParam` *or* `.Site.Params.myparam`, for example, when using [`with`](/functions/with).

+{{% /warning %}}

--- /dev/null

+++ b/content/functions/jsonify.md

@@ -1,0 +1,28 @@

+---

+title: jsonify

+linktitle: jsonify

+description: Encodes a given object to JSON.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings,json]

+signature: ["jsonify INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [plainify]

+deprecated: false

+aliases: []

+---

+```

+{{ dict "title" .Title "content" .Plain | jsonify }}

+```

+See also the `.PlainWords`, `.Plain`, and `.RawContent` [page variables][pagevars].

+[pagevars]: /variables/page/

--- /dev/null

+++ b/content/functions/last.md

@@ -1,0 +1,30 @@

+---

+title: last

+linktitle: last

+description: "slices an array to only the last <em>N</em>th elements."

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: []

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+toc:

+signature: ["last INDEX COLLECTION"]

+workson: [lists, taxonomies, terms, groups]

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+```

+{{ range last 10 .Data.Pages }}

+    {{ .Render "summary" }}

+{{ end }}

+```

--- /dev/null

+++ b/content/functions/len.md

@@ -1,0 +1,64 @@

+---

+title: len

+linktitle: len

+description: Returns the length of a variable according to its type.

+godocref: https://golang.org/pkg/builtin/#len

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-18

+categories: [functions]

+#tags: []

+signature: ["len INPUT"]

+workson: [lists,taxonomies,terms]

+hugoversion:

+relatedfuncs: []

+deprecated: false

+toc: false

+aliases: []

+---

+`len` is a built-in function in Golang that returns the length of a variable according to its type. From the Golang documentation:

+> Array: the number of elements in v.

+>

+> Pointer to array: the number of elements in *v (even if v is nil).

+>

+> Slice, or map: the number of elements in v; if v is nil, len(v) is zero.

+>

+> String: the number of bytes in v.

+>

+> Channel: the number of elements queued (unread) in the channel buffer; if v is nil, len(v) is zero.

+`len` is also considered a [fundamental function for Hugo templating][].

+## `len` Example 1: Longer Headings

+You may want to append a class to a heading according to the length of the string therein. The following templating checks to see if the title's length is greater than 80 characters and, if so, adds a `long-title` class to the `<h1>`:

+{{% code file="check-title-length.html" %}}

+```html

+<header>

+    <h1{{if gt (len .Title) 80}} class="long-title"{{end}}>{{.Title}}</h1>

+</header>

+```

+{{% /code %}}

+## `len` Example 2: Counting Pages with `where`

+The following templating uses [`where`][] in conjunction with `len` to figure out the total number of content pages in a `posts` [section][]:

+{{% code file="how-many-posts.html" %}}

+```html

+{{ $posts := (where .Site.RegularPages "Section" "==" "post") }}

+{{ $postCount := len $posts }}

+```

+{{% /code %}}

+Note the use of `.RegularPages`, a [site variable][] that counts all regular content pages but not the `_index.md` pages used to add front matter and content to [list templates][].

+[fundamental function for Hugo templating]: /templates/introduction/

+[list templates]: /templates/lists/

+[section]: /content-management/sections/

+[site variable]: /variables/site/

+[`where`]: /functions/where/

\ No newline at end of file

--- /dev/null

+++ b/content/functions/lower.md

@@ -1,0 +1,24 @@

+---

+title: lower

+linktitle: lower

+description: Converts all characters in the provided string to lowercase.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings,casing]

+signature: ["lower INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```

+{{lower "BatMan"}} → "batman"

+```

--- /dev/null

+++ b/content/functions/markdownify.md

@@ -1,0 +1,25 @@

+---

+title: markdownify

+linktitle: markdownify

+description: Runs the provided string through the Markdown processor.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [markdown,content]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+signature: ["markdownify INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```

+{{ .Title | markdownify }}

+```

--- /dev/null

+++ b/content/functions/math.md

@@ -1,0 +1,67 @@

+---

+title: Math

+description: Hugo provides six mathematical operators in templates.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [math, operators]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+toc:

+signature: []

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+There are 6 basic mathematical operators that can be used in Hugo templates:

+| Function | Description              | Example                       |

+| -------- | ------------------------ | ----------------------------- |

+| `add`    | Adds two integers.       | `{{add 1 2}}` &rarr; 3        |

+| `div`    | Divides two integers.    | `{{div 6 3}}` &rarr; 2        |

+| `mod`    | Modulus of two integers. | `{{mod 15 3}}` &rarr; 0       |

+| `modBool`| Boolean of modulus of two integers. Evaluates to `true` if = 0. | `{{modBool 15 3}}` &rarr; true |

+| `mul`    | Multiplies two integers. | `{{mul 2 3}}` &rarr; 6        |

+| `sub`    | Subtracts two integers.  | `{{sub 3 2}}` &rarr; 1        |

+## Use `add` with Strings

+You can also use the `add` function with strings. You may like this functionality in many use cases, including creating new variables by combining page- or site-level variables with other strings.

+For example, social media sharing with [Twitter Cards][cards] requires the following `meta` link in your site's `<head>` to display Twitter's ["Summary Card with Large Image"][twtsummary]:

+```html

+<meta name="twitter:image" content="http://yoursite.com/images/my-twitter-image.jpg">

+```

+Let's assume you have an `image` field in the front matter of each of your content files:

+```yaml

+---

+title: My Post

+image: my-post-image.jpg

+---

+```

+You can then concatenate the `image` value (string) with the path to your `images` directory in `static` and leverage a URL-related templating function for increased flexibility:

+{{% code file="partials/head/twitter-card.html" %}}

+```html

+{{$socialimage := add "images/" .Params.image}}

+<meta name="twitter:image" content="{{ $socialimage | absURL }}">

+```

+{{% /code %}}

+{{% note %}}

+The `add` example above makes use of the [`absURL` function](/functions/absurl/). `absURL` and its relative companion `relURL` is the recommended way to construct URLs in Hugo.

+{{% /note %}}

+[cards]: https://dev.twitter.com/cards/overview

+[twtsummary]: https://dev.twitter.com/cards/types/summary-large-image

\ No newline at end of file

--- /dev/null

+++ b/content/functions/md5.md

@@ -1,0 +1,33 @@

+---

+title: md5

+linktitle: md5

+description: hashes the given input and returns its MD5 checksum.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["md5 INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```html

+{{ md5 "Hello world, gophers!" }}

+<!-- returns the string "b3029f756f98f79e7f1b7f1d1f0dd53b" -->

+```

+This can be useful if you want to use [Gravatar](https://en.gravatar.com/) for generating a unique avatar:

+```html

+<img src="https://www.gravatar.com/avatar/{{ md5 "[email protected]" }}?s=100&d=identicon">

+```

--- /dev/null

+++ b/content/functions/now.md

@@ -1,0 +1,44 @@

+---

+title: now

+linktitle: now

+description: Returns the current local time

+godocref: https://godoc.org/time#Time

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-30

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [dates,time]

+signature: ["now"]

+workson: []

+hugoversion:

+relatedfuncs: [Unix,dateFormat]

+deprecated: false

+aliases: []

+---

+See [`time.Time`](https://godoc.org/time#Time).

+For example, building your site on June 24, 2017 with the following templating:

+```html

+<div>

+    <small>&copy; {{ now.Format "2006"}}</small>

+</div>

+```

+Which will produce the following:

+```html

+<div>

+    <small>&copy; 2017</small>

+</div>

+```

+The above example uses the [`.Format` function](/functions/format), which page includes a full listing of date formatting using Golang's layout string.

+{{% note %}}

+Older Hugo themes may use the deprecated `.Now` (uppercase). Be sure to use the lowercase `.now` in your templating.

+{{% /note %}}

--- /dev/null

+++ b/content/functions/param.md

@@ -1,0 +1,41 @@

+---

+title: .Param

+description: Calls page or site variables into your template.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-30

+#tags: ["front matter"]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+toc:

+signature: [".Param KEY"]

+workson: []

+hugoversion:

+relatedfuncs: [default]

+deprecated: false

+draft: false

+aliases: []

+---

+In Hugo, you can declare [site-wide params][sitevars] (i.e. in your [configuration][]), as well as params for [individual pages][pagevars].

+A common use case is to have a general value for the site and a more specific value for some of the pages (e.g., an image).

+You can use the `.Param` method to call these values into your template. The following will first look for an `image` param in a specific content's [front matter][]. If not found, Hugo will look for an `image` param in your site's configuration:

+```

+$.Param "image"

+```

+{{% note %}}

+The `Param` method may not consider empty strings in a content's front matter as "not found." If you are setting preconfigured front matter fields to empty strings using Hugo's archetypes, it may be best to use the [`default` function](/functions/default/) instead of `Param`. See the [related issue on GitHub](https://github.com/gohugoio/hugo/issues/3366).

+{{% /note %}}

+[configuration]: /getting-started/configuration/

+[front matter]: /content-management/front-matter/

+[pagevars]: /variables/page/

+[sitevars]: /variables/site/

--- /dev/null

+++ b/content/functions/partialCached.md

@@ -1,0 +1,42 @@

+---

+title: partialCached

+linktitle: partialCached

+description: Allows for caching of partials that do not need to be re-rendered on every invocation.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["partialCached LAYOUT INPUT [VARIANT...]"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+The `partialCached` template function can offer significant performance gains for complex templates that don't need to be re-rendered on every invocation. Here is the simplest usage:

+```golang

+{{ partialCached "footer.html" . }}

+```

+You can also pass additional parameters to `partialCached` to create *variants* of the cached partial. For example, if you have a complex partial that should be identical when rendered for pages within the same section, you could use a variant based upon section so that the partial is only rendered once per section:

+{{% code file="partial-cached-example.html" %}}

+```

+{{ partialCached "footer.html" . .Section }}

+```

+{{% /code %}}

+If you need to pass additional parameters to create unique variants, you can pass as many variant parameters as you need:

+```

+{{ partialCached "footer.html" . .Params.country .Params.province }}

+```

+Note that the variant parameters are not made available to the underlying partial template. They are only use to create a unique cache key.

--- /dev/null

+++ b/content/functions/plainify.md

@@ -1,0 +1,31 @@

+---

+title: plainify

+linktitle: plainify

+description: Strips any HTML and returns the plain text version of the provided string.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-30

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["plainify INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [jsonify,]

+deprecated: false

+aliases: []

+---

+```

+{{ "<b>BatMan</b>" | plainify }} → "BatMan"

+```

+See also the `.PlainWords`, `.Plain`, and `.RawContent` [page variables][pagevars].

+[pagevars]: /variables/page/

--- /dev/null

+++ b/content/functions/pluralize.md

@@ -1,0 +1,25 @@

+---

+title: pluralize

+linktitle: pluralize

+description: Pluralizes the given word according to a set of common English pluralization rules

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["pluralize INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```

+{{ "cat" | pluralize }} → "cats"

+```

--- /dev/null

+++ b/content/functions/printf.md

@@ -1,0 +1,29 @@

+---

+title: printf

+linktitle: printf

+description: Formats a string using the standard `fmt.Sprintf` function.

+godocref: https://golang.org/pkg/fmt/

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["printf FORMAT INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+See [the go doc](https://golang.org/pkg/fmt/) for additional information.

+```golang

+{{ i18n ( printf "combined_%s" $var ) }}

+```

+```

+{{ printf "formatted %.2f" 3.1416 }}

+```

--- /dev/null

+++ b/content/functions/querify.md

@@ -1,0 +1,34 @@

+---

+title: querify

+linktitle: querify

+description: Takes a set of key-value pairs and returns a query string to be appended to URLs.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [urls]

+godocref:

+signature: ["querify KEY VALUE [KEY VALUE]..."]

+hugoversion:

+deprecated: false

+workson: []

+relatedfuncs: []

+aliases: []

+---

+`querify` takes a set of key-value pairs and returns a [query string](https://en.wikipedia.org/wiki/Query_string) that can be appended to a URL. E.g.

+The following example creates a link to a search results page on Google.

+```html

+<a href="https://www.google.com?{{ (querify "q" "test" "page" 3) | safeURL }}">Search</a>

+```

+This example renders the following HTML:

+```html

+<a href="https://www.google.com?page=3&q=test">Search</a>

+```

--- /dev/null

+++ b/content/functions/range.md

@@ -1,0 +1,25 @@

+---

+title: range

+linktitle:

+description: Iterates over a map, array, or slice.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions,fundamentals]

+menu:

+  docs:

+    parent: "functions"

+#tags: [iteration]

+signature: ["range COLLECTION"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+Just like in the Go programming language, Go and Hugo templates make heavy use of `range` to iterate over a map, array or slice.

+`range` is fundamental to templating in Hugo. (See the [Introduction to Hugo Templates](/templates/introduction/) for more examples.

--- /dev/null

+++ b/content/functions/readdir.md

@@ -1,0 +1,30 @@

+---

+title: readDir

+description: Gets a directory listing from a directory relative to the current working directory.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [files]

+signature: ["readDir PATH"]

+workson: []

+hugoversion:

+relatedfuncs: [readFile]

+deprecated: false

+aliases: []

+---

+If your current project working directory has a single file named `README.txt`:

+```

+{{ range (readDir ".") }}{{ .Name }}{{ end }} → "README.txt"

+```

+For more information on using `readDir` and `readFile` in your templates, see [Local File Templates][local].

+[local]: /templates/files/

--- /dev/null

+++ b/content/functions/readfile.md

@@ -1,0 +1,31 @@

+---

+title: readFile

+description: Reads a file from disk relative to the current project working directory and returns a string.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-30

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [files]

+signature: ["readFile PATH"]

+workson: []

+hugoversion:

+relatedfuncs: [readDir]

+deprecated: false

+aliases: []

+---

+Note that the filename must be relative to the current project working directory.

+So, if you have a file with the name `README.txt` in the root of your project with the content `Hugo Rocks!`:

+```html

+{{readFile "README.txt"}} → "Hugo Rocks!"

+```

+For more information on using `readDir` and `readFile` in your templates, see [Local File Templates][local].

+[local]: /templates/files/

--- /dev/null

+++ b/content/functions/ref.md

@@ -1,0 +1,30 @@

+---

+title: ref

+linktitle: ref

+description: Looks up a content page by logical name.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [cross references, anchors]

+signature: ["ref PAGE CONTENT"]

+workson: []

+hugoversion:

+relatedfuncs: [relref]

+deprecated: false

+aliases: []

+---

+`ref` and `relRef` look up a content page by relative path (`relref`) or logical name (`ref`) to return the permalink. Both functions require a `Page` object (usually satisfied with a "`.`"):

+```golang

+{{ relref . "about.md" }}

+```

+These functions are used in two of Hugo's built-in shortcodes. You can see basic usage examples of both `ref` and `relref` in the [shortcode documentation](/content-management/shortcodes/#ref-and-relref).

+For an extensive explanation of how to leverage `ref` and `relref` for content management, see [Cross References](/content-management/cross-references/).

--- /dev/null

+++ b/content/functions/relLangURL.md

@@ -1,0 +1,30 @@

+---

+title: relLangURL

+description: Adds the relative URL with correct language prefix according to site configuration for multilingual.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [multilingual,i18n,urls]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+signature: ["relLangURL INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+`absLangURL` and `relLangURL` functions are similar to their [`absURL`](/functions/absurl/) and [`relURL`](/functions/relurl/) relatives but will add the correct language prefix when the site is configured with more than one language. (See [Configuring Multilingual][multiliconfig].)

+So for a site  `baseURL` set to `http://yoursite.com/hugo/` and the current language is `en`:

+```golang

+{{ "blog/" | absLangURL }} → "http://yoursite.com/hugo/en/blog/"

+{{ "blog/" | relLangURL }} → "/hugo/en/blog/"

+```

+[multiliconfig]: /content-management/multilingual/#configuring-multilingual-mode

--- /dev/null

+++ b/content/functions/relref.md

@@ -1,0 +1,30 @@

+---

+title: relref

+# linktitle: relref

+description: Looks up a content page by relative path.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [cross references, anchors]

+signature: ["relref PAGE CONTENT"]

+workson: []

+hugoversion:

+relatedfuncs: [relref]

+deprecated: false

+aliases: []

+---

+`ref` and `relRef` look up a content page by relative path (`relref`) or logical name (`ref`) to return the permalink. Both functions require a `Page` object (usually satisfied with a "`.`"):

+```golang

+{{ relref . "about.md" }}

+```

+These functions are used in two of Hugo's built-in shortcodes. You can see basic usage examples of both `ref` and `relref` in the [shortcode documentation](/content-management/shortcodes/#ref-and-relref).

+For an extensive explanation of how to leverage `ref` and `relref` for content management, see [Cross References](/content-management/cross-references/).

--- /dev/null

+++ b/content/functions/relurl.md

@@ -1,0 +1,53 @@

+---

+title: relURL

+description: Given a string, prepends the relative URL according to a page's position in the project directory structure.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [urls]

+signature: ["relURL INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [absURL]

+deprecated: false

+aliases: []

+---

+Both `absURL` and `relURL` consider the configured value of `baseURL` in your site's [`config` file][configuration]. Given a `baseURL` set to `http://yoursite.com/hugo/`:

+```golang

+{{ "mystyle.css" | absURL }} → "http://yoursite.com/hugo/mystyle.css"

+{{ "mystyle.css" | relURL }} → "/hugo/mystyle.css"

+{{ "http://gohugo.io/" | relURL }} →  "http://gohugo.io/"

+{{ "http://gohugo.io/" | absURL }} →  "http://gohugo.io/"

+```

+The last two examples may look strange but can be very useful. For example, the following shows how to use `absURL` in [JSON-LD structured data for SEO][jsonld] where some of your images for a piece of content may or may not be hosted locally:

+{{% code file="layouts/partials/schemaorg-metadata.html" download="schemaorg-metadata.html" %}}

+```html

+<script type="application/ld+json">

+{

+    "@context" : "http://schema.org",

+    "@type" : "BlogPosting",

+    "image" : {{ apply .Params.images "absURL" "." }}

+}

+</script>

+```

+{{% /code %}}

+The above uses the [apply function][] and also exposes how the Go template parser JSON-encodes objects inside `<script>` tags. See [the safeJS template function][safejs] for examples of how to tell Hugo not to escape strings inside of such tags.

+{{% note "Ending Slash" %}}

+`absURL` and `relURL` are smart about missing slashes, but they will *not* add a closing slash to a URL if it is not present.

+{{% /note %}}

+[apply function]: /functions/apply/

+[configuration]: /getting-started/configuration/

+[jsonld]: https://developers.google.com/search/docs/guides/intro-structured-data

+[safejs]: /functions/safejs

--- /dev/null

+++ b/content/functions/render.md

@@ -1,0 +1,34 @@

+---

+title: render

+# linktitle: Render

+description: Takes a view to apply when rendering content.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [views]

+signature: ["render LAYOUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+The view is an alternative layout and should be a file name that points to a template in one of the locations specified in the documentation for [Content Views](/templates/views).

+This function is only available when applied to a single piece of content within a [list context][].

+This example could render a piece of content using the content view located at `/layouts/_default/summary.html`:

+```golang

+{{ range .Data.Pages }}

+    {{ .Render "summary"}}

+{{ end }}

+```

+[list context]: /templates/lists/

--- /dev/null

+++ b/content/functions/replace.md

@@ -1,0 +1,26 @@

+---

+title: replace

+# linktitle: replace

+description: Replaces all occurrences of the search string with the replacement string.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["replace INPUT OLD NEW"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```

+`{{ replace "Batman and Robin" "Robin" "Catwoman" }}`

+→ "Batman and Catwoman"

+```

--- /dev/null

+++ b/content/functions/replacere.md

@@ -1,0 +1,31 @@

+---

+title: replacere

+# linktitle: replaceRE

+description: Replaces all occurrences of a regular expression with the replacement pattern.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-30

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [regex]

+signature: ["replaceRE PATTERN REPLACEMENT INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```golang

+{{ replaceRE "^https?://([^/]+).*" "$1" "http://gohugo.io/docs" }}` → "gohugo.io"

+{{ "http://gohugo.io/docs" | replaceRE "^https?://([^/]+).*" "$1" }}` → "gohugo.io"

+```

+{{% note %}}

+Hugo uses Golang's [Regular Expression package](https://golang.org/pkg/regexp/), which is the same general syntax used by Perl, Python, and other languages but with a few minor differences for those coming from a background in PCRE. For a full syntax listing, see the [GitHub wiki for re2](https://github.com/google/re2/wiki/Syntax).

+If you are just learning RegEx, or at least Golang's flavor, you can practice pattern matching in the browser at <https://regex101.com/>.

+{{% /note %}}

--- /dev/null

+++ b/content/functions/safeCSS.md

@@ -1,0 +1,36 @@

+---

+title: safeCSS

+description: Declares the provided string as a known "safe" CSS string.

+godocref: https://golang.org/src/html/template/content.go?s=919:929#L15

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-26

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [style,css,strings]

+signature: ["safeCSS INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: [safeHTML,safeHTMLAttr,]

+deprecated: false

+aliases: []

+---

+In this context, *safe* means CSS content that matches any of the following:

+1. The CSS3 stylesheet production, such as `p { color: purple }`.

+2. The CSS3 rule production, such as `a[href=~"https:"].foo#bar`.

+3. CSS3 declaration productions, such as `color: red; margin: 2px`.

+4. The CSS3 value production, such as `rgba(0, 0, 255, 127)`.

+Example: Given `style = "color: red;"` defined in the front matter of your `.md` file:

+* <span class="good">`<p style="{{ .Params.style | safeCSS }}">…</p>` &rarr; `<p style="color: red;">…</p>`</span>

+* <span class="bad">`<p style="{{ .Params.style }}">…</p>` &rarr; `<p style="ZgotmplZ">…</p>`</span>

+{{% note "ZgotmplZ" %}}

+"ZgotmplZ" is a special value that indicates that unsafe content reached a CSS or URL context.

+{{% /note %}}

--- /dev/null

+++ b/content/functions/safeHTML.md

@@ -1,0 +1,41 @@

+---

+title: safeHTML

+# linktitle:

+description: Declares a provided string as a "safe" HTML document to avoid escaping by Go templates.

+godocref: https://golang.org/src/html/template/content.go?s=1374:1385#L25

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["safeHTML INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+It should not be used for HTML from a third-party, or HTML with unclosed tags or comments.

+Given a site-wide [`config.toml`][config] with the following `copyright` value:

+```toml

+copyright = "© 2015 Jane Doe.  <a href=\"http://creativecommons.org/licenses/by/4.0/\">Some rights reserved</a>."

+```

+`{{ .Site.Copyright | safeHTML }}` in a template would then output:

+```html

+© 2015 Jane Doe.  <a href="http://creativecommons.org/licenses/by/4.0/">Some rights reserved</a>.

+```

+However, without the `safeHTML` function, html/template assumes `.Site.Copyright` to be unsafe and therefore escapes all HTML tags and renders the whole string as plain text:

+```html

+<p>© 2015 Jane Doe.  &lt;a href=&#34;http://creativecommons.org/licenses by/4.0/&#34;&gt;Some rights reserved&lt;/a&gt;.</p>

+```

+[config]: /getting-started/configuration/

--- /dev/null

+++ b/content/functions/safeHTMLAttr.md

@@ -1,0 +1,32 @@

+---

+title: safeHTMLAttr

+# linktitle: safeHTMLAttr

+description: Declares the provided string as a safe HTML attribute.

+godocref: https://golang.org/src/html/template/content.go?s=1661:1676#L33

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["safeHTMLAttr INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+Example: Given a site-wide `config.toml` that contains this menu entry:

+```toml

+[[menu.main]]

+    name = "IRC: #golang at freenode"

+    url = "irc://irc.freenode.net/#golang"

+```

+* <span class="bad">`<a href="{{ .URL }}">` &rarr; `<a href="#ZgotmplZ">`</span>

+* <span class="good">`<a {{ printf "href=%q" .URL | safeHTMLAttr }}>` &rarr; `<a href="irc://irc.freenode.net/#golang">`</span>

--- /dev/null

+++ b/content/functions/safeJS.md

@@ -1,0 +1,31 @@

+---

+title: safeJS

+# linktitle:

+description: Declares the provided string as a known safe JavaScript string.

+godocref: https://golang.org/src/html/template/content.go?s=2548:2557#L51

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["safeJS INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+In this context, *safe* means the string encapsulates a known safe EcmaScript5 Expression (e.g., `(x + y * z())`).

+Template authors are responsible for ensuring that typed expressions do not break the intended precedence and that there is no statement/expression ambiguity as when passing an expression like `{ foo:bar() }\n['foo']()`, which is both a valid expression and a valid program with a very different meaning.

+Example: Given `hash = "619c16f"` defined in the front matter of your `.md` file:

+* <span class="good">`<script>var form_{{ .Params.hash | safeJS }};…</script>` &rarr; `<script>var form_619c16f;…</script>`</span>

+* <span class="bad">`<script>var form_{{ .Params.hash }};…</script>` &rarr; `<script>var form_"619c16f";…</script>`</span>

--- /dev/null

+++ b/content/functions/safeURL.md

@@ -1,0 +1,82 @@

+---

+title: safeURL

+description: Declares the provided string as a safe URL or URL substring.

+godocref: https://golang.org/pkg/html/template/#HTMLEscape

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [strings,urls]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+signature: ["safeURL INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+`safeURL` declares the provided string as a "safe" URL or URL substring (see [RFC 3986][]). A URL like `javascript:checkThatFormNotEditedBeforeLeavingPage()` from a trusted source should go in the page, but by default dynamic `javascript:` URLs are filtered out since they are a frequently exploited injection vector.

+Without `safeURL`, only the URI schemes `http:`, `https:` and `mailto:` are considered safe by Go templates. If any other URI schemes (e.g., `irc:` and `javascript:`) are detected, the whole URL will be replaced with `#ZgotmplZ`. This is to "defang" any potential attack in the URL by rendering it useless.

+The following examples use a [site `config.toml`][configuration] with the following [menu entry][menus]:

+{{% code file="config.toml" copy="false" %}}

+```toml

+[[menu.main]]

+    name = "IRC: #golang at freenode"

+    url = "irc://irc.freenode.net/#golang"

+```

+{{% /code %}}

+The following is an example of a sidebar partial that may be used in conjunction with the preceding front matter example:

+{{% code file="layouts/partials/bad-url-sidebar-menu.html" copy="false" %}}

+```html

+<!-- This unordered list may be part of a sidebar menu -->

+<ul>

+  {{ range .Site.Menus.main }}

+  <li><a href="{{ .URL }}">{{ .Name }}</a></li>

+  {{ end }}

+</ul>

+```

+{{% /code %}}

+This partial would produce the following HTML output:

+{{% output file="bad-url-sidebar-menu-output.html" %}}

+```html

+<!-- This unordered list may be part of a sidebar menu -->

+<ul>

+    <li><a href="#ZgotmplZ">IRC: #golang at freenode</a></li>

+</ul>

+```

+{{% /output %}}

+The odd output can be remedied by adding ` | safeURL` to our `.Title` page variable:

+{{% code file="layouts/partials/correct-url-sidebar-menu.html" copy="false" %}}

+```html

+<!-- This unordered list may be part of a sidebar menu -->

+<ul>

+    <li><a href="{{ .URL | safeURL }}">{{ .Name }}</a></li>

+</ul>

+```

+{{% /code %}}

+With the `.URL` page variable piped through `safeURL`, we get the desired output:

+{{% output file="correct-url-sidebar-menu-output.html" %}}

+```html

+<ul class="sidebar-menu">

+    <li><a href="irc://irc.freenode.net/#golang">IRC: #golang at freenode</a></li>

+</ul>

+```

+{{% /output %}}

+[configuration]: /getting-started/configuration/

+[menus]: /content-management/menus/

+[RFC 3986]: http://tools.ietf.org/html/rfc3986

--- /dev/null

+++ b/content/functions/scratch.md

@@ -1,0 +1,75 @@

+---

+title: .Scratch

+description: Acts as a "scratchpad" to allow for writable page- or shortcode-scoped variables.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [iteration]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+toc:

+signature: []

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: [/extras/scratch/,/doc/scratch/]

+---

+In most cases you can do well without `Scratch`, but there are some use cases that aren't solvable with Go's templates without `Scratch`'s help, due to scoping issues.

+`Scratch` is added to both `Page` and `Shortcode` -- with following methods:

+* `Set` and `Add` takes a `key` and the `value` to add.

+* `Get` returns the `value` for the `key` given.

+* `SetInMap` takes a `key`, `mapKey` and `value`

+* `GetSortedMapValues` returns array of values from `key` sorted by `mapKey`

+`Set` and `SetInMap` can store values of any type.

+For single values, `Add` accepts values that support Go's `+` operator. If the first `Add` for a key is an array or slice, the following adds will be appended to that list.

+The scope of the backing data is global for the given `Page` or `Shortcode`, and spans partial and shortcode includes.

+Note that `.Scratch` from a shortcode will return the shortcode's `Scratch`, which in most cases is what you want. If you want to store it in the page scroped Scratch, then use `.Page.Scratch`.

+## Sample usage

+The usage is best illustrated with some samples:

+```

+{{ $.Scratch.Add "a1" 12 }}

+{{ $.Scratch.Get "a1" }} {{/* => 12 */}}

+{{ $.Scratch.Add "a1" 1 }}

+{{ $.Scratch.Get "a1" }} // {{/* => 13 */}}

+{{ $.Scratch.Add "a2" "AB" }}

+{{ $.Scratch.Get "a2" }} {{/* => AB */}}

+{{ $.Scratch.Add "a2" "CD" }}

+{{ $.Scratch.Get "a2" }} {{/* => ABCD */}}

+{{ $.Scratch.Add "l1" (slice "A" "B") }}

+{{ $.Scratch.Get "l1" }} {{/* => [A B]  */}}

+{{ $.Scratch.Add "l1" (slice "C" "D") }}

+{{ $.Scratch.Get "l1" }} {{/* => [A B C D] */}}

+{{ $.Scratch.Set "v1" 123 }}

+{{ $.Scratch.Get "v1" }}  {{/* => 123 */}}

+{{ $.Scratch.SetInMap "a3" "b" "XX" }}

+{{ $.Scratch.SetInMap "a3" "a" "AA" }}

+{{ $.Scratch.SetInMap "a3" "c" "CC" }}

+{{ $.Scratch.SetInMap "a3" "b" "BB" }}

+{{ $.Scratch.GetSortedMapValues "a3" }} {{/* => []interface {}{"AA", "BB", "CC"} */}}

+```

+{{% note %}}

+The examples above uses the special `$` variable, which refers to the top-level node. This is the behavior you most likely want, and will help remove some confusion when using `Scratch` inside page range loops -- and you start inadvertently calling the wrong `Scratch`. But there may be use cases for `{{ .Scratch.Add "key" "some value" }}`.

+{{% /note %}}

+[pagevars]: /variables/page/

--- /dev/null

+++ b/content/functions/seq.md

@@ -1,0 +1,51 @@

+---

+title: seq

+# linktitle:

+description: Creates a sequence of integers.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: []

+signature: ["seq LAST", "seq FIRST LAST", "seq FIRST INCREMENT LAST"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+It's named and used in the model of [GNU's seq][].

+```

+3 → 1, 2, 3

+1 2 4 → 1, 3

+-3 → -1, -2, -3

+1 4 → 1, 2, 3, 4

+1 -2 → 1, 0, -1, -2

+```

+## Example: `seq` with `range` and `after`

+You can use `seq` in combination with `range` and `after`. The following will return 19 elements:

+```golang

+{{ range after 1 (seq 20)}}

+{{ end }}

+```

+However, when ranging with an index, the following may be less confusing in that `$indexStartingAt1` and `$num` will return `1,2,3 ... 20`:

+```golang

+{{ range $index, $num := (seq 20) }}

+$indexStartingAt1 := (add $index 1)

+{{ end }}

+```

+[GNU's seq]: http://www.gnu.org/software/coreutils/manual/html_node/seq-invocation.html#seq-invocation

--- /dev/null

+++ b/content/functions/sha.md

@@ -1,0 +1,34 @@

+---

+title: sha

+# linktitle: sha

+description: Hashes the given input and returns either an SHA1 or SHA256 checksum.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [sha,checksum]

+signature: ["sha1 INPUT", "sha256 INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+`sha1` hashes the given input and returns its SHA1 checksum.

+```html

+{{ sha1 "Hello world, gophers!" }}

+<!-- returns the string "c8b5b0e33d408246e30f53e32b8f7627a7a649d4" -->

+```

+`sha256` hashes the given input and returns its SHA256 checksum.

+```html

+{{ sha256 "Hello world, gophers!" }}

+<!-- returns the string "6ec43b78da9669f50e4e422575c54bf87536954ccd58280219c393f2ce352b46" -->

+```

--- /dev/null

+++ b/content/functions/shuffle.md

@@ -1,0 +1,43 @@

+---

+title: shuffle

+# linktitle:

+description: Returns a random permutation of a given array or slice.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-30

+#tags: [ordering]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+signature: ["shuffle COLLECTION"]

+workson: []

+hugoversion:

+relatedfuncs: [seq]

+deprecated: false

+draft: false

+aliases: []

+---

+{{% code file="shuffle-input.html" %}}

+```html

+<!-- Shuffled sequence = -->

+<div>{{ shuffle (seq 1 5) }}</div>

+<!-- Shuffled slice =  -->

+<div>{{ shuffle (slice "foo" "bar" "buzz") }}</div>

+```

+{{% /code %}}

+This example would return the following:

+{{% output file="shuffle-output.html" %}}

+```html

+<!-- Shuffled sequence =  -->

+<div>2 5 3 1 4</div>

+<!-- Shuffled slice =  -->

+<div>buzz foo bar</div>

+```

+{{% /output %}}

+This example also makes use of the [slice](/functions/slice/) and [seq](/functions/seq/) functions.

--- /dev/null

+++ b/content/functions/singularize.md

@@ -1,0 +1,25 @@

+---

+title: singularize

+# linktitle: singularize

+description: Converts a word according to a set of common English singularization rules.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings,singular]

+signature: ["singularize INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+`{{ "cats" | singularize }}` → "cat"

+See also the `.Data.Singular` [taxonomy variable](/variables/taxonomy/) for singularizing taxonomy names.

--- /dev/null

+++ b/content/functions/slice.md

@@ -1,0 +1,34 @@

+---

+title: slice

+# linktitle: slice

+description: Creates a alice (array) of all passed arguments.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [slice, array, interface]

+signature: ["slice ITEM..."]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+toc: false

+---

+One use case is the concatenation of elements in combination with the [`delimit` function][]:

+{{% code file="slice.html" %}}

+```html

+{{ delimit (slice "foo" "bar" "buzz") ", " }}

+<!-- returns the string "foo, bar, buzz" -->

+```

+{{% /code %}}

+[`delimit` function]: /functions/delimit/

--- /dev/null

+++ b/content/functions/slicestr.md

@@ -1,0 +1,27 @@

+---

+title: slicestr

+# linktitle:

+description: Creates a slice of a half-open range, including start and end indices.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["slicestr STRING START [END]"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+For example, 1 and 4 creates a slice including elements 1 through 3.

+The `end` index can be omitted; it defaults to the string's length.

+* `{{slicestr "BatMan" 3}}` → "Man"

+* `{{slicestr "BatMan" 0 3}}` → "Bat"

--- /dev/null

+++ b/content/functions/sort.md

@@ -1,0 +1,65 @@

+---

+title: sort

+# linktitle: sort

+description: Sorts maps, arrays, and slices and returns a sorted slice.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [ordering,sorting,lists]

+signature: []

+workson: [lists,taxonomies,terms,groups]

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+A sorted array of map values will be returned with the keys eliminated. There are two optional arguments: `sortByField` and `sortAsc`. If left blank, sort will sort by keys (for maps) in ascending order as its default behavior.

+```toml

++++

+#tags: [ "tag3", "tag1", "tag2" ]

++++

+// Site config

++++

+[params.authors]

+  [params.authors.Derek]

+    "firstName"  = "Derek"

+    "lastName"   = "Perkins"

+  [params.authors.Joe]

+    "firstName"  = "Joe"

+    "lastName"   = "Bergevin"

+  [params.authors.Tanner]

+    "firstName"  = "Tanner"

+    "lastName"   = "Linsley"

++++

+```

+```

+// Use default sort options - sort by key / ascending

+Tags: {{ range sort .Params.tags }}{{ . }} {{ end }}

+→ Outputs Tags: tag1 tag2 tag3

+// Sort by value / descending

+Tags: {{ range sort .Params.tags "value" "desc" }}{{ . }} {{ end }}

+→ Outputs Tags: tag3 tag2 tag1

+// Use default sort options - sort by value / descending

+Authors: {{ range sort .Site.Params.authors }}{{ .firstName }} {{ end }}

+→ Outputs Authors: Derek Joe Tanner

+// Use default sort options - sort by value / descending

+Authors: {{ range sort .Site.Params.authors "lastName" "desc" }}{{ .lastName }} {{ end }}

+→ Outputs Authors: Perkins Linsley Bergevin

+```

--- /dev/null

+++ b/content/functions/split.md

@@ -1,0 +1,24 @@

+---

+title: split

+# linktitle: split

+description: splits a string into substrings separated by a delimiter

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["split STRING DELIM"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+* `{{split "tag1,tag2,tag3" "," }}` → ["tag1" "tag2" "tag3"]

--- /dev/null

+++ b/content/functions/string.md

@@ -1,0 +1,23 @@

+---

+title: string

+# linktitle: string

+description: Creates a string from the argument passed to the function

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["string INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+* `{{string "BatMan"}}` → "BatMan"

--- /dev/null

+++ b/content/functions/substr.md

@@ -1,0 +1,31 @@

+---

+title: substr

+# linktitle:

+description: Extracts parts of a string from a specified character's position and returns the specified number of characters.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+aliases: []

+signature: ["substr STRING START [LENGTH]"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+It normally takes two parameters: `start` and `length`. It can also take one parameter: `start`, i.e. `length` is omitted, in which case the substring starting from start until the end of the string will be returned.

+To extract characters from the end of the string, use a negative start number.

+In addition, borrowing from the extended behavior described at http://php.net substr, if `length` is given and is negative, that number of characters will be omitted from the end of string.

+```

+{{substr "BatMan" 0 -3}} → "Bat"

+{{substr "BatMan" 3 3}} → "Man"

+```

--- /dev/null

+++ b/content/functions/time.md

@@ -1,0 +1,50 @@

+---

+title: time

+linktitle:

+description: Converts a timestamp string into a `time.Time` structure.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [dates,time]

+signature: ["time INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+`time` converts a timestamp string into a [`time.Time`](https://godoc.org/time#Time) structure so you can access its fields:

+```

+{{ time "2016-05-28" }} → "2016-05-28T00:00:00Z"

+{{ (time "2016-05-28").YearDay }} → 149

+{{ mul 1000 (time "2016-05-28T10:30:00.00+10:00").Unix }} → 1464395400000, or Unix time in milliseconds

+```

+## Example: Using `time` to get Month Index

+The following example takes a UNIX timestamp---set as `utimestamp: "1489276800"` in a content's front matter---converts the timestamp (string) to an integer using the [`int` function][int], and then uses [`printf`][] to convert the `Month` property of `time` into an index.

+The following example may be useful when setting up [multilingual sites][multilingual]:

+{{% code file="unix-to-month-integer.html" %}}

+```html

+{{$time := time (int .Params.addDate)}}

+=> $time = 1489276800

+{{$time.Month}}

+=> "March"

+{{$monthindex := printf "%d" $time.Month }}

+=> $monthindex = 3

+```

+{{% /code %}}

+[int]: /functions/int/

+[multilingual]: /content-management/multilingual/

+[`printf`]: /functions/printf/

--- /dev/null

+++ b/content/functions/title.md

@@ -1,0 +1,25 @@

+---

+title: title

+# linktitle:

+description: Converts all characters in the provided string to title case.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions,fundamentals]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["title INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+---

+```

+{{title "BatMan"}}` → "Batman"

+```

--- /dev/null

+++ b/content/functions/trim.md

@@ -1,0 +1,42 @@

+---

+title: trim

+# linktitle:

+description: Returns a slice of a passed string with all leading and trailing characters from cutset removed.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["trim INPUT CUTSET"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+```

+{{ trim "++Batman--" "+-" }} → "Batman"

+```

+`trim` *requires* the second argument, which tells the function specifically what to remove from the first argument. There is no default value for the second argument, so **the following usage will not work**:

+```

+{{ trim .Inner}}

+```

+Instead, the following example tells `trim` to remove extra new lines from the content contained in the [shortcode `.Inner` variable][shortcodevars]:

+```

+{{ trim .Inner "\n" }}

+```

+{{% note %}}

+Go templates also provide a simple [method for trimming whitespace](/templates/introduction/#whitespace) from either side of a Go tag by including a hyphen (`-`).

+{{% /note %}}

+[shortcodevars]: /variables/shortcodes/

--- /dev/null

+++ b/content/functions/truncate.md

@@ -1,0 +1,29 @@

+---

+title: truncate

+# linktitle: truncate

+description: Truncates a text to a max length without cutting words or leaving unclosed HTML tags.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [strings]

+signature: ["truncate SIZE INPUT", "truncate SIZE ELLIPSIS INPUT"]

+workson: []

+hugoversion: 19

+relatedfuncs: []

+deprecated: false

+---

+Since Go templates are HTML-aware, `truncate` will intelligently handle normal strings vs HTML strings:

+```

+{{ "<em>Keep my HTML</em>" | safeHTML | truncate 10 }}` → <em>Keep my …</em>`

+```

+{{% note %}}

+If you have a raw string that contains HTML tags you want to remain treated as HTML, you will need to convert the string to HTML using the [`safeHTML` template function](/functions/safehtml) before sending the value to truncate. Otherwise, the HTML tags will be escaped when passed through the `truncate` function.

+{{% /note %}}

--- /dev/null

+++ b/content/functions/union.md

@@ -1,0 +1,49 @@

+---

+title: union

+# linktitle: union

+description: Given two arrays or slices, returns a new array that contains the elements or objects that belong to either or both arrays/slices.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-12

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [filtering,lists]

+signature: ["union SET1 SET2"]

+workson: []

+hugoversion: 0.20

+relatedfuncs: [intersect,where]

+deprecated: false

+aliases: []

+---

+Given two arrays (or slices) A and B, this function will return a new array that contains the elements or objects that belong to either A or to B or to both. The elements supported are strings, integers, and floats (only float64).

+```golang

+{{ union (slice 1 2 3) (slice 3 4 5) }}

+<!-- returns [1 2 3 4 5] -->

+{{ union (slice 1 2 3) nil }}

+<!-- returns [1 2 3] -->

+{{ union nil (slice 1 2 3) }}

+<!-- returns [1 2 3] -->

+{{ union nil nil }}

+<!-- returns an error because both arrays/slices have to be of the same type -->

+```

+This is also very useful to use as `OR` filters when combined with where:

+```html

+{{ $pages := where .Site.RegularPages "Type" "not in" (slice "page" "about") }}

+{{ $pages := $pages | union (where .Site.RegularPages "Params.pinned" true) }}

+{{ $pages := $pages | intersect (where .Site.RegularPages "Params.images" "!=" nil) }}

+```

+The above fetches regular pages not of `page` or `about` type unless they are pinned. And finally, we exclude all pages with no `images` set in Page params.

+See [intersect](/functions/intersect) for `AND`.

--- /dev/null

+++ b/content/functions/uniq.md

@@ -1,0 +1,31 @@

+---

+title: uniq

+linktitle: uniq

+description: Takes in a slice or array and returns a slice with subsequent duplicate elements removed.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [multilingual,i18n,urls]

+signature: ["uniq SET"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+aliases: []

+needsexamples: false

+---

+```html

+{{ uniq (slice 1 2 3 2) }}

+{{ slice 1 2 3 2 | uniq }}

+<!-- both return [1 2 3] -->

+```

--- /dev/null

+++ b/content/functions/unix.md

@@ -1,0 +1,40 @@

+---

+title: .Unix

+draft: false

+description: .Unix returns the local Time corresponding to the given Unix time, sec seconds and nsec nanoseconds since January 1, 1970 UTC.

+godocref: https://golang.org/search?q=Unix#Functions

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [dates,time]

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+signature: [".Unix"]

+workson: [times]

+hugoversion:

+relatedfuncs: [Format,dateFormat,now,time]

+deprecated: false

+aliases: []

+---

+## Example: Time Passed Since Last Modification

+This very simple one-liner uses `now.Unix` to calculate the amount of time that has passed between the `.LastMod` for the current page and the last build of the current page.

+{{% code file="time-passed.html" %}}

+```golang

+{{ div (sub now.Unix .Lastmod.Unix) 86400 }}

+```

+{{% /code %}}

+Since both values are integers, they can be subtracted and then divided by the number of seconds in a day (i.e., `60 * 60 * 24 == 86400`).

+{{% note %}}

+Hugo's output is *static*. For the example above to be realistic, the site needs to be built every day.

+ {{% /note %}}

+[partial template]: /templates/partials/

--- /dev/null

+++ b/content/functions/upper.md

@@ -1,0 +1,30 @@

+---

+title: upper

+# linktitle: upper

+description: Converts all characters in a string to uppercase

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: []

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+toc:

+signature: ["upper INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+draft: false

+aliases: []

+---

+Note that `upper` can be applied in your templates in more than one way:

+```

+{{ upper "BatMan" }} → "BATMAN"

+{{ "BatMan" | upper }} → "BATMAN"

+```

--- /dev/null

+++ b/content/functions/urlize.md

@@ -1,0 +1,79 @@

+---

+title: urlize

+# linktitle: urlize

+description: Takes a string, sanitizes it for usage in URLs, and converts spaces to hyphens.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [urls,strings]

+godocref:

+signature: ["urlize INPUT"]

+hugoversion:

+deprecated: false

+workson: []

+relatedfuncs: []

+---

+The following examples pull from a content file with the following front matter:

+{{% code file="content/blog/greatest-city.md" copy="false"%}}

+```toml

++++

+title = "The World's Greatest City"

+location = "Chicago IL"

+tags = ["pizza","beer","hot dogs"]

++++

+```

+{{% /code %}}

+The following might be used as a partial within a [single page template][singletemplate]:

+{{% code file="layouts/partials/content-header.html" download="content-header.html" %}}

+```html

+<header>

+    <h1>{{.Title}}</h1>

+    {{ with .Params.location }}

+        <div><a href="/locations/{{ . | urlize}}">{{.}}</a></div>

+    {{ end }}

+    <!-- Creates a list of tags for the content and links to each of their pages -->

+    {{ with .Params.tags }}

+    <ul>

+        {{range .}}

+            <li>

+                <a href="/tags/{{ . | urlize }}">{{ . }}</a>

+            </li>

+        {{end}}

+    </ul>

+    {{ end }}

+</header>

+```

+{{% /code %}}

+The preceding partial would then output to the rendered page as follows, assuming the page is being built with Hugo's default pretty URLs.

+{{% output file="/blog/greatest-city/index.html" %}}

+```html

+<header>

+    <h1>The World's Greatest City</h1>

+    <div><a href="/locations/chicago-il/">Chicago IL</a></div>

+    <ul>

+        <li>

+            <a href="/tags/pizza">pizza</a>

+        </li>

+        <li>

+            <a href="/tags/beer">beer</a>

+        </li>

+        <li>

+            <a href="/tags/hot-dogs">hot dogs</a>

+        </li>

+    </ul>

+</header>

+```

+{{% /output %}}

+[singletemplate]: /templates/single-page-templates/

--- /dev/null

+++ b/content/functions/where.md

@@ -1,0 +1,141 @@

+---

+title: where

+# linktitle: where

+description: Filters an array to only the elements containing a matching value for a given field.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [functions]

+menu:

+  docs:

+    parent: "functions"

+#tags: [filtering]

+signature: ["where COLLECTION KEY [OPERATOR] MATCH"]

+workson: [lists,taxonomies,terms,groups]

+hugoversion:

+relatedfuncs: [intersect,first,after,last]

+deprecated: false

+toc: true

+needsexample: true

+---

+`where` filters an array to only the elements containing a matching value for a given field.

+```html

+{{ range where .Data.Pages "Section" "post" }}

+  {{ .Content }}

+{{ end }}

+```

+It can be used by dot-chaining the second argument to refer to a nested element of a value.

+```toml

++++

+series: golang

++++

+```

+```html

+{{ range where .Site.Pages "Params.series" "golang" }}

+   {{ .Content }}

+{{ end }}

+```

+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 `=`.

+```html

+{{ range where .Data.Pages "Section" "!=" "post" }}

+   {{ .Content }}

+{{ end }}

+```

+The following logical operators are vailable with `where`:

+`=`, `==`, `eq`

+: `true` if a given field value equals a matching value

+`!=`, `<>`, `ne`

+: `true` if a given field value doesn't equal a matching value

+`>=`, `ge`

+: `true` if a given field value is greater than or equal to a matching value

+`>`, `gt`

+: `true` if a given field value is greater than a matching value

+`<=`, `le`

+: `true` if a given field value is lesser than or equal to a matching value

+`<`, `lt`

+: `true` if a given field value is lesser than a matching value

+`in`

+: `true` if a given field value is included in a matching value; a matching value must be an array or a slice

+`not in`

+: `true` if a given field value isn't included in a matching value; a matching value must be an array or a slice

+`intersect`

+: `true` if a given field value that is a slice/array of strings or integers contains elements in common with the matching value; it follows the same rules as the [`intersect` function][intersect].

+## Use `where` with `intersect`

+```html

+{{ range where .Site.Pages ".Params.tags" "intersect" .Params.tags }}

+  {{ if ne .Permalink $.Permalink }}

+    {{ .Render "summary" }}

+  {{ end }}

+{{ end }}

+```

+You can also put the returned value of the `where` clauses into a variable:

+{{% code file="where-intersect-variables.html" %}}

+```html

+{{ $v1 := where .Site.Pages "Params.a" "v1" }}

+{{ $v2 := where .Site.Pages "Params.b" "v2" }}

+{{ $filtered := $v1 | intersect $v2 }}

+{{ range $filtered }}

+{{ end }}

+```

+{{% /code %}}

+## Use `where` with `first`

+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" %}}

+```html

+{{ range first 5 (where .Data.Pages "Section" "post") }}

+   {{ .Content }}

+{{ end }}

+```

+{{% /code %}}

+## Nest `where` Clauses

+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:

+```html

+{{ range where (where .Data.Pages "Section" "blog" ) ".Params.featured" "!=" "true" }}

+```

+## Unset Fields

+Filtering only works for set fields. To check whether a field is set or exists, you can use the operand `nil`.

+This can be useful to filter a small amount of pages from a large pool. Instead of set field on all pages, you can set field on required pages only.

+Only the following operators are available for `nil`

+* `=`, `==`, `eq`: True if the given field is not set.

+* `!=`, `<>`, `ne`: True if the given field is set.

+```html

+{{ range where .Data.Pages ".Params.specialpost" "!=" nil }}

+   {{ .Content }}

+{{ end }}

+```

+[intersect]: /functions/intersect/

--- /dev/null

+++ b/content/functions/with.md

@@ -1,0 +1,33 @@

+---

+title: with

+# linktitle: with

+description: Rebinds the context (`.`) within its scope and skips the block if the variable is absent.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-12

+categories: [functions,fundamentals]

+menu:

+  docs:

+    parent: "functions"

+#tags: [conditionals]

+signature: ["with INPUT"]

+workson: []

+hugoversion:

+relatedfuncs: []

+deprecated: false

+---

+An alternative way of writing an `if` statement and then referencing the same value is to use `with` instead. `with` rebinds the context (`.`) within its scope and skips the block if the variable is absent or unset.

+The following example checks for a [user-defined site variable](/variables/site/) called `twitteruser`. If the key-value is not set, the following will render nothing:

+{{% code file="layouts/partials/twitter.html" %}}

+```html

+{{with .Site.Params.twitteruser}}<span class="twitter">

+<a href="https://twitter.com/{{.}}" rel="author">

+<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"

+ alt="Twitter"></a>

+</span>{{end}}

+```

+{{% /code %}}

--- /dev/null

+++ b/content/getting-started/_index.md

@@ -1,0 +1,23 @@

+---

+title: Getting Started

+linktitle: Getting Started Overview

+description: Quick start and guides for installing Hugo on your preferred operating system.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [getting started]

+#tags: [usage,docs]

+menu:

+  docs:

+    parent: "getting-started"

+    weight: 1

+weight: 0001	#rem

+draft: false

+aliases: [/overview/introduction/]

+toc: false

+---

+If this is your first time using Hugo and you've [already installed Hugo on your machine][installed], we recommend the [quick start][].

+[installed]: /getting-started/installing/

+[quick start]: /getting-started/quick-start/

--- /dev/null

+++ b/content/getting-started/configuration.md

@@ -1,0 +1,401 @@

+---

+title: Configuring Hugo

+linktitle: Configuration

+description: Often the default settings are good enough, but the config file can provide highly granular control over how your site is rendered.

+date: 2013-07-01

+publishdate: 2017-01-02

+lastmod: 2017-03-05

+categories: [getting started,fundamentals]

+#tags: [configuration,toml,yaml,json]

+menu:

+  docs:

+    parent: "getting-started"

+    weight: 60

+weight: 60

+sections_weight: 60

+draft: false

+aliases: [/overview/source-directory/,/overview/configuration/]

+toc: true

+---

+The [directory structure][] of a Hugo website&mdash;or more precisely, the source organization of files containing the website's content and templates&mdash;provides most of the configuration information that Hugo needs in order to generate a finished website.

+Because of Hugo's sensible defaults, many websites may not need a configuration file. Hugo is designed to recognize certain typical usage patterns.

+## Configuration Lookup Order

+Similar to the template [lookup order][], Hugo has a default set of rules for searching for a configuration file in the root of your website's source directory as a default behavior:

+1. `./config.toml`

+2. `./config.yaml`

+3. `./config.json`

+In your `config` file, you can direct Hugo as to how you want your website rendered, control your website's menus, and arbitrarily define site-wide parameters specific to your project.

+## YAML Configuration

+The following is a typical example of a YAML configuration file. Note the document opens with 3 hyphens and closes with 3 periods. The values nested under `params:` will populate the [`.Site.Params`][] variable for use in [templates][]:

+{{% code file="config.yml"%}}

+```yaml

+---

+baseURL: "https://yoursite.example.com/"

+title: "My Hugo Site"

+footnoteReturnLinkContents: "↩"

+permalinks:

+  post: /:year/:month/:title/

+params:

+  Subtitle: "Hugo is Absurdly Fast!"

+  AuthorName: "Jon Doe"

+  GitHubUser: "spf13"

+  ListOfFoo:

+    - "foo1"

+    - "foo2"

+  SidebarRecentLimit: 5

+...

+```

+{{% /code %}}

+### All Variables, YAML

+The following is the full list of Hugo-defined variables in an example YAML file. The values provided in this example represent the default values used by Hugo.

+{{% code file="config.yml" download="config.yml" %}}

+```yaml

+---

+archetypeDir:               "archetypes"

+# hostname (and path) to the root, e.g. http://spf13.com/

+baseURL:                    ""

+# include content marked as draft

+buildDrafts:                false

+# include content with publishdate in the future

+buildFuture:                false

+# include content already expired

+buildExpired:               false

+# enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs. See the "URL Management" page

+relativeURLs:               false

+canonifyURLs:               false

+# config file (default is path/config.yaml|json|toml)

+config:                     "config.toml"

+contentDir:                 "content"

+dataDir:                    "data"

+defaultExtension:           "html"

+defaultLayout:              "post"

+# Missing translations will default to this content language

+defaultContentLanguage:     "en"

+# Renders the default content language in subdir, e.g. /en/. The root directory / will redirect to /en/

+defaultContentLanguageInSubdir: false

+disableLiveReload:          false

+# Do not build RSS files

+disableRSS:                 false

+# Do not build Sitemap file

+disableSitemap:             false

+# Enable GitInfo feature

+enableGitInfo:              false

+# Build robots.txt file

+enableRobotsTXT:            false

+# Do not render 404 page

+disable404:                 false

+# Do not inject generator meta tag on homepage

+disableHugoGeneratorInject: false

+# Allows you to disable all page types and will render nothing related to 'kind';

+# values = "page", "home", "section", "taxonomy", "taxonomyTerm", "RSS", "sitemap", "robotsTXT", "404"

+disableKinds: []

+# Do not make the url/path to lowercase

+disablePathToLower:         false                   ""

+# Enable Emoji emoticons support for page content; see emoji-cheat-sheet.com

+enableEmoji:                false

+# Show a placeholder instead of the default value or an empty string if a translation is missing

+enableMissingTranslationPlaceholders: false

+footnoteAnchorPrefix:       ""

+footnoteReturnLinkContents: ""

+# google analytics tracking id

+googleAnalytics:            ""

+# if true, auto-detect Chinese/Japanese/Korean Languages in the content. (.Summary and .WordCount can work properly in CJKLanguage)

+hasCJKLanguage:             false

+languageCode:               ""

+layoutDir:                  "layouts"

+# Enable Logging

+log:                        false

+# Log File path (if set, logging enabled automatically)

+logFile:                    ""

+# "toml","yaml", or "json"

+metaDataFormat:             "toml"

+newContentEditor:           ""

+# Don't sync permission mode of files

+noChmod:                    false

+# Don't sync modification time of files

+noTimes:                    false

+# Pagination

+paginate:                   10

+paginatePath:               "page"

+# See "content-management/permalinks"

+permalinks:

+# Pluralize titles in lists using inflect

+pluralizeListTitles:        true

+# Preserve special characters in taxonomy names ("Gérard Depardieu" vs "Gerard Depardieu")

+preserveTaxonomyNames:      false

+# filesystem path to write files to

+publishDir:                 "public"

+# enables syntax guessing for code fences without specified language

+pygmentsCodeFencesGuessSyntax: false

+# color-codes for highlighting derived from this style

+pygmentsStyle:              "monokai"

+# true use pygments-css or false will color code directly

+pygmentsUseClasses:         false

+# maximum number of items in the RSS feed

+rssLimit:                   15

+# see "Section Menu for Lazy Bloggers", /templates/menu-templates for more info

+SectionPagesMenu:           ""

+# default sitemap configuration map

+sitemap:

+# filesystem path to read files relative from

+source:                     ""

+staticDir:                  "static"

+# display memory and timing of different steps of the program

+stepAnalysis:               false

+# theme to use (located by default in /themes/THEMENAME/)

+themesDir:                  "themes"

+theme:                      ""

+title:                      ""

+# if true, use /filename.html instead of /filename/

+uglyURLs:                   false

+# verbose output

+verbose:                    false

+# verbose logging

+verboseLog:                 false

+# watch filesystem for changes and recreate as needed

+watch:                      true

+taxonomies:

+  - category:               "categories"

+  - tag:                    "tags"

+---

+```

+{{% /code %}}

+## TOML Configuration

+The following is an example of a TOML configuration file. The values under `[params]` will populate the `.Site.Params` variable for use in [templates][]:

+```toml

+contentDir = "content"

+layoutDir = "layouts"

+publishDir = "public"

+buildDrafts = false

+baseURL = "https://yoursite.example.com/"

+canonifyURLs = true

+title = "My Hugo Site"

+[taxonomies]

+  category = "categories"

+  tag = "tags"

+[params]

+  subtitle = "Hugo is Absurdly Fast!"

+  author = "John Doe"

+```

+### All Variables, TOML

+The following is the full list of Hugo-defined variables in an example TOML file. The values provided in this example represent the default values used by Hugo.

+{{% code file="config.toml" download="config.toml"%}}

+```toml

++++

+archetypeDir =                "archetypes"

+# hostname (and path) to the root, e.g. http://spf13.com/

+baseURL =                     ""

+# include content marked as draft

+buildDrafts =                 false

+# include content with publishdate in the future

+buildFuture =                 false

+# include content already expired

+buildExpired =                false

+# enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs.

+relativeURLs =                false

+canonifyURLs =                false

+# config file (default is path/config.yaml|json|toml)

+config =                     "config.toml"

+contentDir =                  "content"

+dataDir =                     "data"

+defaultExtension =            "html"

+defaultLayout =               "post"

+# Missing translations will default to this content language

+defaultContentLanguage =      "en"

+# Renders the default content language in subdir, e.g. /en/. The root directory / will redirect to /en/

+defaultContentLanguageInSubdir =  false

+disableLiveReload =           false

+# Do not build RSS files

+disableRSS =                  false

+# Do not build Sitemap file

+disableSitemap =              false

+# Enable GitInfo feature

+enableGitInfo =               false

+# Build robots.txt file

+enableRobotsTXT =             false

+# Do not render 404 page

+disable404 =                  false

+# Do not inject generator meta tag on homepage

+disableHugoGeneratorInject =  false

+# Allows you to disable all page types and will render nothing related to 'kind';

+# values = "page", "home", "section", "taxonomy", "taxonomyTerm", "RSS", "sitemap", "robotsTXT", "404"

+disableKinds = []

+# Do not make the url/path to lowercase

+disablePathToLower =          false

+# Enable Emoji emoticons support for page content; see emoji-cheat-sheet.com

+enableEmoji =                 false

+# Show a placeholder instead of the default value or an empty string if a translation is missing

+enableMissingTranslationPlaceholders = false

+footnoteAnchorPrefix =        ""

+footnoteReturnLinkContents =  ""

+# google analytics tracking id

+googleAnalytics =             ""

+# if true, auto-detect Chinese/Japanese/Korean Languages in the content. (.Summary and .WordCount can work properly in CJKLanguage)

+hasCJKLanguage =              false

+languageCode =                ""

+layoutDir =                   "layouts"

+# Enable Logging

+log =                         false

+# Log File path (if set, logging enabled automatically)

+logFile =

+# maximum number of items in the RSS feed

+rssLimit =                    15

+# "toml","yaml", or "json"

+metaDataFormat =              "toml"

+newContentEditor =            ""

+# Don't sync permission mode of files

+noChmod =                     false

+# Don't sync modification time of files

+noTimes =                     false

+# Pagination

+paginate =                    10

+paginatePath =                "page"

+# See "content-management/permalinks"

+permalinks =

+# Pluralize titles in lists using inflect

+pluralizeListTitles =         true

+# Preserve special characters in taxonomy names ("Gérard Depardieu" vs "Gerard Depardieu")

+preserveTaxonomyNames =       false

+# filesystem path to write files to

+publishDir =                  "public"

+# enables syntax guessing for code fences without specified language

+pygmentsCodeFencesGuessSyntax = false

+# color-codes for highlighting derived from this style

+pygmentsStyle =               "monokai"

+# true: use pygments-css or false: color-codes directly

+pygmentsUseClasses =          false

+# see "Section Menu for Lazy Bloggers", /templates/menu-templates for more info

+SectionPagesMenu =

+# default sitemap configuration map

+sitemap =

+# filesystem path to read files relative from

+source =                      ""

+staticDir =                   "static"

+# display memory and timing of different steps of the program

+stepAnalysis =                false

+# theme to use (located by default in /themes/THEMENAME/)

+themesDir =                   "themes"

+theme =                       ""

+title =                       ""

+# if true, use /filename.html instead of /filename/

+uglyURLs =                    false

+# verbose output

+verbose =                     false

+# verbose logging

+verboseLog =                  false

+# watch filesystem for changes and recreate as needed

+watch =                       true

+[taxonomies]

+  category = "categories"

+  tag = "tags"

++++

+```

+{{% /code %}}

+{{% note %}}

+If you are developing your site on a \*nix machine, here is a handy shortcut for finding a configuration option from the command line:

+```bash

+~/sites/yourhugosite

+hugo config | grep emoji

+enableemoji: true

+```

+{{% /note %}}

+## Environmental Variables

+In addition to the 3 config options already mentioned, configuration key-values can be defined through operating system environment variables.

+For example, the following command will effectively set a website's title on Unix-like systems:

+```bash

+$ env HUGO_TITLE="Some Title" hugo

+```

+{{% note "Setting Environment Variables" %}}

+Names must be prefixed with `HUGO_` and the configuration key must be set in uppercase when setting operating system environment variables.

+{{% /note %}}

+## Ignore Files When Rendering

+The following statement inside `./config.toml` will cause Hugo to ignore files ending with `.foo` and `.boo` when rendering:

+```toml

+ignoreFiles = [ "\\.foo$", "\\.boo$" ]

+```

+The above is a list of regular expressions. Note that the backslash (`\`) character is escaped in this example to keep TOML happy.

+## Configure Blackfriday

+[Blackfriday](https://github.com/russross/blackfriday) is Hugo's built-in Markdown rendering engine.

+Hugo typically configures Blackfriday with sane default values that should fit most use cases reasonably well.

+However, if you have specific needs with respect to Markdown, Hugo exposes some of its Blackfriday behavior options for you to alter. The following table lists these Hugo options, paired with the corresponding flags from Blackfriday's source code ( [html.go](https://github.com/russross/blackfriday/blob/master/html.go) and [markdown.go](https://github.com/russross/blackfriday/blob/master/markdown.go)).

+{{< readfile file="/content/readfiles/bfconfig.md" markdown="true" >}}

+{{% note %}}

+1. Blackfriday flags are *case sensitive* as of Hugo v0.15.

+2. Blackfriday flags must be grouped under the `blackfriday` key and can be set on both the site level *and* the page level. Any setting on a page will override its respective site setting.

+{{% /note %}}

+{{% code file="bf-config.toml" %}}

+```toml

+[blackfriday]

+  angledQuotes = true

+  fractions = false

+  plainIDAnchors = true

+  extensions = ["hardLineBreak"]

+```

+{{% /code %}}

+{{% code file="bf-config.yml" %}}

+```yaml

+blackfriday:

+  angledQuotes: true

+  fractions: false

+  plainIDAnchors: true

+  extensions:

+    - hardLineBreak

+```

+{{% /code %}}

+## Configure Additional Output Formats

+Hugo v0.20 introduced the ability to render your content to multiple output formats (e.g., to JSON, AMP html, or CSV). See [Output Formats][] for information on how to add these values to your Hugo project's configuration file.

+## Configuration Format Specs

+* [TOML Spec][toml]

+* [YAML Spec][yaml]

+* [JSON Spec][json]

+[`.Site.Params`]: /variables/site/

+[directory structure]: /getting-started/directory-structure

+[json]: /documents/ecma-404-json-spec.pdf

+[lookup order]: /templates/lookup-order/

+[Output Formats]: /templates/output-formats/

+[templates]: /templates/

+[toml]: https://github.com/toml-lang/toml

+[yaml]: http://yaml.org/spec/

\ No newline at end of file

--- /dev/null

+++ b/content/getting-started/directory-structure.md

@@ -1,0 +1,82 @@

+---

+title: Directory Structure

+linktitle: Directory Structure

+description: Hugo's CLI scaffolds a project directory structure and then takes that single directory and uses it as the input to create a complete website.

+date: 2017-01-02

+publishdate: 2017-02-01

+lastmod: 2017-03-09

+categories: [getting started,fundamentals]

+#tags: [source, organization, directories]

+menu:

+  docs:

+    parent: "getting-started"

+    weight: 50

+weight: 50

+sections_weight: 50

+draft: false

+aliases: [/overview/source-directory/]

+toc: true

+---

+## New Site Scaffolding

+Running the `hugo new site` generator from the command line will create a directory structure with the following elements:

+```bash

+.

+├── archetypes

+├── config.toml

+├── content

+├── data

+├── layouts

+├── static

+└── themes

+```

+## Directory Structure Explained

+The following is a high-level overview of each of the directories with links to each of their respective sections with in the Hugo docs.

+[`archetypes`](/content-management/archetypes/)

+: You can create new content files in Hugo using the `hugo new` command.

+By default, hugo will create new content files with at least `date`, `title` (inferred from the file name), and `draft = true`. This saves time and promotes consistency for sites using multiple content types. You can create your own [archetypes][] with custom preconfigured front matter fields as well.

+[`config.toml`](/getting-started/configuration/)

+: Every Hugo project should have a configuration file in TOML, YAML, or JSON format at the root. Many sites may need little to no configuration, but Hugo ships with a large number of [configuration directives][] for more granular directions on how you want Hugo to build your website.

+[`content`][]

+: All content for your website will live inside this directory. Each top-level folder in Hugo is considered a [content section][]. For example, if your site has three main sections---`blog`, `articles`, and `tutorials`---you will have three directories at `content/blog`, `content/articles`, and `content/tutorials`. Hugo uses sections to assign default [content types][].

+[`data`](/templates/data-templates/)

+: This directory is used to store configuration files that can be

+used by Hugo when generating your website. You can write these files in YAML, JSON, or TOML format. In addition to the files you add to this folder, you can also create [data templates][] that pull from dynamic content.

+[`layouts`][]

+: Stores templates in the form of `.html` files that specify how views of your content will be rendered into a static website. Templates include [list pages][lists], your [homepage][], [taxonomy templates][], [partials][], [single page templates][singles], and more.

+`static`

+: stores all the static content for your future website: images, CSS, JavaScript, etc. When Hugo builds your site, all assets inside your static directory are copied over as-is. A good example of using the `static` folder is for [verifying site ownership on Google Search Console][searchconsole], where you want Hugo to copy over a complete HTML file without modifying its content.

+{{% note %}}

+Hugo does not currently ship with an asset pipeline ([#3207](https://github.com/gohugoio/hugo/issues/3207)). You can solicit support from the community in the [Hugo forums](https://discourse.gohugo.io) or check out a few of the [Hugo starter kits](/tools/starter-kits/) for examples of how Hugo developers are managing static assets.

+{{% /note %}}

+[archetypes]: /content-management/archetypes/

+[configuration directives]: /getting-started/configuration/#all-variables-yaml

+[`content`]: /content-management/organization/

+[content section]: /content-management/sections/

+[content types]: /content-management/types/

+[data templates]: /templates/data-templates/

+[homepage]: /templates/homepage/

+[`layouts`]: /templates/

+[lists]: /templates/list/

+[pagevars]: /variables/page/

+[partials]: /templates/partials/

+[searchconsole]: https://support.google.com/analytics/answer/1142414?hl=en

+[singles]: /templates/single-page-templates/

+[starters]: /tools/starter-kits/

+[taxonomies]: /content-management/taxonomies/

+[taxonomy templates]: /templates/taxonomy-templates/

+[types]: /content-management/types/

--- /dev/null

+++ b/content/getting-started/installing.md

@@ -1,0 +1,502 @@

+---

+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.

+date: 2016-11-01

+publishdate: 2016-11-01

+lastmod: 2017-02-20

+categories: [getting started,fundamentals]

+authors: ["Michael Henderson"]

+#tags: [install,pc,windows,linux,macos,binary,tarball]

+menu:

+  docs:

+    parent: "getting-started"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+aliases: [/tutorials/installing-on-windows/,/tutorials/installing-on-mac/,/overview/installing/,/getting-started/install,/install/]

+toc: true

+---

+{{% note %}}

+There is lots of talk about "Hugo being written in Go", but you don't need to install Go to enjoy Hugo. Just grab a precompiled binary!

+{{% /note %}}

+Hugo is written in [Go](https://golang.org/) with support for multiple platforms. The latest release can be found at [Hugo Releases][releases].

+Hugo currently provides pre-built binaries for the following:

+* <i class="icon-apple"></i> macOS (Darwin) for x64, i386, and ARM architectures

+* <i class="icon-windows"></i> Windows

+* <i class="icon-linux"></i> Linux

+* <i class="icon-freebsd"></i> 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.

+## Quick Install

+### Binary (Cross-platform)

+Download the appropriate version for your platform from [Hugo Releases][releases]. Once downloaded, the binary can be run from anywhere. You don't need to install it into a global location. This works well for shared hosts and other systems where you don't have a privileged account.

+Ideally, you should install it somewhere in your `PATH` for easy use. `/usr/local/bin` is the most probable location.

+### Homebrew (macOS)

+If you are on macOS and using [Homebrew][brew], you can install Hugo with the following one-liner:

+{{% code file="install-with-homebrew.sh" %}}

+```bash

+brew install hugo

+```

+{{% /code %}}

+For more detailed explanations, read the installation guides that follow for installing on macOS and Windows.

+### Chocolatey (Windows)

+If you are on a Windows machine and use [Chocolatey][] for package management, you can install Hugo with the following one-liner:

+{{% code file="install-with-chocolatey.ps1" %}}

+```powershell

+choco install hugo -confirm

+```

+{{% /code %}}

+### Source

+#### Prerequisite Tools

+* [Git][installgit]

+* [Go 1.5+][installgo]

+* [govendor][]

+#### Vendored Dependencies

+Hugo uses [govendor][] to vendor dependencies, but we don't commit the vendored packages themselves to the Hugo git repository. Therefore, a simple `go get` is *not* supported because the command is not vendor aware. *You must use `govendor` to fetch Hugo's dependencies.*

+#### Fetch from GitHub

+{{% code file="from-gh.sh" %}}

+```sh

+go get github.com/kardianos/govendor

+govendor get github.com/gohugoio/hugo

+go install github.com/gohugoio/hugo

+```

+{{% /code %}}

+`govendor get` will fetch Hugo and all its dependent libraries to `$GOPATH/src/github.com/gohugoio/hugo`, and `go install` compiles everything into a final `hugo` (or `hugo.exe`) executable inside `$GOPATH/bin/`.

+{{% note %}}

+If you are a Windows user, substitute the `$HOME` environment variable above with `%USERPROFILE%`.

+{{% /note %}}

+## <i class="icon-apple"></i>macOS

+### Assumptions

+1. You know how to open the macOS terminal.

+2. You're running a modern 64-bit Mac.

+3. You will use `~/Sites` as the starting point for your site. (`~/Sites` is used for example purposes. If you are familiar enough with the command line and file system, you should have no issues following along with the instructions.)

+### Pick Your Method

+There are three ways to install Hugo on your Mac

+1. The [Homebrew][brew] `brew` utility

+2. Distribution (i.e., tarball)

+3. Building from Source

+There is no "best" way to install Hugo on your Mac. You should use the method that works best for your use case.

+#### Pros and Cons

+There are pros and cons to each of the aforementioned methods:

+1. **Homebrew.** Homebrew is the simplest method and will require the least amount of work to maintain. The drawbacks aren't severe. The default package will be for the most recent release, so it will not have bug fixes until the next release (i.e., unless you install it with the `--HEAD` option). Hugo `brew` releases may lag a few days behind because it has to be coordinated with another team. Nevertheless, `brew` is the recommended installation method if you want to work from a stable, widely used source. Brew works well and is easy to update.

+2. **Tarball.** Downloading and installing from the tarball is also easy, although it requires a few more command line skills than does Homebrew. Updates are easy as well: you just repeat the process with the new binary. This gives you the flexibility to have multiple versions on your computer. If you don't want to use `brew`, then the tarball/binary is a good choice.

+3. **Building from Source.** Building from source is the most work. The advantage of building from source is that you don't have to wait for a release to add features or bug fixes. The disadvantage is that you need to spend more time managing the setup, which is manageable but requires more time than the preceding two options.

+{{% note %}}

+Since building from source is appealing to more seasoned command line users, this guide will focus more on installing Hugo via Homebrew and Tarball.

+{{% /note %}}

+### Install Hugo with Brew

+#### Step 1: Install `brew` if you haven't already

+Go to the `brew` website, <https://brew.sh/>, and follow the directions there. The most important step is the installation from the command line:

+{{% code file="install-brew.sh" %}}

+```bash

+ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

+```

+{{% /code %}}

+#### Step 2: Run the `brew` Command to Install `hugo`

+Installing Hugo using `brew` is as easy as the following:

+{{% code file="install-brew.sh" %}}

+```bash

+brew install hugo

+```

+{{% /code %}}

+If Homebrew is working properly, you should see something similar to the following:

+```sh

+==> Downloading https://homebrew.bintray.com/bottles/hugo-0.21.sierra.bottle.tar.gz

+######################################################################### 100.0%

+==> Pouring hugo-0.21.sierra.bottle.tar.gz

+🍺  /usr/local/Cellar/hugo/0.21: 32 files, 17.4MB

+```

+{{% note "Installing the Latest Hugo with Brew" %}}

+Replace `brew install hugo` with `brew install hugo --HEAD` if you want the absolute latest in-development version.

+{{% /note %}}

+`brew` should have updated your path to include Hugo. You can confirm by opening a new terminal window and running a few commands:

+```bash

+$ # show the location of the hugo executable

+which hugo

+/usr/local/bin/hugo

+# show the installed version

+ls -l $( which hugo )

+lrwxr-xr-x  1 mdhender admin  30 Mar 28 22:19 /usr/local/bin/hugo -> ../Cellar/hugo/0.13_1/bin/hugo

+# verify that hugo runs correctly

+hugo version

+Hugo Static Site Generator v0.13 BuildDate: 2015-03-09T21:34:47-05:00

+```

+### Install Hugo from Tarball

+#### Step 1: Decide on the location

+When installing from the tarball, you have to decide if you're going to install the binary in `/usr/local/bin` or in your home directory. There are three camps on this:

+1. Install it in `/usr/local/bin` so that all the users on your system have access to it. This is a good idea because it's a fairly standard place for executables. The downside is that you may need elevated privileges to put software into that location. Also, if there are multiple users on your system, they will all run the same version. Sometimes this can be an issue if you want to try out a new release.

+2. Install it in `~/bin` so that only you can execute it. This is a good idea because it's easy to do, easy to maintain, and doesn't require elevated privileges. The downside is that only you can run Hugo. If there are other users on your site, they have to maintain their own copies. That can lead to people running different versions. Of course, this does make it easier for you to experiment with different releases.

+3. Install it in your `Sites` directory. This is not a bad idea if you have only one site that you're building. It keeps every thing in a single place. If you want to try out new releases, you can make a copy of the entire site and update the Hugo executable.

+All three locations will work for you. In the interest of brevity, this guide focuses on option #2.

+#### Step 2: Download the Tarball

+1. Open <https://github.com/gohugoio/hugo/releases> in your browser.

+2. Find the current release by scrolling down and looking for the green tag that reads "Latest Release."

+3. Download the current tarball for the Mac. The name will be something like `hugo_X.Y_osx-64bit.tgz`, where `X.YY` is the release number.

+4. By default, the tarball will be saved to your `~/Downloads` directory. If you choose to use a different location, you'll need to change that in the following steps.

+#### Step 3: Confirm your download

+Verify that the tarball wasn't corrupted during the download:

+```bash

+tar tvf ~/Downloads/hugo_X.Y_osx-64bit.tgz

+-rwxrwxrwx  0 0      0           0 Feb 22 04:02 hugo_X.Y_osx-64bit/hugo_X.Y_osx-64bit.tgz

+-rwxrwxrwx  0 0      0           0 Feb 22 03:24 hugo_X.Y_osx-64bit/README.md

+-rwxrwxrwx  0 0      0           0 Jan 30 18:48 hugo_X.Y_osx-64bit/LICENSE.md

+```

+The `.md` files are documentation for Hugo. The other file is the executable.

+#### Step 4: Install Into Your `bin` Directory

+```bash

+# create the directory if needed

+mkdir -p ~/bin

+# make it the working directory

+cd ~/bin

+# extract the tarball

+tar -xvzf ~/Downloads/hugo_X.Y_osx-64bit.tgz

+Archive:  hugo_X.Y_osx-64bit.tgz

+  x ./

+  x ./hugo

+  x ./LICENSE.md

+  x ./README.md

+# verify that it runs

+./hugo version

+Hugo Static Site Generator v0.13 BuildDate: 2015-02-22T04:02:30-06:00

+```

+You may need to add your bin directory to your `PATH` variable. The `which` command will check for us. If it can find `hugo`, it will print the full path to it. Otherwise, it will not print anything.

+```bash

+# check if hugo is in the path

+which hugo

+/Users/USERNAME/bin/hugo

+```

+If `hugo` is not in your `PATH`, add it by updating your `~/.bash_profile` file. First, start up an editor:

+```bash

+nano ~/.bash_profile

+```

+Add a line to update your `PATH` variable:

+```bash

+export PATH=$PATH:$HOME/bin

+```

+Then save the file by pressing Control-X, then Y to save the file and return to the prompt.

+Close the terminal and open a new terminal to pick up the changes to your profile. Verify your success by running the `which hugo` command again.

+You've successfully installed Hugo.

+### Build from Source on Mac

+If you want to compile Hugo yourself, you'll need to install Go (aka Golang). You can [install Go directly from the Go website](https://golang.org/dl/) or via Homebrew using the following command:

+```bash

+brew install go

+```

+#### Step 1: Get the Source

+If you want to compile a specific version of Hugo, go to <https://github.com/gohugoio/hugo/releases> and download the source code for the version of your choice. If you want to compile Hugo with all the latest changes (which might include bugs), clone the Hugo repository:

+```bash

+git clone https://github.com/gohugoio/hugo

+```

+{{% warning "Sometimes \"Latest\" = \"Bugs\""%}}

+Cloning the Hugo repository directly means taking the good with the bad. By using the bleeding-edge version of Hugo, you make your development susceptible to the latest features, as well as the latest bugs. Your feedback is appreciated. If you find a bug in the latest release, [please create an issue on GitHub](https://github.com/gohugoio/hugo/issues/new).

+{{% /warning %}}

+#### Step 2: Compiling

+Make the directory containing the source your working directory and then fetch Hugo's dependencies:

+```bash

+mkdir -p src/github.com/gohugoio

+ln -sf $(pwd) src/github.com/gohugoio/hugo

+# set the build path for Go

+export GOPATH=$(pwd)

+go get

+```

+This will fetch the absolute latest version of the dependencies. If Hugo fails to build, it may be the result of a dependency's author introducing a breaking change.

+Once you have properly configured your directory, you can compile Hugo using the following command:

+```bash

+go build -o hugo main.go

+```

+Then place the `hugo` executable somewhere in your `$PATH`. You're now ready to start using Hugo.

+## <i class="icon-windows"></i>Windows

+The following aims to be a complete guide to installing Hugo on your Windows PC.

+### Assumptions

+1. You will use `C:\Hugo\Sites` as the starting point for your new project.

+2. You will use `C:\Hugo\bin` to store executable files.

+### Set up Your Directories

+You'll need a place to store the Hugo executable, your [content][], and the generated Hugo website:

+1. Open Windows Explorer.

+2. Create a new folder: `C:\Hugo`, assuming you want Hugo on your C drive, although this can go anywhere

+3. Create a subfolder in the Hugo folder: `C:\Hugo\bin`

+4. Create another subfolder in Hugo: `C:\Hugo\Sites`

+### Technical Users

+1. Download the latest zipped Hugo executable from [Hugo Releases][releases].

+2. Extract all contents to your `..\Hugo\bin` folder.

+3. The `hugo` executable will be named as `hugo_hugo-version_platform_arch.exe`. Rename the executable to `hugo.exe` for ease of use.

+4. In PowerShell or your preferred CLI, add the `hugo.exe` executable to your PATH by navigating to `C:\Hugo\bin` (or the location of your hugo.exe file) and use the command `set PATH=%PATH%;C:\Hugo\bin`. If the `hugo` command does not work after a reboot, you may have to run the command prompt as administrator.

+### Less-technical Users

+1. Go to the [Hugo Releases][releases] page.

+2. The latest release is announced on top. Scroll to the bottom of the release announcement to see the downloads. They're all ZIP files.

+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 (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.

+Now you need to add Hugo to your Windows PATH settings:

+#### For Windows 10 Users:

+* Right click on the **Start** button.

+* Click on **System**.

+* Click on **Advanced System Settings** on the left.

+* Click on the **Environment Variables...** button on the bottom.

+* In the User variables section, find the row that starts with PATH (PATH will be all caps).

+* Double-click on **PATH**.

+* Click the **New...** button.

+* Type in the folder where `hugo.exe` was extracted, which is `C:\Hugo\bin` if you went by the instructions above. *The PATH entry should be the folder where Hugo lives and not the binary.* Press <kbd>Enter</kbd> when you're done typing.

+* Click OK at every window to exit.

+{{% note "Path Editor in Windows 10"%}}

+The path editor in Windows 10 was added in the large [November 2015 Update](https://blogs.windows.com/windowsexperience/2015/11/12/first-major-update-for-windows-10-available-today/). You'll need to have that or a later update installed for the above steps to work. You can see what Windows 10 build you have by clicking on the <i class="fa fa-windows"></i>&nbsp;Start button → Settings → System → About. See [here](https://www.howtogeek.com/236195/how-to-find-out-which-build-and-version-of-windows-10-you-have/) for more.)

+{{% /note %}}

+#### For Windows 7 and 8.x users:

+Windows 7 and 8.1 do not include the easy path editor included in Windows 10, so non-technical users on those platforms are advised to install a free third-party path editor like [Windows Environment Variables Editor][Windows Environment Variables Editor] or [Path Editor](https://patheditor2.codeplex.com/).

+### Verify the Executable

+Run a few commands to verify that the executable is ready to run, and then build a sample site to get started.

+#### 1. Open a Command Prompt

+At the prompt, type `hugo help` and press the <kbd>Enter</kbd> key. You should see output that starts with:

+```powershell

+hugo is the main command, used to build your Hugo site.

+Hugo is a Fast and Flexible Static Site Generator

+built with love by spf13 and friends in Go.

+Complete documentation is available at https://gohugo.io/.

+```

+If you do, then the installation is complete. If you don't, double-check the path that you placed the `hugo.exe` file in and that you typed that path correctly when you added it to your `PATH` variable. If you're still not getting the output, search the [Hugo discussion forum][forum] to see if others have already figured out our problem. If not, add a note---in the "Support" category---and be sure to include your command and the output.

+At the prompt, change your directory to the `Sites` directory.

+```powershell

+C:\Program Files> cd C:\Hugo\Sites

+C:\Hugo\Sites>

+```

+#### 2. Run the Command

+Run the command to generate a new site. I'm using `example.com` as the name of the site.

+```powershell

+C:\Hugo\Sites> hugo new site example.com

+```

+You should now have a directory at `C:\Hugo\Sites\example.com`. Change into that directory and list the contents. You should get output similar to the following:

+```powershell

+C:\Hugo\Sites&gt;cd example.com

+C:\Hugo\Sites\example.com&gt;dir

+&nbsp;Directory of C:\hugo\sites\example.com

+&nbsp;

+04/13/2015  10:44 PM    <DIR>          .

+04/13/2015  10:44 PM    <DIR>          ..

+04/13/2015  10:44 PM    <DIR>          archetypes

+04/13/2015  10:44 PM                83 config.toml

+04/13/2015  10:44 PM    <DIR>          content

+04/13/2015  10:44 PM    <DIR>          data

+04/13/2015  10:44 PM    <DIR>          layouts

+04/13/2015  10:44 PM    <DIR>          static

+               1 File(s)             83 bytes

+               7 Dir(s)   6,273,331,200 bytes free

+```

+### Troubleshoot Windows Installation

+[@dhersam][] has created a nice video on common issues:

+{{< youtube c8fJIRNChmU >}}

+## <i class="icon-linux"></i>Linux

+### Debian and Ubuntu

+In any of the [Linux distributions that support snaps](https://snapcraft.io/docs/core/install):

+```sh

+sudo apt install hugo

+```

+#### Pros

+* Native Debian/Ubuntu package maintained by Debian Developers

+* Pre-installed bash completion script and `man` pages

+#### Cons

+* Might not be the latest version, especially if you are using an older, stable version (e.g., Ubuntu 16.04 LTS). Until backports and PPA are available, you may consider installing the Hugo snap package to get the latest version of Hugo, as described below.

+### Arch

+You can also install Hugo from the [Arch user repository](https://aur.archlinux.org/) on Arch Linux or derivatives such as Manjaro.

+Be aware that Hugo is built from source. This means that additional tools like [Git](https://git-scm.com) and [Go](https://golang.org/doc/install) will be installed as well.

+```bash

+sudo pacman -S yaourt

+yaourt -S hugo

+```

+### Fedora, CentOS, and Red Hat

+* <https://copr.fedorainfracloud.org/coprs/spf13/Hugo/> (updated to Hugo v0.16)

+* <https://copr.fedorainfracloud.org/coprs/daftaupe/hugo/> (updated to Hugo v0.22); usually released a few days after the official Hugo release.

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

+### Snap Package

+In any of the [Linux distributions that support snaps][snaps]:

+```bash

+snap install hugo

+```

+{{% note %}}

+Hugo-as-a-snap can write only inside the user’s `$HOME` directory---and gvfs-mounted directories owned by the user---because of Snaps’ confinement and security model. More information is also available [in this related GitHub issue](https://github.com/gohugoio/hugo/issues/3143).

+{{% /note %}}

+## Upgrade Hugo

+Upgrading Hugo is as easy as downloading and replacing the executable you’ve placed in your `PATH`.

+## Install Pygments (Optional)

+The Hugo executable has one *optional* external dependency for source code highlighting ([Pygments][pygments]).

+If you want to have source code highlighting using the [highlight shortcode][], you need to install the Python-based Pygments program. The procedure is outlined on the [Pygments homepage][pygments].

+## Next Steps

+Now that you've installed Hugo, read the [Quick Start guide][quickstart] and explore the rest of the documentation. If you have questions, ask the Hugo community directly by visiting the [Hugo Discussion Forum][forum].

+[brew]: https://brew.sh/

+[Chocolatey]: https://chocolatey.org/

+[content]: /content-management/

+[@dhersam]: https://github.com/dhersam

+[forum]: https://discourse.gohugo.io

+[govendor]: https://github.com/kardianos/govendor

+[highlight shortcode]: /content-management/shortcodes/#highlight

+[installgit]: http://git-scm.com/

+[installgo]: https://golang.org/dl/

+[Path Editor]: https://patheditor2.codeplex.com/

+[pygments]: https://pygments.org

+[quickstart]: /getting-started/quick-start/

+[redhatforum]: https://discourse.gohugo.io/t/solved-fedora-copr-repository-out-of-service/2491

+[releases]: https://github.com/gohugoio/hugo/releases

+[snaps]: http://snapcraft.io/docs/core/install

+[windowsarch]: https://esupport.trendmicro.com/en-us/home/pages/technical-support/1038680.aspx

+[Windows Environment Variables Editor]: http://eveditor.com/

--- /dev/null

+++ b/content/getting-started/quick-start.md

@@ -1,0 +1,574 @@

+---

+title: Quick Start

+linktitle: Quick Start

+description: Build an online bookshelf that taps into Hugo's CLI, directory structure, configuration, and theming.

+date: 2013-07-01

+publishdate: 2013-07-01

+lastmod: 2017-06-22

+categories: [getting started]

+#tags: [quick start,usage]

+authors: [Shekhar Gulati, Ryan Watters]

+menu:

+  docs:

+    parent: "getting-started"

+    weight: 10

+weight: 10

+sections_weight: 10

+draft: false

+aliases: [/overview/quickstart/]

+toc: true

+wip: true

+---

+{{% note %}}

+This Quick Start was originally written by [Shekhar Gulati](https://twitter.com/shekhargulati) in his [52 Technologies in 2016](https://github.com/shekhargulati/52-technologies-in-2016) blog series but has been heavily modified to represent additional features and other changes to Hugo.

+{{% /note %}}

+In this Quick Start, we will build an online bookshelf that lists books and their reviews.

+## Step 1. Install Hugo

+[Install Hugo][install]. If installing from [Hugo releases][releases], you'll need to save the main executable as `hugo` (or `hugo.exe` on Windows) somewhere in your `PATH`. You will need the `hugo` command in the following steps.

+{{% note "Windows Users and Git Bash" %}}

+If you're on Windows, this Quick Start will assume you're using [Git Bash](https://git-for-windows.github.io/) (aka Git for Windows).

+{{% /note %}}

+Once `hugo` is installed, make sure to run the `help` command to verify `hugo` installation. The following is an abridged version of what will write to the console when entering the command:

+```bash

+hugo help

+hugo is the main command, used to build your Hugo site.

+Hugo is a Fast and Flexible Static Site Generator

+built with love by spf13 and friends in Go.

+Complete documentation is available at http://gohugo.io/.

+```

+You can check the version of Hugo you're currently using with the `hugo version` command:

+```bash

+hugo version

+```

+```bash

+Hugo Static Site Generator v0.18.1 BuildDate: 2016-12-30T05:02:43-05:00

+```

+## Step 2. Scaffold Your Hugo Bookshelf Website

+Hugo's CLI has commands that allow you to quickly scaffold a new website. Navigate to your preferred location on your file system and create a new Hugo site `bookshelf` by executing the `hugo new` command:

+```bash

+hugo new site bookshelf

+```

+Change into the newly created `bookshelf` directory. Listing the new directory's content will show the following:

+```bash

+.

+├── archetypes

+├── config.toml

+├── content

+├── data

+├── layouts

+├── static

+└── themes

+6 directories, 1 file

+```

+You'll see the `bookshelf` directory has 6 subdirectories and 1 file. Let's look at each of them quickly. (See [Directory Structure][hugodirectories].)

+* `archetypes`: [Archetypes][archetypes] allow you to preconfigure [front matter][fm] for content files for easier scaffolding of content from the command line using `hugo new`.

+* `config.toml`: Hugo uses `.toml` as its default configuration format but also accepts `.yml` and `.json`. The configuration settings mentioned in the `config.toml` are applied to the full website an include important global variables such as the `baseURL` and `title` of your website. (See [Configuration][configuration].)

+* `content`: This single directory houses all of the content for your website. Each subdirectory in content is considered a [section][]. If your website has sections for posts, events, and tutorials, you would create `content/posts`, `content/events`, and `content/tutorials`.

+* `data`: This directory is used to store files of serialized data (YAML, TOML, or JSON) that can be used in [data templates][datatemplates] and your [website's menu][sitemenu].

+* `layouts`: This is the hub for all your [templating][templating], including [list and section templates](/templates/lists/) and [shortcodes](/templates/shortcode-templates/).

+* `static`: This houses all your static content; i.e., images, JavaScript, and CSS. Everything in `/static` is copied over *as is* to your finished website.

+* `themes`: This is where you will download themes for Hugo. You can see a showcase of all themes at <http://themes.gohugo.io>.

+## Step 3. Add Content

+Let's now add a post to our "bookshelf." We will use the `hugo new` command to add a post. This first post will be on the book [*Good To Great*][bookurl]. Make sure you are inside the `bookshelf` directory.

+{{% code file="create-new-book-review-post.sh" %}}

+```bash

+hugo new post/good-to-great.md

+```

+{{% /code %}}

+You should then see the following output:

+```bash

+/Users/yourusername/bookshelf/content/post/good-to-great.md created

+```

+The above command will create a new directory `post` inside the `content` directory and create `content/post/good-to-great.md`. The directory for your Hugo project will now look like the following:

+```bash

+.

+├── archetypes

+├── config.toml

+├── content

+│   └── post

+│       └── good-to-great.md

+├── data

+├── layouts

+├── static

+└── themes

+```

+Open `good-to-great.md` in your preferred text editor:

+```toml

++++

+date = "2017-02-19T21:09:05-06:00"

+title = "good to great"

+draft = true

++++

+```

+The text bracketed by `+++` is the TOML [front matter][fm] for the content. Front matter enables you to define embedded metadata that travels with the content file. Since we have not configured any [archetypes][archetypes] for our project, Hugo has used its built-in base archetype, which includes the following three values in the front matter:

+* `date` specifies the date and time at which post was created from the command line

+* `title` specifies the title for the post, which Hugo will infer from the file name

+* `draft`, when set to `true`, tells Hugo the content is not yet ready to be published

+Let's update `good-to-great.md` with a short review of *Good to Great*:

+{{% code file="good-to-great-start.md" %}}

+```markdown

++++

+date = "2016-02-14T16:11:58+05:30"

+draft = true

+title = "Good to Great Book Review"

++++

+I read **Good to Great in January 2016**. An awesome read sharing detailed analysis on how good companies became great. Although this book is about how companies became great but we could apply a lot of the learnings on ourselves. Concepts like level 5 leader, hedgehog concept, the stockdale paradox are equally applicable to individuals.

+```

+{{% /code %}}

+## Step 4. Serve Content

+Hugo has a built-in server that can serve your website locally for easy previewing and development. To serve content, execute the following command inside the `bookshelf` directory:

+```bash

+hugo server

+```

+You should see something similar to the following output:

+```bash

+Built site for language en:

+0 of 1 draft rendered

+0 future content

+0 expired content

+0 regular pages created

+1 other pages created

+0 non-page files copied

+0 paginator pages created

+0 tags created

+0 categories created

+total in 1 ms

+Watching for changes in /Users/yourusername/bookshelf/{data,content,layouts,static}

+Serving pages from memory

+Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

+Press Ctrl+C to stop

+```

+This will start the server on port `1313`. You can view your blog at <http://localhost:1313/>. However, when you go to the link, you will see nothing. This is for a couple reasons:

+1. As you can see in the `hugo server` command output, Hugo did *not* render the draft. Hugo will only render drafts if you pass the `buildDrafts` flag to the `hugo server` command.

+2. We have not specified how Markdown content should be rendered. We need to create our own layouts via templates or specify a theme, the latter of which we will do in the next step.

+Kill the server using <kbd>Ctrl</kbd> + <kbd>C</kbd> and then rerun the server with the `--buildDrafts` flag appended to the command:

+```bash

+hugo server --buildDrafts

+```

+You should now see something similar to the following:

+```bash

+Built site for language en:

+1 of 1 draft rendered

+0 future content

+0 expired content

+1 regular pages created

+2 other pages created

+0 non-page files copied

+0 paginator pages created

+0 tags created

+0 categories created

+total in 2 ms

+Watching for changes in /Users/yourusername/bookshelf/{data,content,layouts,static}

+Serving pages from memory

+Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

+Press Ctrl+C to stop

+```

+Okay, so we now have our single page "built," but we're not seeing anything in the browser  at <http://localhost:1313>. This was only to demonstrate the utility of the `--buildDrafts` flag.

+While we are getting closer, we still need to specific a theme for Hugo to use when building our site.

+## Step 5. Add A Theme

+[Themes][themessection] provide Hugo with layout and templates to render your website. You can see the full selection of open-source themes at <http://themes.gohugo.io>.

+{{% note "No Default Hugo Theme" %}}

+Hugo currently doesn’t ship with a default theme, thus allowing end users to pick whichever theme best suits their projects.

+{{% /note %}}

+Themes should be added in the `themes` directory, one of the directories scaffolded with the `hugo new site` command we used to start our Hugo project. To install our themes, first change into the `themes` directory:

+```bash

+cd themes

+```

+You can clone one or more themes from within the `themes` directory. We will use the [Robust theme][robusttheme] but at the most recent commit as of this Quick Start's last update.

+Once inside the `themes` directory, you can use the following one-liner to clone Robust, check out the specific commit, and then return to your project's root directory:

+{{% code file="clone-robust-theme" %}}

+```bash

+git clone https://github.com/dim0627/hugo_theme_robust.git && cd hugo_theme_robust && git checkout 3baae29 && cd ../..

+```

+{{% /code %}}

+Now let's start Hugo's server again but with the addition of the `-theme` flag for Robust:

+{{% code file="hugo-server-with-theme.sh" %}}

+```bash

+hugo server --theme=hugo_theme_robust --buildDrafts

+```

+{{% /code %}}

+You should see an output to the console similar to the following:

+```bash

+Built site for language en:

+1 of 1 draft rendered

+0 future content

+0 expired content

+1 regular pages created

+2 other pages created

+0 non-page files copied

+2 paginator pages created

+0 tags created

+0 categories created

+total in 8 ms

+Watching for changes in /Users/yourusername/bookshelf/{data,content,layouts,static,themes}

+Serving pages from memory

+Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

+Press Ctrl+C to stop

+```

+If Hugo doesn't find the specified theme in the `themes` directory,

+it will throw an exception:

+```bash

+FATAL: 2016/02/14 Unable to find theme Directory: /Users/yourusername/bookshelf/themes/robust

+```

+To view your website, you can go to <http://localhost:1313/>. You should see something similar to the following image:

+![](/images/quickstart/bookshelf-robust-theme.png)

+Similar to the way we looked at the scaffolding for our new Hugo website, let's take a look at what comprises a typical Hugo theme. The following is only a selection of what you would see if you were to list out the contents of the Robust theme directory. These are also some of the default files created by Hugo as of v0.23. (See [Creating a Theme][createtheme])

+```bash

+.

+├── LICENSE.md

+├── archetypes

+│   └── default.md

+├── layouts

+│   ├── 404.html

+│   ├── _default

+│   │   ├── list.html

+│   │   └── single.html

+│   ├── index.html

+│   └── partials

+│       ├── footer.html

+│       └── header.html

+├── static

+│   ├── css

+│   └── js

+└── theme.toml

+```

+* `theme.toml` is the theme configuration file that provides information about the theme; e.g., theme name, theme description, theme author, theme license, and minimum Hugo version, which will default to your locally installed version of Hugo.

+* `layouts` contains different views (i.e., [templates][templating]) for different content types. In this quick start, we see that each content type has a `single.html` and `list.html`. `single.html` is used for rendering a single piece of content. `list.html` is used to view a list of content items. For example, you will use `list.html` to view `*.md` in the posts [section][listsectiontemplates]. Think of `list.html` as `example.com/posts` and `single.html` as `example.com/posts/my-single-post/`.

+* `static` has the same purpose as that of the `static` in our original scaffolding. This directory stores all the static assets used by the theme and is copied over *as is* at build time.

+## Step 6. Use Multiple Themes

+You can very easily switch between different themes in Hugo. Let's suppose we want to try out the [`bleak` theme][bleaktheme]. Kill the Hugo server if you are still running it from the command line.

+From your project root, you can use this one-liner to change into `themes`, clone Bleak, and go back to your project's root directory:

+{{% code file="clone-bleak-theme.sh" %}}

+```bash

+cd themes && git clone https://github.com/Zenithar/hugo-theme-bleak.git && cd ..

+```

+{{% /code %}}

+Now restart the server with our new theme flag:

+{{% code file="run-server-with-bleak.sh" %}}

+```bash

+hugo server --theme=hugo-theme-bleak --buildDrafts

+```

+{{% /code %}}

+Our website is now using the `bleak` theme at <http://localhost:1313>, which should look similar to the following screenshot:

+![Screenshot of the Quick Start website's homepage running with the Bleak Hugo theme.](/images/quickstart/bookshelf-bleak-theme.png)

+## Step 7. Update Your Configuration

+Kill the Hugo server if you are still running it with the Bleak theme, and then restart the server with the `robust` theme. We will use Robust for the duration of this Quick Start:

+{{% code file="restart-with-robust-sh" %}}

+```bash

+hugo server --theme=hugo_theme_robust --buildDrafts

+```

+{{% /code %}}

+### Update Our `config.toml`

+Our website is currently using the dummy values specified in `bookshelf/config.toml`, which were auto-generated with `hugo new site bookshelf`. Let's update the configuration:

+{{% code file="updated-config.toml" %}}

+```toml

+baseURL = "http://example.org/"

+languageCode = "en-us"

+title = "Shekhar Gulati Book Reviews"

+[Params]

+  Author = "Shekhar Gulati"

+```

+{{% /code %}}

+### Watch Your Site Reload Instantly

+Hugo has built-in support for LiveReload. This means that Hugo will rebuild and reload your site every time you save a change to content, templates, static assets, and even your configuration. You should see something similar to the following screenshot at <http://localhost:1313> once you save the above changes to your `config.toml`:

+![](/images/quickstart/bookshelf-updated-config.png)

+The change is also reflected in the console. As soon as you changed the configuration file, Hugo applied those changes to the affected pages and rebuilt the site:

+```

+Config file changed: /Users/yourusername/bookshelf/config.toml

+Started building sites ...

+Built site for language en:

+1 of 1 draft rendered

+0 future content

+0 expired content

+1 regular pages created

+2 other pages created

+0 non-page files copied

+2 paginator pages created

+0 tags created

+0 categories created

+total in 20 ms

+```

+## Step 8. Customize the Robust Theme

+The `robust` theme is a good start towards our online bookshelf, but we want to customize it a bit to meet our desired look and feel. Hugo makes it very easy to [customize existing themes or create your own][themes] themes as well. For the purpose of the Quick Start, we will focus on customization.

+The first change that we have to make is to use a different default image instead of the one used in the theme. The theme's default image used in both the `list.html` and `single.html` views resides inside `themes/hugo_theme_robust/static/images/default.jpg`. We can easily override it by creating a simple directory structure inside our repository's `static` directory.

+Create an images directory inside of `bookshelf/static` and copy an image with name `default.jpg` inside of it. We will use the default image shown below.

+![](/images/quickstart/default.jpg)

+Hugo will sync the changes and reload the website to use the new image:

+![](/images/quickstart/bookshelf-new-default-image.png)

+Now we need to change the layout of the index page so that only images are shown instead of the text. The file at `themes/hugo_theme_robust/layouts/index.html` refers to a partial `li.html` template that renders the following list view:

+```html

+<article class="li">

+  <a href="{{ .Permalink }}" class="clearfix">

+    <div class="image" style="background-image: url({{ $.Site.BaseURL }}images/{{ with .Params.image }}{{ . }}{{ else }}default.jpg{{ end }});"></div>

+    <div class="detail">

+      <time>{{ with .Site.Params.DateForm }}{{ $.Date.Format . }}{{ else }}{{ $.Date.Format "Mon, Jan 2, 2006" }}{{ end }}</time>

+      <h2 class="title">{{ .Title }}</h2>

+      <div class="summary">{{ .Summary }}</div>

+    </div>

+  </a>

+</article>

+```

+Create a new file for `li.html` inside the `bookshelf/layouts/_default` directory. If you are in your project root, you can use the following one-liner to both create the file and return to the project root:

+{{% code file="create-new-li-html.sh" %}}

+```bash

+cd layouts && mkdir _default && cd _default && touch li.html && cd ../..

+```

+{{% /code %}}

+Copy the content shown below into the new `li.html`. When contrasting this with the `li.html` that ships with the Robust theme, you'll notice we have removed details of the book so that only the image is shown:

+{{% code file="layouts/_default/li.html" %}}

+```html

+<article class="li">

+  <a href="{{ .Permalink }}" class="clearfix">

+    <div class="image" style="background-image: url({{ $.Site.BaseURL }}images/{{ with .Params.image }}{{ . }}{{ else }}default.jpg{{ end }});"></div>

+  </a>

+</article>

+```

+{{% /code %}}

+Now, the website should render similar to the following screenshot:

+![](/images/quickstart/bookshelf-only-picture.png)

+Next, we want to remove information related to the theme from the footer. Let's create a new directory at `bookshelf/layouts/partials`. This will hold our new file called `default_foot.html`.

+This is a new [partial template][partials]. If you are still in the project's root directory, you can use the following one-liner to create the partial before returning to the project root:

+{{% code file="create-new-default-foot.sh" %}}

+```bash

+cd layouts && mkdir partials && cd partials && touch default_foot.html && cd ../..

+```

+{{% /code %}}

+Now add the following to our new `default_foot.html` partial template:

+{{% code file="layouts/partials/default_foot.html" %}}

+```html

+<footer class="site">

+  <p>{{ with .Site.Copyright | safeHTML }}{{ . }}{{ else }}&copy; {{ $.Site.LastChange.Year }} {{ if isset $.Site.Params "Author" }}{{ $.Site.Params.Author }}{{ else }}{{ .Site.Title }}{{ end }}{{ end }}</p>

+  <p>Powered by <a href="http://gohugo.io" target="_blank">Hugo</a>,</p>

+</footer>

+```

+{{% /code %}}

+So far we are using the default image, but we would like to use the book image so that we can relate to the book. Every book review will define a configuration setting in its front matter. Update the content and front matter of `good-to-great.md` as shown below.

+{{% code file="content/post/good-to-great.md" %}}

+```markdown

++++

+date = "2017-02-19T21:09:05-06:00"

+draft = true

+title = "Good to Great Book Review"

+image = "good-to-great.jpg"

++++

+I read **Good to Great in January 2016**. An awesome read sharing detailed analysis on how good companies became great. Although this book is about how companies became great but we could apply a lot of the learnings on ourselves. Concepts like level 5 leader, hedgehog concept, the stockdale paradox are equally applicable to individuals.

+```

+{{% /code %}}

+Grab a (legal) image from somewhere, name it `good-to-great.jpg`, and place it in the `bookshelf/static/images` directory.

+After adding a few more books to our shelf, the shelf appears as shown below.

+![](/images/quickstart/bookshelf.png)

+## Step 9. Make Your Posts Public

+So far, all the posts that we have written are in draft status (i.e., `draft = true`). To make a draft public, you can run a Hugo CLI command or manually change the draft status in the post's front matter to `false`. Hugo provides a handy command line argument called `undraft` to do this for us:

+```bash

+hugo undraft content/post/good-to-great.md

+```

+If we check the front matter of `good-to-great.md` after running this command, we'll notice that Hugo has written the change of draft status to the file:

+```toml

++++

+date = "2017-02-19T22:42:53-06:00"

+draft = false

+title = "Good to Great Book Review"

+image = "good-to-great.jpg"

++++

+```

+Now, we can start the server *without* the `buildDrafts` option.

+```bash

+hugo server --theme=hugo_theme_robust

+```

+<!-- ## Step 10. Integrate Disqus Comments

+{{% note "Adding Disqus to Your Website" %}}

+To implement Disqus comments as part of the Quick Start, you'll need to set up a Disqus account. Follow the [Disqus documentation for adding their service to websites](https://help.disqus.com/customer/portal/articles/1257441-adding-disqus-to-your-site).

+{{% /note %}}

+To enable Disqus on our new site, we only need to update the `disqusShortname` in the config.toml as shown below.

+```toml

+[Params]

+  Author = "Shekhar Gulati"

+  disqusShortname = <your disqus shortname>

+```

+Now, commenting will be enabled in your blog.

+![](/images/quickstart/bookshelf-disqus.png)

+ -->

+## Step 10. Build Your Website

+To generate a website that can be deployed to GitHub pages, we first need to change the `baseURL` in our configuration as follows:

+```toml

+baseURL = "https://<yourgithubusername>.github.io/bookshelf/"

+```

+Then type the following command while in the root directory of your Hugo project:

+```bash

+hugo --theme=hugo_theme_robust

+0 draft content

+0 future content

+5 pages created

+2 paginator pages created

+0 tags created

+0 categories created

+in 17 ms

+```

+After you run the `hugo` command, a `bookshelf/public` directory will be created containing the generated website source.

+## Step 11. What Next?

+**Congratulations!** Your new `bookshelf`/public directory is a fully generated, deployable Hugo website. Since all your files are *static*, you have innumerable options for hosting, and your new directory structure and simple content format are going to make scaling your website a breeze.

+Here's what you should look into next:

+1. [See hosting and deployment options][hostinganddeploy] for sharing your newly created Hugo website with the world.

+2. [Learn more about Hugo's powerful templating][templating] to tailor your new Hugo website to your specific needs and keep it scaling accordingly.

+3. [Visit the Hugo Discussion Forum][forum] to ask questions, answer questions, and become an active member of the Hugo community.

+[archetypes]: /content-management/archetypes/

+[bookurl]: https://www.amazon.com/Good-Great-Some-Companies-Others/dp/0066620996/

+[bleaktheme]: http://themes.gohugo.io/bleak/

+[configuration]: /getting-started/configuration/

+[createtheme]: /themes/creating/

+[datatemplates]: /templates/data-templates/

+[forum]: https://discourse.gohugo.io

+[fm]: /content-management/front-matter/

+[hostinganddeploy]: /hosting-and-deployment/

+[hugodirectories]: /getting-started/directory-structure/

+[install]: /getting-started/installing/

+[lists]: /templating/lists/

+[partials]: /templates/partials/

+[quickinstall]: /getting-started/installing/#quick-install

+[releases]: https://github.com/gohugoio/hugo/releases

+[robusttheme]: https://github.com/dim0627/hugo_theme_robust

+[section]: /content-management/sections/

+[sectiontemplates]: /templates/section-templates/

+[shortcodetemplates]: /templates/shortcode-templates/

+[sitemenu]: /content-management/menus/

+[templating]: /templates/introduction/

+[themessection]: /themes/

+[themes]: /themes/

--- /dev/null

+++ b/content/getting-started/usage.md

@@ -1,0 +1,228 @@

+---

+title: Basic Usage

+linktitle: Basic Usage

+description: Hugo's CLI is fully featured but simple to use, even for those who have very limited experience working from the command line.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [getting started]

+#tags: [usage,livereload,command line,flags]

+menu:

+  docs:

+    parent: "getting-started"

+    weight: 40

+weight: 40

+sections_weight: 40

+draft: false

+aliases: [/overview/usage/,/extras/livereload/,/doc/usage/,/usage/]

+toc: true

+---

+The following is a description of the most command commands you will use while developing your Hugo project. See the [Command Line Reference][commands] for a comprehensive view of Hugo's CLI.

+## Test Installation

+Once you have [installed Hugo][install], make sure it is in your `PATH`. You can test that Hugo has been installed correctly via the `help` command:

+```bash

+hugo help

+```

+The output you see in your console should be similar to the following:

+```bash

+hugo is the main command, used to build your Hugo site.

+Hugo is a Fast and Flexible Static Site Generator

+built with love by spf13 and friends in Go.

+Complete documentation is available at http://gohugo.io/.

+Usage:

+  hugo [flags]

+  hugo [command]

+Available Commands:

+  benchmark   Benchmark Hugo by building a site a number of times.

+  check       Contains some verification checks

+  config      Print the site configuration

+  convert     Convert your content to different formats

+  env         Print Hugo version and environment info

+  gen         A collection of several useful generators.

+  help        Help about any command

+  import      Import your site from others.

+  list        Listing out various types of content

+  new         Create new content for your site

+  server      A high performance webserver

+  undraft     Undraft changes the content's draft status from 'True' to 'False'

+  version     Print the version number of Hugo

+Flags:

+  -b, --baseURL string             hostname (and path) to the root, e.g. http://spf13.com/

+  -D, --buildDrafts                include content marked as draft

+  -E, --buildExpired               include expired content

+  -F, --buildFuture                include content with publishdate in the future

+      --cacheDir string            filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache/

+      --canonifyURLs               if true, all relative URLs will be canonicalized using baseURL

+      --cleanDestinationDir        remove files from destination not found in static directories

+      --config string              config file (default is path/config.yaml|json|toml)

+  -c, --contentDir string          filesystem path to content directory

+  -d, --destination string         filesystem path to write files to

+      --disable404                 do not render 404 page

+      --disableKinds stringSlice   disable different kind of pages (home, RSS etc.)

+      --disableRSS                 do not build RSS files

+      --disableSitemap             do not build Sitemap file

+      --enableGitInfo              add Git revision, date and author info to the pages

+      --forceSyncStatic            copy all files when static is changed.

+  -h, --help                       help for hugo

+      --i18n-warnings              print missing translations

+      --ignoreCache                ignores the cache directory

+  -l, --layoutDir string           filesystem path to layout directory

+      --log                        enable Logging

+      --logFile string             log File path (if set, logging enabled automatically)

+      --noChmod                    don't sync permission mode of files

+      --noTimes                    don't sync modification time of files

+      --pluralizeListTitles        pluralize titles in lists using inflect (default true)

+      --preserveTaxonomyNames      preserve taxonomy names as written ("Gérard Depardieu" vs "gerard-depardieu")

+      --quiet                      build in quiet mode

+      --renderToMemory             render to memory (only useful for benchmark testing)

+  -s, --source string              filesystem path to read files relative from

+      --stepAnalysis               display memory and timing of different steps of the program

+  -t, --theme string               theme to use (located in /themes/THEMENAME/)

+      --themesDir string           filesystem path to themes directory

+      --uglyURLs                   if true, use /filename.html instead of /filename/

+  -v, --verbose                    verbose output

+      --verboseLog                 verbose logging

+  -w, --watch                      watch filesystem for changes and recreate as needed

+```

+## The `hugo` Command

+The most common usage is probably to run `hugo` with your current directory being the input directory.

+This generates your website to the `public/` directory by default, although you can customize the output directory in your [site configuration][config] by changing the `publishDir` field.

+The site Hugo renders into `public/` is ready to be deployed to your web server:

+```bash

+hugo

+0 draft content

+0 future content

+99 pages created

+0 paginator pages created

+16 tags created

+0 groups created

+in 90 ms

+```

+## Draft, Future, and Expired Content

+Hugo allows you to set `draft`, `publishdate`, and even `expirydate` in your content's [front matter][]. By default, Hugo will not publish:

+1. Content with a future `publishdate` value

+2. Content with `draft: true` status

+3. Content with a past `expirydate` value

+All three of these can be overridden during both local development *and* deployment by adding the following flags to `hugo` and `hugo server`, respectively, or by changing the boolean values assigned to the fields of the same name (without `--`) in your [configuration][config]:

+1. `--buildFuture`

+2. `--buildDrafts`

+3. `--buildExpired`

+## LiveReload

+Hugo comes with [LiveReload](https://github.com/livereload/livereload-js) built in. There are no additional packages to install. A common way to use Hugo while developing a site is to have Hugo run a server with the `hugo server` command and watch for changes:

+```bash

+hugo server

+0 draft content

+0 future content

+99 pages created

+0 paginator pages created

+16 tags created

+0 groups created

+in 120 ms

+Watching for changes in /Users/yourname/sites/yourhugosite/{data,content,layouts,static}

+Serving pages from /Users/yourname/sites/yourhugosite/public

+Web Server is available at http://localhost:1313/

+Press Ctrl+C to stop

+```

+This will run a fully functioning web server while simultaneously watching your file system for additions, deletions, or changes within the following areas of your [project organization][dirs]:

+* `/static/*`

+* `/content/*`

+* `/data/*`

+* `/i18n/*`

+* `/layouts/*`

+* `/themes/<CURRENT-THEME>/*`

+* `config`

+Whenever you make changes, Hugo will simultaneously rebuild the site and continue to serve content. As soon as the build is finished, LiveReload tells the browser to silently reload the page.

+Most Hugo builds are so fast that you may not notice the change unless looking directly at the site in your browser. This means that keeping the site open on a second monitor (or another half of your current monitor) allows you to see the most up-to-date version of your website without the need to leave your text editor.

+{{% note "Closing `</body>` Tag"%}}

+Hugo injects the LiveReload `<script>` before the closing `</body>` in your templates and will therefore not work if this tag is not present..

+{{% /note %}}

+### Disable LiveReload

+LiveReload works by injecting JavaScript into the pages Hugo generates. The script creates a connection from the browser's web socket client to the Hugo web socket server.

+LiveReload is awesome for development. However, some Hugo users may use `hugo server` in production to instantly display updated content. The following methods make it easy to disable LiveReload:

+```bash

+hugo server --watch=false

+```

+Or...

+```bash

+hugo server --disableLiveReload

+```

+The latter flag can be omitted by adding the following key-value to  your `config.toml` or `config.yml` file, respectively:

+```toml

+disableLiveReload = true

+```

+```yaml

+disableLiveReload: true

+```

+## Deploy Your Website

+After running `hugo server` for local web development, you need to do a final `hugo` run *without the `server` part of the command* to rebuild your site. You may then deploy your site by copying the `public/` directory to your production web server.

+Since Hugo generates a static website, your site can be hosted *anywhere* using any web server. See [Hosting and Deployment][hosting] for methods for hosting and automating deployments contributed by the Hugo community.

+{{% warning "Generated Files are **NOT** Removed on Site Build" %}}

+Running `hugo` *does not* remove generated files before building. This means that you should delete your `public/` directory (or the publish directory you specified via flag or configuration file) before running the `hugo` command. If you do not remove these files, you run the risk of the wrong files (e.g., drafts or future posts) being left in the generated site.

+{{% /warning %}}

+### Dev vs Deploy Destinations

+Hugo does not remove generated files before building. An easy workaround is to use different directories for development and production.

+To start a server that builds draft content (helpful for editing), you can specify a different destination; e.g., a `dev/` directory:

+```bash

+hugo server -wDs ~/Code/hugo/docs -d dev

+```

+When the content is ready for publishing, use the default `public/` dir:

+```bash

+hugo -s ~/Code/hugo/docs

+```

+This prevents draft content from accidentally becoming available.

+[commands]: /commands/

+[config]: /getting-started/configuration/

+[dirs]: /getting-started/directory-structure/

+[front matter]: /content-management/front-matter/

+[hosting]: /hosting-and-deployment/

+[install]: /getting-started/installing/

--- /dev/null

+++ b/content/hosting-and-deployment/_index.md

@@ -1,0 +1,20 @@

+---

+title: Hosting & Deployment

+linktitle: Hosting & Deployment Overview

+description: Site builds, automated deployments, and popular hosting solutions.

+date: 2016-11-01

+publishdate: 2016-11-01

+lastmod: 2016-11-01

+categories: [hosting and deployment]

+#tags: []

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 01

+weight: 01	#rem

+draft: false

+aliases: []

+toc: false

+---

+Because Hugo renders *static* websites, you can host your new Hugo website virtually anywhere. The following represent only a few of the more popular hosting and automated deployment solutions used by the Hugo community.

--- /dev/null

+++ b/content/hosting-and-deployment/deployment-with-rsync.md

@@ -1,0 +1,139 @@

+---

+title: Deployment with Rysnc

+linktitle: Deployment with Rysnc

+description: If you have access to your web host with SSH, you can use a simple rsync one-liner to incrementally deploy your entire Hugo website.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [hosting and deployment]

+#tags: [rysnc,deployment]

+authors: [Adrien Poupin]

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 70

+weight: 70

+sections_weight: 70

+draft: false

+aliases: [/tutorials/deployment-with-rsync/]

+toc: true

+notesforauthors:

+---

+## Assumptions

+* Access to your web host with SSH

+* A functional static website built with Hugo

+The spoiler is that you can deploy your entire website with a command that looks like the following:

+```bash

+hugo && rsync -avz --delete public/ [email protected]:~/www/

+```

+As you will see, we put it in a shell script file, which makes building and deployment as easy as executing `./deploy`.

+## Install SSH Key

+If it is not done yet, we will make an automated way to SSH to your server. If you have already installed an SSH key, switch to the next section.

+First, install the ssh client. On Debian/Ubuntu/derivates, use the following command:

+{{% code file="install-openssh.sh" %}}

+```bash

+sudo apt-get install openssh-client

+```

+{{% /code %}}

+Then generate your ssh key by entering the following commands:

+```bash

+~$ cd && mkdir .ssh & cd .ssh

+~/.ssh/$ ssh-keygen -t rsa -q -C "For SSH" -f rsa_id

+~/.ssh/$ cat >> config <<EOF

+Host HOST

+     Hostname HOST

+     Port 22

+     User USER

+     IdentityFile ~/.ssh/rsa_id

+EOF

+```

+Don't forget to replace the `HOST` and `USER` values with your own ones. Then copy your ssh public key to the remote server:

+```bash

+~/.ssh/$ ssh-copy-id -i rsa_id.pub [email protected]

+```

+Now you can easily connect to the remote server:

+```

+~$ ssh user@host

+Enter passphrase for key '/home/mylogin/.ssh/rsa_id':

+```

+And you've done it!

+## Shell Script

+We will put the first command in a script at the root of your Hugo tree:

+```bash

+~/websites/topologix.fr$ editor deploy

+```

+Here you put the following content. Replace the `USER`, `HOST`, and `DIR` values with your own:

+```bash

+#!/bin/sh

+USER=my-user

+HOST=my-server.com

+DIR=my/directory/to/topologix.fr/   # might sometimes be empty!

+hugo && rsync -avz --delete public/ ${USER}@${HOST}:~/${DIR}

+exit 0

+```

+Note that `DIR` is the relative path from the remote user's home. If you have to specify a full path (for instance `/var/www/mysite/`) you must change `~/${DIR}` to `${DIR}` inside the command line. For most cases you should not have to.

+Save and close, and make the `deploy` file executable:

+```

+~/websites/topologix.fr$ chmod +x deploy

+```

+Now you only have to enter the following command to deploy and update your website:

+```

+~/websites/topologix.fr$ ./deploy

+Started building sites ...

+Built site for language en:

+0 draft content

+0 future content

+0 expired content

+5 pages created

+0 non-page files copied

+0 paginator pages created

+0 tags created

+0 categories created

+total in 56 ms

+sending incremental file list

+404.html

+index.html

+index.xml

+sitemap.xml

+cours-versailles/index.html

+exercices/index.html

+exercices/index.xml

+exercices/barycentre-et-carres-des-distances/index.html

+post/

+post/index.html

+sujets/index.html

+sujets/index.xml

+sujets/2016-09_supelec-jp/index.html

+tarifs-contact/index.html

+sent 9,550 bytes  received 1,708 bytes  7,505.33 bytes/sec

+total size is 966,557  speedup is 85.86

+```

--- /dev/null

+++ b/content/hosting-and-deployment/deployment-with-wercker.md

@@ -1,0 +1,348 @@

+---

+title: Deployment with Wercker

+linktitle: Deployment with Wercker

+description: You can use a free tool called Wercker to automate deployments between your GitHub-hosted source and final website on GitHub pages.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [hosting and deployment]

+#tags: [wercker,deployment,github,git]

+authors: [Arjen Schwarz, Samuel Debruyn]

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 60

+weight: 60

+sections_weight: 60

+draft: false

+aliases: [/tutorials/automated-deployments/]

+toc: true

+wip: false

+notesforauthors:

+---

+## Goals

+By the end of this guide, you will have completed the following:

+* Creating a basic Hugo project and website

+* Version controlling your project with Git

+* Adding your project to GitHub

+* Automating site deployments with a free tool called Wercker

+* Deploying your website to GitHub Pages for free hosting

+## Assumptions

+1. You have a working familiarity with using Git for version control

+2. You have a GitHub account

+3. You have already created a basic Hugo project

+If you do not meet these assumptions, the [GitHub help section][githubhelp] has an explanation of how to install and use git. [Signing up for a GitHub][ghsignup] account is free as well. If you are completely unfamiliar with creating a new Hugo website, visit the [Hugo Quick Start][quickstart].

+## Create a Basic Hugo Site

+{{% note "This Guide Uses the Hugo CLI" %}}

+All the work for setting up a Hugo project and using this guide is done via the Hugo CLI's most basic commands. See the [command line reference page](/commands/) for a more exhaustive account of the CLI's features.

+{{% /note %}}

+First, create your new Hugo website using the [`hugo new site` command][basicusage] and change into the newly created directory for the project. In this guide, we are calling our new project `hugo-wercker-example`:

+{{% code file="hugo-new-site.sh" %}}

+```bash

+hugo new site hugo-wercker-example

+cd hugo-wercker-example

+```

+{{% /code %}}

+We will use the [Herring Cove theme][] by first cloning the theme into the `themes` directory.

+{{% code file="clone-herring-cove-theme.sh" %}}

+```bash

+cd themes

+git clone https://github.com/spf13/herring-cove.git

+```

+{{% /code %}}

+Cloning the project from the command line will conflict with our own version control. So, we need to remove the external git configuration that came with the clone of Herring Cove:

+{{% code file="remove-herring-cove-git.sh" %}}

+```bash

+rm -rf herring-cove/.git

+```

+{{% /code %}}

+We need content for Hugo to build. Let's add a quick `/about` page:

+```bash

+hugo new about.md

+```

+{{% note %}}

+The preceding example for the about page leverages archetypes to scaffold a new content file with preconfigured front matter. [Find out more about Hugo's archetypes](/content-management/archetypes/).

+{{% /note %}}

+Now you can edit `contents/about.md` in your text editor of choice, but this is not necessary for the purposes of this guide. Running the following command will build your Hugo site into the `public` directory. We have added `undraft` to ensure that the example page is no longer in draft mode:

+{{% code file="hugo-build-undraft.sh" %}}

+```bash

+hugo undraft content/about.md

+```

+{{% /code %}}

+Once the website is build, t's a good idea to run the following command to start a local server and ensure you're changes have been implemented:

+```bash

+hugo server --theme=herring-cove

+```

+If everything is fine, you should see something similar to the image below when you go to <http://localhost:1313> in your browser.

+![][1]

+## Set up Version Control in Git

+Adding Git to your project is done by running the `git init` command from the root directory of your project.

+```bash

+git init

+```

+Running `git status` at this point will show you the following entries: the `config.toml` file, the `themes` directory, the `contents` directory, and the `public` directory. However, we don't want the `public` directory version controlled because Wercker is responsible for generating the finished website later on. Therefore, we'll add a `.gitignore` file to our project that will exclude the `/public` directory from being tracked by Git:

+{{% code file="gitignore.sh" %}}

+```bash

+echo "/public" >> .gitignore

+```

+{{% /code %}}

+Wercker might complain when we try to build the site later on because we currently do not have any static files outside of the `themes` directory. We simply have to add *any* file to the static folder to prevent Wercker from complaining. To keep this guide simple, let's add a `robots.txt`. The following command creates the file in `/static`. The contents of the `robots.txt` lets search engines know they have full access to crawl the published website:

+{{% code file="addrobotstxt.sh" %}}

+```bash

+echo "User-agent: *\nDisallow:" > static/robots.txt

+```

+{{% /code %}}

+Now we need to add (i.e., [stage [see Git documentation]][gitbasics]) and commit all of our changes in the repository into Git:

+```bash

+git commit -a -m "Initial commit"

+```

+## Add the Project to GitHub

+Now we need to create a new repository on GitHub. Once you are signed in to GitHub, you can add a new repository by clicking on the **&#43;&#9660;** dropdown at the top right or by going to [https://github.com/new](https://github.com)..

+We then choose a name for the project (`hugo-wercker-example`). When clicking on create repository GitHub displays the commands for adding an existing project to the site. The commands shown below are the ones used for this site, if you're following along you will need to use the ones shown by GitHub. Once we've run those commands the project is in GitHub and we can move on to setting up the Wercker configuration. Be sure to replace `YourUserName` with your GitHub account/username:

+{{% code file="setup-gh-repo.sh" %}}

+```bash

+git remote add origin [email protected]:YourUsername/hugo-wercker-example.git

+git push -u origin master

+```

+{{% /code %}}

+![][2]

+## Set Up Wercker

+To sign up for a free Wercker account, go to <https://wercker.com> and click the the **Sign Up** button on the top right of the home screen.

+![][3]

+### Registe for Wercker with Your GitHub Account

+Sign up for Wercker using your GitHub credentials. If you don't have a GitHub account, or don't want to use it for your account, you have the option to register with a username and password as well. However, the second half of this guide---devoted to hosting your website on GitHub pages---will no longer be of interest to you.

+![][4]

+### Connecte GitHub or Bitbucket

+After you are registered, you will need to link your GitHub or Bitbucket account to Wercker. You can link your account by navigating to your profile settings and then selecting "Git connections."

+![][17]

+If you registered for Wercker using GitHub, it will most likely look like the following image. To connect a missing service, click the **Connect** button, which may send you to either GitHub or Bitbucket to sign into your respective account.

+![][5]

+### Add Your Project

+Now that we've got all the preliminaries out of the way, it's time to set up our application. For this we click on the **+ Create** button next to Applications and choose GitHub as our provider.

+![][6]

+### Select a Repository

+When selecting GitHub, Wercker will show all your GitHub repositories. You have the option to filter repositories using the search input at the top of the repositories list. Once you have your repository selected, click the **Use selected repo** button.

+![][7]

+### Select the Repository Owner

+In the next step, Wercker asks you to select the repository owner. Select your GitHub account and continue.

+![][8]

+### Configure Access

+{{% note %}}

+This guide assumes you are using a public GitHub repository and understand that the [published GitHub Pages website will be available to everyone](https://help.github.com/articles/what-is-github-pages/#usage-limits).

+{{%/note %}}

+This step can be slightly tricky. Wercker does not have privileges to check out your private projects by default and therefore needs your permission to add a deploy key to your repository. By selecting the first option, you're simply allowing Wercker to check out the code via the same methods available to anyone visiting the project on GitHub.

+![][9]

+### Wercker.yml

+Wercker will now attempt to create an initial `wercker.yml` file for you. More specifically, it will create a code block within the Wercker interface that you can copy to your finished file. Wercker gives us a `debian` box because our project does not have any special requirements.

+Now we need to create a *wercker.yml* file in the root of our project. This file will contain our Wercker app's configuration. After we finish setting up our app, we will expand the contents of this file to build and deploy our website.

+![][10]

+### Public or Private

+This is a personal choice. You can make an app public so that everyone can see more details about it. Keeping it private or public does not provide any overt benefits for you as the creator of the app. That said, [the app we are currently creating has been made public][publicappurl] to facilitate easier usage of this hosting and deployment guide.

+![][11]

+#### App Successfully Created

+The application is now added and Wercker will offer you the chance to trigger a build. However, we will decline the offer because we haven't yet pushed our `wercker.yml` file to our GitHub repository.

+![][12]

+### Add the Hugo-build Step

+Now we need to add the Wercker steps to our build process. First, we go to the "Registry" action in the top menu. When in the registry, we can search for "hugo build". Select the "Hugo-Build by **arjen**" step.

+![][13]

+### Use the Hugo-build Step

+A summary of very basic usage is available at the top of the details for the Hugo-Build step. Below the basic usage is the contents of the `README.md` file associated with the step's repository. `README.md`'s on Wercker usually contain more details about the advanced options and examples of usage.

+We're not going to use any of the advanced features of Hugo-Build in this guide. Let's return to our project and add the first section of details we need to our `wercker.yml`.

+{{% warning "Hugo Version in `wercker.yml`" %}}

+The docs are a work in progress. As such, the `version` represented in this guide may not represent the version you've been using for local development. Be sure to use the appropriate Hugo version for your build step.

+{{% /warning %}}

+{{% code file="wercker-build-step.yml" %}}

+```yaml

+box: debian

+build:

+  steps:

+    - arjen/hugo-build:

+        version: "0.17"

+        theme: herring-cove

+        flags: --buildDrafts=true

+```

+{{% /code %}}

+We can conclude this first step by pushing our `wercker.yml` to our GitHub repository and then seeing the magic at work within Wercker's interface.

+{{% code file="push-wecker-to-gh.sh" %}}

+```bash

+git commit -a -m "Add wercker.yml"

+git push origin master

+```

+{{% /code %}}

+If completed and successful, a green check mark should appear in the commit column of your first build. However, this is only the build step. We still need to deploy the website to our free hosting on GitHub Pages. If you would like more details about the build, you can click the commit hash.

+![][14]

+### Add a GitHub Pages Deploy Step to `wercker.yml`

+In order to deploy to GitHub Pages, we need to add a deploy step to our `wercker.yml`. We are going to add `lukevevier/gh-pages`, the most popular GitHub Pages step in the Wercker Steps repository. Additionally, we need to ensure the box Wercker uses for our deployments has git and ssh installed. We can do this using the `install-packages` command. Here is our *final* `wercker.yml` file:

+{{% code file="wercker.yml" %}}

+```yaml

+box: debian

+build:

+  steps:

+    - arjen/hugo-build:

+        version: "0.17"

+        theme: herring-cove

+        flags: --buildDrafts=true

+deploy:

+  steps:

+    - install-packages:

+        packages: git ssh-client

+    - lukevivier/[email protected]:

+        token: $GIT_TOKEN

+        domain: hugo-wercker.ig.nore.me

+        basedir: public

+```

+{{% /code %}}

+### How does the GitHub Pages Configuration Work?

+We've provided a some important information in our `wercker.yml`. First, we've added the domain we want to use for our published website. Configuring the domain here will ensure that GitHub Pages is aware of the domain we want to use.

+Secondly, we've configured the `basedir` to `public`. This is the directory that will be used as the website on GitHub Pages. `public` is also the default publishing directory in Hugo. (For more information, see [hugo's configuration docs][hugoconfig]).

+Lastly, you'll notice a `$GIT_TOKEN` variable. This is used for pushing our changes to GitHub. We will need to configure this token before Wercker can build our website.

+### Set the App's Deploy Target

+We can set our deploy target by going to our app's settings and clicking on **Deploy targets**. Now select **Add deploy target** and then **Custom deploy**.

+![][15]

+### Configure the Deploy Step in Wercker

+The next screen requires you fill in the deploy target name.

+1. Make sure you enable **auto deploy** from the **master** branch.

+2. Add a variable for the **GIT_TOKEN**. You'll need to create an access token in GitHub. Follow the directions in [GitHub help][accesstokenghhelp].

+3. With the deploy step configured in Wercker, we can push the updated wercker.yml file to GitHub and it will create the GitHub pages site for us.

+The website described in this guide is available at <http://hugo-wercker.ig.nore.me>.

+![][16]

+## Conclusion

+Once this workflow is established, you can update your website automatically by pushing any content changes to your GitHub repository.

+### Code for the Wercker Deployment Guide

+[The source code for the site used in this guide is available on GitHub][guidesource], as is the [Wercker Hugo Build step][guidestep].

+If you want to see an example of how you can deploy to S3 instead of GitHub pages, check [Wercker's documentation][werckerdocs] for guidance on setup.

+[1]: /images/hosting-and-deployment/deployment-with-wercker/creating-a-basic-hugo-site.png

+[2]: /images/hosting-and-deployment/deployment-with-wercker/adding-the-project-to-github.png

+[3]: /images/hosting-and-deployment/deployment-with-wercker/wercker-sign-up.png

+[4]: /images/hosting-and-deployment/deployment-with-wercker/wercker-sign-up-page.png

+[5]: /images/hosting-and-deployment/deployment-with-wercker/wercker-git-connections.png

+[6]: /images/hosting-and-deployment/deployment-with-wercker/wercker-add-app.png

+[7]: /images/hosting-and-deployment/deployment-with-wercker/wercker-select-repository.png

+[8]: /images/hosting-and-deployment/deployment-with-wercker/wercker-select-owner.png

+[9]: /images/hosting-and-deployment/deployment-with-wercker/wercker-access.png

+[10]: /images/hosting-and-deployment/deployment-with-wercker/werckeryml.png

+[11]: /images/hosting-and-deployment/deployment-with-wercker/public-or-not.png

+[12]: /images/hosting-and-deployment/deployment-with-wercker/and-we-ve-got-an-app.png

+[13]: /images/hosting-and-deployment/deployment-with-wercker/wercker-search.png

+[14]: /images/hosting-and-deployment/deployment-with-wercker/using-hugo-build.png

+[15]: /images/hosting-and-deployment/deployment-with-wercker/adding-a-github-pages-step.png

+[16]: /images/hosting-and-deployment/deployment-with-wercker/configure-the-deploy-step.png

+[17]: /images/hosting-and-deployment/deployment-with-wercker/wercker-account-settings.png

+[accesstokenghhelp]: https://help.github.com/articles/creating-an-access-token-for-command-line-use/

+[basicusage]: /getting-started/usage/

+[ghsignup]: https://github.com/join

+[gitbasics]: https://git-scm.com/book/en/v2/Getting-Started-Git-Basics

+[githubhelp]: https://help.github.com/articles/set-up-git/

+[guidesource]: https://github.com/ArjenSchwarz/hugo-wercker-example

+[guidestep]: https://github.com/ArjenSchwarz/wercker-step-hugo-build

+[Herring Cove theme]: https://github.com/spf13/herring-cove

+[hugoconfig]: /getting-started/configuration/

+[publicappurl]: https://app.wercker.com/#applications/5586dcbdaf7de9c51b02b0d5

+[quickstart]: /getting-started/quick-start/

+[werckerdocs]: http://devcenter.wercker.com/docs/deploy/s3.html

--- /dev/null

+++ b/content/hosting-and-deployment/hosting-on-bitbucket.md

@@ -1,0 +1,143 @@

+---

+title: Hosting on Bitbucket

+linktitle: Hosting on Bitbucket

+description: You can use Bitbucket in conjunction with Aerobatic to build, deploy, and host a Hugo website.

+date: 2017-02-04

+publishdate: 2017-02-04

+lastmod: 2017-02-04

+categories: [hosting and deployment]

+#tags: [hosting,bitbucket,deployment,aerobatic]

+authors: [Jason Gowans]

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 50

+weight: 50

+sections_weight: 50

+draft: false

+toc: true

+aliases: [/tutorials/hosting-on-bitbucket/]

+---

+You can use [Bitbucket](https://bitbucket.org/) and [Aerobatic](https://www.aerobatic.com) to build, deploy, and host a Hugo website. Aerobatic is a static hosting service that integrates with Bitbucket and provides a free hosting tier.

+## Assumptions

+* Working familiarity with Git for version control

+* A [Bitbucket account](https://bitbucket.org/account/signup/)

+## Install Aerobatic CLI

+If you haven't previously used Aerobatic, you'll first need to install the Command Line Interface (CLI) and create an account. For a list of all commands available, see the [Aerobatic CLI](https://www.aerobatic.com/docs/cli/) docs.

+```bash

+npm install aerobatic-cli -g

+aero register

+```

+## Create and Deploy Site

+```bash

+hugo new site my-new-hugo-site

+cd my-new-hugo-site

+cd themes; git clone https://github.com/eliasson/liquorice

+hugo -t liquorice

+aero create                                           # create the Aerobatic site

+hugo --baseURL https://my-new-hugo-site.aerobatic.io  # build the site overriding baseURL

+aero deploy -d public                                 # deploy output to Aerobatic

+Version v1 deployment complete.

+View now at https://hugo-docs-test.aerobatic.io

+```

+In the rendered page response, the `https://__baseurl__` will be replaced with your actual site url (in this example, `https://my-new-hugo-site.aerobatic.io`). You can always rename your Aerobatic website with the `aero rename` command.

+## Push Hugo site to Bitbucket

+We will now create a git repository and then push our code to Bitbucket. In Bitbucket, create a repository.

+![][1]

+[1]: /images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-create-repo.png

+```bash

+# initialize new git repository

+git init

+# set up our .gitignore file

+echo -e "/public \n/themes \naero-deploy.tar.gz" >> .gitignore

+# commit and push code to master branch

+git add --all

+git commit -m "Initial commit"

+git remote add origin [email protected]:YourUsername/my-new-hugo-site.git

+git push -u origin master

+```

+## Continuous Deployment With Bitbucket Pipelines

+In the example above, we pushed the compiled assets in the `/public` folder to Aerobatic. In the following example, we use Bitbucket Pipelines to continuously create and deploy the compiled assets to Aerobatic.

+### Step 1: Configure Bitbucket Pipelines

+In your Hugo website's Bitbucket repo;

+1. Click the Pipelines link in the left nav menu of your Bitbucket repository.

+2. Click the Enable Pipelines button.

+3. On the next screen, leave the default template and click Next.

+4. In the editor, paste in the yaml contents below and click Commit.

+```bash

+image: beevelop/nodejs-python

+pipelines:

+  branches:

+    master:

+      - step:

+          script:

+            - apt-get update -y && apt-get install wget

+            - apt-get -y install git

+            - wget https://github.com/gohugoio/hugo/releases/download/v0.18/hugo_0.18-64bit.deb

+            - dpkg -i hugo*.deb

+            - git clone https://github.com/eliasson/liquorice themes/liquorice

+            - hugo --theme=liquorice --baseURL https://__baseurl__ --buildDrafts

+            - npm install -g aerobatic-cli

+            - aero deploy

+```

+### Step 2: Create `AEROBATIC_API_KEY` environment variable.

+This step only needs to be done once per account. From the command line;

+```bash

+aero apikey

+```

+1. Navigate to the Bitbucket account settings for the account that the website repo belongs to.

+2. Scroll down to the bottom of the left nav and click the Environment variables link in the PIPELINES section.

+3. Create a new environment variable called AEROBATIC_API_KEY with the value you got by running the `aero apikey` command. Be sure to click the Secured checkbox.

+### Step 3: Edit and Commit Code

+```bash

+hugo new post/good-to-great.md

+hugo server --buildDrafts -t liquorice #Check that all looks good

+# commit and push code to master branch

+git add --all

+git commit -m "New blog post"

+git push -u origin master

+```

+Your code will be committed to Bitbucket, Bitbucket Pipelines will run your build, and a new version of your site will be deployed to Aerobatic.

+At this point, you can now create and edit blog posts directly in the Bitbucket UI.

+![][2]

+[2]: /images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-blog-post.png

+## Suggested next steps

+The code for this example can be found in this Bitbucket [repository](https://bitbucket.org/dundonian/hugo-docs-test). Aerobatic also provides a number of additional [plugins](https://www.aerobatic.com/docs) such as auth and redirects that you can use for your Hugo site.

--- /dev/null

+++ b/content/hosting-and-deployment/hosting-on-firebase.md

@@ -1,0 +1,91 @@

+---

+title: Hosting on Firebase

+linktitle: Hosting on Firebase

+description: You can use Firebase's free tier to host your static website; this also gives you access to Firebase's NOSQL API.

+date: 2017-03-12

+publishdate: 2017-03-12

+lastmod: 2017-03-15

+categories: [hosting and deployment]

+#tags: [hosting,firebase]

+authors: [Michel Racic]

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 20

+weight: 20

+sections_weight: 20

+draft: false

+toc: true

+aliases: []

+---

+## Assumptions

+1. You have an account with [Firebase][signup]. (If you don't, you can sign up for free using your Google account.)

+2. You have completed the [Quick Start][] or have a completed Hugo website ready for deployment.

+## Initial setup

+Go to the [Firebase console][console] and create a new project (unless you already have a project). You will need to globally install `firebase-tools` (node.js):

+```sh

+npm install -g firebase-tools

+```

+Log in to Firebase (setup on your local machine) using `firebase login`, which opens a browser where you can select your account. Use `firebase logout` in case you are already logged in but to the wrong account.

+```sh

+firebase login

+```

+In the root of your Hugo project, initialize the Firebase project with the `firebase init` command:

+```sh

+firebase init

+```

+From here:

+1. Choose Hosting in the feature question

+2. Choose the project you just set up

+3. Accept the default for your database rules file

+4. Accept the default for the publish directory, which is `public`

+5. Choose "No" in the question if you are deploying a single-page app

+## Deploy

+To deploy your Hugo site, execute the `firebase deploy` command, and your site will be up in no time:

+```sh

+hugo && firebase deploy

+```

+## CI Setup

+You can generate a deploy token using

+```sh

+firebase login:ci

+```

+You can also set up your CI (e.g., with [Wercker][]) and add the token to a private variable like `$FIREBASE_DEPLOY_TOKEN`.

+{{% note %}}

+This is a private secret and it should not appear in a public repository. Make sure you understand your chosen CI and that it's not visible to others.

+{{% /note %}}

+You can then add a step in your build to do the deployment using the token:

+```sh

+firebase deploy --token $FIREBASE_DEPLOY_TOKEN

+```

+## Reference links

+* [Firebase CLI Reference](https://firebase.google.com/docs/cli/#administrative_commands)

+[console]: https://console.firebase.google.com

+[Quick Start]: /getting-started/quick-start/

+[signup]: https://console.firebase.google.com/

+[Wercker]: /hosting-and-deployment/deployment-with-wercker/

--- /dev/null

+++ b/content/hosting-and-deployment/hosting-on-github.md

@@ -1,0 +1,244 @@

+---

+title: Hosting on GitHub

+linktitle: Hosting on GitHub

+description: Deploy Hugo as a GitHub Pages project or personal/organizational site and automate the whole process with a simple shell script.

+date: 2014-03-21

+publishdate: 2014-03-21

+lastmod: 2017-03-30

+categories: [hosting and deployment]

+#tags: [github,git,deployment,hosting]

+authors: [Spencer Lyon, Gunnar Morling]

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+toc: true

+aliases: [/tutorials/github-pages-blog/]

+---

+GitHub provides free and fast static hosting over SSL for personal, organization, or project pages directly from a GitHub repository via its [GitHub Pages service][].

+## Assumptions

+1. You have Git 2.5 or greater [installed on your machine][installgit].

+2. You have a GitHub account. [Signing up][ghsignup] for GitHub is free.

+3. You have a ready-to-publish Hugo website or have at least completed the [Quick Start][].

+If you are working within an Organization account or want to set up a User website on GitHub and would like more information, refer to the [GitHub Pages documentation][ghorgs].

+{{% note %}}

+Make sure your `baseURL` key-value in your [site configuration](/getting-started/configuration/) reflects the full URL of your GitHub pages repository if you're using the default GH Pages URL (e.g., `username.github.io/myprojectname/`) and not a custom domain.

+{{% /note %}}

+## Deployment via `/docs` Folder on Master Branch

+[As described in the GitHub Pages documentation][ghpfromdocs], you can deploy from a folder called `docs/` on your master branch. To effectively use this feature with Hugo, you need to change the Hugo publish directory in your [site's][config] `config.toml` and `config.yaml`, respectively:

+```yaml

+publishDir: docs

+```

+```toml

+publishDir = "docs"

+```

+After running `hugo`, push your master branch to the remote repository and choose the `docs/` folder as the website source of your repo. Do the following from within your GitHub project:

+1. Go to **Settings** &rarr; **GitHub Pages**

+2. From **Source**,  select "master branch /docs folder". If the option isn't enabled, you likely do not have a `docs/` folder in the root of your project.

+{{% note %}}

+The `docs/` option is the simplest approach but requires you set a publish directory in your site configuration. You cannot currently configure GitHub pages to publish from another directory on master, and not everyone prefers the output site live concomitantly with source files in version control.

+{{% /note %}}

+## Deployment From Your `gh-pages` Branch

+You can also tell GitHub pages to treat your `master` branch as the published site or point to a separate `gh-pages` branch. The latter approach is a bit more complex but has some advantages:

+* It keeps your source and generated website in different branches and therefore maintains version control history for both.

+* Unlike the preceding `docs/` option, it uses the default `public` folder.

+### Preparations for `gh-pages` Branch

+These steps only need to be done once. Replace `upstream` with the name of your remote; e.g., `origin`:

+#### Add the Public Folder

+First, add the `public` folder to your `.gitignore` file at the project root so that the directory is ignored on the master branch:

+```bash

+echo "public" >> .gitignore

+```

+#### Initialize Your `gh-pages` Branch

+You can now initialize your `gh-pages` branch as an empty [orphan branch][]:

+```bash

+git checkout --orphan gh-pages

+git reset --hard

+git commit --allow-empty -m "Initializing gh-pages branch"

+git push upstream gh-pages

+git checkout master

+```

+### Build and Deployment

+Now check out the `gh-pages` branch into your `public` folder using git's [worktree feature][]. Essentially, the worktree allows you to have multiple branches of the same local repository to be checked out in different directories:

+```sh

+rm -rf public

+git worktree add -B gh-pages public upstream/gh-pages

+```

+Regenerate the site using the `hugo` command and commit the generated files on the `gh-pages` branch:

+{{% code file="commit-gh-pages-files.sh"%}}

+```bash

+hugo

+cd public && git add --all && git commit -m "Publishing to gh-pages" && cd ..

+```

+{{% /code %}}

+If the changes in your local `gh-pages` branch look alright, push them to the remote repo:

+```bash

+git push upstream gh-pages

+```

+#### Set `gh-pages` as Your Publish Branch

+In order to use your `gh-pages` branch as your publishing branch, you'll need to configure the repository within the GitHub UI. This will likely happen automatically once GitHub realizes you've created this branch. You can also set the branch manually from within your GitHub project:

+1. Go to **Settings** &rarr; **GitHub Pages**

+2. From **Source**,  select "gh-pages branch" and then **Save**. If the option isn't enabled, you likely have not created the branch yet OR you have not pushed the branch from your local machine to the hosted repository on GitHub.

+After a short while, you'll see the updated contents on your GitHub Pages site.

+### Put it Into a Script

+To automate these steps, you can create a script with the following contents:

+{{% code file="publish_to_ghpages.sh" %}}

+```sh

+#!/bin/sh

+DIR=$(dirname "$0")

+cd $DIR/..

+if [[ $(git status -s) ]]

+then

+    echo "The working directory is dirty. Please commit any pending changes."

+    exit 1;

+fi

+echo "Deleting old publication"

+rm -rf public

+mkdir public

+git worktree prune

+rm -rf .git/worktrees/public/

+echo "Checking out gh-pages branch into public"

+git worktree add -B gh-pages public upstream/gh-pages

+echo "Removing existing files"

+rm -rf public/*

+echo "Generating site"

+hugo

+echo "Updating gh-pages branch"

+cd public && git add --all && git commit -m "Publishing to gh-pages (publish.sh)"

+```

+{{% /code %}}

+This will abort if there are pending changes in the working directory and also makes sure that all previously existing output files are removed. Adjust the script to taste, e.g. to include the final push to the remote repository if you don't need to take a look at the gh-pages branch before pushing. Or adding `echo yourdomainname.com >> CNAME` if you set up for your gh-pages to use customize domain.

+## Deployment From Your `master` Branch

+To use `master` as your publishing branch, you'll need your rendered website to live at the root of the GitHub repository. Steps should be similar to that of the `gh-pages` branch, with the exception that you will create your GitHub repository with the `public` directory as the root. Note that this does not provide the same benefits of the `gh-pages` branch in keeping your source and output in separate, but version controlled, branches within the same repo.

+You will also need to set `master` as your publishable branch from within the GitHub UI:

+1. Go to **Settings** &rarr; **GitHub Pages**

+2. From **Source**,  select "master branch" and then **Save**.

+## Host GitHub User or Organization Pages

+As mentioned [in this GitHub Help article](https://help.github.com/articles/user-organization-and-project-pages/), you can host a user/organization page in addition to project pages. Here are the key differences in GitHub Pages websites for Users and Organizations:

+1. You must use the `<USERNAME>.github.io` naming scheme for your GitHub repo.

+2. Content from the `master` branch will be used to publish your GitHub Pages site.

+It becomes much simpler in this case: we'll create two separate repos, one for Hugo's content, and a git submodule with the `public` folder's content in it.

+### Step-by-step Instructions

+1. Create a `<YOUR-PROJECT>` git repository on GitHub. This repository will contain Hugo's content and other source files.

+2. Create a `<USERNAME>.github.io` GitHub repository. This is the repository that will contain the fully rendered version of your Hugo website.

+3. `git clone <YOUR-PROJECT-URL> && cd <YOUR-PROJECT>`

+4. Make your website work locally (`hugo server` or `hugo server -t <YOURTHEME>`) and open your browser to <http://localhost:1313>.

+5. Once you are happy with the results:

+    * Press <kbd>Ctrl</kbd>+<kbd>C</kbd> to kill the server

+    * `rm -rf public` to completely remove the `public` directory if there

+6. `git submodule add -b master [email protected]:<USERNAME>/<USERNAME>.github.io.git public`. This creates a git [submodule][]. Now when you run the `hugo` command to build your site to `public`, the created `public` directory will have a different remote origin (i.e. hosted GitHub repository). You can automate some of these steps with the following script.

+#### Put it Into a Script

+You're almost done. You can also add a `deploy.sh` script to automate the preceding steps for you. You can also make it executable with `chmod +x deploy.sh`.

+The following are the contents of the `deploy.sh` script:

+```sh

+#!/bin/bash

+echo -e "\033[0;32mDeploying updates to GitHub...\033[0m"

+# Build the project.

+hugo # if using a theme, replace with `hugo -t <YOURTHEME>`

+# Go To Public folder

+cd public

+# Add changes to git.

+git add .

+# Commit changes.

+msg="rebuilding site `date`"

+if [ $# -eq 1 ]

+  then msg="$1"

+fi

+git commit -m "$msg"

+# Push source and build repos.

+git push origin master

+# Come Back up to the Project Root

+cd ..

+```

+You can then run `./deploy.sh "Your optional commit message"` to send changes to `<USERNAME>.github.io`. Note that you likely will want to commit changes to your `<YOUR-PROJECDT>` repository as well.

+That's it! Your personal page should be up and running at `https://yourusername.github.io` within a couple minutes.

+## Use a Custom Domain

+If you'd like to use a custom domain for your GitHub Pages site, create a file `static/CNAME`. Your custom domain name should be the only contents inside `CNAME`. Since it's inside `static`, the published site will contain the CNAME file at the root of the published site, which is a requirements of GitHub Pages.

+Refer to the [official documentation for custom domains][domains] for further information.

+[config]: /getting-started/configuration/

+[domains]: https://help.github.com/articles/using-a-custom-domain-with-github-pages/

+[ghorgs]: https://help.github.com/articles/user-organization-and-project-pages/#user--organization-pages

+[ghpfromdocs]: https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/#publishing-your-github-pages-site-from-a-docs-folder-on-your-master-branch

+[ghsignup]: https://github.com/join

+[GitHub Pages service]: https://help.github.com/articles/what-is-github-pages/

+[installgit]: https://git-scm.com/downloads

+[orphan branch]: https://git-scm.com/docs/git-checkout/#git-checkout---orphanltnewbranchgt

+[Quick Start]: /getting-started/quick-start/

+[submodule]: https://github.com/blog/2104-working-with-submodules

+[worktree feature]: https://git-scm.com/docs/git-worktree

--- /dev/null

+++ b/content/hosting-and-deployment/hosting-on-gitlab.md

@@ -1,0 +1,83 @@

+---

+title: Hosting on GitLab

+linktitle: Hosting on GitLab

+description: GitLab makes it incredibly easy to build, deploy, and host your Hugo website via their free GitLab Pages service, which provides native support for Hugo.

+date: 2016-06-23

+publishdate: 2016-06-23

+lastmod: 2016-06-23

+categories: [hosting and deployment]

+#tags: [hosting,deployment,git,gitlab]

+authors: [Riku-Pekka Silvola]

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 40

+weight: 40

+sections_weight: 40

+draft: false

+toc: true

+wip: false

+aliases: [/tutorials/hosting-on-gitlab/]

+---

+[GitLab](https://gitlab.com/) makes it incredibly easy to build, deploy, and host your Hugo website via their free GitLab Pages service, which provides [native support for Hugo, as well as numerous other static site generators](https://gitlab.com/pages/hugo).

+## Assumptions

+* Working familiarity with Git for version control

+* Completion of the Hugo [Quick Start][]

+* A [GitLab account](https://gitlab.com/users/sign_in)

+* A Hugo website on your local machine that you are ready to publish

+## Create .gitlab-ci.yml

+```bash

+cd your-hugo-site

+```

+In the root directory of your Hugo site, create a `.gitlab-ci.yml` file. The `.gitlab-ci.yml` configures the GitLab CI on how to build your page. Simply add the content below.

+{{% code file="gitlab-ci.yml" %}}

+```yml

+image: publysher/hugo

+pages:

+  script:

+  - hugo

+  artifacts:

+    paths:

+    - public

+  only:

+  - master

+```

+{{% /code %}}

+## Push Your Hugo Website to GitLab

+Next, create a new repository on GitLab. It is *not* necessary to make the repository public. In addition, you might want to add `/public` to your .gitignore file, as there is no need to push compiled assets to GitLab or keep your output website in version control.

+```bash

+# initialize new git repository

+git init

+# add /public directory to our .gitignore file

+echo "/public" >> .gitignore

+# commit and push code to master branch

+git add .

+git commit -m "Initial commit"

+git remote add origin https://gitlab.com/YourUsername/your-hugo-site.git

+git push -u origin master

+```

+## Wait for Your Page to Build

+That's it! You can now follow the CI agent building your page at https://gitlab.com/<YourUsername>/<your-hugo-site>/pipelines.

+After the build has passed, your new website is available at `https://<YourUsername>.gitlab.io/<your-hugo-site>/`.

+## Next Steps

+GitLab supports using custom CNAME's and TLS certificates. For more details on GitLab Pages, see the [GitLab Pages setup documentation](https://about.gitlab.com/2016/04/07/gitlab-pages-setup/).

+[Quick Start]: /getting-started/quick-start/

--- /dev/null

+++ b/content/hosting-and-deployment/hosting-on-netlify.md

@@ -1,0 +1,123 @@

+---

+title: Hosting on Netlify

+linktitle: Hosting on Netlify

+description: Netlify can host your Hugo site with CDN, continuous deployment, 1-click HTTPS, an admin GUI, and its own CLI.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-11

+categories: [hosting and deployment]

+#tags: [netlify,hosting,deployment]

+authors: [Ryan Watters, Seth MacLeod]

+menu:

+  docs:

+    parent: "hosting-and-deployment"

+    weight: 10

+weight: 10

+sections_weight: 10

+draft: false

+aliases: []

+toc: true

+---

+[Netlify][netlify] provides continuous deployment services, global CDN, ultra-fast DNS, atomic deploys, instant cache invalidation, one-click SSL, a browser-based interface, a CLI, and many other features for managing your Hugo website.

+## Assumptions

+* You have an account with GitHub, GitLab, or Bitbucket.

+* You have completed the [Quick Start][] or have Hugo website you are ready to deploy and share with the world.

+* You do not already have a Netlify account.

+## Create a Netlify account

+Go to [app.netlify.com][] and select your preferred signup method. This will likely be a hosted Git provider, although you also have the option to sign up with an email address.

+The following examples use GitHub, but other git providers will follow a similar process.

+![Screenshot of the homepage for app.netlify.com, containing links to the most popular hosted git solutions.](/images/hosting-and-deployment/hosting-on-netlify/netlify-signup.jpg)

+Selecting GitHub will bring up a typical modal you've seen through other application that use GitHub for authentication. Select "Authorize application."

+![Screenshot of the authorization popup for Netlify and GitHub.](/images/hosting-and-deployment/hosting-on-netlify/netlify-first-authorize.jpg)

+## Create a New Site with Continuous Deployment

+You're now already a Netlify member and should be brought to your new dashboard. Select "New site from git."

+![Screenshot of the blank Netlify admin panel with no sites and highlighted 'add new site' button'](/images/hosting-and-deployment/hosting-on-netlify/netlify-add-new-site.jpg)

+Netlify will then start walking you through the steps necessary for continuous deployment. First, you'll need to select your git provider again, but this time you are giving Netlify added permissions to your repositories.

+![Screenshot of step 1 of create a new site for Netlify: selecting the git provider](/images/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-1.jpg)

+And then again with the GitHub authorization modal:

+![Screenshot of step 1 of create a new site for Netlify: selecting the git provider](/images/hosting-and-deployment/hosting-on-netlify/netlify-authorize-added-permissions.jpg)

+Select the repo you want to use for continuous deployment. If you have a large number of repositories, you can filter through them in real time using repo search:

+![Screenshot of step 1 of create a new site for Netlify: selecting the git provider](/images/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-2.jpg)

+Once selected, you'll be brought to a screen for basic setup. Here you can select the branch you wanted published, your [build command][], and your publish (i.e. deploy) directory. The publish directory should mirror that of what you've set in your [site configuration][config], the default of which is `public`. The following steps assume you are publishing from the `master` branch.

+### Build with a Specific Hugo Version

+Setting the build command to `hugo` will build your site according to the current default Hugo version used by Netlify. You can see the full list of [available Hugo versions in Netlify's Docker file][hugoversions].

+If you want to tell Netlify to build with a specific version, you can append an underscore followed by the version number to the build command:

+```bash

+hugo_0.19

+```

+Your simple configuration should now look similar to the following:

+![Screenshot of 3-step, basic continuous deployment setup with a new Hugo site on Netlify](/images/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-3.jpg)

+Selecting "Deploy site" will immediately take you to a terminal for your build:.

+![Animated gif of deploying a site to Netlify, including the terminal read out for the build.](/images/hosting-and-deployment/hosting-on-netlify/netlify-deploying-site.gif)

+Once the build is finished---this should only take a few seconds--you should now see a "Hero Card" at the top of your screen letting you know the deployment is successful. The Hero Card is the first element that you see in most pages. It allows you to see a quick summary of the page and gives access to the most common/pertinent actions and information. You'll see that the URL is automatically generated by Netlify. You can update the URL in "Settings."

+![Screenshot of successful deploy badge at the top of a deployments screen from within the Netlify admin.](/images/hosting-and-deployment/hosting-on-netlify/netlify-deploy-published.jpg)

+![Screenshot of homepage to https://hugo-netlify-example.netlify.com, which is mostly dummy text](/images/hosting-and-deployment/hosting-on-netlify/netlify-live-site.jpg)

+[Visit the live site][visit].

+Now every time you push changes to your hosted git repository, Netlify will rebuild and redeploy your site.

+## Use Hugo Themes with Netlify

+The [`git clone` method for installing themes][installthemes] is not supported by Netlify. If you were to use `git clone`, it would require you to recursively remove the `.git` subdirectory from the theme folder and would therefore prevent compatibility with future versions of the theme.

+A *better* approach is to install a theme as a proper git submodule. You can [read the GitHub documentation for submodules][ghsm] or those found on [Git's website][gitsm] for more information, but the command is similar to that of `git clone`:

+```bash

+cd themes

+git submodule add https://github.com/<THEMECREATOR>/<THEMENAME>

+```

+## Next Steps

+You now have a live website served over https, distributed through CDN, and configured for continuous deployment. Dig deeper into the Netlify documentation:

+1. [Using a Custom Domain][]

+2. [Setting up HTTPS on Custom Domains][httpscustom]

+3. [Redirects and Rewrite Rules][]

+[app.netlify.com]: https://app.netlify.com

+[build command]: /getting-started/usage/#the-hugo-command

+[config]: /getting-started/configuration/

+[ghsm]: https://github.com/blog/2104-working-with-submodules

+[gitsm]: https://git-scm.com/book/en/v2/Git-Tools-Submodules

+[httpscustom]: https://www.netlify.com/docs/ssl/

+[hugoversions]: https://github.com/netlify/build-image/blob/master/Dockerfile#L166

+[installthemes]: /themes/installing/

+[netlify]: https://www.netlify.com/

+[netlifysignup]: https://app.netlify.com/signup

+[Quick Start]: /getting-started/quick-start/

+[Redirects and Rewrite Rules]: https://www.netlify.com/docs/redirects/

+[Using a Custom Domain]: https://www.netlify.com/docs/custom-domains/

+[visit]: https://hugo-netlify-example.netlify.com

--- a/content/meta/license.md

+++ /dev/null

@@ -1,211 +1,0 @@

----

-aliases:

-- /doc/license/

-- /license/

-- /meta/license/

-lastmod: 2015-11-25

-date: 2013-07-01

-menu:

-  main:

-    parent: about

-title: License

-weight: 50

----

-Hugo v0.15 and later are released under the Apache 2.0 license.

-Earlier releases were under the Simple Public License.

-Apache License

-==============

-_Version 2.0, January 2004_

-_&lt;<http://www.apache.org/licenses/>&gt;_

-### Terms and Conditions for use, reproduction, and distribution

-#### 1. Definitions

-“License” shall mean the terms and conditions for use, reproduction, and

-distribution as defined by Sections 1 through 9 of this document.

-“Licensor” shall mean the copyright owner or entity authorized by the copyright

-owner that is granting the License.

-“Legal Entity” shall mean the union of the acting entity and all other entities

-that control, are controlled by, or are under common control with that entity.

-For the purposes of this definition, “control” means **(i)** the power, direct or

-indirect, to cause the direction or management of such entity, whether by

-contract or otherwise, or **(ii)** ownership of fifty percent (50%) or more of the

-outstanding shares, or **(iii)** beneficial ownership of such entity.

-“You” (or “Your”) shall mean an individual or Legal Entity exercising

-permissions granted by this License.

-“Source” form shall mean the preferred form for making modifications, including

-but not limited to software source code, documentation source, and configuration

-files.

-“Object” form shall mean any form resulting from mechanical transformation or

-translation of a Source form, including but not limited to compiled object code,

-generated documentation, and conversions to other media types.

-“Work” shall mean the work of authorship, whether in Source or Object form, made

-available under the License, as indicated by a copyright notice that is included

-in or attached to the work (an example is provided in the Appendix below).

-“Derivative Works” shall mean any work, whether in Source or Object form, that

-is based on (or derived from) the Work and for which the editorial revisions,

-annotations, elaborations, or other modifications represent, as a whole, an

-original work of authorship. For the purposes of this License, Derivative Works

-shall not include works that remain separable from, or merely link (or bind by

-name) to the interfaces of, the Work and Derivative Works thereof.

-“Contribution” shall mean any work of authorship, including the original version

-of the Work and any modifications or additions to that Work or Derivative Works

-thereof, that is intentionally submitted to Licensor for inclusion in the Work

-by the copyright owner or by an individual or Legal Entity authorized to submit

-on behalf of the copyright owner. For the purposes of this definition,

-“submitted” means any form of electronic, verbal, or written communication sent

-to the Licensor or its representatives, including but not limited to

-communication on electronic mailing lists, source code control systems, and

-issue tracking systems that are managed by, or on behalf of, the Licensor for

-the purpose of discussing and improving the Work, but excluding communication

-that is conspicuously marked or otherwise designated in writing by the copyright

-owner as “Not a Contribution.”

-“Contributor” shall mean Licensor and any individual or Legal Entity on behalf

-of whom a Contribution has been received by Licensor and subsequently

-incorporated within the Work.

-#### 2. Grant of Copyright License

-Subject to the terms and conditions of this License, each Contributor hereby

-grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,

-irrevocable copyright license to reproduce, prepare Derivative Works of,

-publicly display, publicly perform, sublicense, and distribute the Work and such

-Derivative Works in Source or Object form.

-#### 3. Grant of Patent License

-Subject to the terms and conditions of this License, each Contributor hereby

-grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,

-irrevocable (except as stated in this section) patent license to make, have

-made, use, offer to sell, sell, import, and otherwise transfer the Work, where

-such license applies only to those patent claims licensable by such Contributor

-that are necessarily infringed by their Contribution(s) alone or by combination

-of their Contribution(s) with the Work to which such Contribution(s) was

-submitted. If You institute patent litigation against any entity (including a

-cross-claim or counterclaim in a lawsuit) alleging that the Work or a

-Contribution incorporated within the Work constitutes direct or contributory

-patent infringement, then any patent licenses granted to You under this License

-for that Work shall terminate as of the date such litigation is filed.

-#### 4. Redistribution

-You may reproduce and distribute copies of the Work or Derivative Works thereof

-in any medium, with or without modifications, and in Source or Object form,

-provided that You meet the following conditions:

-* **(a)** You must give any other recipients of the Work or Derivative Works a copy of

-this License; and

-* **(b)** You must cause any modified files to carry prominent notices stating that You

-changed the files; and

-* **(c)** You must retain, in the Source form of any Derivative Works that You distribute,

-all copyright, patent, trademark, and attribution notices from the Source form

-of the Work, excluding those notices that do not pertain to any part of the

-Derivative Works; and

-* **(d)** If the Work includes a “NOTICE” text file as part of its distribution, then any

-Derivative Works that You distribute must include a readable copy of the

-attribution notices contained within such NOTICE file, excluding those notices

-that do not pertain to any part of the Derivative Works, in at least one of the

-following places: within a NOTICE text file distributed as part of the

-Derivative Works; within the Source form or documentation, if provided along

-with the Derivative Works; or, within a display generated by the Derivative

-Works, if and wherever such third-party notices normally appear. The contents of

-the NOTICE file are for informational purposes only and do not modify the

-License. You may add Your own attribution notices within Derivative Works that

-You distribute, alongside or as an addendum to the NOTICE text from the Work,

-provided that such additional attribution notices cannot be construed as

-modifying the License.

-You may add Your own copyright statement to Your modifications and may provide

-additional or different license terms and conditions for use, reproduction, or

-distribution of Your modifications, or for any such Derivative Works as a whole,

-provided Your use, reproduction, and distribution of the Work otherwise complies

-with the conditions stated in this License.

-#### 5. Submission of Contributions

-Unless You explicitly state otherwise, any Contribution intentionally submitted

-for inclusion in the Work by You to the Licensor shall be under the terms and

-conditions of this License, without any additional terms or conditions.

-Notwithstanding the above, nothing herein shall supersede or modify the terms of

-any separate license agreement you may have executed with Licensor regarding

-such Contributions.

-#### 6. Trademarks

-This License does not grant permission to use the trade names, trademarks,

-service marks, or product names of the Licensor, except as required for

-reasonable and customary use in describing the origin of the Work and

-reproducing the content of the NOTICE file.

-#### 7. Disclaimer of Warranty

-Unless required by applicable law or agreed to in writing, Licensor provides the

-Work (and each Contributor provides its Contributions) on an “AS IS” BASIS,

-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied,

-including, without limitation, any warranties or conditions of TITLE,

-NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are

-solely responsible for determining the appropriateness of using or

-redistributing the Work and assume any risks associated with Your exercise of

-permissions under this License.

-#### 8. Limitation of Liability

-In no event and under no legal theory, whether in tort (including negligence),

-contract, or otherwise, unless required by applicable law (such as deliberate

-and grossly negligent acts) or agreed to in writing, shall any Contributor be

-liable to You for damages, including any direct, indirect, special, incidental,

-or consequential damages of any character arising as a result of this License or

-out of the use or inability to use the Work (including but not limited to

-damages for loss of goodwill, work stoppage, computer failure or malfunction, or

-any and all other commercial damages or losses), even if such Contributor has

-been advised of the possibility of such damages.

-#### 9. Accepting Warranty or Additional Liability

-While redistributing the Work or Derivative Works thereof, You may choose to

-offer, and charge a fee for, acceptance of support, warranty, indemnity, or

-other liability obligations and/or rights consistent with this License. However,

-in accepting such obligations, You may act only on Your own behalf and on Your

-sole responsibility, not on behalf of any other Contributor, and only if You

-agree to indemnify, defend, and hold each Contributor harmless for any liability

-incurred by, or claims asserted against, such Contributor by reason of your

-accepting any such warranty or additional liability.

-_END OF TERMS AND CONDITIONS_

-### APPENDIX: How to apply the Apache License to your work

-To apply the Apache License to your work, attach the following boilerplate

-notice, with the fields enclosed by brackets `[]` replaced with your own

-identifying information. (Don't include the brackets!) The text should be

-enclosed in the appropriate comment syntax for the file format. We also

-recommend that a file or class name and description of purpose be included on

-the same “printed page” as the copyright notice for easier identification within

-third-party archives.

-    Copyright [yyyy] [name of copyright owner]

-    Licensed under the Apache License, Version 2.0 (the "License");

-    you may not use this file except in compliance with the License.

-    You may obtain a copy of the License at

-      http://www.apache.org/licenses/LICENSE-2.0

-    Unless required by applicable law or agreed to in writing, software

-    distributed under the License is distributed on an "AS IS" BASIS,

-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

-    See the License for the specific language governing permissions and

-    limitations under the License.

--- a/content/meta/roadmap.md

+++ /dev/null

@@ -1,33 +1,0 @@

----

-aliases:

-- /doc/roadmap/

-- /meta/roadmap/

-lastmod: 2015-02-16

-date: 2013-07-01

-menu:

-  main:

-    parent: about

-notoc: true

-title: Hugo Roadmap

-weight: 20

----

-In no particular order, here is what we are working on:

- * Intelligently related posts ([#98][])

- * Even easier deployment to S3, SSH, GitHub, rsync. Give the [tools section](https://gohugo.io/tools/#deployment) a shot or read one of the related tutorials.

- * Import from other website systems. There are already existing [migration tools](https://gohugo.io/tools/#migration) but they don't cover all major platforms.

- * An interactive web based editor (See https://discourse.gohugo.io/t/web-based-editor/155)

- * Additional [themes](https://github.com/gohugoio/hugoThemes) (always on-going, contributions welcome!)

- * Dynamic image resizing via shortcodes ([#1014][])

- * Native support for additional content formats (AsciiDoc [#1435][], reST [#1436][])

- * And, last but not least, ***Your best ideas***!

-[#100]: https://github.com/gohugoio/hugo/issues/100 "hugo import from wordpress · Issue #100 · gohugoio/hugo"

-[#101]: https://github.com/gohugoio/hugo/issues/101 "hugo import from jekyll · Issue #101 · gohugoio/hugo"

-[#1435]: https://github.com/gohugoio/hugo/issues/1435 "Add support for native Go implementation of AsciiDoc · Issue #1435 · gohugoio/hugo"

-[#1436]: https://github.com/gohugoio/hugo/issues/1436 "Add support for native Go implementation of reStructuredText (reST) · Issue #1436 · gohugoio/hugo"

-[#1014]: https://github.com/gohugoio/hugo/issues/1014 "Image Resizing and Cropping · Issue #1014 · gohugoio/hugo"

-[#98]: https://github.com/gohugoio/hugo/issues/98 "Add support for related content · Issue #98 · gohugoio/hugo"

-> Feel free to [contribute]({{< relref "tutorials/how-to-contribute-to-hugo.md" >}}) or open a [new issue](https://github.com/gohugoio/hugo/issues/new) if you have an idea for a new feature.)

--- /dev/null

+++ b/content/news/0-16.md

@@ -1,0 +1,250 @@

+---

+date: 2016-06-06T13:54:06-04:00

+description: "Hugo 0.16 is our best and biggest release ever. The Hugo community has outdone itself with continued performance improvements, beautiful themes and increased stability."

+title: "June Release"

+categories: ["Releases"]

+---

+Hugo 0.16 is our best and biggest release ever. The Hugo community has

+outdone itself with continued performance improvements,

+[beautiful themes](http://themes.gohugo.io) for all types of sites from project

+sites to documentation to blogs to portfolios, and increased stability.

+This release represents **over 550 contributions by over 110 contributors** to

+the main Hugo code base. Since last release Hugo has **gained 3500 stars, 90

+contributors and 23 additional themes.**

+This release celebrates 3 years since  {{< gh "@spf13" >}} wrote the first lines

+of Hugo. During those 3 years Hugo has accomplished some major milestones

+including...

+* 10,000+ stars on GitHub

+* 320+ contributors

+* 90+ themes

+* 1000s of happy websites

+* Many subprojects like {{< gh "@spf13/cobra">}}, {{< gh "@spf13/viper">}} and

+  {{< gh "@spf13/afero">}} which have experienced broad usage across the Go

+  ecosystem.

+{{< gh "@bep" >}} led the development of Hugo for the 3rd consecutive release

+with nearly half of the contributions to 0.16 in addition to his considerable

+contributions as lead maintainer. {{< gh "@anthonyfok" >}}, {{< gh

+"@DigitalCraftsman" >}}, {{< gh "@MooreReason" >}} all made significant

+contributions. A special thanks to {{< gh "@abourget" >}} for his considerable

+work on multilingual support. Due to its broad impact we wanted to spend more

+time testing it and it will be included in Hugo's next release.

+### Highlights

+**Partial Builds:** Prior to this release Hugo would always reread and rebuild

+the entire site. This release introduces support for reactive site building

+while watching (`hugo server`). Hugo will watch the filesystem for changes and

+only re-read the changed files. Depending on the files change Hugo will

+intelligently re-render only the needed portion of the site. Performance gains

+depend on the operation performed and size of the site. In our testing build

+times decreased anywhere from 10% to 99%.

+**Template Improvements:** Template improvements continue to be a mainstay of each Hugo release. Hugo 0.16 adds support for the new `block` keyword introduced in Go 1.6 -- think base templates with default sections -- as well as many new template functions.

+**Polish:** As Hugo matures releases will inevitably contain fewer huge new features. This release represents hundreds of small improvements across ever facet of Hugo which will make for a much better experience for all of our users. Worth mentioning here is the curious bug where live reloading didn't work in some editors on OS X, including the popular TextMate 2. This is now fixed. Oh, and now any error will exit with an error code, a big thing for automated deployments.

+### New Features

+* Support reading configuration variables from the OS environment {{<gh 2090 >}}

+* Add emoji support {{<gh 1892>}}

+* Add `themesDir` option to configuration {{<gh 1556>}}

+* Add support for Go 1.6 `block` keyword in templates {{<gh 1832>}}

+* Partial static sync {{<gh 1644>}}

+* Source file based relative linking (à la GitHub) {{<gh 0x0f6b334b6715253b030c4e783b88e911b6e53e56>}}

+* Add `ByLastmod` sort function to pages. {{<gh 0xeb627ca16de6fb5e8646279edd295a8bf0f72bf1 >}}

+* New templates functions:

+    * `readFile` {{<gh 1551 >}}

+    * `countwords` and `countrunes` {{<gh 1440>}}

+    * `default` {{<gh 1943>}}

+    * `hasPrefix` {{<gh 1243>}}

+    * `humanize` {{<gh 1818>}}

+    * `jsonify` {{<gh 0x435e996c4fd48e9009ffa9f83a19fb55f0777dbd>}}

+    * `md5` and `sha1` {{<gh 1932>}}

+    * `replaceRE` {{<gh 1845>}}

+    * `findRE` {{<gh 2048>}}

+    * `shuffle` {{<gh 1942>}}

+    * `slice` {{<gh 1902>}}

+    * `plainify` {{<gh 1915>}}

+### Enhancements

+* Hugo now exits with error code on any error. This is a big thing for

+  automated deployments. {{<gh 740 >}}

+* Print error when `/index.html` is zero-length {{<gh 947>}}

+* Enable dirname and filename bash autocompletion for more flags {{<gh

+  0x666ddd237791b56fd048992dca9a27d1af50a10e>}}

+* Improve error handling in commands {{<gh 1502>}}

+* Add sanity checks for `hugo import jekyll` {{<gh 1625 >}}

+* Add description to `Page.Params` {{<gh 1484>}}

+* Add async version of Google Analytics internal template {{<gh 1711>}}

+* Add autostart option to YouTube shortcode {{<gh 1784>}}

+* Set Date and Lastmod for main home page {{<gh 1903>}}

+* Allow URL with extension in front matter {{<gh 1923>}}

+* Add list support in Scratch {{<gh

+  0xeaba04e82bdfc5d4c29e970f11b4aab9cc0efeaa>}}

+* Add file option to gist shortcode {{<gh 1955>}}

+* Add config layout and content directory CLI options {{<gh 1698>}}

+* Add boolean value comparison to `where` template function {{<gh

+  0xf3c74c9db484c8961e70cb3458f9e41e7832fa12>}}

+* Do not write to to cache when `ignoreCache` is set  {{<gh 2067>}}

+* Add option to disable rendering of 404 page  {{<gh 2037>}}

+* Mercurial is no longer needed to build Hugo {{<gh 2062 >}}

+* Do not create `robots.txt` by default {{<gh 2049>}}

+* Disable syntax guessing for PygmentsCodeFences by default.  To enable syntax

+  guessing again, add the following to your config file:

+  `PygmentsCodeFencesGuessSyntax = true` {{<gh 2034>}}

+* Make `ByCount` sort consistently {{<gh 1930>}}

+* Add `Scratch` to shortcode {{<gh 2000>}}

+* Add support for symbolic links for content, layout, static, theme  {{<gh 1855

+  >}}

+* Add '+' as one of the valid characters in URLs specified in the front matter

+  {{<gh 1290 >}}

+* Make alias redirect output URLs relative when `RelativeURLs = true` {{<gh

+  2093 >}}

+* Hugo injects meta generator tag on homepage if missing {{<gh

+  2182 >}}

+### Fixes

+* Fix file change watcher for TextMate 2 and friends on OS X {{<gh 1053 >}}

+* Make dynamic reloading of config file reliable on all platform {{<gh 1684 >}}

+* Hugo now works on Linux/arm64 {{<gh 1772 >}}

+* `plainIDAnchors` now defaults to `true`  {{<gh 2057>}}

+* Win32 and ARM builds fixed {{<gh 1716>}}

+* Copy static dir files without theme's static dir {{<gh 1656>}}

+* Make `noTimes` command flag work {{<gh 1657>}}

+* Change most global CLI flags into local ones {{<gh 1624>}}

+* Remove transformation of menu URLs {{<gh 1239>}}

+* Do not fail on unknown Jekyll file {{<gh 1705>}}

+* Use absolute path when editing with editor {{<gh 1589>}}

+* Fix hugo server "Watching for changes" path display {{<gh 1721>}}

+* Do not strip special characters out of URLs {{<gh 1292>}}

+* Fix `RSSLink` when uglyURLs are enabled {{<gh 175>}}

+* Get BaseURL from viper in server mode {{<gh 1821>}}

+* Fix shortcode handling in RST {{<gh 1904>}}

+* Use default sitemap configuration for homepage {{<gh 1304>}}

+* Exit if specific port is unavailable in server mode {{<gh 1901>}}

+* Fix regression in "section menus for lazy blogger" {{<gh 2065>}}

+****

+## **0.15.0**  November 25, 2015

+The v0.15.0 Hugo release brings a lot of polish to Hugo. Exactly 6 months after

+the 0.14 release, Hugo has seen massive growth and changes. Most notably, this

+is Hugo's first release under the Apache 2.0 license. With this license change

+we hope to expand the great community around Hugo and make it easier for our

+many users to contribute.  This release represents over **377 contributions by

+87 contributors** to the main Hugo repo and hundreds of improvements to the

+libraries Hugo uses. Hugo also launched a [new theme

+showcase](http://themes.gohugo.io) and participated in

+[Hacktoberfest](https://hacktoberfest.digitalocean.com).

+Hugo now has:

+* 6700 (+2700) stars on GitHub

+* 235 (+75) contributors

+* 65 (+30) themes

+**Template Improvements:** This release takes Hugo to a new level of speed and

+usability. Considerable work has been done adding features and performance to

+the template system which now has full support of Ace, Amber and Go Templates.

+**Hugo Import:** Have a Jekyll site, but dreaming of porting it to Hugo? This

+release introduces a new `hugo import jekyll`command that makes this easier

+than ever.

+**Performance Improvements:** Just when you thought Hugo couldn't get any faster,

+Hugo continues to improve in speed while adding features. Notably Hugo 0.15

+introduces the ability to render and serve directly from memory resulting in

+30%+ lower render times.

+Huge thanks to all who participated in this release. A special thanks to

+{{< gh "@bep" >}} who led the development of Hugo this release again,

+{{< gh "@anthonyfok" >}},

+{{< gh "@eparis" >}},

+{{< gh "@tatsushid" >}} and

+{{< gh "@DigitalCraftsman" >}}.

+### New features

+* new `hugo import jekyll` command. {{< gh 1469 >}}

+* The new `Param` convenience method on `Page` and `Node` can be used to get the most specific parameter value for a given key. {{< gh 1462 >}}

+* Several new information elements have been added to `Page` and `Node`:

+    * `RuneCount`: The number of [runes](http://blog.golang.org/strings) in the content, excluding any whitespace. This may be a good alternative to `.WordCount`  for Japanese and other CJK languages where a word-split by spaces makes no sense.  {{< gh 1266 >}}

+    * `RawContent`: Raw Markdown as a string. One use case may be of embedding remarkjs.com slides.

+    * `IsHome`: tells the truth about whether you're on the home page or not.

+### Improvements

+* `hugo server` now builds ~30%+ faster by rendering to memory instead of disk. To get the old behavior, start the server with `--renderToDisk=true`.

+* Hugo now supports dynamic reloading of the config file when watching.

+* We now use a custom-built `LazyFileReader` for reading file contents, which means we don't read media files in `/content` into memory anymore -- and file reading is now performed in parallel on multicore PCs. {{< gh 1181 >}}

+* Hugo is now built with `Go 1.5` which, among many other improvements, have fixed the last known data race in Hugo. {{< gh 917 >}}

+* Paginator now also supports page groups. {{< gh 1274 >}}

+* Markdown improvements:

+    * Hugo now supports GitHub-flavoured markdown code fences for highlighting for `md`-files (Blackfriday rendered markdown) and `mmark` files (MMark rendered markdown). {{< gh 362 1258 >}}

+    * Several new Blackfriday options are added:

+        * Option to disable Blackfriday's `Smartypants`.

+        * Option for Blackfriday to open links in a new window/tab. {{< gh 1220 >}}

+        * Option to disable Blackfriday's LaTeX style dashes {{< gh 1231 >}}

+        * Definition lists extension support.

+* `Scratch` now has built-in `map` support.

+* We now fall back to `link title` for the default page sort. {{< gh 1299 >}}

+* Some notable new configuration options:

+    *  `IgnoreFiles` can be set with a list of Regular Expressions that matches files to be ignored during build. {{< gh 1189 >}}

+    * `PreserveTaxonomyNames`, when set to `true`, will preserve what you type as the taxonomy name both in the folders created and the taxonomy `key`, but it will be normalized for the URL.  {{< gh 1180 >}}

+* `hugo gen` can now generate man files, bash auto complete and markdown documentation

+* Hugo will now make suggestions when a command is mistyped

+* Shortcodes now have a boolean `.IsNamedParams` property. {{< gh 1597 >}}

+### New Template Features

+* All template engines:

+    * The new `dict` function that could be used to pass maps into a template. {{< gh 1463 >}}

+    * The new `pluralize` and `singularize` template funcs.

+    * The new `base64Decode` and `base64Encode` template funcs.

+    * The `sort` template func now accepts field/key chaining arguments and pointer values. {{< gh 1330 >}}

+    * Several fixes for `slicestr` and `substr`, most importantly, they now have full `utf-8`-support. {{< gh 1190 1333 1347 >}}

+    * The new `last` template function allows the user to select the last `N` items of a slice. {{< gh 1148 >}}

+    * The new `after` func allows the user to select the items after the `Nth` item. {{< gh 1200 >}}

+    * Add `time.Time` type support to the `where`, `ge`, `gt`, `le`, and `lt` template functions.

+    * It is now possible to use constructs like `where Values ".Param.key" nil` to filter pages that doesn't have a particular parameter. {{< gh 1232 >}}

+    * `getJSON`/`getCSV`: Add retry on invalid content. {{< gh 1166 >}}

+    *   The new `readDir` func lists local files. {{< gh 1204 >}}

+    * The new `safeJS` function allows the embedding of content into JavaScript contexts in Go templates.

+    * Get the main site RSS link from any page by accessing the `.Site.RSSLink` property. {{< gh 1566 >}}

+* Ace templates:

+    * Base templates now also works in themes. {{< gh 1215 >}}.

+    * And now also on Windows. {{< gh 1178 >}}

+* Full support for Amber templates including all template functions.

+* A built-in template for Google Analytics. {{< gh 1505 >}}

+* Hugo is now shipped with new built-in shortcodes: {{< gh 1576 >}}

+  * `youtube` for YouTube videos

+  * `vimeo` for Vimeo videos

+  * `gist` for GitHub gists

+  * `tweet` for Twitter Tweets

+  * `speakerdeck` for Speakerdeck slides

+### Bugfixes

+* Fix data races in page sorting and page reversal. These operations are now also cached. {{< gh 1293 >}}

+* `page.HasMenuCurrent()` and `node.HasMenuCurrent()` now work correctly in multi-level nested menus.

+* Support `Fish and Chips` style section titles. Previously, this would end up as  `Fish And Chips`. Now, the first character is made toupper, but the rest are preserved as-is. {{< gh 1176 >}}

+* Hugo now removes superfluous p-tags around shortcodes. {{< gh 1148 >}}

+### Notices

+* `hugo server` will watch by default now.

+* Some fields and methods were deprecated in `0.14`. These are now removed, so the error message isn't as friendly if you still use the old values. So please change:

+    *   `getJson` to `getJSON`, `getCsv` to `getCSV`, `safeHtml` to

+  `safeHTML`, `safeCss` to `safeCSS`, `safeUrl` to `safeURL`, `Url` to `URL`,

+  `UrlPath` to `URLPath`, `BaseUrl` to `BaseURL`, `Recent` to `Pages`.

+### Known Issues

+Using the Hugo v0.15 32-bit Windows or ARM binary, running `hugo server` would crash or hang due to a [memory alignment issue](https://golang.org/pkg/sync/atomic/#pkg-note-BUG) in [Afero](https://github.com/spf13/afero).  The bug was discovered shortly after the v0.15.0 release and has since been [fixed](https://github.com/spf13/afero/pull/23) by {{< gh "@tpng" >}}.  If you encounter this bug, you may either compile Hugo v0.16-DEV from source, or use the following solution/workaround:

+* **64-bit Windows users: Please use [hugo_0.15_windows_amd64.zip](https://github.com/gohugoio/hugo/releases/download/v0.15/hugo_0.15_windows_amd64.zip)** (amd64 == x86-64).  It is only the 32-bit hugo_0.15_windows_386.zip that crashes/hangs (see {{< gh 1621 >}} and {{< gh 1628 >}}).

+* **32-bit Windows and ARM users: Please run `hugo server --renderToDisk` as a workaround** until Hugo v0.16 is released (see [“hugo server” returns runtime error on armhf](https://discourse.gohugo.io/t/hugo-server-returns-runtime-error-on-armhf/2293) and {{< gh 1716 >}}).

--- /dev/null

+++ b/content/news/0-17.md

@@ -1,0 +1,92 @@

+---

+author: bep

+categories: ["Releases"]

+date: 2016-10-07T13:54:06-04:00

+description: "Hugo now supports multilingual sites with the most simple and elegant experience."

+link: ""

+title: "October Release: Hugo is going global"

+draft: false

+---

+Hugo is going global with our 0.17 release.  We put a lot of thought into how we could extend Hugo

+to support multilingual websites with the most simple and elegant experience. Hugo's multilingual

+capabilities rival the best web and documentation software, but Hugo's experience is unmatched.

+If you have a single language website, the simple Hugo experience you already love is unchanged.

+Adding additional languages to your website is simple and straightforward. Hugo has been completely

+internally rewritten to be multilingual aware with translation and internationalization features

+embedded throughout Hugo.

+Hugo continues its trend of each release being faster than the last. It's quite a challenge to consistently add

+significant new functionality and simultaneously dramatically improve performance. {{<gh "@bep">}} has made it

+his personal mission to apply the Go mantra of "Enable more. Do less" to Hugo. Hugo's consistent improvement

+is a testament to his brilliance and his dedication to his craft. Hugo additionally benefits from the

+performance improvements from the Go team in the Go 1.7 release.

+This release represents **over 300 contributions by over 70 contributors** to

+the main Hugo code base. Since last release Hugo has **gained 2000 stars, 50 new

+contributors and 20 additional themes.**

+Hugo now has:

+* 12,000 stars on GitHub

+* 370+ contributors

+* 110+ themes

+{{<gh "@bep" >}} continues to lead the project with the lionshare of contributions

+and reviews. A special thanks to {{<gh "@bep" >}} and {{<gh "@abourget" >}} for their

+considerable work on multilingual support.

+A big welcome to newcomers {{<gh "@MarkDBlackwell" >}}, {{<gh "@bogem" >}} and

+{{<gh "@g3wanghc" >}} for their critical contributions.

+### Highlights

+**Multilingual Support:**

+Hugo now supports multiple languages side-by-side. A single site can now have multiple languages rendered with

+full support for translation and i18n.

+**Performance:**

+Hugo is faster than ever! Hugo 0.17 is not only our fastest release, it's also the most efficient.

+Hugo 0.17 is **nearly twice as fast as Hugo 0.16** and uses about 10% less memory.

+This means that the same site will build in nearly half the time it took with Hugo 0.16.

+For the first time Hugo sites are averaging well under 1ms per rendered content.

+**Docs overhaul:**

+This release really focused on improving the documentation. [Gohugo.io](http://gohugo.io) is

+more accurate and complete than ever.

+**Support for macOS Sierra**

+### New Features

+* Multilingual support {{<gh 2303>}}

+* Allow content expiration {{<gh 2137 >}}

+* New templates functions:

+  * `querify` function to generate query strings inside templates {{<gh 2257>}}

+  * `htmlEscape` and `htmlUnescape` template functions {{<gh 2287>}}

+  * `time` converts a timestamp string into a time.Time structure {{<gh 2329>}}

+### Enhancements

+* Render the shortcodes as late as possible {{<gh 0xed0985404db4630d1b9d3ad0b7e41fb186ae0112>}}

+* Remove unneeded casts in page.getParam {{<gh 2186 >}}

+* Automatic page date fallback {{<gh 2239>}}

+* Enable safeHTMLAttr {{<gh 2234>}}

+* Add TODO list support for markdown {{<gh 2296>}}

+* Make absURL and relURL accept any type {{<gh 2352>}}

+* Suppress 'missing static' error {{<gh 2344>}}

+* Make summary, wordcount etc. more efficient {{<gh 2378>}}

+* Better error reporting in `hugo convert` {{<gh 2440>}}

+* Reproducible builds thanks to govendor {{<gh 2461>}}

+### Fixes

+* Fix shortcode in markdown headers {{<gh 2210 >}}

+* Explicitly bind livereload to hugo server port {{<gh 2205>}}

+* Fix Emojify for certain text patterns {{<gh 2198>}}

+* Normalize file name to NFC {{<gh 2259>}}

+* Ignore emacs temp files {{<gh 2266>}}

+* Handle symlink change event {{<gh 2273>}}

+* Fix panic when using URLize {{<gh 2274>}}

+* `hugo import jekyll`: Fixed target path location check {{<gh 2293>}}

+* Return all errors from casting in templates {{<gh 2356>}}

+* Fix paginator counter on x86-32 {{<gh 2420>}}

+* Fix half-broken self-closing shortcodes {{<gh 2499>}}

--- /dev/null

+++ b/content/news/0-18.md

@@ -1,0 +1,113 @@

+---

+date: 2016-12-30T13:54:02-04:00

+categories: ["Releases"]

+description: "The primary new feature in Hugo 0.18 is that every piece of content is now a Page."

+link: ""

+title: "December Hugo Release"

+draft: false

+author: bep

+---

+Hugo 0.18.1 is a bug fix release fixing some issues introduced in Hugo 0.18:

+* Fix 32-bit binaries {{<gh 2847 >}}

+* Fix issues with `preserveTaxonomyNames` {{<gh 2809 >}}

+* Fix `.URL` for taxonomy pages when `uglyURLs=true` {{<gh 2819 >}}

+* Fix `IsTranslated` and `Translations` for node pages {{<gh 2812 >}}

+* Make template error messages more verbose {{<gh 2820 >}}

+## **0.18.0** December 19th 2016

+Today, we're excited to release the much-anticipated Hugo 0.18!

+We're heading towards the end of the year 2016, and we can look back on three releases and a steady growing community around the project.

+This release includes **over 220 contributions by nearly 50 contributors** to the main codebase.

+Since the last release, Hugo has **gained 1750 stars and 27 additional themes**.

+Hugo now has:

+- 13750+ stars

+- 408+ contributors

+- 137+ themes

+{{< gh "@bep" >}} once again took the lead of Hugo and contributed a significant amount of additions.

+Also a big shoutout to {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition,

+and also a big thanks to {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their contributions.

+We wish you all a Merry Christmas and a Happy New Year.<br>

+*The Hugo team*

+### Highlights

+The primary new feature in Hugo 0.18 is that every piece of content is now a `Page` ({{<gh 2297>}}). This means that every page, including the homepage, can have a content file with front matter.

+Not only is this a much simpler model to understand, it is also faster and paved the way for several important new features:

+* Enable proper titles for Nodes {{<gh 1051>}}

+* Sitemap.xml should include nodes, as well as pages {{<gh 1303>}}

+* Document homepage content workaround {{<gh 2240>}}

+* Allow home page to be easily authored in markdown {{<gh 720>}}

+* Minimalist website with homepage as content {{<gh 330>}}

+Hugo again continues its trend of each release being faster than the last. It's quite a challenge to consistently add significant new functionality and simultaneously dramatically improve performance. Running [this benchmark]( https://github.com/bep/hugo-benchmark) with [these sites](https://github.com/bep/hugo-benchmark/tree/master/sites) (renders to memory) shows about   60% reduction in time spent and 30% reduction in memory usage compared to Hugo 0.17.

+### Other New Features

+* Every `Page` now has a `Kind` property. Since everything is a `Page` now, the `Kind` is used to differentiate different kinds of pages.

+  Possible values are `page`, `home`, `section`, `taxonomy`, and `taxonomyTerm`.

+  (Internally, we also define `RSS`, `sitemap`, `robotsTXT`, and `404`, but those have no practical use for end users at the moment since they are not included in any collections.)

+* Add a `GitInfo` object to `Page` if `enableGitInfo` is set. It then also sets `Lastmod` for the given `Page` to the author date provided by Git. {{<gh 2291>}}

+* Implement support for alias templates  {{<gh 2533 >}}

+* New template functions:

+  * Add `imageConfig` function {{<gh 2677>}}

+  * Add `sha256` function {{<gh 2762>}}

+  * Add `partialCached` template function {{<gh 1368>}}

+* Add shortcode to display Instagram images {{<gh 2690>}}

+* Add `noChmod` option to disable perm sync {{<gh 2749>}}

+* Add `quiet` build mode {{<gh 1218>}}

+### Notices

+* `.Site.Pages` will now contain *several kinds of pages*, including regular pages, sections, taxonomies, and the home page.

+  If you want a specific kind of page, you can filter it with `where` and `Kind`.

+  `.Site.RegularPages` is a shortcut to the page collection you have been used to getting.

+* `RSSlink` is now deprecated.  Use `RSSLink` instead.

+  Note that in Hugo 0.17 both of them existed, so there is a fifty-fifty chance you will not have to do anything

+  (if you use a theme, the chance is close to 0), and `RSSlink` will still work for two Hugo versions.

+### Fixes

+* Revise the `base` template lookup logic so it now better matches the behavior of regular templates, making it easier to override the master templates from the theme {{<gh 2783>}}

+* Add workaround for `block` template crash.

+  Block templates are very useful, but there is a bug in Go 1.6 and 1.7 which makes the template rendering crash if you use the block template in more complex scenarios.

+  This is fixed in the upcoming Go 1.8, but Hugo adds a temporary workaround in Hugo 0.18. {{<gh 2549>}}

+* All the `Params` configurations are now case insensitive {{<gh 1129>}} {{<gh 2590>}} {{<gh 2615>}}

+* Make RawContent raw again {{<gh 2601>}}

+* Fix archetype title and date handling {{<gh 2750>}}

+* Fix TOML archetype parsing in `hugo new` {{<gh 2745>}}

+* Fix page sorting when weight is zero {{<gh 2673>}}

+* Fix page names that contain dot {{<gh 2555>}}

+* Fix RSS Title regression {{<gh 2645>}}

+* Handle ToC before handling shortcodes {{<gh 2433>}}

+* Only watch relevant themes dir {{<gh 2602>}}

+* Hugo new content creates TOML slices with closing bracket on new line {{<gh 2800>}}

+### Improvements

+* Add page information to error logging in rendering {{<gh 2570>}}

+* Deprecate `RSSlink` in favor of `RSSLink`

+* Make benchmark command more useful {{<gh 2432>}}

+* Consolidate the `Param` methods {{<gh 2590>}}

+* Allow to set cache dir in config file

+* Performance improvements:

+  * Avoid repeated Viper loads of `sectionPagesMenu` {{<gh 2728>}}

+  * Avoid reading from Viper for path and URL funcs {{<gh 2495>}}

+  * Add `partialCached` template function. This can be a significant performance boost if you have complex partials that does not need to be rerendered for every page. {{<gh 1368>}}

+### Documentation Updates

+* Update roadmap {{<gh 2666>}}

+* Update multilingual example {{<gh 2417>}}

+* Add a "Deployment with rsync" tutorial page {{<gh 2658>}}

+* Refactor `/docs` to use the `block` keyword {{<gh 2226>}}

--- /dev/null

+++ b/content/news/0-19.md

@@ -1,0 +1,82 @@

+---

+date: 2017-02-27T13:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.19 brings native Emacs Org-mode content support, and Hugo has its own Twitter account"

+link: ""

+title: "February Release"

+draft: false

+author: budparr

+---

+We're happy to announce the first release of Hugo in 2017.

+This release represents **over 180 contributions by over 50 contributors** to the main Hugo code base. Since last release Hugo has **gained 1450 stars, 35 new contributors, and 15 additional themes.**

+Hugo now has:

+* 15200+ stars

+* 470+ contributors

+* 151+ themes

+Furthermore, Hugo has its own Twitter account ([@gohugoio](https://twitter.com/gohugoio)) where we share bite-sized news and themes from the Hugo community.

+{{< gh "@bep" >}} leads the Hugo development and once again contributed a significant amount of additions. Also a big shoutout to  {{< gh "@chaseadamsio" >}} for the Emacs Org-mode support, {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition, {{< gh "@fj" >}}for his work on revising the `params` handling in Hugo, and {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their ongoing contributions.

+### Highlights

+Hugo `0.19` brings native Emacs Org-mode content support ({{<gh 1483>}}), big thanks to {{< gh "@chaseadamsio" >}}.

+Also, a considerably amount of work have been put into cleaning up the Hugo source code, in an issue titled [Refactor the globals out of site build](https://github.com/gohugoio/hugo/issues/2701). This is not immediately visible to the Hugo end user, but will speed up future development.

+Hugo `0.18` was bringing full-parallel page rendering, so workarounds depending on rendering order did not work anymore, and pages with duplicate target paths (common examples would be `/index.md` or `/about/index.md`) would now conflict with the home page or the section listing.

+With Hugo `0.19`, you can control this behaviour by turning off page types you do not want ({{<gh 2534 >}}). In its most extreme case, if you put the below setting in your [`config.toml`](/getting-started/configuration/), you will get **nothing!**:

+```

+disableKinds = ["page", "home", "section", "taxonomy", "taxonomyTerm", "RSS", "sitemap", "robotsTXT", "404"]

+```

+### Other New Features

+* Add ability to sort pages by front matter parameters, enabling easy custom "top 10" page lists. {{<gh 3022 >}}

+* Add `truncate` template function {{<gh 2882 >}}

+* Add `now` function, which replaces the now deprecated `.Now` {{<gh 2859 >}}

+* Make RSS item limit configurable {{<gh 3035 >}}

+### Enhancements

+*  Enhance `.Param` to permit arbitrarily nested parameter references {{<gh 2598 >}}

+* Use `Page.Params` more consistently when adding metadata {{<gh 3033 >}}

+* The `sectionPagesMenu` feature ("Section menu for the lazy blogger") is now integrated with the section content pages. {{<gh 2974 >}}

+* Hugo `0.19` is compiled with Go 1.8!

+* Make template funcs like `findRE` and friends more liberal in what argument types they accept {{<gh 3018 >}} {{<gh 2822 >}}

+* Improve generation of OpenGraph date tags {{<gh 2979 >}}

+### Notes

+* `sourceRelativeLinks` is now deprecated and will be removed in Hugo `0.21` if  no one is stepping up to the plate and fixes and maintains this feature. {{<gh 3028 >}}

+### Fixes

+* Fix `.Site.LastChange` on sites where the default sort order is not chronological. {{<gh 2909 >}}

+* Fix regression of `.Truncated` evaluation in manual summaries. {{<gh 2989 >}}

+* Fix `preserveTaxonomyNames` regression {{<gh 3070 >}}

+* Fix issue with taxonomies when only some have content page {{<gh 2992 >}}

+* Fix instagram shortcode panic on invalid ID {{<gh 3048 >}}

+* Fix subtle data race in `getJSON` {{<gh 3045 >}}

+* Fix deadlock in cached partials {{<gh 2935 >}}

+* Avoid double-encoding of paginator URLs {{<gh 2177 >}}

+* Allow tilde in URLs {{<gh 2177 >}}

+* Fix `.Site.Pages` handling on live reloads {{<gh 2869 >}}

+* `UniqueID` now correctly uses the fill file path from the content root to calculate the hash, and is finally ... unique!

+* Discard current language based on `.Lang()`, go get translations correct for paginated pages. {{<gh 2972 >}}

+* Fix infinite loop in template AST handling for recursive templates  {{<gh 2927 >}}

+* Fix issue with watching when config loading fails {{<gh 2603 >}}

+* Correctly flush the imageConfig on live-reload {{<gh 3016 >}}

+* Fix parsing of TOML arrays in front matter {{<gh 2752 >}}

+### Docs

+* Add tutorial "How to use Google Firebase to host a Hugo site" {{<gh 3007 >}}

+* Improve documentation for menu rendering {{<gh 3056 >}}

+* Revise GitHub Pages deployment tutorial {{<gh 2930 >}}

--- /dev/null

+++ b/content/news/0-20-1.md

@@ -1,0 +1,14 @@

+---

+date: 2017-04-13T13:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.20.1 is a bug fix release, fixing some important regressions introduced in 0.20"

+link: ""

+title: "April Release"

+draft: false

+author: bep

+---

+*   Fix logic for base template in work dir vs in the theme [#3323](//github.com/gohugoio/hugo/issues/3323)

+*   camelCased templates (partials, shortcodes etc.) not found [#3333](//github.com/gohugoio/hugo/issues/3333)

+*   Live-reload fails with `_index.md` with paginator [#3315](//github.com/gohugoio/hugo/issues/3315)

+*   `rssURI` WARNING always shown [#3319](//github.com/gohugoio/hugo/issues/3319)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-20-2.md

@@ -1,0 +1,44 @@

+---

+date: 2017-04-16T13:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.20.2 adds support for plain text partials included into HTML templates"

+link: ""

+title: "April Release"

+draft: false

+author: bep

+---

+Hugo `0.20.2` adds support for plain text partials included into `HTML` templates. This was a side-effect of the big new [Custom Output Format](https://gohugo.io/extras/output-formats/) feature in `0.20`, and while the change was intentional and there was an ongoing discussion about fixing it in [#3273](//github.com/gohugoio/hugo/issues/3273), it did break some themes. There were valid workarounds for these themes, but we might as well get it right.

+The most obvious use case for this is inline `CSS` styles, which you now can do without having to name your partials with a `html` suffix.

+A simple example:

+In `layouts/partials/mystyles.css`:

+    body {

+    	background-color: {{ .Param "colors.main" }}

+    }

+Then in `config.toml` (note that by using the `.Param` lookup func, we can override the color in a page’s front matter if we want):

+    [params]

+    [params.colors]

+    main = "green"

+    text = "blue"

+And then in `layouts/partials/head.html` (or the partial used to include the head section into your layout):

+    <head>

+        <style type="text/css">

+        {{ partial "mystyles.css" . | safeCSS }}

+        </style>

+    </head>

+Of course, `0.20` also made it super-easy to create external `CSS` stylesheets based on your site and page configuration. A simple example:

+Add “CSS” to your home page’s `outputs` list, create the template `/layouts/index.css` using Go template syntax for the dynamic parts, and then include it into your `HTML` template with:

+    {{ with  .OutputFormats.Get "css" }}

+    <link rel="{{ .Rel }}" type="{{ .MediaType.Type }}" href="{{ .Permalink |  safeURL }}">

+    {{ end }}`

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-20-3.md

@@ -1,0 +1,25 @@

+---

+date: 2017-04-24T13:53:58-04:00

+categories: ["Releases"]

+description: "This is a bug-fix release with one important fix. But it also adds some harness around GoReleaser"

+link: ""

+title: "April Release"

+draft: false

+author: bep

+---

+This is a bug-fix release with one important fix. But it also adds some harness around [GoReleaser](https://github.com/goreleaser/goreleaser) to automate the Hugo release process. Big thanks to [@caarlos0](https://github.com/caarlos0) for great and super-fast support fixing issues along the way.

+Hugo now has:

+* 16619&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 458&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 156&#43; [themes](http://themes.gohugo.io/)

+## Enhancement

+* Automate the Hugo release process [550eba64](https://github.com/gohugoio/hugo/commit/550eba64705725eb54fdb1042e0fb4dbf6f29fd0) [@bep](https://github.com/bep) [#3358](https://github.com/gohugoio/hugo/issues/3358)

+## Fix

+* Fix handling of zero-length files [9bf5c381](https://github.com/gohugoio/hugo/commit/9bf5c381b6b3e69d4d8dbfd7a40074ac44792bbf) [@bep](https://github.com/bep) [#3355](https://github.com/gohugoio/hugo/issues/3355)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-20-4.md

@@ -1,0 +1,23 @@

+---

+date: 2017-04-24T17:53:58-04:00

+categories: ["Releases"]

+description: "This is the second bug-fix release of the day, fixing a couple of issues related to the new release scripts"

+link: ""

+title: "April Release"

+draft: false

+author: bep

+---

+This is the second bug-fix release of the day, fixing a couple of issues related to the new release scripts.

+Hugo now has:

+* 16626&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 457&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 156&#43; [themes](http://themes.gohugo.io/)

+## Fixes

+* Fix statically linked binaries [275bcf56](https://github.com/gohugoio/hugo/commit/275bcf566c7cb72367d4423cf4810319311ff680) [@munnerz](https://github.com/munnerz) [#3382](https://github.com/gohugoio/hugo/issues/3382)

+* Filename change in Hugo 0.20.3 binaries [#3385](https://github.com/gohugoio/hugo/issues/3385)

+* Fix version calculation [cb3c6b6f](https://github.com/gohugoio/hugo/commit/cb3c6b6f7670f85189a4a3637e7132901d1ed6e9) [@bep](https://github.com/bep)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-20-5.md

@@ -1,0 +1,11 @@

+---

+date: 2017-04-25T17:53:58-04:00

+categories: ["Releases"]

+description: ""

+link: ""

+title: "April Release"

+draft: false

+author: bep

+---

+This is a bug-fix release which fixes the version number of `0.20.4` (which wrongly shows up as `0.21-DEV`) ([#3388](https://github.com/gohugoio/hugo/issues/3388)).

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-20-6.md

@@ -1,0 +1,23 @@

+---

+date: 2017-04-27T17:53:58-04:00

+categories: ["Releases"]

+description: ""

+link: ""

+title: "April Release"

+draft: false

+author: bep

+---

+There have been some [shouting on discuss.gohugo.io](https://discuss.gohugo.io/t/index-md-is-generated-in-subfolder-index-index-html-hugo-0-20/6338/15) about some broken sites after the release of Hugo `0.20`. This release reintroduces the old behaviour, making  `/my-blog-post/index.md` work as expected.

+Hugo now has:

+* 16675&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 456&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 156&#43; [themes](http://themes.gohugo.io/)

+## Fixes

+* Avoid index.md in /index/index.html [#3396](https://github.com/gohugoio/hugo/issues/3396)

+* Make missing GitInfo a WARNING [b30ca4be](https://github.com/gohugoio/hugo/commit/b30ca4bec811dbc17e9fd05925544db2b75e0e49) [@bep](https://github.com/bep) [#3376](https://github.com/gohugoio/hugo/issues/3376)

+* Fix some of the fpm fields for deb [3bd1d057](https://github.com/gohugoio/hugo/commit/3bd1d0571d5f2f6bf0dc8f90a8adf2dbfcb2fdfd) [@anthonyfok](https://github.com/anthonyfok)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-20-7.md

@@ -1,0 +1,22 @@

+---

+date: 2017-05-03T17:53:58-04:00

+categories: ["Releases"]

+description: "This just fixes an issue with the release scripts, no change in the binaries"

+link: ""

+title: "May Release"

+draft: false

+author: bep

+---

+This just fixes an issue with the release scripts, no change in the binaries.

+Hugo now has:

+* 16782&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 458&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 156&#43; [themes](http://themes.gohugo.io/)

+## Fix

+* Push the tag before goreleaser is run [3682bf52](https://github.com/gohugoio/hugo/commit/3682bf527989e86d9da32d76809306cb576383e8) [@bep](https://github.com/bep) [#3405](https://github.com/gohugoio/hugo/issues/3405)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-20.md

@@ -1,0 +1,71 @@

+---

+date: 2017-04-10T13:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.20 introduces the powerful and long sought after feature Custom Output Formats"

+link: ""

+title: "April Release"

+draft: false

+author: bep

+---

+Hugo `0.20` introduces the powerful and long sought after feature [Custom Output Formats](http://gohugo.io/extras/output-formats/); Hugo isn’t just that “static HTML with an added RSS feed” anymore. _Say hello_ to calendars, e-book formats, Google AMP, and JSON search indexes, to name a few ( [#2828](//github.com/gohugoio/hugo/issues/2828) ).

+This release represents **over 180 contributions by over 30 contributors** to the main Hugo code base. Since last release Hugo has **gained 1100 stars, 20 new contributors and 5 additional themes.**

+Hugo now has:

+*   16300+ stars

+*   495+ contributors

+*   156+ themes

+[@bep](//github.com/bep) still leads the Hugo development with his witty Norwegian humor, and once again contributed a significant amount of additions. Also a big shoutout to [@digitalcraftsman](//github.com/digitalcraftsman) for his relentless work on keeping the documentation and the themes site in pristine condition, and [@moorereason](//github.com/moorereason) and [@bogem](//github.com/bogem) for their ongoing contributions.

+## Other Highlights

+[@bogem](//github.com/bogem) has also contributed TOML as an alternative and much simpler format for language/i18n files ([#3200](//github.com/gohugoio/hugo/issues/3200)). A feature you will appreciate when you start to work on larger translations.

+Also, there have been some important updates in the Emacs Org-mode handling: [@chaseadamsio](//github.com/chaseadamsio) has fixed the newline-handling ( [#3126](//github.com/gohugoio/hugo/issues/3126) ) and [@clockoon](//github.com/clockoon) has added basic footnote support.

+Worth mentioning is also the ongoing work that [@rdwatters](//github.com/rdwatters) and [@budparr](//github.com/budparr) is doing to re-do the [gohugo.io](https://gohugo.io/) site, including a total restructuring and partial rewrite of the documentation. It is getting close to finished, and it looks fantastic!

+## Notes

+*   `RSS` description in the built-in template is changed from full `.Content` to `.Summary`. This is a somewhat breaking change, but is what most people expect from their RSS feeds. If you want full content, please provide your own RSS template.

+*   The deprecated `.RSSlink` is now removed. Use `.RSSLink`.

+*   `RSSUri` is deprecated and will be removed in a future Hugo version, replace it with an output format definition.

+*   The deprecated `.Site.GetParam` is now removed, use `.Site.Param`.

+*   Hugo does no longer append missing trailing slash to `baseURL` set as a command line parameter, making it consistent with how it behaves from site config. [#3262](//github.com/gohugoio/hugo/issues/3262)

+## Enhancements

+*   Hugo `0.20` is built with Go 1.8.1.

+*   Add `.Site.Params.mainSections` that defaults to the section with the most pages. Plan is to get themes to use this instead of the hardcoded `blog` in `where` clauses. [#3206](//github.com/gohugoio/hugo/issues/3206)

+*   File extension is now configurable. [#320](//github.com/gohugoio/hugo/issues/320)

+*   Impove `markdownify` template function performance. [#3292](//github.com/gohugoio/hugo/issues/3292)

+*   Add taxonomy terms’ pages to `.Data.Pages` [#2826](//github.com/gohugoio/hugo/issues/2826)

+*   Change `RSS` description from full `.Content` to `.Summary`.

+*   Ignore “.” dirs in `hugo --cleanDestinationDir` [#3202](//github.com/gohugoio/hugo/issues/3202)

+*   Allow `jekyll import` to accept both `2006-01-02` and `2006-1-2` date format [#2738](//github.com/gohugoio/hugo/issues/2738)

+*   Raise the default `rssLimit` [#3145](//github.com/gohugoio/hugo/issues/3145)

+*   Unify section list vs single template lookup order [#3116](//github.com/gohugoio/hugo/issues/3116)

+*   Allow `apply` to be used with the built-in Go template funcs `print`, `printf` and `println`. [#3139](//github.com/gohugoio/hugo/issues/3139)

+## Fixes

+*   Fix deadlock in `getJSON` [#3211](//github.com/gohugoio/hugo/issues/3211)

+*   Make sure empty terms pages are created. [#2977](//github.com/gohugoio/hugo/issues/2977)

+*   Fix base template lookup order for sections [#2995](//github.com/gohugoio/hugo/issues/2995)

+*   `URL` fixes:

+    *   Fix pagination URLs with `baseURL` with sub-root and `canonifyUrls=false` [#1252](//github.com/gohugoio/hugo/issues/1252)

+    *   Fix pagination URL for resources with “.” in name [#2110](//github.com/gohugoio/hugo/issues/2110) [#2374](//github.com/gohugoio/hugo/issues/2374) [#1885](//github.com/gohugoio/hugo/issues/1885)

+    *   Handle taxonomy names with period [#3169](//github.com/gohugoio/hugo/issues/3169)

+    *   Handle `uglyURLs` ambiguity in `Permalink` [#3102](//github.com/gohugoio/hugo/issues/3102)

+    *   Fix `Permalink` for language-roots wrong when `uglyURLs` is `true` [#3179](//github.com/gohugoio/hugo/issues/3179)

+    *   Fix misc case issues for `URLs` [#1641](//github.com/gohugoio/hugo/issues/1641)

+    *   Fix for taxonomies URLs when `uglyUrls=true` [#1989](//github.com/gohugoio/hugo/issues/1989)

+    *   Fix empty `RSSLink` for list pages with content page. [#3131](//github.com/gohugoio/hugo/issues/3131)

+*   Correctly identify regular pages on the form “my_index_page.md” [#3234](//github.com/gohugoio/hugo/issues/3234)

+*   `Exit -1` on `ERROR` in global logger [#3239](//github.com/gohugoio/hugo/issues/3239)

+*   Document hugo `help command` [#2349](//github.com/gohugoio/hugo/issues/2349)

+*   Fix internal `Hugo` version handling for bug fix releases. [#3025](//github.com/gohugoio/hugo/issues/3025)

+*   Only return `RSSLink` for pages that actually have a RSS feed. [#1302](//github.com/gohugoio/hugo/issues/1302)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-21.md

@@ -1,0 +1,104 @@

+---

+date: 2017-05-22T17:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.21 brings full support for shortcodes per Output Format, the last vital piece of that puzzle"

+link: ""

+title: "May Release"

+draft: false

+author: bep

+---

+Hugo `0.21` brings full support for shortcodes per [Output Format](https://gohugo.io/extras/output-formats/) ([#3220](https://github.com/gohugoio/hugo/issues/3220)), the last vital piece of that puzzle. This is especially useful for `Google AMP` with its many custom media tags.

+This release represents **126 contributions by 29 contributors** to the main Hugo code base. Since last main release Hugo has **gained 850 stars and 7 additional themes**.

+Hugo now has:

+* 17156&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 457&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 163&#43; [themes](http://themes.gohugo.io/)

+[@bep](https://github.com/bep) leads the Hugo development with a significant amount of contributions, but also a big shoutout to [@moorereason](https://github.com/moorereason), [@bogem](https://github.com/bogem), and [@munnerz](https://github.com/munnerz) for their ongoing contributions. And as always a big thanks to [@digitalcraftsman](https://github.com/digitalcraftsman) for his relentless work on keeping the documentation and the themes site in pristine condition.

+## Other Highlights

+On a more technical side, [@moorereason](https://github.com/moorereason) and [@bep](https://github.com/bep) have introduced namespaces for Hugo&#39;s many template funcs ([#3042](https://github.com/gohugoio/hugo/issues/3042) ). There are so many now, and adding more into that big pile would be a sure path toward losing control.  Now they are nicely categorised into namespaces with its own tests and examples, with an API that the documentation site can use to make sure it is correct and up-to-date.

+## Notes

+* The deprecated `.Extension`, `.Now` and `.TargetPath` will now `ERROR` [544f0a63](https://github.com/gohugoio/hugo/commit/544f0a6394b0e085d355e8217fc5bb3d96c12a98) [@bep](https://github.com/bep)

+* The config settings and flags `disable404`, `disableRSS`, `disableSitemap`, `disableRobotsTXT` are now deprecated. Use `disableKinds`. [5794a265](https://github.com/gohugoio/hugo/commit/5794a265b41ffdeebfd8485eecf65cf4088d49d6) [@bep](https://github.com/bep) [#3345](https://github.com/gohugoio/hugo/issues/3345)

+## Enhancements

+### Templates

+* Log a WARNING on wrong usage of `IsSet` [38661c17](https://github.com/gohugoio/hugo/commit/38661c17bb8c31c9f31ee18f8eba5e3bfddd5574) [@moorereason](https://github.com/moorereason) [#3092](https://github.com/gohugoio/hugo/issues/3092)

+* Add support for ellipsed paginator navigator, making paginators with lots of pages more compact  [b6ea492b](https://github.com/gohugoio/hugo/commit/b6ea492b7a6325d04d44eeb00a990a3a0e29e0c0) [@bep](https://github.com/bep) [#3466](https://github.com/gohugoio/hugo/issues/3466)

+* Add support for interfaces to `intersect` [f1c29b01](https://github.com/gohugoio/hugo/commit/f1c29b017bbd88e701cd5151dd186e868672ef89) [@moorereason](https://github.com/moorereason) [#1952](https://github.com/gohugoio/hugo/issues/1952)

+* Add `NumFmt` function [93b3b138](https://github.com/gohugoio/hugo/commit/93b3b1386714999d716e03b131f77234248f1724) [@moorereason](https://github.com/moorereason) [#1444](https://github.com/gohugoio/hugo/issues/1444)

+* Add template function namespaces [#3418](https://github.com/gohugoio/hugo/issues/3418)  [#3042](https://github.com/gohugoio/hugo/issues/3042)  [@moorereason](https://github.com/moorereason)  [@bep](https://github.com/bep)

+* Add translation links to the default sitemap template [90d3fbf1](https://github.com/gohugoio/hugo/commit/90d3fbf1da93a279cfe994a226ae82cf5441deab) [@rayjolt](https://github.com/rayjolt) [#2569](https://github.com/gohugoio/hugo/issues/2569)

+* Allow text partials in HTML templates and the other way around [1cf29200](https://github.com/gohugoio/hugo/commit/1cf29200b4bb0a9c006155ec76759b7f4b1ad925) [@bep](https://github.com/bep) [#3273](https://github.com/gohugoio/hugo/issues/3273)

+### Output

+* Refactor site rendering with an &#34;output format context&#34;. In this release, this is used for shortcode handling only, but this paves the way for future niceness [1e4d082c](https://github.com/gohugoio/hugo/commit/1e4d082cf5b92fedbc60b1b4f0e9d1ee6ec45e33) [@bep](https://github.com/bep) [#3397](https://github.com/gohugoio/hugo/issues/3397)  [2bcbf104](https://github.com/gohugoio/hugo/commit/2bcbf104006e0ec03be4fd500f2519301d460f8c) [@bep](https://github.com/bep) [#3220](https://github.com/gohugoio/hugo/issues/3220)

+### Core

+* Handle `shortcode` per `Output Format` [af72db80](https://github.com/gohugoio/hugo/commit/af72db806f2c1c0bf1dfe5832275c41eeba89906) [@bep](https://github.com/bep) [#3220](https://github.com/gohugoio/hugo/issues/3220)

+* Improve shortcode error message [58d9cbd3](https://github.com/gohugoio/hugo/commit/58d9cbd31bcf7c296a39860fd7e566d10faaff28) [@bep](https://github.com/bep)

+* Avoid `index.md` in `/index/index.html` [fea4fd86](https://github.com/gohugoio/hugo/commit/fea4fd86a324bf9679df23f8289887d91b42e919) [@bep](https://github.com/bep) [#3396](https://github.com/gohugoio/hugo/issues/3396)

+* Make missing `GitInfo` a `WARNING` [5ad2f176](https://github.com/gohugoio/hugo/commit/5ad2f17693a9860be76ef8089c8728d2b59d6b04) [@bep](https://github.com/bep) [#3376](https://github.com/gohugoio/hugo/issues/3376)

+* Prevent decoding `pageParam` in common cases [e98f885b](https://github.com/gohugoio/hugo/commit/e98f885b8af27f5473a89d31d0b1f02e61e8a5ec) [@bogem](https://github.com/bogem)

+* Ignore non-source files on partial rebuild [b5b6e81c](https://github.com/gohugoio/hugo/commit/b5b6e81c0269abf9b0f4bc6a127744a25344e5c6) [@xofyarg](https://github.com/xofyarg) [#3325](https://github.com/gohugoio/hugo/issues/3325)

+* Log `WARNING` only on unknown `/data` files [ab692e73](https://github.com/gohugoio/hugo/commit/ab692e73dea3ddfe979c88ee236cc394e47e82f1) [@bep](https://github.com/bep) [#3361](https://github.com/gohugoio/hugo/issues/3361)

+* Avoid processing the same notify event twice [3b677594](https://github.com/gohugoio/hugo/commit/3b67759495c9268c30e6ba2d8c7e3b75d52d2960) [@bep](https://github.com/bep)

+* Only show `rssURI` deprecation `WARNING` if it is actually set [cfd3af8e](https://github.com/gohugoio/hugo/commit/cfd3af8e691119461effa4385251b9d3818e2291) [@bep](https://github.com/bep) [#3319](https://github.com/gohugoio/hugo/issues/3319)

+### Docs

+* Add documentation on slug translation [635b3bb4](https://github.com/gohugoio/hugo/commit/635b3bb4eb873978c7d52e6c0cb85da0c4d25299) [@xavib](https://github.com/xavib)

+* Replace `cdn.mathjax.org` with `cdnjs.cloudflare.com` [4b637ac0](https://github.com/gohugoio/hugo/commit/4b637ac041d17b22187f5ccd0f65461f0065aaa9) [@takuti](https://github.com/takuti)

+* Add notes about some output format behaviour [162d3a58](https://github.com/gohugoio/hugo/commit/162d3a586d36cabf6376a76b096fd8b6414487ae) [@jpatters](https://github.com/jpatters)

+* Add `txtpen` as alternative commenting service [7cdc244a](https://github.com/gohugoio/hugo/commit/7cdc244a72de4c08edc0008e37aec83d945dccdf) [@rickyhan](https://github.com/rickyhan)

+### Other

+* Embed `Page` in `WeightedPage` [ebf677a5](https://github.com/gohugoio/hugo/commit/ebf677a58360126d8b9a1e98d086aa4279f53181) [@bep](https://github.com/bep) [#3435](https://github.com/gohugoio/hugo/issues/3435)

+* Improve the detection of untranslated strings [a40d1f6e](https://github.com/gohugoio/hugo/commit/a40d1f6ed2aedddc99725658993258cd557640ed) [@bogem](https://github.com/bogem) [#2607](https://github.com/gohugoio/hugo/issues/2607)

+* Make first letter of the Hugo commands flags&#39; usage lowercase [f0f69d03](https://github.com/gohugoio/hugo/commit/f0f69d03c551acb8ac2eeedaad579cf0b596f9ef) [@bogem](https://github.com/bogem)

+* Import `Octopress` image tag in `Jekyll importer` [5f3ad1c3](https://github.com/gohugoio/hugo/commit/5f3ad1c31985450fab8d6772e9cbfcb57cf5cc53) [@buynov](https://github.com/buynov)

+## Fixes

+### Templates

+*  Do not lower case template names [6d2ea0f7](https://github.com/gohugoio/hugo/commit/6d2ea0f7d7e8a54b8edfc36e52ff74266c30dc27) [@bep](https://github.com/bep) [#3333](https://github.com/gohugoio/hugo/issues/3333)

+### Output

+* Fix output format mixup in example [10287263](https://github.com/gohugoio/hugo/commit/10287263f529181d3169668b044cb84e2e3b049a) [@bep](https://github.com/bep) [#3481](https://github.com/gohugoio/hugo/issues/3481)

+* Fix base theme vs project base template logic [077005e5](https://github.com/gohugoio/hugo/commit/077005e514b1ed50d84ceb90c7c72f184cb04521) [@bep](https://github.com/bep) [#3323](https://github.com/gohugoio/hugo/issues/3323)

+### Core

+* Render `404` in default language only [154e18dd](https://github.com/gohugoio/hugo/commit/154e18ddb9ad205055d5bd4827c87f3f0daf499f) [@mitchchn](https://github.com/mitchchn) [#3075](https://github.com/gohugoio/hugo/issues/3075)

+* Fix `RSSLink` vs `RSS` `Output Format` [e682fcc6](https://github.com/gohugoio/hugo/commit/e682fcc62233b47cf5bdcaf598ac0657ef089471) [@bep](https://github.com/bep) [#3450](https://github.com/gohugoio/hugo/issues/3450)

+* Add default config for `ignoreFiles`, making that option work when running in server mode [42f4ce15](https://github.com/gohugoio/hugo/commit/42f4ce15a9d68053da36f9efcf7a7d975cc59559) [@chaseadamsio](https://github.com/chaseadamsio)

+* Fix output formats override when no outputs definition given [6e2f2dd8](https://github.com/gohugoio/hugo/commit/6e2f2dd8d3ca61c92a2ee8824fbf05cadef08425) [@bep](https://github.com/bep) [#3447](https://github.com/gohugoio/hugo/issues/3447)

+* Fix handling of zero-length files [0e87b18b](https://github.com/gohugoio/hugo/commit/0e87b18b66d2c8ba9e2abc429630cb03f5b093d6) [@bep](https://github.com/bep) [#3355](https://github.com/gohugoio/hugo/issues/3355)

+* Must recreate `Paginator` on live-reload [45c74526](https://github.com/gohugoio/hugo/commit/45c74526686f6a2afa02bcee767d837d6b9dd028) [@bep](https://github.com/bep) [#3315](https://github.com/gohugoio/hugo/issues/3315)

+### Docs

+* Fix incorrect path in `templates/list` [27e88154](https://github.com/gohugoio/hugo/commit/27e88154af2dd9af6d0523d6e67b612e6336f91c) [@MunifTanjim](https://github.com/MunifTanjim)

+* Fixed incorrect specification of directory structure [a28fbca6](https://github.com/gohugoio/hugo/commit/a28fbca6dcfa80b6541f5ef6c8c12cd1804ae9ed) [@TejasQ](https://github.com/TejasQ)

+* Fix `bash` command in `tutorials/github-pages-blog` [c9976155](https://github.com/gohugoio/hugo/commit/c99761555c014e4d041438d5d7e53a6cbaee4492) [@hansott](https://github.com/hansott)

+* Fix `.Data.Pages` range in example [b5e32eb6](https://github.com/gohugoio/hugo/commit/b5e32eb60993b4656918af2c959ae217a68c461e) [@hxlnt](https://github.com/hxlnt)

+### Other

+* Fix data race in live-reload close, avoiding some rare panics [355736ec](https://github.com/gohugoio/hugo/commit/355736ec357c81dfb2eb6851ee019d407090c5ec) [@bep](https://github.com/bep) [#2625](https://github.com/gohugoio/hugo/issues/2625)

+* Skip `.git` directories in file scan [94b5be67](https://github.com/gohugoio/hugo/commit/94b5be67fc73b87d114d94a7bb1a33ab997f30f1) [@bogem](https://github.com/bogem) [#3468](https://github.com/gohugoio/hugo/issues/3468)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-22-1.md

@@ -1,0 +1,36 @@

+---

+date: 2017-06-13T17:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.22.1 fixes a couple of issues reported after the 0.22 release"

+link: ""

+title: "June Release"

+draft: false

+author: bep

+---

+Hugo `0.22.1` fixes a couple of issues reported after the [0.22 release](https://github.com/gohugoio/hugo/releases/tag/v0.22) Monday. Most importantly a fix for detecting regular subfolders below the root-sections.

+Also, we forgot to adapt the `permalink settings` with support for nested sections, which made that feature less useful than it could be.

+With this release you can configure **permalinks with sections** like this:

+**First level only:**

+```toml

+[permalinks]

+blog = ":section/:title"

+```

+**Nested (all levels):**

+```toml

+[permalinks]

+blog = ":sections/:title"

+```

+## Fixes

+* Fix section logic for root folders with subfolders [a30023f5](https://github.com/gohugoio/hugo/commit/a30023f5cbafd06034807255181a5b7b17f3c25f) [@bep](https://github.com/bep) [#3586](https://github.com/gohugoio/hugo/issues/3586)

+* Support sub-sections in permalink settings [1f26420d](https://github.com/gohugoio/hugo/commit/1f26420d392a5ab4c7b7fe1911c0268b45d01ab8) [@bep](https://github.com/bep) [#3580](https://github.com/gohugoio/hugo/issues/3580)

+* Adjust rlimit to 64000 [ff54b6bd](https://github.com/gohugoio/hugo/commit/ff54b6bddcefab45339d8dc2b13776b92bdc04b9) [@bep](https://github.com/bep) [#3582](https://github.com/gohugoio/hugo/issues/3582)

+* Make error on setting rlimit a warning only [629e1439](https://github.com/gohugoio/hugo/commit/629e1439e819a7118ae483381d4634f16d3474dd) [@bep](https://github.com/bep) [#3582](https://github.com/gohugoio/hugo/issues/3582)

+* Revert: Remove the rlimit tweaking on macOS [26aa06a3](https://github.com/gohugoio/hugo/commit/26aa06a3db57ab7134a900d641fa2976f7971520) [@bep](https://github.com/bep) [#3582](https://github.com/gohugoio/hugo/issues/3582)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-22.md

@@ -1,0 +1,88 @@

+---

+date: 2017-06-12T17:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.22 brings nested sections, by popular demand and a long sought after feature"

+link: ""

+title: "June Release"

+draft: false

+author: bep

+---

+Hugo `0.22` brings **nested sections**, by popular demand and a long sought after feature ([#465](https://github.com/gohugoio/hugo/issues/465)).  We are still low on documentation for this great feature, but [@bep](https://github.com/bep)  has been kind enough to accompany his implementation with a [demo site](http://hugotest.bep.is/).

+This release represents **58 contributions by 10 contributors** to the main Hugo code base. Since last release Hugo has **gained 420 stars and 2 additional themes.**

+[@bep](https://github.com/bep) still leads the Hugo development with his witty Norwegian humor, and once again contributed a significant amount of additions. But also a big shoutout to [@bogem](https://github.com/bogem), [@moorereason](https://github.com/moorereason), and [@onedrawingperday](https://github.com/onedrawingperday) for their ongoing contributions. And as always big thanks to [@digitalcraftsman](https://github.com/digitalcraftsman) for his relentless work on keeping the documentation and the themes site in pristine condition.

+Hugo now has:

+* 17576&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 455&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 165&#43; [themes](http://themes.gohugo.io/)

+## Other Highlights

+`.Site.GetPage` can now also be used to get regular pages ([#2844](https://github.com/gohugoio/hugo/issues/2844)):

+```go

+{{ (.Site.GetPage "page" "blog" "mypost.md" ).Title }}

+```

+Also, considerable work has been put into writing automated benchmark tests for the site builds, and we&#39;re happy to report that although this release comes with fundamental structural changes, this version is -- in general -- even faster than the previous. It’s quite a challenge to consistently add significant new functionality and simultaneously maintain the stellar performance Hugo is famous for.

+## Notes

+`.Site.Sections` is replaced. We have reworked how sections work in Hugo, they can now be nested and are no longer taxonomies. If you use the old collection, you should get detailed upgrade instructions in the log when you run `hugo`. For more information, see this [demo site](http://hugotest.bep.is/).

+## Enhancements

+### Templates

+* Add `uint` support to `In` [b82cd82f](https://github.com/gohugoio/hugo/commit/b82cd82f1198a371ed94bda7faafe22813f4cb29) [@moorereason](https://github.com/moorereason)

+* Support interfaces in `union` [204c3a9e](https://github.com/gohugoio/hugo/commit/204c3a9e32fcf6617ede978e35d3e2e89a5b491c) [@moorereason](https://github.com/moorereason) [#3411](https://github.com/gohugoio/hugo/issues/3411)

+* Add `uniq` function [e28d9aa4](https://github.com/gohugoio/hugo/commit/e28d9aa42c3429d22fe254e69e4605aaf1e684f3) [@adiabatic](https://github.com/adiabatic)

+* Handle `template.HTML` and friends in `ToInt` [4113693a](https://github.com/gohugoio/hugo/commit/4113693ac1b275f3a40aa5c248269340ef9b57f6) [@moorereason](https://github.com/moorereason) [#3308](https://github.com/gohugoio/hugo/issues/3308)

+### Core

+* Make the `RSS feed` use the date for the node it represents [f1da5a15](https://github.com/gohugoio/hugo/commit/f1da5a15a37666ee59350d6600a8c14c1383f5bc) [@bep](https://github.com/bep) [#2708](https://github.com/gohugoio/hugo/issues/2708)

+* Enable `nested sections` [b3968939](https://github.com/gohugoio/hugo/commit/b39689393ccb8434d9a57658a64b77568c718e99) [@bep](https://github.com/bep) [#465](https://github.com/gohugoio/hugo/issues/465)

+* Add test for &#34;no 404&#34; in `sitemap` [8aaec644](https://github.com/gohugoio/hugo/commit/8aaec644a90d09bd7f079d35d382f76bb4ed35db) [@bep](https://github.com/bep) [#3563](https://github.com/gohugoio/hugo/issues/3563)

+* Support regular pages in `.Site.GetPage` [e0c2e798](https://github.com/gohugoio/hugo/commit/e0c2e798201f75ae6e9a81a7442355288c2d141b) [@bep](https://github.com/bep) [#2844](https://github.com/gohugoio/hugo/issues/2844)

+[#3082](https://github.com/gohugoio/hugo/issues/3082)

+### Performance

+* Add site building benchmarks [8930e259](https://github.com/gohugoio/hugo/commit/8930e259d78cba4041b550cc51a7f40bc91d7c20) [@bep](https://github.com/bep) [#3535](https://github.com/gohugoio/hugo/issues/3535)

+* Add a cache to `GetPage` which makes it much faster [50d11138](https://github.com/gohugoio/hugo/commit/50d11138f3e18b545c15fadf52f7b0b744bf3e7c) [@bep](https://github.com/bep)

+* Speed up `GetPage` [fbb78b89](https://github.com/gohugoio/hugo/commit/fbb78b89df8ccef8f0ab26af00aa45d35c1ee2cf) [@bep](https://github.com/bep) [#3503](https://github.com/gohugoio/hugo/issues/3503)

+* Add BenchmarkFrontmatterTags [3d9c4f51](https://github.com/gohugoio/hugo/commit/3d9c4f513b0443648d7e88995e351df1739646d2) [@bep](https://github.com/bep) [#3464](https://github.com/gohugoio/hugo/issues/3464)

+* Add `benchSite.sh` to make it easy to run Hugo performance benchmarks [d74452cf](https://github.com/gohugoio/hugo/commit/d74452cfe8f69a85ec83e05481e16bebf199a5cb) [@bep](https://github.com/bep)

+* Cache language config [4aff2b6e](https://github.com/gohugoio/hugo/commit/4aff2b6e7409a308f30cff1825fec02991e0d56a) [@bep](https://github.com/bep)

+* Temporarily revert to BurntSushi for `TOML` front matter handling; it is currently much faster [0907a5c1](https://github.com/gohugoio/hugo/commit/0907a5c1c293755e6bf297246f07888448d81f8b) [@bep](https://github.com/bep) [#3541](https://github.com/gohugoio/hugo/issues/3541) [#3464](https://github.com/gohugoio/hugo/issues/3464)

+* Add a simple partitioned lazy cache [87203139](https://github.com/gohugoio/hugo/commit/87203139c38e0b992c96d7b8a23c7730649c68e5) [@bep](https://github.com/bep)

+### Other

+* Add `noindex` tag to HTML generated by Hugo aliases [d5ab7f08](https://github.com/gohugoio/hugo/commit/d5ab7f087d967b30e7de7d789e6ad3091b42f1f7) [@onedrawingperday](https://github.com/onedrawingperday)

+* Update Go versions [bde807bd](https://github.com/gohugoio/hugo/commit/bde807bd1e560fb4cc765c0fc22132db7f8a0801) [@bep](https://github.com/bep)

+* Remove the `rlimit` tweaking on `macOS` [bcd32f10](https://github.com/gohugoio/hugo/commit/bcd32f1086c8c604fb22a7496924e41cc46b1605) [@bep](https://github.com/bep) [#3512](https://github.com/gohugoio/hugo/issues/3512)

+### Docs

+* Rewrite “Archetypes” article [@davidturnbull](https://github.com/davidturnbull) [#3543](https://github.com/gohugoio/hugo/pull/3543/)

+* Remove Unmaintaned Frontends from Tools. [f41f7282](https://github.com/gohugoio/hugo/commit/f41f72822251c9a31031fd5b3dda585c57c8b028) [@onedrawingperday](https://github.com/onedrawingperday)

+## Fixes

+### Core

+* Improve `live-reload` on directory structure changes making removal of directories or pasting new content directories into  `/content` just work [fe901b81](https://github.com/gohugoio/hugo/commit/fe901b81191860b60e6fcb29f8ebf87baef2ee79) [@bep](https://github.com/bep) [#3570](https://github.com/gohugoio/hugo/issues/3570)

+* Respect `disableKinds=[&#34;sitemap&#34;]` [69d92dc4](https://github.com/gohugoio/hugo/commit/69d92dc49cb8ab9276ab013d427ba2d9aaf9135d) [@bep](https://github.com/bep) [#3544](https://github.com/gohugoio/hugo/issues/3544)

+* Fix `disablePathToLower` regression [5be04486](https://github.com/gohugoio/hugo/commit/5be0448635fdf5fe6b1ee673e869f2b9baf1a5c6) [@bep](https://github.com/bep) [#3374](https://github.com/gohugoio/hugo/issues/3374)

+* Fix `ref`/`relref` issue with duplicate base filenames [612f6e3a](https://github.com/gohugoio/hugo/commit/612f6e3afe0510c31f70f3621f3dc8ba609dade4) [@bep](https://github.com/bep) [#2507](https://github.com/gohugoio/hugo/issues/2507)

+### Docs

+* Fix parameter name in `YouTube` shortcode section [37e37877](https://github.com/gohugoio/hugo/commit/37e378773fbc127863f2b7a389d5ce3a14674c73) [@zivbk1](https://github.com/zivbk1)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-23.md

@@ -1,0 +1,45 @@

+---

+date: 2017-06-16T17:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.23 is mainly a release that handles all the small changes needed to get Hugo moved to a GitHub organisation"

+link: ""

+title: "June Release"

+draft: false

+author: bep

+---

+Hugo `0.23` is mainly a release that handles all the small changes needed to get Hugo moved to a GitHub organisation: [gohugoio](https://github.com/gohugoio), but it also contains a couple of important fixes that makes this an update worth-while for all.

+Hugo now has:

+* 17739&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 494&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 165&#43; [themes](http://themes.gohugo.io/)

+## Fixes

+* Fix handling of duplicate footnotes [a9e551a1](https://github.com/gohugoio/hugo/commit/a9e551a100e60a603210ee083103dd73369d6a98) [@bep](https://github.com/bep) [#1912](https://github.com/gohugoio/hugo/issues/1912)

+*  Add support for spaces in project folder for `GitInfo` #3533 #3552

+## GitHub organisation related changes

+* Update layout references to gohugoio/hugo [66d4850b](https://github.com/gohugoio/hugo/commit/66d4850b89db293dc58e828de784037f06c6c8dc) [@bep](https://github.com/bep)

+* Update content references to gohugoio/hugo [715ff1f8](https://github.com/gohugoio/hugo/commit/715ff1f87406edf27738c8c0f52fe185fa974ee8) [@bep](https://github.com/bep)

+* Add note on updates for rpm-based distros [52a0cea6](https://github.com/gohugoio/hugo/commit/52a0cea65de7b75ae1662abe3dec36fca3604617) [@daftaupe](https://github.com/daftaupe)

+* Update logo link in README [ccb8300d](https://github.com/gohugoio/hugo/commit/ccb8300d380636d75a39f4133284eb0109e836c3) [@bep](https://github.com/bep)

+* Remove docs building from CI builds [214dbdfb](https://github.com/gohugoio/hugo/commit/214dbdfb6f016d21415bc1ed511a37a084238878) [@bep](https://github.com/bep)

+* Adjust docs path [729be807](https://github.com/gohugoio/hugo/commit/729be8074bddb58c9111f32c55cc769e49cd0d5a) [@bep](https://github.com/bep)

+* Add docs as submodule [6cee0dfe](https://github.com/gohugoio/hugo/commit/6cee0dfe53899d433afc3c173a87d56265904cb0) [@bep](https://github.com/bep)

+* Update Gitter link in README [fbb25014](https://github.com/gohugoio/hugo/commit/fbb25014e1306ce7127d53e5fc4fc49867790336) [@bep](https://github.com/bep)

+* Change Windows build badge link, take #3 [86543d6a](https://github.com/gohugoio/hugo/commit/86543d6a50251b40540ebd0b851d45eb99d017c7) [@bep](https://github.com/bep)

+* Update Windows build link [e6ae32a0](https://github.com/gohugoio/hugo/commit/e6ae32a0ba75b9894418227e87391defbb1b3b49) [@bep](https://github.com/bep)

+* Update links in CONTRIBUTING.md due to the org transition [95386544](https://github.com/gohugoio/hugo/commit/95386544e858949a2baa414f395f30aaf66a6257) [@digitalcraftsman](https://github.com/digitalcraftsman)

+* Update source path in Dockerfile due to the org transition [7b99fb9f](https://github.com/gohugoio/hugo/commit/7b99fb9f1ca8381457afe9d8e953a388b8ada182) [@digitalcraftsman](https://github.com/digitalcraftsman)

+* Update clone folder in appveyor.yml due to the org transition [d531d17b](https://github.com/gohugoio/hugo/commit/d531d17b3be0b14faf4934611e01ac3289e37835) [@digitalcraftsman](https://github.com/digitalcraftsman)

+* Update import path in snapcraft.yaml due to the org transition [9266bf9d](https://github.com/gohugoio/hugo/commit/9266bf9d4c24592b875a7f6b92f761b4cea40879) [@digitalcraftsman](https://github.com/digitalcraftsman)

+* Run gofmt to get imports in line vs gohugoio/hugo [873a6f18](https://github.com/gohugoio/hugo/commit/873a6f18851bcda79d562ff6c02e1109e8e31a88) [@bep](https://github.com/bep)

+* Update Makefile vs gohugoio/hugo [f503d76a](https://github.com/gohugoio/hugo/commit/f503d76a3b2719bbb65ab9df5595d0dbc871fae9) [@bep](https://github.com/bep)

+* Update README to point to gohugoio/hugo [93643860](https://github.com/gohugoio/hugo/commit/93643860c9db10c6c32176b17cc83f1c317279bd) [@bep](https://github.com/bep)

+* Update examples to point to gohugoio/hugo [db46bcf8](https://github.com/gohugoio/hugo/commit/db46bcf82d060656d4bc731550e63ec9cf8576f2) [@bep](https://github.com/bep)

+* Update textual references in Go source to point to gohugoio/hugo [c17ad675](https://github.com/gohugoio/hugo/commit/c17ad675e8fcdb2db40fc50816b8f016bc14294c) [@bep](https://github.com/bep)

+* Update import paths to gohugoio/hugo [d8717cd4](https://github.com/gohugoio/hugo/commit/d8717cd4c74e80ea8e20adead9321412a2d76022) [@bep](https://github.com/bep)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-24-1.md

@@ -1,0 +1,21 @@

+---

+date: 2017-06-24T17:53:58-04:00

+categories: ["Releases"]

+description: "This release fixes some important archetype-related regressions from Hugo 0.24"

+link: ""

+title: "June Release"

+draft: false

+author: bep

+---

+This release fixes some important **archetype-related regressions** from the recent Hugo 0.24-release.

+## Fixes

+* Fix archetype regression when no archetype file [4294dd8d](https://github.com/gohugoio/hugo/commit/4294dd8d9d22bd8107b7904d5389967da1f83f27) [@bep](https://github.com/bep) [#3626](https://github.com/gohugoio/hugo/issues/3626)

+* Preserve shortcodes in archetype templates [b63e4ee1](https://github.com/gohugoio/hugo/commit/b63e4ee198c875b73a6a9af6bb809589785ed589) [@bep](https://github.com/bep) [#3623](https://github.com/gohugoio/hugo/issues/3623)

+* Fix handling of timezones with positive UTC offset (e.g., +0800) in TOML [0744f81e](https://github.com/gohugoio/hugo/commit/0744f81ec00bb8888f59d6c8b5f57096e07e70b1) [@bep](https://github.com/bep) [#3628](https://github.com/gohugoio/hugo/issues/3628)

+## Enhancements

+* Create default archetype on new site [bfa336d9](https://github.com/gohugoio/hugo/commit/bfa336d96173377b9bbe2298dbd101f6a718c174) [@bep](https://github.com/bep) [#3626](https://github.com/gohugoio/hugo/issues/3626)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-24.md

@@ -1,0 +1,73 @@

+---

+date: 2017-06-17T17:53:58-04:00

+categories: ["Releases"]

+description: "The Revival of the Archetypes!"

+link: ""

+title: "June Release"

+draft: false

+author: bep

+---

+> "A feature that could be the name of the next Indiana Jones movie deserves its own release," says [@bep](https://github.com/bep).

+Hugo now handles the **archetype files as Go templates**. This means that the issues with sorting and lost comments are long gone. This also means that you will have to supply all values, including title and date. But this also opens up a lot of new windows.

+A fictional example for the section `newsletter` and the archetype file `archetypes/newsletter.md`:

+```markdown

+---

+title: "{{ replace .TranslationBaseName "-" " " | title }}"

+date: {{ .Date }}

+draft: true

+---

+**Insert Lead paragraph here.**

+<!--more-->

+## New Cool Posts

+{{ range first 10 ( where .Site.RegularPages "Type" "cool" ) }}

+* {{ .Title }}

+{{ end }}

+```

+And then create a new post with:

+```bash

+hugo new newsletter/the-latest-cool.stuff.md

+```

+**Note:** the site will only be built if the `.Site` is in use in the archetype file, and this can be time consuming for big sites.

+**Hot Tip:** If you set the `newContentEditor` configuration variable to an editor on your `PATH`, the newly created article will be opened.

+The above _newsletter type archetype_ illustrates the possibilities: The full Hugo `.Site` and all of Hugo&#39;s template funcs can be used in the archetype file.

+**Also, Hugo now supports archetype files for all content formats, not just markdown.**

+Hugo now has:

+* 17839&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 493&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 166&#43; [themes](http://themes.gohugo.io/)

+## Notes

+* Archetype files now need to be complete, including `title` and `date`.

+* The `-f` (format) flag in `hugo new` is removed: Now use the archetype files as is.

+## Enhancements

+* Support extension-less media types. The motivation behind this change is to support Netlify&#39;s `_redirects` files, so we can generate server-side redirects for the Hugo docs site. See [this commit](https://github.com/gohugoio/hugoDocs/commit/c1ab9894e8292e0a74c43bbca2263b1fb3840f9e) to see how we configured that. [0f40e1fa](https://github.com/gohugoio/hugo/commit/0f40e1fadfca2276f65adefa6d7d5d63aef9160a) [@bep](https://github.com/bep) [#3614](https://github.com/gohugoio/hugo/issues/3614)

+* Add `disableAliases` [516e6c6d](https://github.com/gohugoio/hugo/commit/516e6c6dc5733cdaf985317d58eedbc6ec0ef2f7) [@bep](https://github.com/bep) [#3613](https://github.com/gohugoio/hugo/issues/3613)

+* Support non-md files as archetype files [19f2e729](https://github.com/gohugoio/hugo/commit/19f2e729135af700c5d4aa06e7b3540e6d4847fd) [@bep](https://github.com/bep) [#3597](https://github.com/gohugoio/hugo/issues/3597) [#3618](https://github.com/gohugoio/hugo/issues/3618)

+* Identify extension-less text types as text [c43b512b](https://github.com/gohugoio/hugo/commit/c43b512b4700f76ac77f12d632bb030c3a241393) [@bep](https://github.com/bep) [#3614](https://github.com/gohugoio/hugo/issues/3614)

+* Add `.Site` to the archetype templates [662e12f3](https://github.com/gohugoio/hugo/commit/662e12f348a638a6fcc92a416ee7f7c2a7ef8792) [@bep](https://github.com/bep) [#1629](https://github.com/gohugoio/hugo/issues/1629)

+* Use archetype template as-is as a Go template [422057f6](https://github.com/gohugoio/hugo/commit/422057f60709696bbbd1c38c9ead2bf114d47e31) [@bep](https://github.com/bep) [#452](https://github.com/gohugoio/hugo/issues/452) [#1629](https://github.com/gohugoio/hugo/issues/1629)

+* Update links to new discuss URL [4aa12390](https://github.com/gohugoio/hugo/commit/4aa1239070bb9d4324d3582f3e809b702a59d3ac) [@bep](https://github.com/bep)

+## Fixes

+* Fix error handling for `JSON` front matter [fb53987a](https://github.com/gohugoio/hugo/commit/fb53987a4ff2acb9da8dec6ec7b11924d37352ce) [@bep](https://github.com/bep) [#3610](https://github.com/gohugoio/hugo/issues/3610)

+* Fix handling of quoted brackets in `JSON` front matter [3183b9a2](https://github.com/gohugoio/hugo/commit/3183b9a29d8adac962fbc73f79b04542f4c4c55d) [@bep](https://github.com/bep) [#3511](https://github.com/gohugoio/hugo/issues/3511)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-25-1.md

@@ -1,0 +1,24 @@

+---

+date: 2017-07-10T17:53:58-04:00

+categories: ["Releases"]

+description: "This is a bug-fix release with a couple of important fixes"

+link: ""

+title: "July Release"

+draft: false

+author: bep

+---

+This is a bug-fix release with a couple of important fixes.

+Hugo now has:

+* 18277+ [stars](https://github.com/gohugoio/hugo/stargazers)

+* 456+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 170+ [themes](http://themes.gohugo.io/)

+## Fixes

+* Fix union when the first slice is empty [dbbc5c48](https://github.com/gohugoio/hugo/commit/dbbc5c4810a04ac06fad7500d88cf5c3bfe0c7fd) [@bep](https://github.com/bep) [#3686](https://github.com/gohugoio/hugo/issues/3686)

+* Navigate to changed on CREATE When working with content from IntelliJ IDE, like WebStorm, every file save is followed by two events: "RENAME" and then "CREATE". [7bcc1ce6](https://github.com/gohugoio/hugo/commit/7bcc1ce659710f2220b400ce3b76e50d2e48b241) [@miltador](https://github.com/miltador)

+* Final (!) fix for issue with escaped JSON front matter [7f82b41a](https://github.com/gohugoio/hugo/commit/7f82b41a24af0fd04d28fbfebf9254766a3c6e6f) [@bep](https://github.com/bep) [#3682](https://github.com/gohugoio/hugo/issues/3682)

+* Fix issue with escaped JSON front matter [84db6c74](https://github.com/gohugoio/hugo/commit/84db6c74a084d2b52117b999d4ec343cd3389a68) [@bep](https://github.com/bep) [#3682](https://github.com/gohugoio/hugo/issues/3682)

\ No newline at end of file

--- /dev/null

+++ b/content/news/0-25.md

@@ -1,0 +1,77 @@

+---

+date: 2017-07-07T17:53:58-04:00

+categories: ["Releases"]

+description: "Hugo 0.25 automatically opens the page you&#39;re working on in the browser"

+link: ""

+title: "July Release"

+draft: false

+author: bep

+---

+Hugo `0.25` is the **Kinder Surprise**: It automatically opens the page you&#39;re working on in the browser, it adds full `AND` and `OR` support in page queries, and you can now have templates per language.

+![Hugo Open on Save](https://cdn-standard5.discourse.org/uploads/gohugo/optimized/2X/6/622088d4a8eacaf62bbbaa27dab19d789e10fe09_1_690x345.gif "Hugo Open on Save")

+If you start with `hugo server --navigateToChanged`, Hugo will navigate to the relevant page on save (see animated GIF). This is extremely useful for site-wide edits. Another very useful feature in this version is the added support for `AND` (`intersect`)  and `OR` (`union`)  filters when combined with `where`.

+Example:

+```go

+{{ $pages := where .Site.RegularPages "Type" "not in" (slice "page" "about") }}

+{{ $pages := $pages | union (where .Site.RegularPages "Params.pinned" true) }}

+{{ $pages := $pages | intersect (where .Site.RegularPages "Params.images" "!=" nil) }}

+```

+The above fetches regular pages not of `page` or `about` type unless they are pinned. And finally, we exclude all pages with no `images` set in Page params.

+This release represents **36 contributions by 12 contributors** to the main Hugo code base. [@bep](https://github.com/bep) still leads the Hugo development with his witty Norwegian humor, and once again contributed a significant amount of additions. But also a big shoutout to [@yihui](https://github.com/yihui), [@anthonyfok](https://github.com/anthonyfok), and [@kropp](https://github.com/kropp) for their ongoing contributions. And as always a big thanks to [@digitalcraftsman](https://github.com/digitalcraftsman) for his relentless work on keeping the documentation and the themes site in pristine condition.

+Hugo now has:

+* 18209&#43; [stars](https://github.com/gohugoio/hugo/stargazers)

+* 455&#43; [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

+* 168&#43; [themes](http://themes.gohugo.io/)

+## Enhancements

+### Templates

+* Add `Pages` support to `intersect` (`AND`) and `union`(`OR`). This makes the `where` template func even more powerful. [ccdd08d5](https://github.com/gohugoio/hugo/commit/ccdd08d57ab64441e93d6861ae126b5faacdb92f) [@bep](https://github.com/bep) [#3174](https://github.com/gohugoio/hugo/issues/3174)

+* Add `math.Log` function. This is very handy for creating tag clouds. [34c56677](https://github.com/gohugoio/hugo/commit/34c566773a1364077e1397daece85b22948dc721) [@artem-sidorenko](https://github.com/artem-sidorenko)

+* Add `WebP` images support [8431c8d3](https://github.com/gohugoio/hugo/commit/8431c8d39d878c18c6b5463d9091a953608df10b) [@bep](https://github.com/bep) [#3529](https://github.com/gohugoio/hugo/issues/3529)

+* Only show post&#39;s own keywords in schema.org [da72805a](https://github.com/gohugoio/hugo/commit/da72805a4304a57362e8e79a01cc145767b027c5) [@brunoamaral](https://github.com/brunoamaral) [#2635](https://github.com/gohugoio/hugo/issues/2635)[#2646](https://github.com/gohugoio/hugo/issues/2646)

+* Simplify the `Disqus` template a little bit (#3655) [eccb0647](https://github.com/gohugoio/hugo/commit/eccb0647821e9db20ba9800da1b4861807cc5205) [@yihui](https://github.com/yihui)

+* Improve the built-in Disqus template (#3639) [2e1e4934](https://github.com/gohugoio/hugo/commit/2e1e4934b60ce8081a7f3a79191ed204f3098481) [@yihui](https://github.com/yihui)

+### Output

+* Support templates per site/language. This is for both regular templates and shortcode templates. [aa6b1b9b](https://github.com/gohugoio/hugo/commit/aa6b1b9be7c9d7322333893b642aaf8c7a5f2c2e) [@bep](https://github.com/bep) [#3360](https://github.com/gohugoio/hugo/issues/3360)

+### Core

+* Extend the sections API [a1d260b4](https://github.com/gohugoio/hugo/commit/a1d260b41a6673adef679ec4e262c5f390432cf5) [@bep](https://github.com/bep) [#3591](https://github.com/gohugoio/hugo/issues/3591)

+* Make `.Site.Sections` return the top level sections [dd9b1baa](https://github.com/gohugoio/hugo/commit/dd9b1baab0cb860a3eb32fd9043bac18cab3f9f0) [@bep](https://github.com/bep) [#3591](https://github.com/gohugoio/hugo/issues/3591)

+* Render `404.html` for all languages [41805dca](https://github.com/gohugoio/hugo/commit/41805dca9e40e9b0952e04d06074e6fc91140495) [@mitchchn](https://github.com/mitchchn) [#3598](https://github.com/gohugoio/hugo/issues/3598)

+### Other

+* Support human-readable `YAML` boolean values in `undraft` [1039356e](https://github.com/gohugoio/hugo/commit/1039356edf747f044c989a5bc0e85d792341ed5d) [@kropp](https://github.com/kropp)

+* `hugo import jekyll` support nested `_posts` directories [7ee1f25e](https://github.com/gohugoio/hugo/commit/7ee1f25e9ef3be8f99c171e8e7982f4f82c13e16) [@coderzh](https://github.com/coderzh) [#1890](https://github.com/gohugoio/hugo/issues/1890)[#1911](https://github.com/gohugoio/hugo/issues/1911)

+* Update `Dockerfile` and add Docker optimizations [118f8f7c](https://github.com/gohugoio/hugo/commit/118f8f7cf22d756d8a894ff93551974a806f2155) [@ellerbrock](https://github.com/ellerbrock)

+* Add Blackfriday `joinLines` extension support (#3574) [a5440496](https://github.com/gohugoio/hugo/commit/a54404968a4b36579797f2e7ff7f5eada94866d9) [@choueric](https://github.com/choueric)

+* add `--initial-header-level=2` to rst2html (#3528) [bfce30d8](https://github.com/gohugoio/hugo/commit/bfce30d85972c27c27e8a2caac9db6315f813298) [@frankbraun](https://github.com/frankbraun)

+* Support open "current content page" in browser [c825a731](https://github.com/gohugoio/hugo/commit/c825a7312131b4afa67ee90d593640dee3525d98) [@bep](https://github.com/bep) [#3643](https://github.com/gohugoio/hugo/issues/3643)

+* Make `--navigateToChanged` more robust on Windows [30e14cc3](https://github.com/gohugoio/hugo/commit/30e14cc31678ddc204b082ab362f86b6b8063881) [@anthonyfok](https://github.com/anthonyfok) [#3645](https://github.com/gohugoio/hugo/issues/3645)

+* Remove the docs submodule [31393f60](https://github.com/gohugoio/hugo/commit/31393f6024416ea1b2e61d1080dfd7104df36eda) [@bep](https://github.com/bep) [#3647](https://github.com/gohugoio/hugo/issues/3647)

+* Use `example.com` as homepage for new theme [aff1ac32](https://github.com/gohugoio/hugo/commit/aff1ac3235b6c075d01f7237addf44fecdd36d82) [@anthonyfok](https://github.com/anthonyfok)

+## Fixes

+### Templates

+* Fix `in` function for JSON arrays [d12cf5a2](https://github.com/gohugoio/hugo/commit/d12cf5a25df00fa16c59f0b2ae282187a398214c) [@bep](https://github.com/bep) [#1468](https://github.com/gohugoio/hugo/issues/1468)

+### Other

+* Fix handling of `JSON` front matter with escaped quotes [e10e51a0](https://github.com/gohugoio/hugo/commit/e10e51a00827b9fdc1bee51439fef05afc529831) [@bep](https://github.com/bep) [#3661](https://github.com/gohugoio/hugo/issues/3661)

+* Fix typo in code comment [56d82aa0](https://github.com/gohugoio/hugo/commit/56d82aa025f4d2edb1dc6315132cd7ab52df649a) [@dvic](https://github.com/dvic)

\ No newline at end of file

--- /dev/null

+++ b/content/news/_index.md

@@ -1,0 +1,3 @@

+---

+title: "Hugo News"

+---

--- /dev/null

+++ b/content/news/press-and-articles.md

@@ -1,0 +1,28 @@

+---

+title: Press and Articles

+linktitle: Press and Articles

+description: A list of articles, blog posts, or tutorials where Hugo is featured.

+date: 2016-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [articles, tutorials, press]

+categories: [news and articles]

+menu:

+  main:

+    parent: "News"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+aliases: [/community/press/]

+toc: false

+notesforauthors: "If adding an item to the articles list, be sure to follow the format of '| [Linked Title]() | Author Name | YYYY-MM-DD |'."

+---

+{{% note "Help Keep This List Up to Date" %}}

+Know of a post, article, or tutorial on Hugo? [Please add it to this list](https://github.com/gohugoio/hugo/edit/master/docs/content/news/press-and-articles.md).

+{{% /note %}}

+Hugo has been featured in the following Blog Posts, Press, and Media.

+{{< articlelist >}}

--- /dev/null

+++ b/content/news/release-notes.md

@@ -1,0 +1,981 @@

+---

+title: Release Notes

+linktitle: Release Notes

+description: See the full list of Hugo release notes since v0.05 in June 2015.

+date: 2016-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [releases]

+draft: false

+aliases: [/meta/release-notes/]

+toc: true

+---

+## **0.20.2** April 16th 2017

+Hugo `0.20.2` adds support for plain text partials included into `HTML` templates. This was a side-effect of the big new [Custom Output Format](/templates/output-formats/) feature in `0.20`, and while the change was intentional and there was an ongoing discussion about fixing it in {{< gh 3273  >}}, it did break some themes. There were valid workarounds for these themes, but we might as well get it right.

+The most obvious use case for this is inline `CSS` styles,  which you now can do without having to name your partials with a `html` suffix.

+A simple example:

+In `layouts/partials/mystyles.css`:

+```css

+body {

+  background-color: {{ .Param "colors.main" }}

+}

+```

+Then in `config.toml` (note that by using the `.Param` lookup func, we can override the color in a page's front matter if we want):

+```toml

+[params]

+[params.colors]

+main = "green"

+text = "blue"

+```

+And then in `layouts/partials/head.html` (or the partial used to include the head section into your layout):

+```html

+<head>

+    <style type="text/css">

+    {{ partial "mystyles.css" . | safeCSS }}

+    </style>

+</head>

+```

+Of course, `0.20` also made it super-easy to create external `CSS` stylesheets based on your site and page configuration. A simple example:

+Add "CSS" to your home page's `outputs` list, create the template `/layouts/index.css` using Go template syntax for the dynamic parts, and then include it into your `HTML` template with:

+```html

+{{ with  .OutputFormats.Get "css" }}

+<link rel="{{ .Rel }}" type="{{ .MediaType.Type }}" href="{{ .Permalink |  safeURL }}">

+{{ end }}`

+```

+## **0.20.1** April 13th 2017

+Hugo `0.20.1` is a bug fix release, fixing some important regressions introduced in `0.20` a couple of days ago:

+* Fix logic for base template in a work directory vs in a theme {{< gh 3323 >}}

+* camelCased templates (partials, shortcodes, etc.) not found {{< gh 3333 >}}

+* LiveReload fails with `_index.md` with paginator {{< gh 3315 >}}

+* `rssURI` WARNING always shown {{< gh 3319 >}}

+See the [full list of closed issues on GitHub](https://github.com/gohugoio/hugo/milestone/16?closed=1).

+## **0.20** April 10th 2017

+Hugo `0.20` introduces the powerful and long sought after feature [Custom Output Formats](/templates/output-formats/)); Hugo isn't just that "static HTML with an added RSS feed" anymore. *Say hello* to calendars, e-book formats, Google AMP, and JSON search indexes, to name a few ({{< gh 2828 >}}).

+This release represents **over 180 contributions by over 30 contributors** to the main Hugo code base. Since last release Hugo has **gained 1100 stars, 20 new contributors and 5 additional themes.**

+Hugo now has:

+* 16300+ stars

+* 495+ contributors

+* 156+ themes

+{{< gh "@bep" >}} still leads the Hugo development with his witty Norwegian humor, and once again contributed a significant amount of additions. Also a big shoutout to {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition, and {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their ongoing contributions.

+### Other Highlights

+{{< gh "@bogem" >}} has also contributed TOML as an alternative and much simpler format for language/i18n files ({{< gh 3200 >}}). A feature you will appreciate when you start to work on larger translations.

+Also, there have been some important updates in the Emacs Org-mode handling: {{< gh "@chaseadamsio" >}} has fixed the newline-handling ({{< gh 3126 >}}) and {{< gh "@clockoon" >}}  has added basic footnote support.

+Worth mentioning is also the ongoing work that {{< gh "@rdwatters" >}} and {{< gh "@budparr" >}} is doing to re-do the [gohugo.io](https://gohugo.io/) site, including a total restructuring and partial rewrite of the documentation. It is getting close to finished, and it looks fantastic!

+### Notes

+* `RSS` description in the built-in template is changed from full `.Content` to `.Summary`. This is a somewhat breaking change, but is what most people expect from their RSS feeds. If you want full content, please provide your own RSS template.

+* The deprecated `.RSSlink` is now removed. Use `.RSSLink`.

+* `RSSUri` is deprecated and will be removed in a future Hugo version, replace it with an output format definition.

+* The deprecated `.Site.GetParam` is now removed, use `.Site.Param`.

+* Hugo does no longer append missing trailing slash to `baseURL` set as a command line parameter, making it consistent with how it behaves from site config. {{< gh 3262 >}}

+### Enhancements

+* Hugo `0.20` is built with Go 1.8.1.

+* Add `.Site.Params.mainSections` that defaults to the section with the most pages. Plan is to get themes to use this instead of the hardcoded `blog` in `where` clauses.  {{< gh 3206 >}}

+* File extension is now configurable. {{< gh 320 >}}

+* Impove `markdownify` template function performance. {{< gh 3292 >}}

+* Add taxonomy terms' pages to `.Data.Pages` {{< gh 2826 >}}

+* Change `RSS` description from full `.Content` to `.Summary`.

+* Ignore "." dirs in `hugo --cleanDestinationDir` {{< gh 3202 >}}

+* Allow `jekyll import` to accept both `2006-01-02` and `2006-1-2` date format {{< gh 2738 >}}

+* Raise the default `rssLimit` {{< gh 3145 >}}

+* Unify section list vs single template lookup order {{< gh 3116 >}}

+* Allow `apply` to be used with the built-in Go template funcs `print`, `printf` and `println`. {{< gh 3139 >}}

+### Fixes

+* Fix deadlock in `getJSON` {{< gh 3211 >}}

+* Make sure empty terms pages are created. {{< gh 2977 >}}

+* Fix base template lookup order for sections {{< gh 2995 >}}

+* `URL` fixes:

+    * Fix pagination URLs with `baseURL` with sub-root and `canonifyUrls=false` {{< gh 1252 >}}

+    * Fix pagination URL for resources with "." in name {{< gh 2110 >}} {{< gh 2374 >}} {{< gh 1885 >}}

+    * Handle taxonomy names with period {{< gh 3169 >}}

+    * Handle `uglyURLs` ambiguity in `Permalink` {{< gh 3102 >}}

+    * Fix `Permalink` for language-roots wrong when `uglyURLs` is `true` {{< gh 3179 >}}

+    * Fix misc case issues for `URLs` {{< gh 1641 >}}

+    * Fix for taxonomies URLs when `uglyUrls=true` {{< gh 1989 >}}

+    * Fix empty `RSSLink` for list pages with content page. {{< gh 3131 >}}

+* Correctly identify regular pages on the form "my_index_page.md" {{< gh 3234 >}}

+*  `Exit -1` on `ERROR` in global logger {{< gh 3239 >}}

+* Document hugo `help command` {{< gh 2349 >}}

+* Fix internal `Hugo` version handling for bug fix releases. {{< gh 3025 >}}

+* Only return `RSSLink` for pages that actually have a RSS feed. {{< gh 1302 >}}

+## **0.19** February 27th 2017

+We're happy to announce the first release of Hugo in 2017.

+This release represents **over 180 contributions by over 50 contributors** to the main Hugo code base. Since last release Hugo has **gained 1450 stars, 35 new contributors, and 15 additional themes.**

+Hugo now has:

+* 15200+ stars

+* 470+ contributors

+* 151+ themes

+Furthermore, Hugo has its own Twitter account ([@gohugoio](https://twitter.com/gohugoio)) where we share bite-sized news and themes from the Hugo community.

+{{< gh "@bep" >}} leads the Hugo development and once again contributed a significant amount of additions. Also a big shoutout to  {{< gh "@chaseadamsio" >}} for the Emacs Org-mode support, {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition, {{< gh "@fj" >}}for his work on revising the `params` handling in Hugo, and {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their ongoing contributions.

+### Highlights

+Hugo `0.19` brings native Emacs Org-mode content support ({{<gh 1483>}}), big thanks to {{< gh "@chaseadamsio" >}}.

+Also, a considerably amount of work have been put into cleaning up the Hugo source code, in an issue titled [Refactor the globals out of site build](https://github.com/gohugoio/hugo/issues/2701). This is not immediately visible to the Hugo end user, but will speed up future development.

+Hugo `0.18` was bringing full-parallel page rendering, so workarounds depending on rendering order did not work anymore, and pages with duplicate target paths (common examples would be `/index.md` or `/about/index.md`) would now conflict with the homepage or the section listing.

+With Hugo `0.19`, you can control this behaviour by turning off page types you do not want ({{<gh 2534 >}}). In its most extreme case, if you put the below setting in your [`config.toml`](/getting-started/configuration/), you will get **nothing!**:

+```

+disableKinds = ["page", "home", "section", "taxonomy", "taxonomyTerm", "RSS", "sitemap", "robotsTXT", "404"]

+```

+### Other New Features

+* Add ability to sort pages by front matter parameters, enabling easy custom "top 10" page lists. {{<gh 3022 >}}

+* Add `truncate` template function {{<gh 2882 >}}

+* Add `now` function, which replaces the now deprecated `.Now` {{<gh 2859 >}}

+* Make RSS item limit configurable {{<gh 3035 >}}

+### Enhancements

+*  Enhance `.Param` to permit arbitrarily nested parameter references {{<gh 2598 >}}

+* Use `Page.Params` more consistently when adding metadata {{<gh 3033 >}}

+* The `sectionPagesMenu` feature ("Section menu for the lazy blogger") is now integrated with the section content pages. {{<gh 2974 >}}

+* Hugo `0.19` is compiled with Go 1.8!

+* Make template funcs like `findRE` and friends more liberal in what argument types they accept {{<gh 3018 >}} {{<gh 2822 >}}

+* Improve generation of OpenGraph date tags {{<gh 2979 >}}

+### Notes

+* `sourceRelativeLinks` is now deprecated and will be removed in Hugo `0.21` if  no one is stepping up to the plate and fixes and maintains this feature. {{<gh 3028 >}}

+### Fixes

+* Fix `.Site.LastChange` on sites where the default sort order is not chronological. {{<gh 2909 >}}

+* Fix regression of `.Truncated` evaluation in manual summaries. {{<gh 2989 >}}

+* Fix `preserveTaxonomyNames` regression {{<gh 3070 >}}

+* Fix issue with taxonomies when only some have content page {{<gh 2992 >}}

+* Fix instagram shortcode panic on invalid ID {{<gh 3048 >}}

+* Fix subtle data race in `getJSON` {{<gh 3045 >}}

+* Fix deadlock in cached partials {{<gh 2935 >}}

+* Avoid double-encoding of paginator URLs {{<gh 2177 >}}

+* Allow tilde in URLs {{<gh 2177 >}}

+* Fix `.Site.Pages` handling on live reloads {{<gh 2869 >}}

+* `UniqueID` now correctly uses the fill file path from the content root to calculate the hash, and is finally ... unique!

+* Discard current language based on `.Lang()`, go get translations correct for paginated pages. {{<gh 2972 >}}

+* Fix infinite loop in template AST handling for recursive templates  {{<gh 2927 >}}

+* Fix issue with watching when config loading fails {{<gh 2603 >}}

+* Correctly flush the imageConfig on live-reload {{<gh 3016 >}}

+* Fix parsing of TOML arrays in front matter {{<gh 2752 >}}

+### Docs

+* Add tutorial "How to use Google Firebase to host a Hugo site" {{<gh 3007 >}}

+* Improve documentation for menu rendering {{<gh 3056 >}}

+* Revise GitHub Pages deployment tutorial {{<gh 2930 >}}

+## **0.18.1** December 30th 2016

+Hugo 0.18.1 is a bug fix release fixing some issues introduced in Hugo 0.18:

+* Fix 32-bit binaries {{<gh 2847 >}}

+* Fix issues with `preserveTaxonomyNames` {{<gh 2809 >}}

+* Fix `.URL` for taxonomy pages when `uglyURLs=true` {{<gh 2819 >}}

+* Fix `IsTranslated` and `Translations` for node pages {{<gh 2812 >}}

+* Make template error messages more verbose {{<gh 2820 >}}

+## **0.18.0** December 19th 2016

+Today, we're excited to release the much-anticipated Hugo 0.18!

+We're heading towards the end of the year 2016, and we can look back on three releases and a steady growing community around the project.

+This release includes **over 220 contributions by nearly 50 contributors** to the main codebase.

+Since the last release, Hugo has **gained 1750 stars and 27 additional themes**.

+Hugo now has:

+- 13750+ stars

+- 408+ contributors

+- 137+ themes

+{{< gh "@bep" >}} once again took the lead of Hugo and contributed a significant amount of additions.

+Also a big shoutout to {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition,

+and also a big thanks to {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their contributions.

+We wish you all a Merry Christmas and a Happy New Year.<br>

+*The Hugo team*

+### Highlights

+The primary new feature in Hugo 0.18 is that every piece of content is now a `Page` ({{<gh 2297>}}). This means that every page, including the homepage, can have a content file with front matter.

+Not only is this a much simpler model to understand, it is also faster and paved the way for several important new features:

+* Enable proper titles for Nodes {{<gh 1051>}}

+* Sitemap.xml should include nodes, as well as pages {{<gh 1303>}}

+* Document homepage content workaround {{<gh 2240>}}

+* Allow homepage to be easily authored in markdown {{<gh 720>}}

+* Minimalist website with homepage as content {{<gh 330>}}

+Hugo again continues its trend of each release being faster than the last. It's quite a challenge to consistently add significant new functionality and simultaneously dramatically improve performance. Running [this benchmark]( https://github.com/bep/hugo-benchmark) with [these sites](https://github.com/bep/hugo-benchmark/tree/master/sites) (renders to memory) shows about   60% reduction in time spent and 30% reduction in memory usage compared to Hugo 0.17.

+### Other New Features

+* Every `Page` now has a `Kind` property. Since everything is a `Page` now, the `Kind` is used to differentiate different kinds of pages.

+  Possible values are `page`, `home`, `section`, `taxonomy`, and `taxonomyTerm`.

+  (Internally, we also define `RSS`, `sitemap`, `robotsTXT`, and `404`, but those have no practical use for end users at the moment since they are not included in any collections.)

+* Add a `GitInfo` object to `Page` if `enableGitInfo` is set. It then also sets `Lastmod` for the given `Page` to the author date provided by Git. {{<gh 2291>}}

+* Implement support for alias templates  {{<gh 2533 >}}

+* New template functions:

+  * Add `imageConfig` function {{<gh 2677>}}

+  * Add `sha256` function {{<gh 2762>}}

+  * Add `partialCached` template function {{<gh 1368>}}

+* Add shortcode to display Instagram images {{<gh 2690>}}

+* Add `noChmod` option to disable perm sync {{<gh 2749>}}

+* Add `quiet` build mode {{<gh 1218>}}

+### Notices

+* `.Site.Pages` will now contain *several kinds of pages*, including regular pages, sections, taxonomies, and the homepage.

+  If you want a specific kind of page, you can filter it with `where` and `Kind`.

+  `.Site.RegularPages` is a shortcut to the page collection you have been used to getting.

+* `RSSlink` is now deprecated.  Use `RSSLink` instead.

+  Note that in Hugo 0.17 both of them existed, so there is a fifty-fifty chance you will not have to do anything

+  (if you use a theme, the chance is close to 0), and `RSSlink` will still work for two Hugo versions.

+### Fixes

+* Revise the `base` template lookup logic so it now better matches the behavior of regular templates, making it easier to override the master templates from the theme {{<gh 2783>}}

+* Add workaround for `block` template crash.

+  Block templates are very useful, but there is a bug in Go 1.6 and 1.7 which makes the template rendering crash if you use the block template in more complex scenarios.

+  This is fixed in the upcoming Go 1.8, but Hugo adds a temporary workaround in Hugo 0.18. {{<gh 2549>}}

+* All the `Params` configurations are now case insensitive {{<gh 1129>}} {{<gh 2590>}} {{<gh 2615>}}

+* Make RawContent raw again {{<gh 2601>}}

+* Fix archetype title and date handling {{<gh 2750>}}

+* Fix TOML archetype parsing in `hugo new` {{<gh 2745>}}

+* Fix page sorting when weight is zero {{<gh 2673>}}

+* Fix page names that contain dot {{<gh 2555>}}

+* Fix RSS Title regression {{<gh 2645>}}

+* Handle ToC before handling shortcodes {{<gh 2433>}}

+* Only watch relevant themes dir {{<gh 2602>}}

+* Hugo new content creates TOML slices with closing bracket on new line {{<gh 2800>}}

+### Improvements

+* Add page information to error logging in rendering {{<gh 2570>}}

+* Deprecate `RSSlink` in favor of `RSSLink`

+* Make benchmark command more useful {{<gh 2432>}}

+* Consolidate the `Param` methods {{<gh 2590>}}

+* Allow to set cache dir in config file

+* Performance improvements:

+  * Avoid repeated Viper loads of `sectionPagesMenu` {{<gh 2728>}}

+  * Avoid reading from Viper for path and URL funcs {{<gh 2495>}}

+  * Add `partialCached` template function. This can be a significant performance boost if you have complex partials that does not need to be rerendered for every page. {{<gh 1368>}}

+### Documentation Updates

+* Update roadmap {{<gh 2666>}}

+* Update multilingual example {{<gh 2417>}}

+* Add a "Deployment with rsync" tutorial page {{<gh 2658>}}

+* Refactor `/docs` to use the `block` keyword {{<gh 2226>}}

+## **0.17.0** October 7th 2016

+Hugo is going global with our 0.17 release.  We put a lot of thought into how we could extend Hugo

+to support multilingual websites with the most simple and elegant experience. Hugo's multilingual

+capabilities rival the best web and documentation software, but Hugo's experience is unmatched.

+If you have a single language website, the simple Hugo experience you already love is unchanged.

+Adding additional languages to your website is simple and straightforward. Hugo has been completely

+internally rewritten to be multilingual aware with translation and internationalization features

+embedded throughout Hugo.

+Hugo continues its trend of each release being faster than the last. It's quite a challenge to consistently add

+significant new functionality and simultaneously dramatically improve performance. {{<gh "@bep">}} has made it

+his personal mission to apply the Go mantra of "Enable more. Do less" to Hugo. Hugo's consistent improvement

+is a testament to his brilliance and his dedication to his craft. Hugo additionally benefits from the

+performance improvements from the Go team in the Go 1.7 release.

+This release represents **over 300 contributions by over 70 contributors** to

+the main Hugo code base. Since last release Hugo has **gained 2000 stars, 50 new

+contributors and 20 additional themes.**

+Hugo now has:

+* 12,000 stars on GitHub

+* 370+ contributors

+* 110+ themes

+{{<gh "@bep" >}} continues to lead the project with the lionshare of contributions

+and reviews. A special thanks to {{<gh "@bep" >}} and {{<gh "@abourget" >}} for their

+considerable work on multilingual support.

+A big welcome to newcomers {{<gh "@MarkDBlackwell" >}}, {{<gh "@bogem" >}} and

+{{<gh "@g3wanghc" >}} for their critical contributions.

+### Highlights

+**Multilingual Support:**

+Hugo now supports multiple languages side-by-side. A single site can now have multiple languages rendered with

+full support for translation and i18n.

+**Performance:**

+Hugo is faster than ever! Hugo 0.17 is not only our fastest release, it's also the most efficient.

+Hugo 0.17 is **nearly twice as fast as Hugo 0.16** and uses about 10% less memory.

+This means that the same site will build in nearly half the time it took with Hugo 0.16.

+For the first time Hugo sites are averaging well under 1ms per rendered content.

+**Docs overhaul:**

+This release really focused on improving the documentation. [Gohugo.io](http://gohugo.io) is

+more accurate and complete than ever.

+**Support for macOS Sierra**

+### New Features

+* Multilingual support {{<gh 2303>}}

+* Allow content expiration {{<gh 2137 >}}

+* New templates functions:

+  * `querify` function to generate query strings inside templates {{<gh 2257>}}

+  * `htmlEscape` and `htmlUnescape` template functions {{<gh 2287>}}

+  * `time` converts a timestamp string into a time.Time structure {{<gh 2329>}}

+### Enhancements

+* Render the shortcodes as late as possible {{<gh 0xed0985404db4630d1b9d3ad0b7e41fb186ae0112>}}

+* Remove unneeded casts in page.getParam {{<gh 2186 >}}

+* Automatic page date fallback {{<gh 2239>}}

+* Enable safeHTMLAttr {{<gh 2234>}}

+* Add TODO list support for markdown {{<gh 2296>}}

+* Make absURL and relURL accept any type {{<gh 2352>}}

+* Suppress 'missing static' error {{<gh 2344>}}

+* Make summary, wordcount etc. more efficient {{<gh 2378>}}

+* Better error reporting in `hugo convert` {{<gh 2440>}}

+* Reproducible builds thanks to govendor {{<gh 2461>}}

+### Fixes

+* Fix shortcode in markdown headers {{<gh 2210 >}}

+* Explicitly bind livereload to hugo server port {{<gh 2205>}}

+* Fix Emojify for certain text patterns {{<gh 2198>}}

+* Normalize file name to NFC {{<gh 2259>}}

+* Ignore emacs temp files {{<gh 2266>}}

+* Handle symlink change event {{<gh 2273>}}

+* Fix panic when using URLize {{<gh 2274>}}

+* `hugo import jekyll`: Fixed target path location check {{<gh 2293>}}

+* Return all errors from casting in templates {{<gh 2356>}}

+* Fix paginator counter on x86-32 {{<gh 2420>}}

+* Fix half-broken self-closing shortcodes {{<gh 2499>}}

+****

+## **0.16.0** June 6th 2016

+Hugo 0.16 is our best and biggest release ever. The Hugo community has

+outdone itself with continued performance improvements,

+[beautiful themes](http://themes.gohugo.io) for all types of sites from project

+sites to documentation to blogs to portfolios, and increased stability.

+This release represents **over 550 contributions by over 110 contributors** to

+the main Hugo code base. Since last release Hugo has **gained 3500 stars, 90

+contributors and 23 additional themes.**

+This release celebrates 3 years since  {{< gh "@spf13" >}} wrote the first lines

+of Hugo. During those 3 years Hugo has accomplished some major milestones

+including...

+* 10,000+ stars on GitHub

+* 320+ contributors

+* 90+ themes

+* 1000s of happy websites

+* Many subprojects like {{< gh "@spf13/cobra">}}, {{< gh "@spf13/viper">}} and

+  {{< gh "@spf13/afero">}} which have experienced broad usage across the Go

+  ecosystem.

+{{< gh "@bep" >}} led the development of Hugo for the 3rd consecutive release

+with nearly half of the contributions to 0.16 in addition to his considerable

+contributions as lead maintainer. {{< gh "@anthonyfok" >}}, {{< gh

+"@DigitalCraftsman" >}}, {{< gh "@MooreReason" >}} all made significant

+contributions. A special thanks to {{< gh "@abourget" >}} for his considerable

+work on multilingual support. Due to its broad impact we wanted to spend more

+time testing it and it will be included in Hugo's next release.

+### Highlights

+**Partial Builds:** Prior to this release Hugo would always reread and rebuild

+the entire site. This release introduces support for reactive site building

+while watching (`hugo server`). Hugo will watch the filesystem for changes and

+only re-read the changed files. Depending on the files change Hugo will

+intelligently re-render only the needed portion of the site. Performance gains

+depend on the operation performed and size of the site. In our testing build

+times decreased anywhere from 10% to 99%.

+**Template Improvements:** Template improvements continue to be a mainstay of each Hugo release. Hugo 0.16 adds support for the new `block` keyword introduced in Go 1.6 -- think base templates with default sections -- as well as many new template functions.

+**Polish:** As Hugo matures releases will inevitably contain fewer huge new features. This release represents hundreds of small improvements across ever facet of Hugo which will make for a much better experience for all of our users. Worth mentioning here is the curious bug where live reloading didn't work in some editors on OS X, including the popular TextMate 2. This is now fixed. Oh, and now any error will exit with an error code, a big thing for automated deployments.

+### New Features

+* Support reading configuration variables from the OS environment {{<gh 2090 >}}

+* Add emoji support {{<gh 1892>}}

+* Add `themesDir` option to configuration {{<gh 1556>}}

+* Add support for Go 1.6 `block` keyword in templates {{<gh 1832>}}

+* Partial static sync {{<gh 1644>}}

+* Source file based relative linking (à la GitHub) {{<gh 0x0f6b334b6715253b030c4e783b88e911b6e53e56>}}

+* Add `ByLastmod` sort function to pages. {{<gh 0xeb627ca16de6fb5e8646279edd295a8bf0f72bf1 >}}

+* New templates functions:

+    * `readFile` {{<gh 1551 >}}

+    * `countwords` and `countrunes` {{<gh 1440>}}

+    * `default` {{<gh 1943>}}

+    * `hasPrefix` {{<gh 1243>}}

+    * `humanize` {{<gh 1818>}}

+    * `jsonify` {{<gh 0x435e996c4fd48e9009ffa9f83a19fb55f0777dbd>}}

+    * `md5` and `sha1` {{<gh 1932>}}

+    * `replaceRE` {{<gh 1845>}}

+    * `findRE` {{<gh 2048>}}

+    * `shuffle` {{<gh 1942>}}

+    * `slice` {{<gh 1902>}}

+    * `plainify` {{<gh 1915>}}

+### Enhancements

+* Hugo now exits with error code on any error. This is a big thing for

+  automated deployments. {{<gh 740 >}}

+* Print error when `/index.html` is zero-length {{<gh 947>}}

+* Enable dirname and filename bash autocompletion for more flags {{<gh

+  0x666ddd237791b56fd048992dca9a27d1af50a10e>}}

+* Improve error handling in commands {{<gh 1502>}}

+* Add sanity checks for `hugo import jekyll` {{<gh 1625 >}}

+* Add description to `Page.Params` {{<gh 1484>}}

+* Add async version of Google Analytics internal template {{<gh 1711>}}

+* Add autostart option to YouTube shortcode {{<gh 1784>}}

+* Set Date and Lastmod for main homepage {{<gh 1903>}}

+* Allow URL with extension in front matter {{<gh 1923>}}

+* Add list support in Scratch {{<gh

+  0xeaba04e82bdfc5d4c29e970f11b4aab9cc0efeaa>}}

+* Add file option to gist shortcode {{<gh 1955>}}

+* Add config layout and content directory CLI options {{<gh 1698>}}

+* Add boolean value comparison to `where` template function {{<gh

+  0xf3c74c9db484c8961e70cb3458f9e41e7832fa12>}}

+* Do not write to to cache when `ignoreCache` is set  {{<gh 2067>}}

+* Add option to disable rendering of 404 page  {{<gh 2037>}}

+* Mercurial is no longer needed to build Hugo {{<gh 2062 >}}

+* Do not create `robots.txt` by default {{<gh 2049>}}

+* Disable syntax guessing for PygmentsCodeFences by default.  To enable syntax

+  guessing again, add the following to your config file:

+  `PygmentsCodeFencesGuessSyntax = true` {{<gh 2034>}}

+* Make `ByCount` sort consistently {{<gh 1930>}}

+* Add `Scratch` to shortcode {{<gh 2000>}}

+* Add support for symbolic links for content, layout, static, theme  {{<gh 1855

+  >}}

+* Add '+' as one of the valid characters in URLs specified in the front matter

+  {{<gh 1290 >}}

+* Make alias redirect output URLs relative when `RelativeURLs = true` {{<gh

+  2093 >}}

+* Hugo injects meta generator tag on homepage if missing {{<gh

+  2182 >}}

+### Fixes

+* Fix file change watcher for TextMate 2 and friends on OS X {{<gh 1053 >}}

+* Make dynamic reloading of config file reliable on all platform {{<gh 1684 >}}

+* Hugo now works on Linux/arm64 {{<gh 1772 >}}

+* `plainIDAnchors` now defaults to `true`  {{<gh 2057>}}

+* Win32 and ARM builds fixed {{<gh 1716>}}

+* Copy static dir files without theme's static dir {{<gh 1656>}}

+* Make `noTimes` command flag work {{<gh 1657>}}

+* Change most global CLI flags into local ones {{<gh 1624>}}

+* Remove transformation of menu URLs {{<gh 1239>}}

+* Do not fail on unknown Jekyll file {{<gh 1705>}}

+* Use absolute path when editing with editor {{<gh 1589>}}

+* Fix hugo server "Watching for changes" path display {{<gh 1721>}}

+* Do not strip special characters out of URLs {{<gh 1292>}}

+* Fix `RSSLink` when uglyURLs are enabled {{<gh 175>}}

+* Get BaseURL from viper in server mode {{<gh 1821>}}

+* Fix shortcode handling in RST {{<gh 1904>}}

+* Use default sitemap configuration for homepage {{<gh 1304>}}

+* Exit if specific port is unavailable in server mode {{<gh 1901>}}

+* Fix regression in "section menus for lazy blogger" {{<gh 2065>}}

+****

+## **0.15.0**  November 25, 2015

+The v0.15.0 Hugo release brings a lot of polish to Hugo. Exactly 6 months after

+the 0.14 release, Hugo has seen massive growth and changes. Most notably, this

+is Hugo's first release under the Apache 2.0 license. With this license change

+we hope to expand the great community around Hugo and make it easier for our

+many users to contribute.  This release represents over **377 contributions by

+87 contributors** to the main Hugo repo and hundreds of improvements to the

+libraries Hugo uses. Hugo also launched a [new theme

+showcase](http://themes.gohugo.io) and participated in

+[Hacktoberfest](https://hacktoberfest.digitalocean.com).

+Hugo now has:

+* 6700 (+2700) stars on GitHub

+* 235 (+75) contributors

+* 65 (+30) themes

+**Template Improvements:** This release takes Hugo to a new level of speed and

+usability. Considerable work has been done adding features and performance to

+the template system which now has full support of Ace, Amber and Go Templates.

+**Hugo Import:** Have a Jekyll site, but dreaming of porting it to Hugo? This

+release introduces a new `hugo import jekyll`command that makes this easier

+than ever.

+**Performance Improvements:** Just when you thought Hugo couldn't get any faster,

+Hugo continues to improve in speed while adding features. Notably Hugo 0.15

+introduces the ability to render and serve directly from memory resulting in

+30%+ lower render times.

+Huge thanks to all who participated in this release. A special thanks to

+{{< gh "@bep" >}} who led the development of Hugo this release again,

+{{< gh "@anthonyfok" >}},

+{{< gh "@eparis" >}},

+{{< gh "@tatsushid" >}} and

+{{< gh "@DigitalCraftsman" >}}.

+### New features

+* new `hugo import jekyll` command. {{< gh 1469 >}}

+* The new `Param` convenience method on `Page` and `Node` can be used to get the most specific parameter value for a given key. {{< gh 1462 >}}

+* Several new information elements have been added to `Page` and `Node`:

+    * `RuneCount`: The number of [runes](http://blog.golang.org/strings) in the content, excluding any whitespace. This may be a good alternative to `.WordCount`  for Japanese and other CJK languages where a word-split by spaces makes no sense.  {{< gh 1266 >}}

+    * `RawContent`: Raw Markdown as a string. One use case may be of embedding remarkjs.com slides.

+    * `IsHome`: tells the truth about whether you're on the homepage or not.

+### Improvements

+* `hugo server` now builds ~30%+ faster by rendering to memory instead of disk. To get the old behavior, start the server with `--renderToDisk=true`.

+* Hugo now supports dynamic reloading of the config file when watching.

+* We now use a custom-built `LazyFileReader` for reading file contents, which means we don't read media files in `/content` into memory anymore -- and file reading is now performed in parallel on multicore PCs. {{< gh 1181 >}}

+* Hugo is now built with `Go 1.5` which, among many other improvements, have fixed the last known data race in Hugo. {{< gh 917 >}}

+* Paginator now also supports page groups. {{< gh 1274 >}}

+* Markdown improvements:

+    * Hugo now supports GitHub-flavoured markdown code fences for highlighting for `md`-files (Blackfriday rendered markdown) and `mmark` files (MMark rendered markdown). {{< gh 362 1258 >}}

+    * Several new Blackfriday options are added:

+        * Option to disable Blackfriday's `Smartypants`.

+        * Option for Blackfriday to open links in a new window/tab. {{< gh 1220 >}}

+        * Option to disable Blackfriday's LaTeX style dashes {{< gh 1231 >}}

+        * Definition lists extension support.

+* `Scratch` now has built-in `map` support.

+* We now fall back to `link title` for the default page sort. {{< gh 1299 >}}

+* Some notable new configuration options:

+    *  `IgnoreFiles` can be set with a list of Regular Expressions that matches files to be ignored during build. {{< gh 1189 >}}

+    * `PreserveTaxonomyNames`, when set to `true`, will preserve what you type as the taxonomy name both in the folders created and the taxonomy `key`, but it will be normalized for the URL.  {{< gh 1180 >}}

+* `hugo gen` can now generate man files, bash auto complete and markdown documentation

+* Hugo will now make suggestions when a command is mistyped

+* Shortcodes now have a boolean `.IsNamedParams` property. {{< gh 1597 >}}

+### New Template Features

+* All template engines:

+    * The new `dict` function that could be used to pass maps into a template. {{< gh 1463 >}}

+    * The new `pluralize` and `singularize` template funcs.

+    * The new `base64Decode` and `base64Encode` template funcs.

+    * The `sort` template func now accepts field/key chaining arguments and pointer values. {{< gh 1330 >}}

+    * Several fixes for `slicestr` and `substr`, most importantly, they now have full `utf-8`-support. {{< gh 1190 1333 1347 >}}

+    * The new `last` template function allows the user to select the last `N` items of a slice. {{< gh 1148 >}}

+    * The new `after` func allows the user to select the items after the `Nth` item. {{< gh 1200 >}}

+    * Add `time.Time` type support to the `where`, `ge`, `gt`, `le`, and `lt` template functions.

+    * It is now possible to use constructs like `where Values ".Param.key" nil` to filter pages that doesn't have a particular parameter. {{< gh 1232 >}}

+    * `getJSON`/`getCSV`: Add retry on invalid content. {{< gh 1166 >}}

+    *   The new `readDir` func lists local files. {{< gh 1204 >}}

+    * The new `safeJS` function allows the embedding of content into JavaScript contexts in Go templates.

+    * Get the main site RSS link from any page by accessing the `.Site.RSSLink` property. {{< gh 1566 >}}

+* Ace templates:

+    * Base templates now also works in themes. {{< gh 1215 >}}.

+    * And now also on Windows. {{< gh 1178 >}}

+* Full support for Amber templates including all template functions.

+* A built-in template for Google Analytics. {{< gh 1505 >}}

+* Hugo is now shipped with new built-in shortcodes: {{< gh 1576 >}}

+  * `youtube` for YouTube videos

+  * `vimeo` for Vimeo videos

+  * `gist` for GitHub gists

+  * `tweet` for Twitter Tweets

+  * `speakerdeck` for Speakerdeck slides

+### Bugfixes

+* Fix data races in page sorting and page reversal. These operations are now also cached. {{< gh 1293 >}}

+* `page.HasMenuCurrent()` and `node.HasMenuCurrent()` now work correctly in multi-level nested menus.

+* Support `Fish and Chips` style section titles. Previously, this would end up as  `Fish And Chips`. Now, the first character is made toupper, but the rest are preserved as-is. {{< gh 1176 >}}

+* Hugo now removes superfluous p-tags around shortcodes. {{< gh 1148 >}}

+### Notices

+* `hugo server` will watch by default now.

+* Some fields and methods were deprecated in `0.14`. These are now removed, so the error message isn't as friendly if you still use the old values. So please change:

+    *   `getJson` to `getJSON`, `getCsv` to `getCSV`, `safeHtml` to

+  `safeHTML`, `safeCss` to `safeCSS`, `safeUrl` to `safeURL`, `Url` to `URL`,

+  `UrlPath` to `URLPath`, `BaseUrl` to `BaseURL`, `Recent` to `Pages`.

+### Known Issues

+Using the Hugo v0.15 32-bit Windows or ARM binary, running `hugo server` would crash or hang due to a [memory alignment issue](https://golang.org/pkg/sync/atomic/#pkg-note-BUG) in [Afero](https://github.com/spf13/afero).  The bug was discovered shortly after the v0.15.0 release and has since been [fixed](https://github.com/spf13/afero/pull/23) by {{< gh "@tpng" >}}.  If you encounter this bug, you may either compile Hugo v0.16-DEV from source, or use the following solution/workaround:

+* **64-bit Windows users: Please use [hugo_0.15_windows_amd64.zip](https://github.com/gohugoio/hugo/releases/download/v0.15/hugo_0.15_windows_amd64.zip)** (amd64 == x86-64).  It is only the 32-bit hugo_0.15_windows_386.zip that crashes/hangs (see {{< gh 1621 >}} and {{< gh 1628 >}}).

+* **32-bit Windows and ARM users: Please run `hugo server --renderToDisk` as a workaround** until Hugo v0.16 is released (see [“hugo server” returns runtime error on armhf](https://discourse.gohugo.io/t/hugo-server-returns-runtime-error-on-armhf/2293) and {{< gh 1716 >}}).

+----

+## **0.14.0** May 25, 2015

+The v0.14.0 Hugo release brings of the most demanded features to Hugo. The

+foundation of Hugo is stabilizing nicely and a lot of polish has been added.

+We’ve expanded support for additional content types with support for AsciiDoc,

+Restructured Text, HTML and Markdown. Some of these types depend on external

+libraries as there does not currently exist native support in Go. We’ve tried

+to make the experience as seamless as possible. Look for more improvements here

+in upcoming releases.

+A lot of work has been done to improve the user experience, with extra polish

+to the Windows experience. Hugo errors are more helpful overall and Hugo now

+can detect if it’s being run in Windows Explorer and provide additional

+instructions to run it via the command prompt.

+The Hugo community continues to grow. Hugo has over 4000 stars on github, 165

+contributors, 35 themes and 1000s of happy users. It is now the 5th most

+popular static site generator (by Stars) and has the 3rd largest contributor

+community.

+This release represents over **240 contributions by 36 contributors** to the main

+Hugo codebase.

+Big shout out to {{< gh "@bep" >}} who led the development of Hugo

+this release, {{< gh "@anthonyfok" >}},

+{{< gh "@eparis" >}},

+{{< gh "@SchumacherFM" >}},

+{{< gh "@RickCogley" >}} &

+{{< gh "@mdhender" >}} for their significant contributions

+and {{< gh "@tatsushid" >}} for his continuous improvements

+to the templates. Also a big thanks to all the theme creators. 11 new themes

+have been added since last release and the [hugoThemes repo now has previews of

+all of

+them](https://github.com/gohugoio/hugoThemes/blob/master/README.md#theme-list).

+Hugo also depends on a lot of other great projects. A big thanks to all of our dependencies including:

+[cobra](https://github.com/spf13/cobra),

+[viper](https://github.com/spf13/viper),

+[blackfriday](https://github.com/russross/blackfriday),

+[pflag](https://github.com/spf13/pflag),

+[HugoThemes](https://github.com/gohugoio/hugothemes),

+[BurntSushi](https://github.com/BurntSushi/toml),

+[goYaml](https://github.com/go-yaml/yaml/tree/v2), and the Go standard library.

+### New features

+* Support for all file types in content directory.

+    * If dedicated file type handler isn’t found it will be copied to the destination.

+* Add `AsciiDoc` support using external helpers.

+* Add experimental support for [`Mmark`](https://github.com/miekg/mmark) markdown processor

+* Bash autocomplete support via `genautocomplete` command

+* Add section menu support for a [Section Menu for "the Lazy Blogger"](/templates/menu-templates/)

+* Add support for `Ace` base templates

+* Adding `RelativeURLs = true` to site config will now make all the relative URLs relative to the content root.

+* New template functions:

+  * `getenv`

+  * The string functions `substr` and `slicestr`

+  * `seq`, a sequence generator very similar to its Gnu counterpart

+  * `absURL` and `relURL`, both of which takes the `BaseURL` setting into account

+### Improvements

+* Highlighting with `Pygments` is now cached to disk -- expect a major speed boost if you use it!

+* More Pygments highlighting options, including `line numbers`

+* Show help information to Windows users who try to double click on `hugo.exe`.

+* Add `bind` flag to `hugo server` to set the interface to which the server will bind

+* Add support for `canonifyURLs` in `srcset`

+* Add shortcode support for HTML (content) files

+* Allow the same `shortcode` to  be used with or without inline content

+* Configurable RSS output filename

+### Bugfixes

+* Fix panic with paginator and zero pages in result set.

+* Fix crossrefs on Windows.

+* Fix `eq` and `ne` template functions when used with a raw number combined with the result of `add`, `sub` etc.

+* Fix paginator with uglyURLs

+* Fix {{< gh 998 >}}, supporting UTF8 characters in Permalinks.

+### Notices

+* To get variable and function names in line with the rest of the Go community,

+  a set of variable and function names has been deprecated: These will still

+  work in 0.14, but will be removed in 0.15. What to do should be obvious by

+  the build log; `getJson` to `getJSON`, `getCsv` to `getCSV`, `safeHtml` to

+  `safeHTML`, `safeCss` to `safeCSS`, `safeUrl` to `safeURL`, `Url` to `URL`,

+  `UrlPath` to `URLPath`, `BaseUrl` to `BaseURL`, `Recent` to `Pages`,

+  `Indexes` to `Taxonomies`.

+----

+## **0.13.0** Feb 21, 2015

+The v0.13.0 release is the largest Hugo release to date. The release introduced

+some long sought after features (pagination, sequencing, data loading, tons of

+template improvements) as well as major internal improvements. In addition to

+the code changes, the Hugo community has grown significantly and now has over

+3000 stars on github, 134 contributors, 24 themes and 1000s of happy users.

+This release represents **448 contributions by 65 contributors**

+A special shout out to {{< gh "@bep" >}} and

+{{< gh "@anthonyfok" >}} for their new role as Hugo

+maintainers and their tremendous contributions this release.

+### New major features

+* Support for [data files](/templates/data-templates/) in [YAML](http://yaml.org/),

+  [JSON](http://www.json.org/), or [TOML](https://github.com/toml-lang/toml)

+  located in the `data` directory ({{< gh 885 >}})

+* Support for [dynamic content](/templates/data-templates/) by loading JSON & CSV

+  from remote sources via GetJson and GetCsv in short codes or other layout

+  files ({{< gh 748 >}})

+* [Pagination support](/templates/pagination/) for homepage, sections and

+  taxonomies ({{< gh 750 >}})

+* Universal sequencing support

+    * A new, generic Next/Prev functionality is added to all lists of pages

+      (sections, taxonomies, etc.)

+    * Add in-section [Next/Prev](/variables/) content pointers

+* `Scratch` -- [a "scratchpad"](/functions/scratch/) for your node- and page-scoped

+  variables

+* [Cross Reference](/content-management/cross-references/) support to easily link documents

+  together with the ref and relref shortcodes.

+* [Ace](https://github.com/yosssi/ace) template engine support ({{< gh 541 >}})

+* A new [shortcode](/content-management/shortcodes/) token of `{{</* */>}}` (raw HTML)

+  alongside the existing `{{%/* */%}}` (Markdown)

+* A top level `Hugo` variable (on Page & Node) is added with various build

+  information

+* Several new ways to order and group content:

+    * `ByPublishDate`

+    * `GroupByPublishDate(format, order)`

+    * `GroupByParam(key, order)`

+    * `GroupByParamDate(key, format, order)`

+* Hugo has undergone a major refactoring, with a new handler system and a

+  generic file system. This sounds and is technical, but will pave the way for

+  new features and make Hugo even speedier

+### Notable enhancements to existing features

+* The [shortcode](/content-management/shortcodes/) handling is rewritten for speed and

+  better error messages.

+* Several improvements to the [template functions](/functions/):

+    * [`where`](/functions/where/) is now even more powerful and accepts SQL-like syntax with the

+      operators `==`, `eq`; `!=`, `<>`, `ne`; `>=`, `ge`; `>`, `gt`; `<=`,

+      `le`; `<`, `lt`; `in`, `not in`

+    * `where` template function now also accepts dot chaining key argument

+      (e.g. `"Params.foo.bar"`)

+* New template functions:

+    * `apply`

+    * `chomp`

+    * `delimit`

+    * `sort`

+    * `markdownify`

+    * `in` and `intersect`

+    * `trim`

+    * `replace`

+    * `dateFormat`

+* Several [configurable improvements related to Markdown

+  rendering](/getting-started/configuration/):

+    * Configuration of footnote rendering

+    * Optional support for smart angled quotes, e.g. `"Hugo"` → «Hugo»

+    * Enable descriptive header IDs

+* URLs in XML output is now correctly canonified ({{< gh 725 728 >}}, and part

+  of {{< gh 789 >}})

+### Other improvements

+* Internal change to use byte buffer pool significantly lowering memory usage

+  and providing measurable performance improvements overall

+* Changes to docs:

+    * A new [Troubleshooting](/troubleshooting/) section is added

+    * It's now searchable through Google Custom Search ({{< gh 753 >}})

+    * Some new great tutorials:

+        * [Automated deployments with

+          Wercker](/tutorials/automated-deployments/)

+        * [Creating a new theme](/tutorials/creating-a-new-theme/)

+* [`hugo new`](/content-management/archetypes/) now copies the content in addition to the front matter

+* Improved unit test coverage

+* Fixed a lot of Windows-related path issues

+* Improved error messages for template and rendering errors

+* Enabled soft LiveReload of CSS and images ({{< gh 490 >}})

+* Various fixes in RSS feed generation ({{< gh 789 >}})

+* `HasMenuCurrent` and `IsMenuCurrent` is now supported on Nodes

+* A bunch of [bug fixes](https://github.com/gohugoio/hugo/commits/master)

+----

+## **0.12.0** Sept 1, 2014

+A lot has happened since Hugo v0.11.0 was released. Most of the work has been

+focused on polishing the theme engine and adding critical functionality to the

+templates.

+This release represents over 90 code commits from 28 different contributors.

+  * 10 [new themes](https://github.com/gohugoio/hugoThemes) created by the community

+  * Fully themable [Partials](/templates/partials/)

+  * [404 template](/templates/404/) support in themes

+  * [Shortcode](/content-management/shortcodes/) support in themes

+  * [Views](/templates/views/) support in themes

+  * Inner [shortcode](/content-management/shortcodes/) content now treated as Markdown

+  * Support for header ids in Markdown (# Header {#myid})

+  * [Where](/templates/lists/) template function to filter lists of content, taxonomies, etc.

+  * [GroupBy](/templates/lists/) & [GroupByDate](/templates/list/) methods to group pages

+  * Taxonomy [pages list](/templates/taxonomy-templates/) now sortable, filterable, limitable & groupable

+  * General cleanup to taxonomies & documentation to make it more clear and consistent

+  * [Showcase](/showcase/) returned and has been expanded

+  * Pretty links now always have trailing slashes

+  * [BaseUrl](/getting-started/configuration/) can now include a subdirectory

+  * Better feedback about draft & future post rendering

+  * A variety of improvements to [the website](http://gohugo.io/)

+----

+## **0.11.0** May 28, 2014

+This release represents over 110 code commits from 29 different contributors.

+  * Considerably faster... about 3 - 4x faster on average

+  * [LiveReload](/getting-started/usage/). Hugo will automatically reload the browser when the build is complete

+  * Theme engine w/[Theme Repository](https://github.com/gohugoio/hugoThemes)

+  * [Menu system](/content-management/menus/) with support for active page

+  * [Builders](/getting-started/usage/) to quickly create a new site, content or theme

+  * [XML sitemap](/templates/sitemap-template/) generation

+  * [Integrated Disqus](/content-management/comments/) support

+  * Streamlined [template organization](/templates/)

+  * [Brand new docs site](http://gohugo.io/)

+  * Support for publishDate which allows for posts to be dated in the future

+  * More [sort](/templates/lists/) options

+  * Logging support

+  * Much better error handling

+  * More informative verbose output

+  * Renamed Indexes > [Taxonomies](/content-management/taxonomies/)

+  * Renamed Chrome > [Partials](/templates/partials/)

+----

+## **0.10.0** March 1, 2014

+This release represents over 110 code commits from 29 different contributors.

+  * [Syntax highlighting](/tools/syntax-highlighting/) powered by pygments (**slow**)

+  * Ability to [sort content](/templates/lists/) many more ways

+  * Automatic [table of contents](/content-management/toc/) generation

+  * Support for Unicode URLs, aliases and indexes

+  * Configurable per-section [permalink](/content-management/urls/) pattern support

+  * Support for [paired shortcodes](/content-management/shortcodes/)

+  * Shipping with some [shortcodes](/content-management/shortcodes/) (highlight & figure)

+  * Adding [canonify](/content-management/urls/) option to keep urls relative

+  * A bunch of [additional template functions](/functions/)

+  * Watching very large sites now works on Mac

+  * RSS generation improved. Limited to 50 items by default, can limit further in [template](/templates/rss/)

+  * Boolean params now supported in [fm](/content-management/front-matter/)

+  * Launched website [showcase](/showcase/). Show off your own hugo site!

+  * A bunch of [bug fixes](https://github.com/gohugoio/hugo/commits/master)

+----

+## **0.9.0** November 15, 2013

+This release represents over 220 code commits from 22 different contributors.

+  * New [command based interface](/getting-started/usage/) similar to git (`hugo server -s ./`)

+  * Amber template support

+  * [Aliases](/content-management/urls/) (redirects)

+  * Support for top level pages (in addition to homepage)

+  * Complete overhaul of the documentation site

+  * Full Windows support

+  * Better index support including [ordering by content weight](/templates/lists/)

+  * Add params to site config, available in .Site.Params from templates

+  * Friendlier JSON support

+  * Support for html & xml content (with front matter support)

+  * Support for [summary](/content-management/summaries/) content divider (<code>&lt;!&#45;&#45;more&#45;&#45;&gt;</code>)

+  * HTML in [summary](/content-management/summaries/) (when using divider)

+  * Added ["Minutes to Read"](/variables/) functionality

+  * Support for a custom 404 page

+  * Cleanup of how content organization is handled

+  * Loads of unit and performance tests

+  * Integration with travis ci

+  * Static directory now watched and copied on any addition or modification

+  * Support for relative permalinks

+  * Fixed watching being triggered multiple times for the same event

+  * Watch now ignores temp files (as created by Vim)

+  * Configurable number of posts on [homepage](/templates/homepage/)

+  * [Front matter](/content-management/front-matter/) supports multiple types (int, string, date, float)

+  * Indexes can now use a default template

+  * Addition of truncated bool to content to determine if should show 'more' link

+  * Support for [linkTitles](/variables/)

+  * Better handling of most errors with directions on how to resolve

+  * Support for more date / time formats

+  * Support for go 1.2

+  * Support for `first` in templates

+----

+## **0.8.0** August 2, 2013

+This release represents over 65 code commits from 6 different contributors.

+* Added support for pretty urls (filename/index.html vs filename.html)

+* Hugo supports a destination directory

+* Will efficiently sync content in static to destination directory

+* Cleaned up options.. now with support for short and long options

+* Added support for TOML

+* Added support for YAML

+* Added support for Previous & Next

+* Added support for indexes for the indexes

+* Better Windows compatibility

+* Support for series

+* Adding verbose output

+* Loads of bugfixes

+----

+## **0.7.0** July 4, 2013

+* Hugo now includes a simple server

+* First public release

+----

+## **0.6.0** July 2, 2013

+* Hugo includes an example documentation site which it builds

+----

+## **0.5.0** June 25, 2013

+  * Hugo is quite usable and able to build spf13.com

--- a/content/overview/configuration.md

+++ /dev/null

@@ -1,458 +1,0 @@

----

-aliases:

-- /doc/configuration/

-lastmod: 2016-09-17

-date: 2013-07-01

-linktitle: Configuration

-menu:

-  main:

-    parent: getting started

-next: /overview/source-directory

-toc: true

-prev: /overview/usage

-title: Configuring Hugo

-weight: 40

----

-The directory structure of a Hugo web site&mdash;or more precisely,

-of the source files containing its content and templates&mdash;provide

-most of the configuration information that Hugo needs.

-Therefore, in essence,

-many web sites wouldn't actually need a configuration file.

-This is because Hugo is designed to recognize certain typical usage patterns

-(and it expects them, by default).

-Nevertheless, Hugo does search for a configuration file bearing

-a particular name in the root of your web site's source directory.

-First, it looks for a `./config.toml` file.

-If that's not present, it will seek a `./config.yaml` file,

-followed by a `./config.json` file.

-In this `config` file for your web site,

-you can include precise directions to Hugo regarding

-how it should render your site, as well as define its menus,

-and set various other site-wide parameters.

-Another way that web site configuration can be accomplished is through

-operating system environment variables.

-For instance, the following command will work on Unix-like systems&mdash;it

-sets a web site's title:

-```bash

-$ env HUGO_TITLE="Some Title" hugo

-```

-(**Note:** all such environment variable names must be prefixed with

-<code>HUGO_</code>.)

-## Examples

-Following is a typical example of a YAML configuration file.

-Three periods end the document:

-```yaml

----

-baseURL: "http://yoursite.example.com/"

-...

-```

-Following is an example TOML configuration file with some default values.

-The values under `[params]` will populate the `.Site.Params` variable

-for use in templates:

-```toml

-contentDir = "content"

-layoutDir = "layouts"

-publishDir = "public"

-buildDrafts = false

-baseURL = "http://yoursite.example.com/"

-canonifyURLs = true

-[taxonomies]

-  category = "categories"

-  tag = "tags"

-[params]

-  description = "Tesla's Awesome Hugo Site"

-  author = "Nikola Tesla"

-```

-Here is a YAML configuration file which sets a few more options:

-```yaml

----

-baseURL: "http://yoursite.example.com/"

-title: "Yoyodyne Widget Blogging"

-footnoteReturnLinkContents: "↩"

-permalinks:

-  post: /:year/:month/:title/

-params:

-  Subtitle: "Spinning the cogs in the widgets"

-  AuthorName: "John Doe"

-  GitHubUser: "spf13"

-  ListOfFoo:

-    - "foo1"

-    - "foo2"

-  SidebarRecentLimit: 5

-...

-```

-## Configuration variables

-Following is a list of Hugo-defined variables you can configure,

-along with their current, default values:

-    ---

-    archetypeDir:               "archetypes"

-    # hostname (and path) to the root, e.g. http://spf13.com/

-    baseURL:                    ""

-    # include content marked as draft

-    buildDrafts:                false

-    # include content with publishdate in the future

-    buildFuture:                false

-    # include content already expired

-    buildExpired:               false

-    # enable this to make all relative URLs relative to content root. Note that this does not affect absolute URLs.

-    relativeURLs:               false

-    canonifyURLs:               false

-    # config file (default is path/config.yaml|json|toml)

-    config:                     "config.toml"

-    contentDir:                 "content"

-    dataDir:                    "data"

-    defaultExtension:           "html"

-    defaultLayout:              "post"

-    # Missing translations will default to this content language

-    defaultContentLanguage:     "en"

-    # Renders the default content language in subdir, e.g. /en/. The root directory / will redirect to /en/

-    defaultContentLanguageInSubdir: false

-    # The below example will disable all page types and will render nothing.

-    disableKinds = ["page", "home", "section", "taxonomy", "taxonomyTerm", "RSS", "sitemap", "robotsTXT", "404"]

-    disableLiveReload:          false

-    # Do not build RSS files

-    disableRSS:                 false

-    # Do not build Sitemap file

-    disableSitemap:             false

-    # Enable GitInfo feature

-    enableGitInfo:              false

-    # Build robots.txt file

-    enableRobotsTXT:            false

-    # Do not render 404 page

-    disable404:                 false

-    # Do not inject generator meta tag on homepage

-    disableHugoGeneratorInject: false

-    # Enable Emoji emoticons support for page content.

-    # See www.emoji-cheat-sheet.com

-    enableEmoji:				false

-    # Show a placeholder instead of the default value or an empty string if a translation is missing

-    enableMissingTranslationPlaceholders: false

-    footnoteAnchorPrefix:       ""

-    footnoteReturnLinkContents: ""

-    # google analytics tracking id

-    googleAnalytics:            ""

-    languageCode:               ""

-    layoutDir:                  "layouts"

-    # Enable Logging

-    log:                        false

-    # Log File path (if set, logging enabled automatically)

-    logFile:                    ""

-    # "yaml", "toml", "json"

-    metaDataFormat:             "toml"

-    # Edit new content with this editor, if provided

-    newContentEditor:           ""

-    # Don't sync permission mode of files

-    noChmod:                    false

-    # Don't sync modification time of files

-    noTimes:                    false

-    paginate:                   10

-    paginatePath:               "page"

-    permalinks:

-    # Pluralize titles in lists using inflect

-    pluralizeListTitles:        true

-    # Preserve special characters in taxonomy names ("Gérard Depardieu" vs "Gerard Depardieu")

-    preserveTaxonomyNames:      false

-    # filesystem path to write files to

-    publishDir:                 "public"

-    # enables syntax guessing for code fences without specified language

-    pygmentsCodeFencesGuessSyntax: false

-    # color-codes for highlighting derived from this style

-    pygmentsStyle:              "monokai"

-    # true: use pygments-css or false: color-codes directly

-    pygmentsUseClasses:         false

-    # maximum number of items in the RSS feed

-    rssLimit:                   15

-    # default sitemap configuration map

-    sitemap:

-    # filesystem path to read files relative from

-    source:                     ""

-    staticDir:                  "static"

-    # display memory and timing of different steps of the program

-    stepAnalysis:               false

-    # theme to use (located by default in /themes/THEMENAME/)

-    themesDir:                  "themes"

-    theme:                      ""

-    title:                      ""

-    # if true, use /filename.html instead of /filename/

-    uglyURLs:                   false

-    # Do not make the url/path to lowercase

-    disablePathToLower:         false

-    # if true, auto-detect Chinese/Japanese/Korean Languages in the content. (.Summary and .WordCount can work properly in CJKLanguage)

-    hasCJKLanguage:             false

-    # verbose output

-    verbose:                    false

-    # verbose logging

-    verboseLog:                 false

-    # watch filesystem for changes and recreate as needed

-    watch:                      true

-    ---

-## Ignore various files when rendering

-The following statement inside `./config.toml` will cause Hugo to ignore files

-ending with `.foo` and `.boo` when rendering:

-```toml

-ignoreFiles = [ "\\.foo$", "\\.boo$" ]

-```

-The above is a list of regular expressions.

-Note that the backslash (`\`) character is escaped, to keep TOML happy.

-## Configure Blackfriday rendering

-[Blackfriday](https://github.com/russross/blackfriday) is Hugo's

-[Markdown](http://daringfireball.net/projects/markdown/)

-rendering engine.

-In the main, Hugo typically configures Blackfriday with a sane set of defaults.

-These defaults should fit most use cases, reasonably well.

-However, if you have unusual needs with respect to Markdown,

-Hugo exposes some of its Blackfriday behavior options for you to alter.

-The following table lists these Hugo options,

-paired with the corresponding flags from Blackfriday's source code (for the latter, see

-[html.go](https://github.com/russross/blackfriday/blob/master/html.go) and

-[markdown.go](https://github.com/russross/blackfriday/blob/master/markdown.go)):

-<table class="table table-bordered-configuration">

-    <thead>

-        <tr>

-            <th>Flag</th>

-            <th>Default</th>

-            <th>Blackfriday flag</th>

-        </tr>

-    </thead>

-    <tbody>

-        <tr>

-            <td><code><strong>taskLists</strong></code></td>

-            <td><code>true</code></td>

-            <td><code></code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>false</code> turns off GitHub-style automatic task/TODO

-                list generation.

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>smartypants</strong></code></td>

-            <td><code>true</code></td>

-            <td><code>HTML_USE_SMARTYPANTS</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>false</code> disables smart punctuation substitutions

-                including smart quotes, smart dashes, smart fractions, etc.

-                If <code>true</code>, it may be fine-tuned with the

-                <code>angledQuotes</code>,

-                <code>fractions</code>,

-                <code>smartDashes</code> and

-                <code>latexDashes</code> flags (see below).

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>angledQuotes</strong></code></td>

-            <td><code>false</code></td>

-            <td><code>HTML_SMARTYPANTS_ANGLED_QUOTES</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>true</code> enables smart, angled double quotes.<br>

-                <small>

-                    <strong>Example:</strong>

-                    <code>"Hugo"</code> renders to

-                    «Hugo» instead of “Hugo”.

-                </small>

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>fractions</strong></code></td>

-            <td><code>true</code></td>

-            <td><code>HTML_SMARTYPANTS_FRACTIONS</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>false</code> disables smart fractions.<br>

-                <small>

-                    <strong>Example:</strong>

-                    <code>5/12</code> renders to

-                    <sup>5</sup>&frasl;<sub>12</sub>

-                    (<code>&lt;sup&gt;5&lt;/sup&gt;&amp;frasl;&lt;sub&gt;12&lt;/sub&gt;</code>).<br>

-                    <strong>Caveat:</strong>

-                    Even with <code>fractions = false</code>,

-                    Blackfriday still converts

-                    1/2, 1/4 and 3/4 respectively to

-                    ½ (<code>&amp;frac12;</code>),

-                    ¼ (<code>&amp;frac14;</code>) and

-                    ¾ (<code>&amp;frac34;</code>),

-                    but only these three.</small>

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>smartDashes</strong></code></td>

-            <td><code>true</code></td>

-            <td><code>HTML_SMARTYPANTS_DASHES</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>false</code> disables smart dashes; i.e., the conversion

-                of multiple hyphens into en&nbsp;dash or em&nbsp;dash.

-                If <code>true</code>, its behavior can be modified with the

-                <code>latexDashes</code> flag below.

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>latexDashes</strong></code></td>

-            <td><code>true</code></td>

-            <td><code>HTML_SMARTYPANTS_LATEX_DASHES</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>false</code> disables LaTeX-style smart dashes and

-                selects conventional smart dashes. Assuming

-                <code>smartDashes</code> (above), if this is:

-                <ul>

-                    <li>

-                        <strong><code>true</code>,</strong> then

-                        <code>--</code> is translated into “&ndash;”

-                        (<code>&amp;ndash;</code>), whereas

-                        <code>---</code> is translated into “&mdash;”

-                        (<code>&amp;mdash;</code>).

-                    </li>

-                    <li>

-                        <strong><code>false</code>,</strong> then

-                        <code>--</code> is translated into “&mdash;”

-                        (<code>&amp;mdash;</code>), whereas a

-                        <em>spaced</em> single hyphen between two words

-                        is translated into an en&nbsp;dash&mdash;e.g.,

-                        <code>12 June - 3 July</code> becomes

-                        <code>12 June &amp;ndash; 3 July</code>.

-                    </li>

-                </ul>

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>hrefTargetBlank</strong></code></td>

-            <td><code>false</code></td>

-            <td><code>HTML_HREF_TARGET_BLANK</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>true</code> opens external links in a new window or tab.

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>plainIDAnchors</strong></code></td>

-            <td><code>true</code></td>

-            <td>

-                <code>FootnoteAnchorPrefix</code> and

-                <code>HeaderIDSuffix</code>

-            </td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                <code>true</code> renders any header and footnote IDs

-                without the document ID.<br>

-                <small>

-                    <strong>Example:</strong>

-                    renders <code>#my-header</code> instead of

-                    <code>#my-header:bec3ed8ba720b9073ab75abcf3ba5d97</code>.

-                </small>

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>extensions</strong></code></td>

-            <td><code>[]</code></td>

-            <td><code>EXTENSION_*</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                Enable one or more of Blackfriday's Markdown extensions

-                (if they aren't Hugo defaults).<br>

-                <small>

-                    <strong>Example:</strong> &nbsp;

-                    Include <code>"hardLineBreak"</code>

-                    in the list to enable Blackfriday's

-                    <code>EXTENSION_HARD_LINE_BREAK</code>.

-                </small>

-            </td>

-        </tr>

-        <tr>

-            <td><code><strong>extensionsmask</strong></code></td>

-            <td><code>[]</code></td>

-            <td><code>EXTENSION_*</code></td>

-        </tr>

-        <tr>

-            <td class="purpose-description" colspan="3">

-                <span class="purpose-title">Purpose:</span>

-                Disable one or more of Blackfriday's Markdown extensions

-                (if they are Hugo defaults).<br>

-                <small>

-                    <strong>Example:</strong> &nbsp;

-                    Include <code>"autoHeaderIds"</code>

-                    in the list to disable Blackfriday's

-                    <code>EXTENSION_AUTO_HEADER_IDS</code>.

-                </small>

-            </td>

-        </tr>

-        </tbody>

-</table>

-**Notes**

-* These flags are **case sensitive** (as of Hugo v0.15)!

-* These flags must be grouped under the `blackfriday` key

-and can be set on **both the site level and the page level**.

-Any setting on a page will override the site setting

-there. For example:

-<table class="table">

-    <thead>

-        <tr>

-            <th>TOML</th>

-            <th>YAML</th>

-        </tr>

-    </thead>

-    <tbody>

-        <tr style="vertical-align: top;">

-            <td style="width: 50%;">

-<pre><code>[blackfriday]

-  angledQuotes = true

-  fractions = false

-  plainIDAnchors = true

-  extensions = ["hardLineBreak"]

-</code></pre>

-            </td>

-            <td>

-<pre><code>blackfriday:

-  angledQuotes: true

-  fractions: false

-  plainIDAnchors: true

-  extensions:

-    - hardLineBreak

-</code></pre>

-            </td>

-        </tr>

-    </tbody>

-</table>

--- a/content/overview/installing.md

+++ /dev/null

@@ -1,149 +1,0 @@

----

-aliases:

-- /doc/installing/

-lastmod: 2016-01-04

-date: 2013-07-01

-menu:

-  main:

-    parent: getting started

-next: /overview/usage

-prev: /overview/quickstart

-title: Installing Hugo

-weight: 20

----

-Hugo is written in [Go][] with support for multiple platforms.

-The latest release can be found at [Hugo Releases](https://github.com/gohugoio/hugo/releases).

-We currently provide pre-built binaries for

-<i class="fa fa-windows"></i>&nbsp;Windows,

-<i class="fa fa-linux"></i>&nbsp;Linux,

-<i class="fa freebsd-19px"></i>&nbsp;FreeBSD

-and <i class="fa fa-apple"></i>&nbsp;OS&nbsp;X (Darwin)

-for x64, i386 and ARM architectures.

-Hugo may also be compiled from source wherever the Go compiler tool chain can run, e.g. for other operating systems including DragonFly BSD, OpenBSD, Plan&nbsp;9 and Solaris.  See http://golang.org/doc/install/source for the full set of supported combinations of target operating systems and compilation architectures.

-## Installing Hugo (binary)

-Installation is very easy. Simply download the appropriate version for your

-platform from [Hugo Releases](https://github.com/gohugoio/hugo/releases).

-Once downloaded it can be run from anywhere. You don't need to install

-it into a global location. This works well for shared hosts and other systems

-where you don't have a privileged account.

-Ideally, you should install it somewhere in your `PATH` for easy use.

-`/usr/local/bin` is the most probable location.

-On macOS, if you have [Homebrew](http://brew.sh/), installation is even

-easier: just run `brew install hugo`.

-For a more detailed explanation follow the corresponding installation guides:

-- [Installation on macOS]({{< relref "tutorials/installing-on-mac.md" >}})

-- [Installation on Windows]({{< relref "tutorials/installing-on-windows.md" >}})

-### Installing Pygments (optional)

-The Hugo executable has one *optional* external dependency for source code highlighting (Pygments).

-If you want to have source code highlighting using the [highlight shortcode](/extras/highlighting/),

-you need to install the Python-based Pygments program. The procedure is outlined on the [Pygments home page](http://pygments.org/).

-## Upgrading Hugo

-Upgrading Hugo is as easy as downloading and replacing the executable you’ve

-placed in your `PATH`.

-On macOS, if you have [Homebrew](http://brew.sh/), upgrading is even

-easier: just run `brew upgrade hugo`.

-## Installing Hugo on Linux from native packages

-### Arch Linux

-You can install Hugo from the [Arch user repository](https://aur.archlinux.org/) on Arch Linux or derivatives such as Manjaro.

-    sudo pacman -S yaourt

-    yaourt -S hugo

-Be aware that Hugo is built from source. This means that additional tools like [Git](https://git-scm.com/) and [Go](https://golang.org/doc/install) will be installed as well.

-### Debian and Ubuntu

-Hugo has been included in Debian and Ubuntu since 2016, and thus installing Hugo is as simple as:

-    sudo apt install hugo

-Pros:

-* Native Debian/Ubuntu package maintained by Debian Developers

-* Pre-installed bash completion script and man pages for best interactive experience

-Cons:

-* Might not be the latest version, especially if you are using an older stable version (e.g., Ubuntu 16.04&nbsp;LTS).

-  Until backports and PPA are available, you may consider installing the Hugo snap package to get the latest version of Hugo, as described below.

-### Fedora, CentOS and Red Hat

-* https://copr.fedorainfracloud.org/coprs/daftaupe/hugo/ : updated as soon as possible after the official Hugo release.

-* https://copr.fedorainfracloud.org/coprs/spf13/Hugo/ (updated to Hugo v0.16)

-See also [this discussion](https://discourse.gohugo.io/t/solved-fedora-copr-repository-out-of-service/2491).

-## Alternate Installation Methods

-### Snap Package

-In any of the [Linux distributions that support snaps](http://snapcraft.io/docs/core/install):

-    snap install hugo

-> Note: Hugo-as-a-snap can write only inside the user’s `$HOME` directory—and gvfs-mounted directories owned by the user—because of Snaps’ confinement and security model.

-> More information is also available [in this related GitHub issue](https://github.com/gohugoio/hugo/issues/3143).

-### Docker Image (unofficial)

-[Docker Hugo](https://hub.docker.com/r/felicianotech/docker-hugo/) is a Docker image that can be used for local development but more importantly, can be easily used for continuous integration builds of your Hugo site on [CircleCI](https://circleci.com/) or [Travis CI](https://travis-ci.org/). Source available on [GitHub](https://github.com/felicianotech/docker-hugo).

-## Installing from source

-### Prerequisite tools for downloading and building source code

-* [Git](http://git-scm.com/)

-* [Go][] 1.8+

-* [govendor][]

-### Vendored Dependencies

-Hugo uses [govendor][] to vendor dependencies, but we don't commit the vendored packages themselves to the Hugo git repository.

-Therefore, a simple `go get` is not supported since `go get` is not vendor-aware.

-You **must use govendor** to fetch Hugo's dependencies.

-### Fetch from GitHub

-	The commands below assume that you have [Go](https://golang.org/dl/) installed with your `$GOPATH` set.

-    go get github.com/kardianos/govendor

-    govendor get github.com/gohugoio/hugo

-`govendor get` will fetch Hugo and all its dependent libraries to

-`$GOPATH/src/github.com/gohugoio/hugo`, and compile everything into a final `hugo`

-(or `hugo.exe`) executable, which you will find sitting inside

-`$GOPATH/go/bin/`, all ready to go!

-*Windows users: where you see the `$HOME` environment variable above, replace it with `%USERPROFILE%`.*

-*Note: For syntax highlighting using the [highlight shortcode](/extras/highlighting/),

-you need to install the Python-based [Pygments](http://pygments.org/) program.*

-## Contributing

-Please see the [contributing guide](/doc/contributing/) if you are interested in

-working with the Hugo source or contributing to the project in any way.

-[Go]: http://golang.org/

-[govendor]: https://github.com/kardianos/govendor

--- a/content/overview/introduction.md

+++ /dev/null

@@ -1,197 +1,0 @@

----

-lastmod: 2016-08-14

-date: 2013-07-01

-linktitle: Introduction

-menu:

-  main:

-    parent: getting started

-next: /overview/quickstart

-title: Introduction to Hugo

-weight: 5

----

-## What is Hugo?

-Hugo is a general-purpose website framework. Technically speaking, Hugo is

-a static site generator. Unlike other systems which dynamically build a page

-every time a visitor requests one, Hugo does the building when you create

-your content. Since websites are viewed far more often than they are

-edited, Hugo is optimized for website viewing while providing a great

-writing experience.

-Sites built with Hugo are extremely fast and very secure. Hugo sites can

-be hosted anywhere, including [Heroku][], [GoDaddy][], [DreamHost][],

-[GitHub Pages][], [Netlify][], [Surge][], [Aerobatic][], [Firebase Hosting][],

-[Google Cloud Storage][], [Amazon S3][] and [CloudFront][], and work well

-with CDNs. Hugo sites run without dependencies on expensive runtimes

-like Ruby, Python or PHP and without dependencies on any databases.

-[Heroku]: https://www.heroku.com/

-[GoDaddy]: https://www.godaddy.com/

-[DreamHost]: http://www.dreamhost.com/

-[GitLab]: https://about.gitlab.com

-[GitHub Pages]: https://pages.github.com/

-[Aerobatic]: https://www.aerobatic.com/

-[Firebase Hosting]: https://firebase.google.com/docs/hosting/

-[Google Cloud Storage]: http://cloud.google.com/storage/

-[Amazon S3]: http://aws.amazon.com/s3/

-[CloudFront]: http://aws.amazon.com/cloudfront/ "Amazon CloudFront"

-[Surge]: https://surge.sh

-[Netlify]: https://www.netlify.com

-We think of Hugo as the ideal website creation tool. With nearly instant

-build times and the ability to rebuild whenever a change is made, Hugo

-provides a very fast feedback loop. This is essential when you are

-designing websites, but also very useful when creating content.

-## What makes Hugo different?

-Web site generators render content into HTML files. Most are "dynamic

-site generators." That means the HTTP

-server (which is the program running on your website that the user's

-browser talks to) runs the generator to create a new HTML file

-each and every time a user wants to view a page.

-Creating the page dynamically means that the computer hosting

-the HTTP server has to have enough memory and CPU to effectively run

-the generator around the clock. If not, then the user has to wait

-in a queue for the page to be generated.

-Nobody wants users to wait longer than needed, so the dynamic site

-generators programmed their systems to cache the HTML files. When

-a file is cached, a copy of it is temporarily stored on the computer.

-It is much faster for the HTTP server to send that copy the next time

-the page is requested than it is to generate it from scratch.

-Hugo takes caching a step further. All HTML files are rendered on your

-computer. You can review the files before you copy them to the computer

-hosting the HTTP server. Since the HTML files aren't generated dynamically,

-we say that Hugo is a "static site generator."

-Not running a web site generator on your HTTP server has many benefits.

-The most noticeable is performance - HTTP servers are very good at

-sending files. So good that you can effectively serve the same number

-of pages with a fraction of the memory and CPU needed for a dynamic site.

-Hugo has two components to help you build and test your web site. The

-one that you'll probably use most often is the built-in HTTP server.

-When you run `hugo server`, Hugo renders all of your content into

-HTML files and then runs an HTTP server on your computer so that you

-can see what the pages look like.

-The second component is used when you're ready to publish your web

-site to the computer running your website. Running Hugo without any

-actions will rebuild your entire web site using the `baseURL` setting

-from your site's configuration file. That's required to have your page

-links work properly with most hosting companies.

-## How fast is Hugo?

-{{% youtube CdiDYZ51a2o %}}

-## What does Hugo do?

-In technical terms, Hugo takes a source directory of files and

-templates and uses these as input to create a complete website.

-Hugo boasts the following features:

-### General

-  * Extremely fast build times (~1 ms per page)

-  * Completely cross platform: Runs on <i class="fa fa-apple"></i>&nbsp;macOS, <i class="fa fa-linux"></i>&nbsp;Linux, <i class="fa fa-windows"></i>&nbsp;Windows, and more!

-  * Easy [installation](/overview/installing/)

-  * Render changes [on the fly](/overview/usage/) with [LiveReload](/extras/livereload/) as you develop

-  * Complete theme support

-  * Host your site anywhere

-### Organization

-  * Straightforward [organization](/content/organization/)

-  * Support for [website sections](/content/sections/)

-  * Completely customizable [URLs](/extras/urls/)

-  * Support for configurable [taxonomies](/taxonomies/overview/) which includes categories and tags.  Create your own custom organization of content

-  * Ability to [sort content](/content/ordering/) as you desire

-  * Automatic [table of contents](/extras/toc/) generation

-  * Dynamic menu creation

-  * [Pretty URLs](/extras/urls/) support

-  * [Permalink](/extras/permalinks/) pattern support

-  * [Aliases](/extras/aliases/) (redirects)

-### Content

-  * Native support for content written in [Markdown](/content/example/)

-    * Support for other languages through _external helpers_, see [supported formats](/content/supported-formats)

-  * Support for TOML, YAML and JSON metadata in [frontmatter](/content/front-matter/)

-  * Completely [customizable homepage](/layout/homepage/)

-  * Support for multiple [content types](/content/types/)

-  * Automatic and user defined [summaries](/content/summaries/)

-  * [Shortcodes](/extras/shortcodes/) to enable rich content inside of Markdown

-  * ["Minutes to Read"](/layout/variables/) functionality

-  * ["Wordcount"](/layout/variables/) functionality

-### Additional Features

-  * Integrated [Disqus](https://disqus.com/) comment support

-  * Integrated [Google Analytics](https://google-analytics.com/) support

-  * Automatic [RSS](/layout/rss/) creation

-  * Support for [Go](http://golang.org/pkg/html/template/), [Amber](https://github.com/eknkc/amber) and [Ace](https://github.com/yosssi/ace) HTML templates

-  * Syntax [highlighting](/extras/highlighting/) powered by [Pygments](http://pygments.org/)

-See what's coming next in the [roadmap](/meta/roadmap/).

-## Who should use Hugo?

-Hugo is for people that prefer writing in a text editor over

-a browser.

-Hugo is for people who want to hand code their own website without

-worrying about setting up complicated runtimes, dependencies and

-databases.

-Hugo is for people building a blog, company site, portfolio, tumblog,

-documentation, single page site or a site with thousands of

-pages.

-## Why did you write Hugo?

-I wrote Hugo ultimately for a few reasons. First, I was disappointed with

-WordPress, my then website solution. With it, I couldn't create

-content as efficiently as I wanted to.

-It rendered slowly. It required me to be online to write

-posts: plus its constant security updates and the horror stories of people's

-hacked blogs! I hated how content for it was written only in HTML, instead of the much

-simpler Markdown. Overall, I felt like WordPress got in my way

-much more than it helped me. It kept

-me from writing great content.

-I looked at the existing static site generators

-like [Jekyll][], [Middleman][] and [Nanoc][].

-All had complicated installation dependencies and took far longer to render

-my blog with its hundreds of posts than I felt was acceptable. I wanted

-a framework to be able to give me rapid feedback while making changes to the

-templates, and the 5+-minute render times were just too slow. In general,

-they were also very blog minded and didn't have the ability to provide

-other content types and flexible URLs.

-[Jekyll]: http://jekyllrb.com/

-[Middleman]: https://middlemanapp.com/

-[Nanoc]: http://nanoc.ws/

-I wanted to develop a fast and full-featured website framework without any

-dependencies. The [Go language][] seemed to have all the features I needed

-in a language. I began developing Hugo in Go and fell in love with the

-language. I hope you will enjoy using Hugo (and contributing to it) as much

-as I have writing it.

-&mdash;Steve Francia (@spf13)

-[Go language]: http://golang.org/ "The Go Programming Language"

-## Next Steps

- * [Install Hugo](/overview/installing/)

- * [Quick start](/overview/quickstart/)

- * [Join the Mailing List](/community/mailing-list/)

- * [Star us on GitHub](https://github.com/gohugoio/hugo)

- * [Discussion Forum](https://discourse.gohugo.io/)

--- a/content/overview/quickstart.md

+++ /dev/null

@@ -1,573 +1,0 @@

----

-lastmod: 2016-10-20

-date: 2013-07-01

-linktitle: Quickstart

-menu:

-  main:

-    parent: getting started

-next: /overview/installing

-prev: /overview/introduction

-title: Hugo Quickstart Guide

-weight: 10

----

-Building a bookshelf

----

-In this quickstart, we will build an online bookshelf that will list books and their reviews.

-> _Note: This quickstart depends on features introduced in Hugo v0.15.  If you have an earlier version of Hugo, you will need to [upgrade](/overview/installing/) before proceeding._

-{{% youtube w7Ft2ymGmfc %}}

-## Step 1. Install Hugo

-Go to [Hugo Releases](https://github.com/gohugoio/hugo/releases) and download the

-appropriate version for your OS and architecture.

-Save the main executable as `hugo` (or `hugo.exe` on Windows) somewhere in your `PATH` as we will be using it in the next step.

-More complete instructions are available

-at [Installing Hugo]({{< relref "overview/installing.md" >}}).

-If you're on Windows, this quickstart will assume

-you're using [Git Bash](https://git-for-windows.github.io/)

-(also known as Git for Windows).

-Thus all commands will begin with the Bash prompt character (which is `$`).

-Once `hugo` is installed, make sure to run the `help` command to verify `hugo` installation. Below you can see part of the `help` command output for brevity.

-```bash

-$ hugo help

-```

-```

-hugo is the main command, used to build your Hugo site.

-Hugo is a Fast and Flexible Static Site Generator

-built with love by spf13 and friends in Go.

-Complete documentation is available at http://gohugo.io/.

-```

-You can check `hugo` version using the command shown below.

-```bash

-$ hugo version

-```

-```

-Hugo Static Site Generator v0.15 BuildDate: 2015-11-26T11:59:00+05:30

-```

-## Step 2. Scaffold bookshelf hugo site

-Hugo has commands that allows us to quickly scaffold a Hugo managed website. Navigate to a convenient location on your filesystem and create a new Hugo site `bookshelf` by executing the following command.

-```bash

-$ hugo new site bookshelf

-```

-Change directory to `bookshelf` and you will see the following directory layout.

-```bash

-$ tree -a

-```

-```

-.

-|-- archetypes

-|-- config.toml

-|-- content

-|-- data

-|-- layouts

-|-- static

-`-- themes

-6 directories, 1 file

-```

-As mentioned in the command output, `bookshelf` directory has 6 sub-directories and 1 file. Let's look at each of them one by one.

-* **archetypes**: You can create new content files in Hugo using the `hugo new` command. When you run that command, it adds few configuration properties to the post like date and title. [Archetype]({{< relref "content/archetypes.md" >}}) allows you to define your own configuration properties that will be added to the post front matter whenever `hugo new` command is used.

-* **config.toml**: Every website should have a configuration file at the root. By default, the configuration file uses `TOML` format but you can also use `YAML` or `JSON` formats as well. [TOML](https://github.com/toml-lang/toml) is minimal configuration file format that's easy to read due to obvious semantics. The configuration settings mentioned in the `config.toml` are applied to the full site. These configuration settings include `baseURL` and `title` of the website.

-* **content**: This is where you will store content of the website. Inside content, you will create sub-directories for different sections. Let's suppose your website has three sections -- `blog`, `article`, and `tutorial` then you will have three different directories for each of them inside the `content` directory. The name of the section i.e. `blog`, `article`, or `tutorial` will be used by Hugo to apply a specific layout applicable to that section.

-* **data**: This directory is used to store configuration files that can be

-used by Hugo when generating your website.

-You can write these files in YAML, JSON, or TOML format.

-* **layouts**: The content inside this directory is used to specify how your content will be converted into the static website.

-* **static**: This directory is used to store all the static content that your website will need like images, CSS, JavaScript or other static content.

-* **themes**: This is where you will create a theme for your site to use. Themes provide the layout and templates that renders content. There's a wide variety of open-source themes available to download and use but you can also create your own if you prefer.

-## Step 3. Add content

-Let's now add a post to our `bookshelf`. We will use the `hugo new` command to add a post. In January, I read [Good To Great](http://www.amazon.com/Good-Great-Some-Companies-Others/dp/0066620996/) book so we will start with creating a post for it. **Make sure you are inside the `bookshelf` directory.**

-```bash

-$ hugo new post/good-to-great.md

-```

-```

-/Users/shekhargulati/bookshelf/content/post/good-to-great.md created

-```

-The above command will create a new directory `post`

-inside the `bookshelf/content` directory

-and create `good-to-great.md` file inside it.

-```bash

-$ tree -a content

-```

-```

-content

-`-- post

-    `-- good-to-great.md

-1 directory, 1 file

-```

-The content inside the `good-to-great.md` file looks as shown below.

-```

-+++

-date = "2016-02-14T16:11:58+05:30"

-draft = true

-title = "good to great"

-+++

-```

-The content inside `+++` is the TOML configuration for the post.

-This configuration is called **front matter**.

-It enables you to define post configuration along with its content.

-By default, each post will have the three configuration properties shown above.

-* **date** specifies the date and time at which post was created.

-* **draft** specifies that post is not ready for publication yet so it will not be in the generated site.

-* **title** specifies title for the post.

-Let's add a small review for **Good to Great** book.

-```

-+++

-date = "2016-02-14T16:11:58+05:30"

-draft = true

-title = "Good to Great Book Review"

-+++

-I read **Good to Great in January 2016**. An awesome read sharing detailed analysis on how good companies became great.

-```

-## Step 4. Serve content

-Hugo has an inbuilt server that can serve your website content so that you can preview it. You can also use the inbuilt Hugo server in production. To serve content, execute the following command inside the `bookshelf` directory.

-```bash

-$ hugo server

-```

-```

-0 of 1 draft rendered

-0 future content

-0 pages created

-0 paginator pages created

-0 tags created

-0 categories created

-in 9 ms

-Watching for changes in /Users/shekhargulati/bookshelf/{data,content,layouts,static}

-Serving pages from memory

-Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

-Press Ctrl+C to stop

-```

-This will start the server on port `1313`.

-You can view your blog at http://localhost:1313/.

-When you go to the link, you will see nothing.

-There are couple of reasons for that:

-1. As you can see in the `hugo server` command output, Hugo didn't render the draft. Hugo will only render drafts if you pass the `buildDrafts` flag to the `hugo server` command.

-2. We have not specified how Markdown content should be rendered. We have to specify a theme that Hugo can use. We will do that in the next step.

-To render drafts, re-run the server with command shown below.

-```bash

-$ hugo server --buildDrafts

-```

-```

-1 of 1 draft rendered

-0 future content

-1 pages created

-0 paginator pages created

-0 tags created

-0 categories created

-in 6 ms

-Watching for changes in /Users/shekhargulati/bookshelf/{data,content,layouts,static}

-Serving pages from memory

-Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

-Press Ctrl+C to stop

-```

-If you go to [http://localhost:1313/](http://localhost:1313/),

-you still will not see anything as we have not specified a theme that Hugo should use.

-## Step 5. Add theme

-Themes provide the layout and templates that will be used by Hugo to render your website. There are a lot of Open-source themes available at [https://themes.gohugo.io/](https://themes.gohugo.io/) that you can use.

-> **Hugo currently doesn’t ship with a `default` theme, allowing the user to pick whichever theme best suits their project.**

-Themes should be added in the `themes` directory inside the repository root.

-```bash

-$ cd themes

-```

-Now, you can clone one or more themes inside the `themes` directory.

-We will use the `robust` theme,

-but at a commit (in its history) that works with this quickstart.

-```bash

-$ git clone https://github.com/dim0627/hugo_theme_robust.git

-$ (cd hugo_theme_robust; git checkout b8ce466)

-```

-Leave the themes folder.

-```bash

-$ cd ..

-```

-Start the server again.

-```bash

-$ hugo server --theme=hugo_theme_robust --buildDrafts

-```

-```

-1 of 1 draft rendered

-0 future content

-1 pages created

-2 paginator pages created

-0 tags created

-0 categories created

-in 10 ms

-Watching for changes in /Users/shekhargulati/bookshelf/{data,content,layouts,static,themes}

-Serving pages from memory

-Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

-Press Ctrl+C to stop

-```

-> *Note: If Hugo doesn't find the specified theme in the `themes` directory,

-it will throw an exception as shown below.*

-```

-FATAL: 2016/02/14 Unable to find theme Directory: /Users/shekhargulati/bookshelf/themes/robust

-```

-To view your website, you can go to http://localhost:1313/. You will see as shown below.

-![](/img/quickstart/bookshelf-robust-theme.png)

-Let's understand the layout of the theme. A theme consists of the following:

-* **theme.toml** is the theme configuration file that gives information

-about the theme like name and description of theme,

-author details, and theme license.

-* **images** directory contains two images -- `screenshot.png` and `tn.png`. `screenshot.png` is the image of the list view and `tn.png` is the single post view.

-* **layouts** directory contains different views for different content types.

-Every content type should have two files `single.html` and `list.html`.

-`single.html` is used for rendering a single piece of content.

-`list.html` is used to view a list of content items.

-For example, you will use `list.html` to view all the posts

-that have the `programming` tag.

-* **static** directory stores all the static assets used by the template.

-Static assets could be JavaScript libraries like jQuery or CSS styles or images,

-or any other static content.

-This directory will be copied into the final site when rendered.

-## Step 6. Use multiple themes

-You can very easily test different layouts by switching between different themes.

-Let's suppose we want to try out the `bleak` theme.

-We clone the `bleak` theme inside the `bookshelf/themes` directory.

-```bash

-$ git clone https://github.com/Zenithar/hugo-theme-bleak.git

-```

-Restart the server using `hugo-theme-bleak` as shown below.

-```bash

-$ hugo server --theme=hugo-theme-bleak --buildDrafts

-```

-Now, the website will use the `bleak` theme

-and will be rendered differently as shown below.

-![](/img/quickstart/bookshelf-bleak-theme.png)

-## Step 7. Update config.toml and live reloading in action

-Restart the server with the `robust` theme, as we will use it in this quickstart.

-```bash

-$ hugo server --theme=hugo_theme_robust --buildDrafts

-```

-The website uses the dummy values specified in `bookshelf/config.toml`.

-Let's update the configuration.

-```toml

-baseURL = "http://example.org/"

-languageCode = "en-us"

-title = "Shekhar Gulati Book Reviews"

-[Params]

-  Author = "Shekhar Gulati"

-```

-Hugo has inbuilt support for live reloading.

-So, as soon as you save your changes it will apply the change

-and reload the web page. You will see the changes shown below.

-![](/img/quickstart/bookshelf-updated-config.png)

-The same is reflected in the Hugo server logs as well.

-As soon as you changed the configuration file,

-Hugo applied those changes to the affected pages.

-```

-Config file changed: /Users/shekhargulati/bookshelf/config.toml

-1 of 1 draft rendered

-0 future content

-1 pages created

-2 paginator pages created

-0 tags created

-0 categories created

-in 11 ms

-```

-## Step 8. Customize robust theme

-The `robust` theme is a good start towards our online bookshelf but we want to

-customize it a bit to meet the look and feel required for the bookshelf.

-Hugo makes it very easy to customize themes.

-You can also create your themes but we will not do that today.

-If you want to create your own theme, then you should refer to

-the [Hugo documentation]({{< relref "themes/creation.md" >}}).

-The first change that we have to make is to use a different default image

-instead of the one used in the theme.

-The theme's default image used in both the list and single view page resides

-inside `themes/hugo_theme_robust/static/images/default.jpg`.

-We can easily override it by creating a simple directory structure

-inside the repository's `static` directory.

-Create an images directory inside the `bookshelf/static` directory

-and copy an image with name `default.jpg` inside it.

-We will use the default image shown below.

-![](/img/quickstart/default.jpg)

-Hugo will sync the changes and reload the website to use new image as shown below.

-![](/img/quickstart/bookshelf-new-default-image.png)

-Now, we need to change the layout of the index page so that only images are shown instead of the text. The index.html inside the layouts directory of the theme refer to partial `li` that renders the list view shown below.

-```html

-<article class="li">

-  <a href="{{ .Permalink }}" class="clearfix">

-    <div class="image" style="background-image: url({{ $.Site.BaseURL }}images/{{ with .Params.image }}{{ . }}{{ else }}default.jpg{{ end }});"></div>

-    <div class="detail">

-      <time>{{ with .Site.Params.DateForm }}{{ $.Date.Format . }}{{ else }}{{ $.Date.Format "Mon, Jan 2, 2006" }}{{ end }}</time>

-      <h2 class="title">{{ .Title }}</h2>

-      <div class="summary">{{ .Summary }}</div>

-    </div>

-  </a>

-</article>

-```

-Create a new file li.html inside the `bookshelf/layouts/_default` directory. Copy the content shown below into the li.html. We have removed details of the book so that only image is shown.

-```html

-<article class="li">

-  <a href="{{ .Permalink }}" class="clearfix">

-    <div class="image" style="background-image: url({{ $.Site.BaseURL }}images/{{ with .Params.image }}{{ . }}{{ else }}default.jpg{{ end }});"></div>

-  </a>

-</article>

-```

-Now, the website will be rendered as shown below.

-![](/img/quickstart/bookshelf-only-picture.png)

-Next, we want to remove information related to theme from the footer.

-So, create a new directory `partials` inside `bookshelf/layouts`.

-There, create a new file `default_foot.html` with the content copied

-from the theme's `layouts/partials/default_foot.html`.

-Replace the footer section with the one shown below.

-```html

-<footer class="site">

-  <p>{{ with .Site.Copyright | safeHTML }}{{ . }}{{ else }}&copy; {{ $.Site.LastChange.Year }} {{ if isset $.Site.Params "Author" }}{{ $.Site.Params.Author }}{{ else }}{{ .Site.Title }}{{ end }}{{ end }}</p>

-  <p>Powered by <a href="http://gohugo.io" target="_blank">Hugo</a>,</p>

-</footer>

-```

-We also have to remove the sidebar on the right.

-Copy the `index.html` from the theme's `layouts` directory to

-the `bookshelf/layouts` directory.

-Remove the section related to the sidebar from the HTML:

-```html

-<div class="col-sm-3">

-  {{ partial "sidebar.html" . }}

-</div>

-```

-So far we are using the default image but we would like to use the book image so that we can relate to the book. Every book review will define a configuration setting in its front matter. Update the `good-to-great.md` as shown below.

-```

-+++

-date = "2016-02-14T16:11:58+05:30"

-draft = true

-title = "Good to Great Book Review"

-image = "good-to-great.jpg"

-+++

-I read **Good to Great in January 2016**. An awesome read sharing detailed analysis on how good companies became great. Although this book is about how companies became great but we could apply a lot of the learnings on ourselves. Concepts like level 5 leader, hedgehog concept, the stockdale paradox are equally applicable to individuals.

-```

-Grab a (legal) image from somewhere, name it `good-to-great.jpg`,

-and place it in the `bookshelf/static/images` directory.

-After adding few more books to our shelf, the shelf appears as shown below.

-These are a few of the books that I have read within the last year.

-![](/img/quickstart/bookshelf.png)

-## Step 9. Make posts public

-So far all the posts that we have written are in draft status.

-To make a draft public, you can either run a command

-or manually change the draft status in the post to `false`.

-```bash

-$ hugo undraft content/post/good-to-great.md

-```

-Now, you can start the server without the `buildDrafts` option.

-```

-$ hugo server --theme=hugo_theme_robust

-```

-## Step 10. Integrate Disqus

-Disqus allows you to integrate comments in your static blog. To enable Disqus, you just have to set `disqusShortname`  in the config.toml as shown below.

-```

-[Params]

-  Author = "Shekhar Gulati"

-  disqusShortname = <your disqus shortname>

-```

-Now, commenting will be enabled in your blog.

-![](/img/quickstart/bookshelf-disqus.png)

-## Step 11. Generate website

-To generate Hugo website source you can use

-to deploy your website on GitHub pages,

-first edit `bookshelf/config.toml`, changing the `baseURL` line to:

-```

-baseURL = "https://<your GitHub username>.github.io/bookshelf/"

-```

-Then type the following command.

-```bash

-$ hugo --theme=hugo_theme_robust

-```

-```

-0 draft content

-0 future content

-5 pages created

-2 paginator pages created

-0 tags created

-0 categories created

-in 17 ms

-```

-After you run the `hugo` command, a `bookshelf/public` directory

-will be created containing the generated website source.

-BTW (in case you tried),

-the website isn't properly accessible via the `file:///` protocol.

-## Step 12. Deploy bookshelf on GitHub pages

-Let's version control your bookshelf:

-```bash

-$ git init

-$ echo "/public/" >> .gitignore

-$ echo "/themes/" >> .gitignore

-$ git add --all

-$ git commit -m "Initial commit"

-```

-Now the Git repositories under `bookshelf/themes`

-won't conflict with your `bookshelf` repository,

-and neither will a Git repository in `bookshelf/public`.

-Create a new repository on GitHub named `bookshelf` (without a README).

-Once that's done, create a new Git repository on your local system

-in `bookshelf/public` and add remote:

-```bash

-$ cd public

-$ git init

-$ git remote add origin [email protected]:<github-username>/bookshelf.git

-```

-There, create and check out a new branch `gh-pages`.

-```bash

-$ git checkout -b gh-pages

-Switched to a new branch 'gh-pages'

-```

-Add all the files (within `bookshelf/public`) to the index,

-commit them, and push the changes to GitHub.

-```bash

-$ git add --all

-$ git commit -m "bookshelf added"

-$ git push -f origin gh-pages

-```

-In couple of minutes, your website will be live

-at `https://<github-username>.github.io/bookshelf/`.

-Anytime, you can regenerate your site with:

-```bash

-$ (cd ..; hugo --theme=hugo_theme_robust)

-$ git add --all

-$ git commit -m "<some change message>"

-$ git push -f origin gh-pages

-```

-----

-This quickstart was originally written by [Shekhar Gulati](https://twitter.com/shekhargulati) in his [52 Technologies in 2016](https://github.com/shekhargulati/52-technologies-in-2016) blog series.

--- a/content/overview/source-directory.md

+++ /dev/null

@@ -1,126 +1,0 @@

----

-aliases:

-- /doc/source-directory/

-lastmod: 2015-02-09

-date: 2013-07-01

-menu:

-  main:

-    parent: getting started

-next: /content/organization

-notoc: true

-prev: /overview/configuration

-title: Source Organization

-weight: 50

----

-Hugo takes a single directory and uses it as the input for creating a complete

-website.

-The top level of a source directory will typically have the following elements:

-    ▸ archetypes/

-    ▸ content/

-    ▸ data/

-    ▸ i18n/

-    ▸ layouts/

-    ▸ static/

-    ▸ themes/

-      config.toml

-Learn more about the different directories and what their purpose is:

-* [config]({{< relref "overview/configuration.md" >}})

-* [data]({{< relref "extras/datafiles.md" >}})

-* [i18n]({{< relref "content/multilingual.md#translation-of-strings" >}})

-* [archetypes]({{< relref "content/archetypes.md" >}})

-* [content]({{< relref "content/organization.md" >}})

-* [layouts]({{< relref "templates/overview.md" >}})

-* [static]({{< relref "themes/creation.md#static" >}})

-* [themes]({{< relref "themes/overview.md" >}})

-## Example

-An example directory may look like:

-    .

-    ├── config.toml

-    ├── archetypes

-    |   └── default.md

-    ├── content

-    |   ├── post

-    |   |   ├── firstpost.md

-    |   |   └── secondpost.md

-    |   └── quote

-    |   |   ├── first.md

-    |   |   └── second.md

-    ├── data

-    ├── i18n

-    ├── layouts

-    |   ├── _default

-    |   |   ├── single.html

-    |   |   └── list.html

-    |   ├── partials

-    |   |   ├── header.html

-    |   |   └── footer.html

-    |   ├── taxonomy

-    |   |   ├── category.html

-    |   |   ├── post.html

-    |   |   ├── quote.html

-    |   |   └── tag.html

-    |   ├── post

-    |   |   ├── li.html

-    |   |   ├── single.html

-    |   |   └── summary.html

-    |   ├── quote

-    |   |   ├── li.html

-    |   |   ├── single.html

-    |   |   └── summary.html

-    |   ├── shortcodes

-    |   |   ├── img.html

-    |   |   ├── vimeo.html

-    |   |   └── youtube.html

-    |   ├── index.html

-    |   └── sitemap.xml

-    ├── themes

-    |   ├── hyde

-    |   └── doc

-    └── static

-        ├── css

-        └── js

-This directory structure tells us a lot about this site:

-1. The website intends to have two different types of content: *posts* and *quotes*.

-2. It will also apply two different taxonomies to that content: *categories* and *tags*.

-3. It will be displaying content in 3 different views: a list, a summary and a full page view.

-## Content for home page and other list pages

-Since Hugo 0.18, "everything" is a `Page` that can have content and metadata, like `.Params`, attached to it -- and share the same set of [page variables](/templates/variables/).

-To add content and frontmatter to the home page, a section, a taxonomy or a taxonomy terms listing, add a markdown file with the base name `_index` on the relevant place on the file system.

-For the default Markdown content, the filename will be `_index.md`.

-Se the example directory tree below.

-**Note that you don't have to create `_index` file for every section, taxonomy and similar, a default page will be created if not present, but with no content and default values for `.Title` etc.**

-```bash

-└── content

-    ├── _index.md

-    ├── categories

-    │   ├── _index.md

-    │   └── photo

-    │       └── _index.md

-    ├── post

-    │   ├── _index.md

-    │   └── firstpost.md

-    └── tags

-        ├── _index.md

-        └── hugo

-            └── _index.md

-```

--- a/content/overview/usage.md

+++ /dev/null

@@ -1,224 +1,0 @@

----

-aliases:

-- /doc/usage/

-lastmod: 2016-08-19

-date: 2013-07-01

-menu:

-  main:

-    parent: getting started

-next: /overview/configuration

-notoc: true

-prev: /overview/installing

-title: Using Hugo

-weight: 30

----

-Make sure Hugo is in your `PATH` (or provide a path to it). Test this by:

-{{< nohighlight >}}$ hugo help

-hugo is the main command, used to build your Hugo site.

-Hugo is a Fast and Flexible Static Site Generator

-built with love by spf13 and friends in Go.

-Complete documentation is available at http://gohugo.io/.

-Usage:

-  hugo [flags]

-  hugo [command]

-Available Commands:

-  benchmark   Benchmark Hugo by building a site a number of times.

-  check       Contains some verification checks

-  config      Print the site configuration

-  convert     Convert your content to different formats

-  env         Print Hugo version and environment info

-  gen         A collection of several useful generators.

-  help        Help about any command

-  import      Import your site from others.

-  list        Listing out various types of content

-  new         Create new content for your site

-  server      A high performance webserver

-  undraft     Undraft changes the content's draft status from 'True' to 'False'

-  version     Print the version number of Hugo

-Flags:

-  -b, --baseURL string             hostname (and path) to the root, e.g. http://spf13.com/

-  -D, --buildDrafts                include content marked as draft

-  -E, --buildExpired               include expired content

-  -F, --buildFuture                include content with publishdate in the future

-      --cacheDir string            filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache/

-      --canonifyURLs               if true, all relative URLs will be canonicalized using baseURL

-      --cleanDestinationDir        remove files from destination not found in static directories

-      --config string              config file (default is path/config.yaml|json|toml)

-  -c, --contentDir string          filesystem path to content directory

-  -d, --destination string         filesystem path to write files to

-      --disable404                 do not render 404 page

-      --disableKinds stringSlice   disable different kind of pages (home, RSS etc.)

-      --disableRSS                 do not build RSS files

-      --disableSitemap             do not build Sitemap file

-      --enableGitInfo              add Git revision, date and author info to the pages

-      --forceSyncStatic            copy all files when static is changed.

-  -h, --help                       help for hugo

-      --i18n-warnings              print missing translations

-      --ignoreCache                ignores the cache directory

-  -l, --layoutDir string           filesystem path to layout directory

-      --log                        enable Logging

-      --logFile string             log File path (if set, logging enabled automatically)

-      --noChmod                    don't sync permission mode of files

-      --noTimes                    don't sync modification time of files

-      --pluralizeListTitles        pluralize titles in lists using inflect (default true)

-      --preserveTaxonomyNames      preserve taxonomy names as written ("Gérard Depardieu" vs "gerard-depardieu")

-      --quiet                      build in quiet mode

-      --renderToMemory             render to memory (only useful for benchmark testing)

-  -s, --source string              filesystem path to read files relative from

-      --stepAnalysis               display memory and timing of different steps of the program

-  -t, --theme string               theme to use (located in /themes/THEMENAME/)

-      --themesDir string           filesystem path to themes directory

-      --uglyURLs                   if true, use /filename.html instead of /filename/

-  -v, --verbose                    verbose output

-      --verboseLog                 verbose logging

-  -w, --watch                      watch filesystem for changes and recreate as needed

-Use "hugo [command] --help" for more information about a command.

-{{< /nohighlight >}}

-## Common Usage Example

-The most common use is probably to run `hugo` with your current directory being the input directory:

-{{< nohighlight >}}$ hugo

-0 draft content

-0 future content

-99 pages created

-0 paginator pages created

-16 tags created

-0 groups created

-in 120 ms

-{{< /nohighlight >}}

-This generates your web site to the `public/` directory,

-ready to be deployed to your web server.

-## Instant feedback as you develop your web site

-If you are working on things and want to see the changes immediately, by default

-Hugo will watch the filesystem for changes, and rebuild your site as soon as a file is saved:

-{{< nohighlight >}}$ hugo -s ~/Code/hugo/docs

-0 draft content

-0 future content

-99 pages created

-0 paginator pages created

-16 tags created

-0 groups created

-in 120 ms

-Watching for changes in /Users/spf13/Code/hugo/docs/content

-Press Ctrl+C to stop

-{{< /nohighlight >}}

-Hugo can even run a server and create a site preview at the same time!

-Hugo implements [LiveReload](/extras/livereload/) technology to automatically

-reload any open pages in all JavaScript-enabled browsers, including mobile.

-This is the easiest and most common way to develop a Hugo web site:

-{{< nohighlight >}}$ hugo server -ws ~/Code/hugo/docs

-0 draft content

-0 future content

-99 pages created

-0 paginator pages created

-16 tags created

-0 groups created

-in 120 ms

-Watching for changes in /Users/spf13/Code/hugo/docs/content

-Serving pages from /Users/spf13/Code/hugo/docs/public

-Web Server is available at http://localhost:1313/

-Press Ctrl+C to stop

-{{< /nohighlight >}}

-## Deploying your web site

-After running `hugo server` for local web development,

-you need to do a final `hugo` run

-**without the `server` part of the command**

-to rebuild your site.

-You may then **deploy your site** by copying the `public/` directory

-(by FTP, SFTP, WebDAV, Rsync, `git push`, etc.)

-to your production web server.

-Since Hugo generates a static website, your site can be hosted anywhere,

-including [Heroku][], [GoDaddy][], [DreamHost][], [GitHub Pages][],

-[Amazon S3][] with [CloudFront][], [Firebase Hosting][],

-or any other cheap (or even free) static web hosting service.

-[Apache][], [nginx][], [IIS][]...  Any web server software would do!

-[Apache]: http://httpd.apache.org/ "Apache HTTP Server"

-[nginx]: http://nginx.org/

-[IIS]: http://www.iis.net/

-[Heroku]: https://www.heroku.com/

-[GoDaddy]: https://www.godaddy.com/

-[DreamHost]: http://www.dreamhost.com/

-[GitHub Pages]: https://pages.github.com/

-[GitLab]: https://about.gitlab.com

-[Amazon S3]: http://aws.amazon.com/s3/

-[CloudFront]: http://aws.amazon.com/cloudfront/ "Amazon CloudFront"

-[Firebase Hosting]: https://firebase.google.com/docs/hosting/

-### A note about deployment

-Running `hugo` *does not* remove generated files before building. This means that you should delete your `public/` directory (or the directory you specified with `-d`/`--destination`) before running the `hugo` command, or you run the risk of the wrong files (e.g. drafts and/or future posts) being left in the generated site.

-An easy way to work around this is to use different directories for development and production.

-To start a server that builds draft content (helpful for editing), you can specify a different destination: the `dev/` dir.

-{{< nohighlight >}}$ hugo server -wDs ~/Code/hugo/docs -d dev

-{{< /nohighlight >}}

-When the content is ready for publishing, use the default `public/` dir:

-{{< nohighlight >}}$ hugo -s ~/Code/hugo/docs

-{{< /nohighlight >}}

-This prevents content you're not yet ready to share

-from accidentally becoming available.

-### Alternatively, serve your web site with Hugo!

-Yes, that's right!  Because Hugo is so blazingly fast both in web site creation

-*and* in web serving (thanks to its concurrent and multi-threaded design and

-its Go heritage), some users actually prefer using Hugo itself to serve their

-web site *on their production server*!

-No other web server software (Apache, nginx, IIS...) is necessary.

-Here is the command:

-{{< nohighlight >}}$ hugo server --baseURL=http://yoursite.org/ \

-              --port=80 \

-              --appendPort=false \

-              --bind=87.245.198.50

-{{< /nohighlight >}}

-Note the `bind` option,

-which is the interface to which the server will bind

-(defaults to `127.0.0.1`:

-fine for most development use cases).

-Some hosts, such as Amazon Web Services,

-run NAT (network address translation);

-sometimes it can be hard to figure out the actual IP address.

-Using `--bind=0.0.0.0` will bind to all interfaces.

-This way, you may actually deploy just the source files,

-and Hugo on your server will generate the resulting web site

-on-the-fly and serve them at the same time.

-You may optionally add `--disableLiveReload=true` if you do not want

-the JavaScript code for LiveReload to be added to your web pages.

-Interested? Here are some great tutorials contributed by Hugo users:

-* [hugo, syncthing](http://fredix.xyz/2014/10/hugo-syncthing/) (French) by Frédéric Logier (@fredix)

--- /dev/null

+++ b/content/readfiles/README.md

@@ -1,0 +1,16 @@

+# readdirs Directory for Reusable Content

+Files in this directory are:

+1. Used in *more than one place* within the Hugo docs

+2. Used in Examples of readdir (i.e. in local file templates)

+These files are called using the [`readfile` shortcode (source)](../layouts/readfile.html).

+You can call this shortcode in the docs as follows:

+<code>{</code><code>{</code>% readfile file="/path/to/file.txt" markdown="true" %<code>}</code><code>}</code>

+`markdown="true"` is optional (default = `"false"`) and parses the string through the Blackfriday renderer.

--- /dev/null

+++ b/content/readfiles/bfconfig.md

@@ -1,0 +1,55 @@

+`taskLists`

+: default: **`true`**<br>

+    Blackfriday flag: <br>

+    Purpose: `false` turns off GitHub-style automatic task/TODO list generation

+`smartypants`

+: default: **`true`** <br>

+    Blackfriday flag: **`HTML_USE_SMARTYPANTS`** <br>

+    Purpose: `false` disables smart punctuation substitutions, including smart quotes, smart dashes, smart fractions, etc. If `true`, it may be fine-tuned with the `angledQuotes`, `fractions`, `smartDashes`, and `latexDashes` flags (see below).

+`angledQuotes`

+: default: **`false`**<br>

+    Blackfriday flag: **`HTML_SMARTYPANTS_ANGLED_QUOTES`**<br>

+    Purpose: `true` enables smart, angled double quotes. Example: "Hugo" renders to renders to «Hugo» instead of “Hugo”.

+`fractions`

+: default: **`true`**<br>

+    Blackfriday flag: **`HTML_SMARTYPANTS_FRACTIONS`** <br>

+    Purpose: <code>false</code> disables smart fractions.<br>

+    Example: `5/12` renders to <sup>5</sup>&frasl;<sub>12</sub>(<code>&lt;sup&gt;5&lt;/sup&gt;&amp;frasl;&lt;sub&gt;12&lt;/sub&gt;</code>).<br> <strong>Caveat:</strong> Even with <code>fractions = false</code>, Blackfriday still converts `1/2`, `1/4`, and `3/4` respectively to ½ (<code>&amp;frac12;</code>), ¼ (<code>&amp;frac14;</code>) and ¾ (<code>&amp;frac34;</code>), but only these three.</small>

+`smartDashes`

+: default: **`true`** <br>

+    Blackfriday flag: **`HTML_SMARTY_DASHES`** <br>

+    Purpose: `false` disables smart dashes; i.e., the conversion of multiple hyphens into an en dash or em dash. If `true`, its behavior can be modified with the `latexDashes` flag below.

+`latexDashes`

+: default: **`true`** <br>

+    Blackfriday flag: **`HTML_SMARTYPANTS_LATEX_DASHES`** <br>

+    Purpose: `false` disables LaTeX-style smart dashes and selects conventional smart dashes. Assuming `smartDashes`: <br>

+    If `true`, `--` is translated into &ndash; (`&ndash;`), whereas `---` is translated into &mdash; (`&mdash;`). <br>

+    However, *spaced* single hyphen between two words is translated into an en&nbsp;dash&mdash; e.g., "`12 June - 3 July`" becomes `12 June ndash; 3 July` upon rendering.

+`hrefTargetBlank`

+: default: **`false`** <br>

+    Blackfriday flag: **`HTML_HREF_TARGET_BLANK`** <br>

+    Purpose: `true` opens external links in a new window or tab.

+`plainIDAnchors`

+: default **`true`** <br>

+    Blackfriday flag: **`FootnoteAnchorPrefix` and `HeaderIDSuffix`** <br>

+    Purpose: `true` renders any heading and footnote IDs without the document ID. <br>

+    Example: renders `#my-heading` instead of `#my-heading:bec3ed8ba720b970`

+`extensions`

+: default: **`[]`** <br>

+    Blackfriday flag: **`EXTENSION_*`** <br>

+    Purpose: Enable one or more Blackfriday's Markdown extensions (if they aren't Hugo defaults). <br>

+    Example: Include `hardLineBreak` in the list to enable Blackfriday's `EXTENSION_HARD_LINK_BREAK`

+`extensionsmask`

+: default: **`[]`** <br>

+    Blackfriday flag: **`EXTENSION_*`** <br>

+    Purpose: Enable one or more of Blackfriday's Markdown extensions (if they aren't Hugo defaults). <br>

+    Example: Include `autoHeaderIds` as `false` in the list to disable Blackfriday's `EXTENSION_AUTO_HEADER_IDS`.

\ No newline at end of file

--- /dev/null

+++ b/content/readfiles/dateformatting.md

@@ -1,0 +1,87 @@

+Go templates [format your dates][time] according to a single reference time:

+```

+Mon Jan 2 15:04:05 MST 2006

+```

+You can think of `MST` as `07`, thus making the reference format string a sequence of numbers. The following is [taken directly from the Go docs][gdex]:

+```

+Jan 2 15:04:05 2006 MST

+  1 2  3  4  5    6  -7

+```

+### Hugo Date Templating Reference

+Each of the following examples show the reference formatting string followed by the string Hugo will output in your HTML.

+Note that the examples were rendered and tested in [CST][] and pull from a single example date you might have in your content's front matter:

+```

+date: 2017-03-03T14:15:59-06:00

+```

+`.Date` (i.e. called via [page variable][pagevars])

+: **Returns**: `2017-03-03 14:15:59 -0600 CST`

+`"Monday, January 2, 2006"`

+: **Returns**: `Friday, March 3, 2017`

+`"Mon Jan 2 2006"`

+: **Returns**: `Fri Mar 3 2017`

+`"January 2nd"`

+: **Returns**: `March 3rd`

+`"January 2006"`

+: **Returns**: `March 2017`

+`"2006-01-02"`

+: **Returns**: `2017-03-03`

+`"Monday"`

+: **Returns**: `Friday`

+`"02 Jan 06 15:04 MST"` (RFC822)

+: **Returns**: `03 Mar 17 14:15 CST`

+`"02 Jan 06 15:04 -0700"` (RFC822Z)

+: **Returns**: `03 Mar 17 14:15 -0600`

+`"Mon, 02 Jan 2006 15:04:05 MST"` (RFC1123)

+: **Returns**: `Fri, 03 Mar 2017 14:15:59 CST`

+`"Mon, 02 Jan 2006 15:04:05 -0700"` (RFC339)

+: **Returns**: `Fri, 03 Mar 2017 14:15:59 -0600`

+### Cardinal Numbers and Ordinal Abbreviations

+Spelled-out cardinal numbers (e.g. "one", "two", and "three") and ordinal abbreviations (e.g. "1st", "2nd", and "3rd") are not currently supported.

+To continue with the example above:

+```

+{{.Date.Format "Jan 2nd 2006"}}

+```

+Hugo assumes you want to append `nd` as a string to the day of the month and outputs the following:

+```

+Mar 3nd 2017

+```

+### Use `.Local` and `.UTC`

+In conjunction with the [`dateFormat` function][dateFormat], you can also convert your dates to `UTC` or to local timezones:

+`{{ dateFormat "02 Jan 06 15:04 MST" .Date.UTC }}`

+: **Returns**: `03 Mar 17 20:15 UTC`

+`{{ dateFormat "02 Jan 06 15:04 MST" .Date.Local }}`

+: **Returns**: `03 Mar 17 14:15 CST`

+[CST]: https://en.wikipedia.org/wiki/Central_Time_Zone

+[dateFormat]: /functions/dateformat/

+[gdex]: https://golang.org/pkg/time/#example_Time_Format

+[pagevars]: /variables/page/

+[time]: https://golang.org/pkg/time/

\ No newline at end of file

--- /dev/null

+++ b/content/readfiles/menuvars.md

@@ -1,0 +1,39 @@

+`.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

\ No newline at end of file

--- /dev/null

+++ b/content/readfiles/testing.txt

@@ -1,0 +1,3 @@

+##### Hello World!

+Testing one, **two**, *three*. Don't delete this sample file used in the [templates](/templates/) section of the Hugo docs.

\ No newline at end of file

--- a/content/release-notes/0.20.3-relnotes.md

+++ /dev/null

@@ -1,23 +1,0 @@

----

-date: 2017-04-24

-title: 0.20.3

----

-This is a bug-fix release with one important fix. But it also adds some harness around [GoReleaser](https://github.com/goreleaser/goreleaser) to automate the Hugo release process. Big thanks to [@caarlos0](https://github.com/caarlos0) for great and super-fast support fixing issues along the way.

-Hugo now has:

-* 16619+ [stars](https://github.com/gohugoio/hugo/stargazers)

-* 458+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

-* 156+ [themes](http://themes.gohugo.io/)

-## Enhancement

-* Automate the Hugo release process [550eba64](https://github.com/gohugoio/hugo/commit/550eba64705725eb54fdb1042e0fb4dbf6f29fd0) [@bep](https://github.com/bep) [#3358](https://github.com/gohugoio/hugo/issues/3358)

-## Fix

-* Fix handling of zero-length files [9bf5c381](https://github.com/gohugoio/hugo/commit/9bf5c381b6b3e69d4d8dbfd7a40074ac44792bbf) [@bep](https://github.com/bep) [#3355](https://github.com/gohugoio/hugo/issues/3355)

--- a/content/release-notes/0.20.4-relnotes.md

+++ /dev/null

@@ -1,28 +1,0 @@

----

-date: 2017-04-24T21:12:31+01:00

-title: 0.20.4

----

-This is the second bug-fix release of the day, fixing a couple of issues related to the new release scripts.

-Hugo now has:

-* 16626+ [stars](https://github.com/gohugoio/hugo/stargazers)

-* 457+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

-* 156+ [themes](http://themes.gohugo.io/)

-## Fixes

-* Fix statically linked binaries [275bcf56](https://github.com/gohugoio/hugo/commit/275bcf566c7cb72367d4423cf4810319311ff680) [@munnerz](https://github.com/munnerz) [#3382](https://github.com/gohugoio/hugo/issues/3382)

-* Filename change in Hugo 0.20.3 binaries [#3385](https://github.com/gohugoio/hugo/issues/3385)

-* Fix version calculation [cb3c6b6f](https://github.com/gohugoio/hugo/commit/cb3c6b6f7670f85189a4a3637e7132901d1ed6e9) [@bep](https://github.com/bep)

--- a/content/release-notes/0.20.5-relnotes.md

+++ /dev/null

@@ -1,9 +1,0 @@

----

-date: 2017-04-25

-title: 0.20.5

----

-This is a bug-fix release which fixes the version number of `0.20.4` (which wrongly shows up as `0.21-DEV`) ([#3388](https://github.com/gohugoio/hugo/issues/3388)).

--- a/content/release-notes/0.20.6-relnotes.md

+++ /dev/null

@@ -1,26 +1,0 @@

----

-date: 2017-04-27

-title: 0.20.6

----

-There have been some [shouting on discuss.gohugo.io](https://discourse.gohugo.io/t/index-md-is-generated-in-subfolder-index-index-html-hugo-0-20/6338/15) about some broken sites after the release of Hugo `0.20`. This release reintroduces the old behaviour, making  `/my-blog-post/index.md` work as expected.

-Hugo now has:

-* 16675+ [stars](https://github.com/gohugoio/hugo/stargazers)

-* 456+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

-* 156+ [themes](http://themes.gohugo.io/)

-## Fixes

-* Avoid index.md in /index/index.html [#3396](https://github.com/gohugoio/hugo/issues/3396)

-* Make missing GitInfo a WARNING [b30ca4be](https://github.com/gohugoio/hugo/commit/b30ca4bec811dbc17e9fd05925544db2b75e0e49) [@bep](https://github.com/bep) [#3376](https://github.com/gohugoio/hugo/issues/3376)

-* Fix some of the fpm fields for deb [3bd1d057](https://github.com/gohugoio/hugo/commit/3bd1d0571d5f2f6bf0dc8f90a8adf2dbfcb2fdfd) [@anthonyfok](https://github.com/anthonyfok)

--- a/content/release-notes/0.21-relnotes.md

+++ /dev/null

@@ -1,106 +1,0 @@

----

-date: 2017-05-22

-title: 0.21

----

-	Hugo `0.21` brings full support for shortcodes per [Output Format](https://gohugo.io/extras/output-formats/) ([#3220](https://github.com/gohugoio/hugo/issues/3220)), the last vital piece of that puzzle. This is especially useful for `Google AMP` with its many custom media tags.

-This release represents **126 contributions by 29 contributors** to the main Hugo code base. Since last main release Hugo has **gained 850 stars and 7 additional themes**.

-Hugo now has:

-* 17156+ [stars](https://github.com/gohugoio/hugo/stargazers)

-* 457+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

-* 163+ [themes](http://themes.gohugo.io/)

-[@bep](https://github.com/bep) leads the Hugo development with a significant amount of contributions, but also a big shoutout to [@moorereason](https://github.com/moorereason), [@bogem](https://github.com/bogem), and [@munnerz](https://github.com/munnerz) for their ongoing contributions. And as always a big thanks to [@digitalcraftsman](https://github.com/digitalcraftsman) for his relentless work on keeping the documentation and the themes site in pristine condition.

-## Other Highlights

-On a more technical side, [@moorereason](https://github.com/moorereason) and [@bep](https://github.com/bep) have introduced namespaces for Hugo's many template funcs ([#3042](https://github.com/gohugoio/hugo/issues/3042) ). There are so many now, and adding more into that big pile would be a sure path toward losing control.  Now they are nicely categorised into namespaces with its own tests and examples, with an API that the documentation site can use to make sure it is correct and up-to-date.

-## Notes

-* The deprecated `.Extension`, `.Now` and `.TargetPath` will now `ERROR` [544f0a63](https://github.com/gohugoio/hugo/commit/544f0a6394b0e085d355e8217fc5bb3d96c12a98) [@bep](https://github.com/bep)

-* The config settings and flags `disable404`, `disableRSS`, `disableSitemap`, `disableRobotsTXT` are now deprecated. Use `disableKinds`. [5794a265](https://github.com/gohugoio/hugo/commit/5794a265b41ffdeebfd8485eecf65cf4088d49d6) [@bep](https://github.com/bep) [#3345](https://github.com/gohugoio/hugo/issues/3345)

-## Enhancements

-### Templates

-* Log a WARNING on wrong usage of `IsSet` [38661c17](https://github.com/gohugoio/hugo/commit/38661c17bb8c31c9f31ee18f8eba5e3bfddd5574) [@moorereason](https://github.com/moorereason) [#3092](https://github.com/gohugoio/hugo/issues/3092)

-* Add support for ellipsed paginator navigator, making paginators with lots of pages more compact  [b6ea492b](https://github.com/gohugoio/hugo/commit/b6ea492b7a6325d04d44eeb00a990a3a0e29e0c0) [@bep](https://github.com/bep) [#3466](https://github.com/gohugoio/hugo/issues/3466)

-* Add support for interfaces to `intersect` [f1c29b01](https://github.com/gohugoio/hugo/commit/f1c29b017bbd88e701cd5151dd186e868672ef89) [@moorereason](https://github.com/moorereason) [#1952](https://github.com/gohugoio/hugo/issues/1952)

-* Add `NumFmt` function [93b3b138](https://github.com/gohugoio/hugo/commit/93b3b1386714999d716e03b131f77234248f1724) [@moorereason](https://github.com/moorereason) [#1444](https://github.com/gohugoio/hugo/issues/1444)

-* Add template function namespaces [#3418](https://github.com/gohugoio/hugo/issues/3418)  [#3042](https://github.com/gohugoio/hugo/issues/3042)  [@moorereason](https://github.com/moorereason)  [@bep](https://github.com/bep)

-* Add translation links to the default sitemap template [90d3fbf1](https://github.com/gohugoio/hugo/commit/90d3fbf1da93a279cfe994a226ae82cf5441deab) [@rayjolt](https://github.com/rayjolt) [#2569](https://github.com/gohugoio/hugo/issues/2569)

-* Allow text partials in HTML templates and the other way around [1cf29200](https://github.com/gohugoio/hugo/commit/1cf29200b4bb0a9c006155ec76759b7f4b1ad925) [@bep](https://github.com/bep) [#3273](https://github.com/gohugoio/hugo/issues/3273)

-### Output

-* Refactor site rendering with an "output format context". In this release, this is used for shortcode handling only, but this paves the way for future niceness [1e4d082c](https://github.com/gohugoio/hugo/commit/1e4d082cf5b92fedbc60b1b4f0e9d1ee6ec45e33) [@bep](https://github.com/bep) [#3397](https://github.com/gohugoio/hugo/issues/3397)  [2bcbf104](https://github.com/gohugoio/hugo/commit/2bcbf104006e0ec03be4fd500f2519301d460f8c) [@bep](https://github.com/bep) [#3220](https://github.com/gohugoio/hugo/issues/3220)

-### Core

-* Handle `shortcode` per `Output Format` [af72db80](https://github.com/gohugoio/hugo/commit/af72db806f2c1c0bf1dfe5832275c41eeba89906) [@bep](https://github.com/bep) [#3220](https://github.com/gohugoio/hugo/issues/3220)

-* Improve shortcode error message [58d9cbd3](https://github.com/gohugoio/hugo/commit/58d9cbd31bcf7c296a39860fd7e566d10faaff28) [@bep](https://github.com/bep)

-* Avoid `index.md` in `/index/index.html` [fea4fd86](https://github.com/gohugoio/hugo/commit/fea4fd86a324bf9679df23f8289887d91b42e919) [@bep](https://github.com/bep) [#3396](https://github.com/gohugoio/hugo/issues/3396)

-* Make missing `GitInfo` a `WARNING` [5ad2f176](https://github.com/gohugoio/hugo/commit/5ad2f17693a9860be76ef8089c8728d2b59d6b04) [@bep](https://github.com/bep) [#3376](https://github.com/gohugoio/hugo/issues/3376)

-* Prevent decoding `pageParam` in common cases [e98f885b](https://github.com/gohugoio/hugo/commit/e98f885b8af27f5473a89d31d0b1f02e61e8a5ec) [@bogem](https://github.com/bogem)

-* Ignore non-source files on partial rebuild [b5b6e81c](https://github.com/gohugoio/hugo/commit/b5b6e81c0269abf9b0f4bc6a127744a25344e5c6) [@xofyarg](https://github.com/xofyarg) [#3325](https://github.com/gohugoio/hugo/issues/3325)

-* Log `WARNING` only on unknown `/data` files [ab692e73](https://github.com/gohugoio/hugo/commit/ab692e73dea3ddfe979c88ee236cc394e47e82f1) [@bep](https://github.com/bep) [#3361](https://github.com/gohugoio/hugo/issues/3361)

-* Avoid processing the same notify event twice [3b677594](https://github.com/gohugoio/hugo/commit/3b67759495c9268c30e6ba2d8c7e3b75d52d2960) [@bep](https://github.com/bep)

-* Only show `rssURI` deprecation `WARNING` if it is actually set [cfd3af8e](https://github.com/gohugoio/hugo/commit/cfd3af8e691119461effa4385251b9d3818e2291) [@bep](https://github.com/bep) [#3319](https://github.com/gohugoio/hugo/issues/3319)

-### Docs

-* Add documentation on slug translation [635b3bb4](https://github.com/gohugoio/hugo/commit/635b3bb4eb873978c7d52e6c0cb85da0c4d25299) [@xavib](https://github.com/xavib)

-* Replace `cdn.mathjax.org` with `cdnjs.cloudflare.com` [4b637ac0](https://github.com/gohugoio/hugo/commit/4b637ac041d17b22187f5ccd0f65461f0065aaa9) [@takuti](https://github.com/takuti)

-* Add notes about some output format behaviour [162d3a58](https://github.com/gohugoio/hugo/commit/162d3a586d36cabf6376a76b096fd8b6414487ae) [@jpatters](https://github.com/jpatters)

-* Add `txtpen` as alternative commenting service [7cdc244a](https://github.com/gohugoio/hugo/commit/7cdc244a72de4c08edc0008e37aec83d945dccdf) [@rickyhan](https://github.com/rickyhan)

-### Other

-* Embed `Page` in `WeightedPage` [ebf677a5](https://github.com/gohugoio/hugo/commit/ebf677a58360126d8b9a1e98d086aa4279f53181) [@bep](https://github.com/bep) [#3435](https://github.com/gohugoio/hugo/issues/3435)

-* Improve the detection of untranslated strings [a40d1f6e](https://github.com/gohugoio/hugo/commit/a40d1f6ed2aedddc99725658993258cd557640ed) [@bogem](https://github.com/bogem) [#2607](https://github.com/gohugoio/hugo/issues/2607)

-* Make first letter of the Hugo commands flags' usage lowercase [f0f69d03](https://github.com/gohugoio/hugo/commit/f0f69d03c551acb8ac2eeedaad579cf0b596f9ef) [@bogem](https://github.com/bogem)

-* Import `Octopress` image tag in `Jekyll importer` [5f3ad1c3](https://github.com/gohugoio/hugo/commit/5f3ad1c31985450fab8d6772e9cbfcb57cf5cc53) [@buynov](https://github.com/buynov)

-## Fixes

-### Templates

-*  Do not lower case template names [6d2ea0f7](https://github.com/gohugoio/hugo/commit/6d2ea0f7d7e8a54b8edfc36e52ff74266c30dc27) [@bep](https://github.com/bep) [#3333](https://github.com/gohugoio/hugo/issues/3333)

-### Output

-* Fix output format mixup in example [10287263](https://github.com/gohugoio/hugo/commit/10287263f529181d3169668b044cb84e2e3b049a) [@bep](https://github.com/bep) [#3481](https://github.com/gohugoio/hugo/issues/3481)

-* Fix base theme vs project base template logic [077005e5](https://github.com/gohugoio/hugo/commit/077005e514b1ed50d84ceb90c7c72f184cb04521) [@bep](https://github.com/bep) [#3323](https://github.com/gohugoio/hugo/issues/3323)

-### Core

-* Render `404` in default language only [154e18dd](https://github.com/gohugoio/hugo/commit/154e18ddb9ad205055d5bd4827c87f3f0daf499f) [@mitchchn](https://github.com/mitchchn) [#3075](https://github.com/gohugoio/hugo/issues/3075)

-* Fix `RSSLink` vs `RSS` `Output Format` [e682fcc6](https://github.com/gohugoio/hugo/commit/e682fcc62233b47cf5bdcaf598ac0657ef089471) [@bep](https://github.com/bep) [#3450](https://github.com/gohugoio/hugo/issues/3450)

-* Add default config for `ignoreFiles`, making that option work when running in server mode [42f4ce15](https://github.com/gohugoio/hugo/commit/42f4ce15a9d68053da36f9efcf7a7d975cc59559) [@chaseadamsio](https://github.com/chaseadamsio)

-* Fix output formats override when no outputs definition given [6e2f2dd8](https://github.com/gohugoio/hugo/commit/6e2f2dd8d3ca61c92a2ee8824fbf05cadef08425) [@bep](https://github.com/bep) [#3447](https://github.com/gohugoio/hugo/issues/3447)

-* Fix handling of zero-length files [0e87b18b](https://github.com/gohugoio/hugo/commit/0e87b18b66d2c8ba9e2abc429630cb03f5b093d6) [@bep](https://github.com/bep) [#3355](https://github.com/gohugoio/hugo/issues/3355)

-* Must recreate `Paginator` on live-reload [45c74526](https://github.com/gohugoio/hugo/commit/45c74526686f6a2afa02bcee767d837d6b9dd028) [@bep](https://github.com/bep) [#3315](https://github.com/gohugoio/hugo/issues/3315)

-### Docs

-* Fix incorrect path in `templates/list` [27e88154](https://github.com/gohugoio/hugo/commit/27e88154af2dd9af6d0523d6e67b612e6336f91c) [@MunifTanjim](https://github.com/MunifTanjim)

-* Fixed incorrect specification of directory structure [a28fbca6](https://github.com/gohugoio/hugo/commit/a28fbca6dcfa80b6541f5ef6c8c12cd1804ae9ed) [@TejasQ](https://github.com/TejasQ)

-* Fix `bash` command in `tutorials/github-pages-blog` [c9976155](https://github.com/gohugoio/hugo/commit/c99761555c014e4d041438d5d7e53a6cbaee4492) [@hansott](https://github.com/hansott)

-* Fix `.Data.Pages` range in example [b5e32eb6](https://github.com/gohugoio/hugo/commit/b5e32eb60993b4656918af2c959ae217a68c461e) [@hxlnt](https://github.com/hxlnt)

-### Other

-* Fix data race in live-reload close, avoiding some rare panics [355736ec](https://github.com/gohugoio/hugo/commit/355736ec357c81dfb2eb6851ee019d407090c5ec) [@bep](https://github.com/bep) [#2625](https://github.com/gohugoio/hugo/issues/2625)

-* Skip `.git` directories in file scan [94b5be67](https://github.com/gohugoio/hugo/commit/94b5be67fc73b87d114d94a7bb1a33ab997f30f1) [@bogem](https://github.com/bogem) [#3468](https://github.com/gohugoio/hugo/issues/3468)

--- a/content/release-notes/0.22-relnotes.md

+++ /dev/null

@@ -1,85 +1,0 @@

----

-date: 2017-06-12

-title: 0.22

----

-Hugo `0.22` brings **nested sections**, by popular demand and a long sought after feature ([#465](https://github.com/gohugoio/hugo/issues/465)).  We are still low on documentation for this great feature, but [@bep](https://github.com/bep)  has been kind enough to accompany his implementation with a [demo site](http://hugotest.bep.is/).

-This release represents **58 contributions by 10 contributors** to the main Hugo code base. Since last release Hugo has **gained 420 stars and 2 additional themes.**

-[@bep](https://github.com/bep) still leads the Hugo development with his witty Norwegian humor, and once again contributed a significant amount of additions. But also a big shoutout to [@bogem](https://github.com/bogem), [@moorereason](https://github.com/moorereason), and [@onedrawingperday](https://github.com/onedrawingperday) for their ongoing contributions. And as always big thanks to [@digitalcraftsman](https://github.com/digitalcraftsman) for his relentless work on keeping the documentation and the themes site in pristine condition.

-Hugo now has:

-* 17576+ [stars](https://github.com/gohugoio/hugo/stargazers)

-* 455+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

-* 165+ [themes](http://themes.gohugo.io/)

-## Other Highlights

-`.Site.GetPage` can now also be used to get regular pages ([#2844](https://github.com/gohugoio/hugo/issues/2844)):

-```go

-{{ (.Site.GetPage "page" "blog" "mypost.md" ).Title }}

-```

-Also, considerable work has been put into writing automated benchmark tests for the site builds, and we're happy to report that although this release comes with fundamental structural changes, this version is -- in general -- even faster than the previous. It’s quite a challenge to consistently add significant new functionality and simultaneously maintain the stellar performance Hugo is famous for.

-## Notes

-`.Site.Sections` is replaced. We have reworked how sections work in Hugo, they can now be nested and are no longer taxonomies. If you use the old collection, you should get detailed upgrade instructions in the log when you run `hugo`. For more information, see this [demo site](http://hugotest.bep.is/).

-## Enhancements

-### Templates

-* Add `uint` support to `In` [b82cd82f](https://github.com/gohugoio/hugo/commit/b82cd82f1198a371ed94bda7faafe22813f4cb29) [@moorereason](https://github.com/moorereason)

-* Support interfaces in `union` [204c3a9e](https://github.com/gohugoio/hugo/commit/204c3a9e32fcf6617ede978e35d3e2e89a5b491c) [@moorereason](https://github.com/moorereason) [#3411](https://github.com/gohugoio/hugo/issues/3411)

-* Add `uniq` function [e28d9aa4](https://github.com/gohugoio/hugo/commit/e28d9aa42c3429d22fe254e69e4605aaf1e684f3) [@adiabatic](https://github.com/adiabatic)

-* Handle `template.HTML` and friends in `ToInt` [4113693a](https://github.com/gohugoio/hugo/commit/4113693ac1b275f3a40aa5c248269340ef9b57f6) [@moorereason](https://github.com/moorereason) [#3308](https://github.com/gohugoio/hugo/issues/3308)

-### Core

-* Make the `RSS feed` use the date for the node it represents [f1da5a15](https://github.com/gohugoio/hugo/commit/f1da5a15a37666ee59350d6600a8c14c1383f5bc) [@bep](https://github.com/bep) [#2708](https://github.com/gohugoio/hugo/issues/2708)

-* Enable `nested sections` [b3968939](https://github.com/gohugoio/hugo/commit/b39689393ccb8434d9a57658a64b77568c718e99) [@bep](https://github.com/bep) [#465](https://github.com/gohugoio/hugo/issues/465)

-* Add test for "no 404" in `sitemap` [8aaec644](https://github.com/gohugoio/hugo/commit/8aaec644a90d09bd7f079d35d382f76bb4ed35db) [@bep](https://github.com/bep) [#3563](https://github.com/gohugoio/hugo/issues/3563)

-* Support regular pages in `.Site.GetPage` [e0c2e798](https://github.com/gohugoio/hugo/commit/e0c2e798201f75ae6e9a81a7442355288c2d141b) [@bep](https://github.com/bep) [#2844](https://github.com/gohugoio/hugo/issues/2844)

-[#3082](https://github.com/gohugoio/hugo/issues/3082)

-### Performance

-* Add site building benchmarks [8930e259](https://github.com/gohugoio/hugo/commit/8930e259d78cba4041b550cc51a7f40bc91d7c20) [@bep](https://github.com/bep) [#3535](https://github.com/gohugoio/hugo/issues/3535)

-* Add a cache to `GetPage` which makes it much faster [50d11138](https://github.com/gohugoio/hugo/commit/50d11138f3e18b545c15fadf52f7b0b744bf3e7c) [@bep](https://github.com/bep)

-* Speed up `GetPage` [fbb78b89](https://github.com/gohugoio/hugo/commit/fbb78b89df8ccef8f0ab26af00aa45d35c1ee2cf) [@bep](https://github.com/bep) [#3503](https://github.com/gohugoio/hugo/issues/3503)

-* Add BenchmarkFrontmatterTags [3d9c4f51](https://github.com/gohugoio/hugo/commit/3d9c4f513b0443648d7e88995e351df1739646d2) [@bep](https://github.com/bep) [#3464](https://github.com/gohugoio/hugo/issues/3464)

-* Add `benchSite.sh` to make it easy to run Hugo performance benchmarks [d74452cf](https://github.com/gohugoio/hugo/commit/d74452cfe8f69a85ec83e05481e16bebf199a5cb) [@bep](https://github.com/bep)

-* Cache language config [4aff2b6e](https://github.com/gohugoio/hugo/commit/4aff2b6e7409a308f30cff1825fec02991e0d56a) [@bep](https://github.com/bep)

-* Temporarily revert to BurntSushi for `TOML` front matter handling; it is currently much faster [0907a5c1](https://github.com/gohugoio/hugo/commit/0907a5c1c293755e6bf297246f07888448d81f8b) [@bep](https://github.com/bep) [#3541](https://github.com/gohugoio/hugo/issues/3541) [#3464](https://github.com/gohugoio/hugo/issues/3464)

-* Add a simple partitioned lazy cache [87203139](https://github.com/gohugoio/hugo/commit/87203139c38e0b992c96d7b8a23c7730649c68e5) [@bep](https://github.com/bep)

-### Other

-* Add `noindex` tag to HTML generated by Hugo aliases [d5ab7f08](https://github.com/gohugoio/hugo/commit/d5ab7f087d967b30e7de7d789e6ad3091b42f1f7) [@onedrawingperday](https://github.com/onedrawingperday)

-* Update Go versions [bde807bd](https://github.com/gohugoio/hugo/commit/bde807bd1e560fb4cc765c0fc22132db7f8a0801) [@bep](https://github.com/bep)

-* Remove the `rlimit` tweaking on `macOS` [bcd32f10](https://github.com/gohugoio/hugo/commit/bcd32f1086c8c604fb22a7496924e41cc46b1605) [@bep](https://github.com/bep) [#3512](https://github.com/gohugoio/hugo/issues/3512)

-### Docs

-* Rewrite “Archetypes” article [@davidturnbull](https://github.com/davidturnbull) [#3543](https://github.com/gohugoio/hugo/pull/3543/)

-* Remove Unmaintaned Frontends from Tools. [f41f7282](https://github.com/gohugoio/hugo/commit/f41f72822251c9a31031fd5b3dda585c57c8b028) [@onedrawingperday](https://github.com/onedrawingperday)

-## Fixes

-### Core

-* Improve `live-reload` on directory structure changes making removal of directories or pasting new content directories into  `/content` just work [fe901b81](https://github.com/gohugoio/hugo/commit/fe901b81191860b60e6fcb29f8ebf87baef2ee79) [@bep](https://github.com/bep) [#3570](https://github.com/gohugoio/hugo/issues/3570)

-* Respect `disableKinds=["sitemap"]` [69d92dc4](https://github.com/gohugoio/hugo/commit/69d92dc49cb8ab9276ab013d427ba2d9aaf9135d) [@bep](https://github.com/bep) [#3544](https://github.com/gohugoio/hugo/issues/3544)

-* Fix `disablePathToLower` regression [5be04486](https://github.com/gohugoio/hugo/commit/5be0448635fdf5fe6b1ee673e869f2b9baf1a5c6) [@bep](https://github.com/bep) [#3374](https://github.com/gohugoio/hugo/issues/3374)

-* Fix `ref`/`relref` issue with duplicate base filenames [612f6e3a](https://github.com/gohugoio/hugo/commit/612f6e3afe0510c31f70f3621f3dc8ba609dade4) [@bep](https://github.com/bep) [#2507](https://github.com/gohugoio/hugo/issues/2507)

-### Docs

-* Fix parameter name in `YouTube` shortcode section [37e37877](https://github.com/gohugoio/hugo/commit/37e378773fbc127863f2b7a389d5ce3a14674c73) [@zivbk1](https://github.com/zivbk1)

--- a/content/release-notes/0.22.1-relnotes.md

+++ /dev/null

@@ -1,40 +1,0 @@

----

-date: 2017-06-13

-title: 0.22.1

----

-Hugo `0.22.1` fixes a couple of issues reported after the [0.22 release](https://github.com/gohugoio/hugo/releases/tag/v0.22) Monday. Most importantly a fix for detecting regular subfolders below the root-sections.

-Also, we forgot to adapt the `permalink settings` with support for nested sections, which made that feature less useful than it could be.

-With this release you can configure **permalinks with sections** like this:

-**First level only:**

-```toml

-[permalinks]

-blog = ":section/:title"

-```

-**Nested (all levels):**

-```toml

-[permalinks]

-blog = ":sections/:title"

-```

-## Fixes

-* Fix section logic for root folders with subfolders [a30023f5](https://github.com/gohugoio/hugo/commit/a30023f5cbafd06034807255181a5b7b17f3c25f) [@bep](https://github.com/bep) [#3586](https://github.com/gohugoio/hugo/issues/3586)

-* Support sub-sections in permalink settings [1f26420d](https://github.com/gohugoio/hugo/commit/1f26420d392a5ab4c7b7fe1911c0268b45d01ab8) [@bep](https://github.com/bep) [#3580](https://github.com/gohugoio/hugo/issues/3580)

-* Adjust rlimit to 64000 [ff54b6bd](https://github.com/gohugoio/hugo/commit/ff54b6bddcefab45339d8dc2b13776b92bdc04b9) [@bep](https://github.com/bep) [#3582](https://github.com/gohugoio/hugo/issues/3582)

-* Make error on setting rlimit a warning only [629e1439](https://github.com/gohugoio/hugo/commit/629e1439e819a7118ae483381d4634f16d3474dd) [@bep](https://github.com/bep) [#3582](https://github.com/gohugoio/hugo/issues/3582)

-* Revert: Remove the rlimit tweaking on macOS" [26aa06a3](https://github.com/gohugoio/hugo/commit/26aa06a3db57ab7134a900d641fa2976f7971520) [@bep](https://github.com/bep) [#3582](https://github.com/gohugoio/hugo/issues/3582)

--- a/content/release-notes/0.23-relnotes.md

+++ /dev/null

@@ -1,52 +1,0 @@

----

-date: 2017-06-16

-title: 0.23

----

-Hugo `0.23` is mainly a release that handles all the small changes needed to get Hugo moved to a GitHub organisation: [gohugoio](https://github.com/gohugoio), but it also contains a couple of important fixes that makes this an update worth-while for all.

-Hugo now has:

-* 17739+ [stars](https://github.com/gohugoio/hugo/stargazers)

-* 494+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

-* 165+ [themes](http://themes.gohugo.io/)

-## Fixes

-* Fix handling of duplicate footnotes [a9e551a1](https://github.com/gohugoio/hugo/commit/a9e551a100e60a603210ee083103dd73369d6a98) [@bep](https://github.com/bep) [#1912](https://github.com/gohugoio/hugo/issues/1912)

-*  Add support for spaces in project folder for `GitInfo` #3533 #3552

-## GitHub organisation related changes

-* Update layout references to gohugoio/hugo [66d4850b](https://github.com/gohugoio/hugo/commit/66d4850b89db293dc58e828de784037f06c6c8dc) [@bep](https://github.com/bep)

-* Update content references to gohugoio/hugo [715ff1f8](https://github.com/gohugoio/hugo/commit/715ff1f87406edf27738c8c0f52fe185fa974ee8) [@bep](https://github.com/bep)

-* Add note on updates for rpm-based distros [52a0cea6](https://github.com/gohugoio/hugo/commit/52a0cea65de7b75ae1662abe3dec36fca3604617) [@daftaupe](https://github.com/daftaupe)

-* Update logo link in README [ccb8300d](https://github.com/gohugoio/hugo/commit/ccb8300d380636d75a39f4133284eb0109e836c3) [@bep](https://github.com/bep)

-* Remove docs building from CI builds [214dbdfb](https://github.com/gohugoio/hugo/commit/214dbdfb6f016d21415bc1ed511a37a084238878) [@bep](https://github.com/bep)

-* Adjust docs path [729be807](https://github.com/gohugoio/hugo/commit/729be8074bddb58c9111f32c55cc769e49cd0d5a) [@bep](https://github.com/bep)

-* Add docs as submodule [6cee0dfe](https://github.com/gohugoio/hugo/commit/6cee0dfe53899d433afc3c173a87d56265904cb0) [@bep](https://github.com/bep)

-* Update Gitter link in README [fbb25014](https://github.com/gohugoio/hugo/commit/fbb25014e1306ce7127d53e5fc4fc49867790336) [@bep](https://github.com/bep)

-* Change Windows build badge link, take #3 [86543d6a](https://github.com/gohugoio/hugo/commit/86543d6a50251b40540ebd0b851d45eb99d017c7) [@bep](https://github.com/bep)

-* Update Windows build link [e6ae32a0](https://github.com/gohugoio/hugo/commit/e6ae32a0ba75b9894418227e87391defbb1b3b49) [@bep](https://github.com/bep)

-* Update links in CONTRIBUTING.md due to the org transition [95386544](https://github.com/gohugoio/hugo/commit/95386544e858949a2baa414f395f30aaf66a6257) [@digitalcraftsman](https://github.com/digitalcraftsman)

-* Update source path in Dockerfile due to the org transition [7b99fb9f](https://github.com/gohugoio/hugo/commit/7b99fb9f1ca8381457afe9d8e953a388b8ada182) [@digitalcraftsman](https://github.com/digitalcraftsman)

-* Update clone folder in appveyor.yml due to the org transition [d531d17b](https://github.com/gohugoio/hugo/commit/d531d17b3be0b14faf4934611e01ac3289e37835) [@digitalcraftsman](https://github.com/digitalcraftsman)

-* Update import path in snapcraft.yaml due to the org transition [9266bf9d](https://github.com/gohugoio/hugo/commit/9266bf9d4c24592b875a7f6b92f761b4cea40879) [@digitalcraftsman](https://github.com/digitalcraftsman)

-* Run gofmt to get imports in line vs gohugoio/hugo [873a6f18](https://github.com/gohugoio/hugo/commit/873a6f18851bcda79d562ff6c02e1109e8e31a88) [@bep](https://github.com/bep)

-* Update Makefile vs gohugoio/hugo [f503d76a](https://github.com/gohugoio/hugo/commit/f503d76a3b2719bbb65ab9df5595d0dbc871fae9) [@bep](https://github.com/bep)

-* Update README to point to gohugoio/hugo [93643860](https://github.com/gohugoio/hugo/commit/93643860c9db10c6c32176b17cc83f1c317279bd) [@bep](https://github.com/bep)

-* Update examples to point to gohugoio/hugo [db46bcf8](https://github.com/gohugoio/hugo/commit/db46bcf82d060656d4bc731550e63ec9cf8576f2) [@bep](https://github.com/bep)

-* Update textual references in Go source to point to gohugoio/hugo [c17ad675](https://github.com/gohugoio/hugo/commit/c17ad675e8fcdb2db40fc50816b8f016bc14294c) [@bep](https://github.com/bep)

-* Update import paths to gohugoio/hugo [d8717cd4](https://github.com/gohugoio/hugo/commit/d8717cd4c74e80ea8e20adead9321412a2d76022) [@bep](https://github.com/bep)

--- a/content/release-notes/0.24-relnotes.md

+++ /dev/null

@@ -1,72 +1,0 @@

----

-date: 2017-06-21

-title: 0.24

----

-This is **The Revival of the Archetypes!**

-> "A feature that could be the name of the next Indiana Jones movie deserves its own release," says [@bep](https://github.com/bep).

-Hugo now handles the **archetype files as Go templates**. This means that the issues with sorting and lost comments are long gone. This also means that you will have to supply all values, including title and date. But this also opens up a lot of new windows.

-A fictional example for the section `newsletter` and the archetype file `archetypes/newsletter.md`:

-```markdown

----

-title: "{{ replace .TranslationBaseName "-" " " | title }}"

-date: {{ .Date }}

-draft: true

----

-**Insert Lead paragraph here.**

-<!--more-->

-## New Cool Posts

-{{ range first 10 ( where .Site.RegularPages "Type" "cool" ) }}

-* {{ .Title }}

-{{ end }}

-```

-And then create a new post with:

-```bash

-hugo new newsletter/the-latest-cool.stuff.md

-```

-**Note:** the site will only be built if the `.Site` is in use in the archetype file, and this can be time consuming for big sites.

-**Hot Tip:** If you set the `newContentEditor` configuration variable to an editor on your `PATH`, the newly created article will be opened.

-The above _newsletter type archetype_ illustrates the possibilities: The full Hugo `.Site` and all of Hugo's template funcs can be used in the archetype file.

-**Also, Hugo now supports archetype files for all content formats, not just markdown.**

-Hugo now has:

-* 17839+ [stars](https://github.com/gohugoio/hugo/stargazers)

-* 493+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)

-* 166+ [themes](http://themes.gohugo.io/)

-## Notes

-Archetype files now need to be complete, including `title` and `date`.

-## Enhancements

-* Support extension-less media types. The motivation behind this change is to support Netlify's `_redirects` files, so we can generate server-side redirects for the Hugo docs site. See [this commit](https://github.com/gohugoio/hugoDocs/commit/c1ab9894e8292e0a74c43bbca2263b1fb3840f9e) to see how we configured that. [0f40e1fa](https://github.com/gohugoio/hugo/commit/0f40e1fadfca2276f65adefa6d7d5d63aef9160a) [@bep](https://github.com/bep) [#3614](https://github.com/gohugoio/hugo/issues/3614)

-* Add `disableAliases` [516e6c6d](https://github.com/gohugoio/hugo/commit/516e6c6dc5733cdaf985317d58eedbc6ec0ef2f7) [@bep](https://github.com/bep) [#3613](https://github.com/gohugoio/hugo/issues/3613)

-* Support non-md files as archetype files [19f2e729](https://github.com/gohugoio/hugo/commit/19f2e729135af700c5d4aa06e7b3540e6d4847fd) [@bep](https://github.com/bep) [#3597](https://github.com/gohugoio/hugo/issues/3597) [#3618](https://github.com/gohugoio/hugo/issues/3618)

-* Identify extension-less text types as text [c43b512b](https://github.com/gohugoio/hugo/commit/c43b512b4700f76ac77f12d632bb030c3a241393) [@bep](https://github.com/bep) [#3614](https://github.com/gohugoio/hugo/issues/3614)

-* Add `.Site` to the archetype templates [662e12f3](https://github.com/gohugoio/hugo/commit/662e12f348a638a6fcc92a416ee7f7c2a7ef8792) [@bep](https://github.com/bep) [#1629](https://github.com/gohugoio/hugo/issues/1629)

-* Use archetype template as-is as a Go template [422057f6](https://github.com/gohugoio/hugo/commit/422057f60709696bbbd1c38c9ead2bf114d47e31) [@bep](https://github.com/bep) [#452](https://github.com/gohugoio/hugo/issues/452) [#1629](https://github.com/gohugoio/hugo/issues/1629)

-* Update links to new discuss URL [4aa12390](https://github.com/gohugoio/hugo/commit/4aa1239070bb9d4324d3582f3e809b702a59d3ac) [@bep](https://github.com/bep)

-## Fixes

-* Fix error handling for `JSON` front matter [fb53987a](https://github.com/gohugoio/hugo/commit/fb53987a4ff2acb9da8dec6ec7b11924d37352ce) [@bep](https://github.com/bep) [#3610](https://github.com/gohugoio/hugo/issues/3610)

-* Fix handling of quoted brackets in `JSON` front matter [3183b9a2](https://github.com/gohugoio/hugo/commit/3183b9a29d8adac962fbc73f79b04542f4c4c55d) [@bep](https://github.com/bep) [#3511](https://github.com/gohugoio/hugo/issues/3511)

--- a/content/release-notes/0.24.1-relnotes.md

+++ /dev/null

@@ -1,23 +1,0 @@

----

-date: 2017-06-24

-title: 0.24.1

----

-This release fixes some important **archetype-related regressions** from the recent Hugo 0.24-release.

-## Fixes

-* Fix archetype regression when no archetype file [4294dd8d](https://github.com/gohugoio/hugo/commit/4294dd8d9d22bd8107b7904d5389967da1f83f27) [@bep](https://github.com/bep) [#3626](https://github.com/gohugoio/hugo/issues/3626)

-* Preserve shortcodes in archetype templates [b63e4ee1](https://github.com/gohugoio/hugo/commit/b63e4ee198c875b73a6a9af6bb809589785ed589) [@bep](https://github.com/bep) [#3623](https://github.com/gohugoio/hugo/issues/3623)

-* Fix handling of timezones with positive UTC offset (e.g., +0800) in TOML [0744f81e](https://github.com/gohugoio/hugo/commit/0744f81ec00bb8888f59d6c8b5f57096e07e70b1) [@bep](https://github.com/bep) [#3628](https://github.com/gohugoio/hugo/issues/3628)

-## Enhancements

-* Create default archetype on new site [bfa336d9](https://github.com/gohugoio/hugo/commit/bfa336d96173377b9bbe2298dbd101f6a718c174) [@bep](https://github.com/bep) [#3626](https://github.com/gohugoio/hugo/issues/3626)

--- a/content/release-notes/_index.md

+++ /dev/null

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

----

-date: 2017-04-17

-aliases:

-- /doc/release-notes/

-- /meta/release-notes/

-title: Release Notes

-weight: 10

----

--- a/content/release-notes/release-notes.md

+++ /dev/null

@@ -1,959 +1,0 @@

----

-aliases:

-- /doc/release-notes/

-- /meta/release-notes/

-date: 2017-04-16

-title: Older Release Notes

----

-# **0.20.2** April 16th 2017

-Hugo `0.20.2` adds support for plain text partials included into `HTML` templates. This was a side-effect of the big new [Custom Output Format](https://gohugo.io/extras/output-formats/) feature in `0.20`, and while the change was intentional and there was an ongoing discussion about fixing it in {{< gh 3273  >}}, it did break some themes. There were valid workarounds for these themes, but we might as well get it right.

-The most obvious use case for this is inline `CSS` styles,  which you now can do without having to name your partials with a `html` suffix.

-A simple example:

-In `layouts/partials/mystyles.css`:

-```css

-body {

-	background-color: {{ .Param "colors.main" }}

-}

-```

-Then in `config.toml` (note that by using the `.Param` lookup func, we can override the color in a page's front matter if we want):

-```toml

-[params]

-[params.colors]

-main = "green"

-text = "blue"

-```

-And then in `layouts/partials/head.html` (or the partial used to include the head section into your layout):

-```html

-<head>

-    <style type="text/css">

-    {{ partial "mystyles.css" . | safeCSS }}

-    </style>

-</head>

-```

-Of course, `0.20` also made it super-easy to create external `CSS` stylesheets based on your site and page configuration. A simple example:

-Add "CSS" to your home page's `outputs` list, create the template `/layouts/index.css` using Go template syntax for the dynamic parts, and then include it into your `HTML` template with:

-```html

-{{ with  .OutputFormats.Get "css" }}

-<link rel="{{ .Rel }}" type="{{ .MediaType.Type }}" href="{{ .Permalink |  safeURL }}">

-{{ end }}`

-```

-# **0.20.1** April 13th 2017

-Hugo `0.20.1` is a bug fix release, fixing some important regressions introduced in `0.20` a couple of days ago:

-* Fix logic for base template in work dir vs in the theme {{< gh 3323 >}}

-* camelCased templates (partials, shortcodes etc.) not found {{< gh 3333 >}}

-* Live-reload fails with `_index.md` with paginator {{< gh 3315 >}}

-* `rssURI` WARNING always shown {{< gh 3319 >}}

-See the [full list](https://github.com/gohugoio/hugo/milestone/16?closed=1).

-# **0.20** April 10th 2017

-Hugo `0.20` introduces the powerful and long sought after feature [Custom Output Formats]({{< ref "extras/output-formats.md" >}}); Hugo isn't just that "static HTML with an added RSS feed" anymore. *Say hello* to calendars, e-book formats, Google AMP, and JSON search indexes, to name a few ({{< gh 2828 >}}).

-This release represents **over 180 contributions by over 30 contributors** to the main Hugo code base. Since last release Hugo has **gained 1100 stars, 20 new contributors and 5 additional themes.**

-Hugo now has:

-- 16300+ stars

-- 495+ contributors

-- 156+ themes

-{{< gh "@bep" >}} still leads the Hugo development with his witty Norwegian humor, and once again contributed a significant amount of additions. Also a big shoutout to {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition, and {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their ongoing contributions.

-## Other Highlights

-{{< gh "@bogem" >}} has also contributed TOML as an alternative and much simpler format for language/i18n files ({{< gh 3200 >}}). A feature you will appreciate when you start to work on larger translations.

-Also, there have been some important updates in the Emacs Org-mode handling: {{< gh "@chaseadamsio" >}} has fixed the newline-handling ({{< gh 3126 >}}) and {{< gh "@clockoon" >}}  has added basic footnote support.

-Worth mentioning is also the ongoing work that {{< gh "@rdwatters" >}} and {{< gh "@budparr" >}} is doing to re-do the [gohugo.io](https://gohugo.io/) site, including a total restructuring and partial rewrite of the documentation. It is getting close to finished, and it looks fantastic!

-## Notes

-* `RSS` description in the built-in template is changed from full `.Content` to `.Summary`. This is a somewhat breaking change, but is what most people expect from their RSS feeds. If you want full content, please provide your own RSS template.

-* The deprecated `.RSSlink` is now removed. Use `.RSSLink`.

-* `RSSUri` is deprecated and will be removed in a future Hugo version, replace it with an output format definition.

-* The deprecated `.Site.GetParam` is now removed, use `.Site.Param`.

-* Hugo does no longer append missing trailing slash to `baseURL` set as a command line parameter, making it consistent with how it behaves from site config. {{< gh 3262 >}}

-## Enhancements

-* Hugo `0.20` is built with Go 1.8.1.

-* Add `.Site.Params.mainSections` that defaults to the section with the most pages. Plan is to get themes to use this instead of the hardcoded `blog` in `where` clauses.  {{< gh 3206 >}}

-* File extension is now configurable. {{< gh 320 >}}

-* Impove `markdownify` template function performance. {{< gh 3292 >}}

-* Add taxonomy terms' pages to `.Data.Pages` {{< gh 2826 >}}

-* Change `RSS` description from full `.Content` to `.Summary`.

-* Ignore "." dirs in `hugo --cleanDestinationDir` {{< gh 3202 >}}

-* Allow `jekyll import` to accept both `2006-01-02` and `2006-1-2` date format {{< gh 2738 >}}

-* Raise the default `rssLimit` {{< gh 3145 >}}

-* Unify section list vs single template lookup order {{< gh 3116 >}}

-* Allow `apply` to be used with the built-in Go template funcs `print`, `printf` and `println`. {{< gh 3139 >}}

-## Fixes

-* Fix deadlock in `getJSON` {{< gh 3211 >}}

-* Make sure empty terms pages are created. {{< gh 2977 >}}

-* Fix base template lookup order for sections {{< gh 2995 >}}

-* `URL` fixes:

-    * Fix pagination URLs with `baseURL` with sub-root and `canonifyUrls=false` {{< gh 1252 >}}

-    * Fix pagination URL for resources with "." in name {{< gh 2110 >}} {{< gh 2374 >}} {{< gh 1885 >}}

-    * Handle taxonomy names with period {{< gh 3169 >}}

-    * Handle `uglyURLs` ambiguity in `Permalink` {{< gh 3102 >}}

-    * Fix `Permalink` for language-roots wrong when `uglyURLs` is `true` {{< gh 3179 >}}

-    * Fix misc case issues for `URLs` {{< gh 1641 >}}

-    * Fix for taxonomies URLs when `uglyUrls=true` {{< gh 1989 >}}

-    * Fix empty `RSSLink` for list pages with content page. {{< gh 3131 >}}

-* Correctly identify regular pages on the form "my_index_page.md" {{< gh 3234 >}}

-*  `Exit -1` on `ERROR` in global logger {{< gh 3239 >}}

-* Document hugo `help command` {{< gh 2349 >}}

-* Fix internal `Hugo` version handling for bug fix releases. {{< gh 3025 >}}

-* Only return `RSSLink` for pages that actually have a RSS feed. {{< gh 1302 >}}

-# **0.19** February 27th 2017

-We're happy to announce the first release of Hugo in 2017.

-This release represents **over 180 contributions by over 50 contributors** to the main Hugo code base. Since last release Hugo has **gained 1450 stars, 35 new contributors and 15 additional themes.**

-Hugo now has:

-- 15200+ stars

-- 470+ contributors

-- 151+ themes

-Furthermore, Hugo has its own Twitter account ([@gohugoio](https://twitter.com/gohugoio)) where we share bite-sized news and themes from the Hugo community.

-{{< gh "@bep" >}} leads the Hugo development and once again contributed a significant amount of additions. Also a big shoutout to  {{< gh "@chaseadamsio" >}} for the Emacs Org-mode support, {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition, {{< gh "@fj" >}}for his work on revising the `params` handling in Hugo, and {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their ongoing contributions.

-## Highlights

-Hugo `0.19` brings native Emacs Org-mode content support ({{<gh 1483>}}), big thanks to {{< gh "@chaseadamsio" >}}.

-Also, a considerably amount of work have been put into cleaning up the Hugo source code, in an issue titled [Refactor the globals out of site build](https://github.com/gohugoio/hugo/issues/2701). This is not immediately visible to the Hugo end user, but will speed up future development.

-Hugo `0.18` was bringing full-parallel page rendering, so workarounds depending on rendering order did not work anymore, and pages with duplicate target paths (common examples would be `/index.md` or `/about/index.md`) would now conflict with the home page or the section listing.

-With Hugo `0.19`, you can control this behaviour by turning off page types you do not want ({{<gh 2534 >}}). In its most extreme case, if you put the below setting in your `config.toml`, you will get **nothing!**:

-```

-disableKinds = ["page", "home", "section", "taxonomy", "taxonomyTerm", "RSS", "sitemap", "robotsTXT", "404"]

-```

-## Other New Features

-* Add ability to sort pages by frontmatter parameters, enabling easy custom "top 10" page lists. {{<gh 3022 >}}

-* Add `truncate` template function {{<gh 2882 >}}

-* Add `now` function, which replaces the now deprecated `.Now` {{<gh 2859 >}}

-* Make RSS item limit configurable {{<gh 3035 >}}

-## Enhancements

-*  Enhance `.Param` to permit arbitrarily nested parameter references {{<gh 2598 >}}

-* Use `Page.Params` more consistently when adding metadata {{<gh 3033 >}}

-* The `sectionPagesMenu` feature ("Section menu for the lazy blogger") is now integrated with the section content pages. {{<gh 2974 >}}

-* Hugo `0.19` is compiled with Go 1.8!

-* Make template funcs like `findRE` and friends more liberal in what argument types they accept {{<gh 3018 >}} {{<gh 2822 >}}

-* Improve generation of OpenGraph date tags {{<gh 2979 >}}

-## Notes

-* `sourceRelativeLinks` is now deprecated and will be removed in Hugo `0.21` if  no one is stepping up to the plate and fixes and maintains this feature. {{<gh 3028 >}}

-## Fixes

-* Fix `.Site.LastChange` on sites where the default sort order is not chronological. {{<gh 2909 >}}

-* Fix regression of `.Truncated` evaluation in manual summaries. {{<gh 2989 >}}

-* Fix `preserveTaxonomyNames` regression {{<gh 3070 >}}

-* Fix issue with taxonomies when only some have content page {{<gh 2992 >}}

-* Fix instagram shortcode panic on invalid ID {{<gh 3048 >}}

-* Fix subtle data race in `getJSON` {{<gh 3045 >}}

-* Fix deadlock in cached partials {{<gh 2935 >}}

-* Avoid double-encoding of paginator URLs {{<gh 2177 >}}

-* Allow tilde in URLs {{<gh 2177 >}}

-* Fix `.Site.Pages` handling on live reloads {{<gh 2869 >}}

-* `UniqueID` now correctly uses the fill file path from the content root to calculate the hash, and is finally ... unique!

-* Discard current language based on `.Lang()`, go get translations correct for paginated pages. {{<gh 2972 >}}

-* Fix infinite loop in template AST handling for recursive templates  {{<gh 2927 >}}

-* Fix issue with watching when config loading fails {{<gh 2603 >}}

-* Correctly flush the imageConfig on live-reload {{<gh 3016 >}}

-* Fix parsing of TOML arrays in frontmatter {{<gh 2752 >}}

-## Docs

-* Add tutorial "How to use Google Firebase to host a Hugo site" {{<gh 3007 >}}

-* Improve documentation for menu rendering {{<gh 3056 >}}

-* Revise GitHub Pages deployment tutorial {{<gh 2930 >}}

-# **0.18.1** December 30th 2016

-Hugo 0.18.1 is a bug fix release fixing some issues introduced in Hugo 0.18:

-* Fix 32-bit binaries {{<gh 2847 >}}

-* Fix issues with `preserveTaxonomyNames` {{<gh 2809 >}}

-* Fix `.URL` for taxonomy pages when `uglyURLs=true` {{<gh 2819 >}}

-* Fix `IsTranslated` and `Translations` for node pages {{<gh 2812 >}}

-* Make template error messages more verbose {{<gh 2820 >}}

-# **0.18.0** December 19th 2016

-Today, we're excited to release the much-anticipated Hugo 0.18!

-We're heading towards the end of the year 2016, and we can look back on three releases and a steady growing community around the project.

-This release includes **over 220 contributions by nearly 50 contributors** to the main codebase.

-Since the last release, Hugo has **gained 1750 stars and 27 additional themes**.

-Hugo now has:

-- 13750+ stars

-- 408+ contributors

-- 137+ themes

-{{< gh "@bep" >}} once again took the lead of Hugo and contributed a significant amount of additions.

-Also a big shoutout to {{< gh "@digitalcraftsman" >}} for his relentless work on keeping the documentation and the themes site in pristine condition,

-and also a big thanks to {{< gh "@moorereason" >}} and {{< gh "@bogem" >}} for their contributions.

-We wish you all a Merry Christmas and a Happy New Year.<br>

-*The Hugo team*

-## Highlights

-The primary new feature in Hugo 0.18 is that every piece of content is now a `Page` ({{<gh 2297>}}).

-This means that every page, including the home page, can have a content file with frontmatter.

-Not only is this a much simpler model to understand, it is also faster and paved the way for several important new features:

-* Enable proper titles for Nodes {{<gh 1051>}}

-* Sitemap.xml should include nodes, as well as pages {{<gh 1303>}}

-* Document homepage content workaround {{<gh 2240>}}

-* Allow home page to be easily authored in markdown {{<gh 720>}}

-* Minimalist website with homepage as content {{<gh 330>}}

-Hugo again continues its trend of each release being faster than the last. It's quite a challenge to consistently add significant new functionality and simultaneously dramatically improve performance. Running [this benchmark]( https://github.com/bep/hugo-benchmark) with [these sites](https://github.com/bep/hugo-benchmark/tree/master/sites) (renders to memory) shows about	60% reduction in time spent and 30% reduction in memory usage compared to Hugo 0.17.

-## Other New Features

-* Every `Page` now has a `Kind` property. Since everything is a `Page` now, the `Kind` is used to differentiate different kinds of pages.

-  Possible values are `page`, `home`, `section`, `taxonomy`, and `taxonomyTerm`.

-  (Internally, we also define `RSS`, `sitemap`, `robotsTXT`, and `404`, but those have no practical use for end users at the moment since they are not included in any collections.)

-* Add a `GitInfo` object to `Page` if `enableGitInfo` is set. It then also sets `Lastmod` for the given `Page` to the author date provided by Git. {{<gh 2291>}}

-* Implement support for alias templates  {{<gh 2533 >}}

-* New template functions:

-  * Add `imageConfig` function {{<gh 2677>}}

-  * Add `sha256` function {{<gh 2762>}}

-  * Add `partialCached` template function {{<gh 1368>}}

-* Add shortcode to display Instagram images {{<gh 2690>}}

-* Add `noChmod` option to disable perm sync {{<gh 2749>}}

-* Add `quiet` build mode {{<gh 1218>}}

-## Notices

-* `.Site.Pages` will now contain *several kinds of pages*, including regular pages, sections, taxonomies, and the home page.

-  If you want a specific kind of page, you can filter it with `where` and `Kind`.

-  `.Site.RegularPages` is a shortcut to the page collection you have been used to getting.

-* `RSSlink` is now deprecated.  Use `RSSLink` instead.

-  Note that in Hugo 0.17 both of them existed, so there is a fifty-fifty chance you will not have to do anything

-  (if you use a theme, the chance is close to 0), and `RSSlink` will still work for two Hugo versions.

-## Fixes

-* Revise the `base` template lookup logic so it now better matches the behavior of regular templates, making it easier to override the master templates from the theme {{<gh 2783>}}

-* Add workaround for `block` template crash.

-  Block templates are very useful, but there is a bug in Go 1.6 and 1.7 which makes the template rendering crash if you use the block template in more complex scenarios.

-  This is fixed in the upcoming Go 1.8, but Hugo adds a temporary workaround in Hugo 0.18. {{<gh 2549>}}

-* All the `Params` configurations are now case insensitive {{<gh 1129>}} {{<gh 2590>}} {{<gh 2615>}}

-* Make RawContent raw again {{<gh 2601>}}

-* Fix archetype title and date handling {{<gh 2750>}}

-* Fix TOML archetype parsing in `hugo new` {{<gh 2745>}}

-* Fix page sorting when weight is zero {{<gh 2673>}}

-* Fix page names that contain dot {{<gh 2555>}}

-* Fix RSS Title regression {{<gh 2645>}}

-* Handle ToC before handling shortcodes {{<gh 2433>}}

-* Only watch relevant themes dir {{<gh 2602>}}

-* Hugo new content creates TOML slices with closing bracket on new line {{<gh 2800>}}

-## Improvements

-* Add page information to error logging in rendering {{<gh 2570>}}

-* Deprecate `RSSlink` in favor of `RSSLink`

-* Make benchmark command more useful {{<gh 2432>}}

-* Consolidate the `Param` methods {{<gh 2590>}}

-* Allow to set cache dir in config file

-* Performance improvements:

-  * Avoid repeated Viper loads of `sectionPagesMenu` {{<gh 2728>}}

-  * Avoid reading from Viper for path and URL funcs {{<gh 2495>}}

-  * Add `partialCached` template function. This can be a significant performance boost if you have complex partials that does not need to be rerendered for every page. {{<gh 1368>}}

-## Documentation Updates

-* Update roadmap {{<gh 2666>}}

-* Update multilingual example {{<gh 2417>}}

-* Add a "Deployment with rsync" tutorial page {{<gh 2658>}}

-* Refactor `/docs` to use the `block` keyword {{<gh 2226>}}

-## **0.17.0** October 7th 2016

-Hugo is going global with our 0.17 release.  We put a lot of thought into how we could extend Hugo

-to support multilingual websites with the most simple and elegant experience. Hugo's multilingual

-capabilities rival the best web and documentation software, but Hugo's experience is unmatched.

-If you have a single language website, the simple Hugo experience you already love is unchanged.

-Adding additional languages to your website is simple and straightforward. Hugo has been completely

-internally rewritten to be multilingual aware with translation and internationalization features

-embedded throughout Hugo.

-Hugo continues its trend of each release being faster than the last. It's quite a challenge to consistently add

-significant new functionality and simultaneously dramatically improve performance. {{<gh "@bep">}} has made it

-his personal mission to apply the Go mantra of "Enable more. Do less" to Hugo. Hugo's consistent improvement

-is a testament to his brilliance and his dedication to his craft. Hugo additionally benefits from the

-performance improvements from the Go team in the Go 1.7 release.

-This release represents **over 300 contributions by over 70 contributors** to

-the main Hugo code base. Since last release Hugo has **gained 2000 stars, 50 new

-contributors and 20 additional themes.**

-Hugo now has:

-* 12,000 stars on GitHub

-* 370+ contributors

-* 110+ themes

-{{<gh "@bep" >}} continues to lead the project with the lionshare of contributions

-and reviews. A special thanks to {{<gh "@bep" >}} and {{<gh "@abourget" >}} for their

-considerable work on multilingual support.

-A big welcome to newcomers {{<gh "@MarkDBlackwell" >}}, {{<gh "@bogem" >}} and

-{{<gh "@g3wanghc" >}} for their critical contributions.

-### Highlights

-**Multilingual Support:**

-Hugo now supports multiple languages side-by-side. A single site can now have multiple languages rendered with

-full support for translation and i18n.

-**Performance:**

-Hugo is faster than ever! Hugo 0.17 is not only our fastest release, it's also the most efficient.

-Hugo 0.17 is **nearly twice as fast as Hugo 0.16** and uses about 10% less memory.

-This means that the same site will build in nearly half the time it took with Hugo 0.16.

-For the first time Hugo sites are averaging well under 1ms per rendered content.

-**Docs overhaul:**

-This release really focused on improving the documentation. [Gohugo.io](http://gohugo.io) is

-more accurate and complete than ever.

-**Support for macOS Sierra**

-### New Features

-* Multilingual support {{<gh 2303>}}

-* Allow content expiration {{<gh 2137 >}}

-* New templates functions:

-  * `querify` function to generate query strings inside templates {{<gh 2257>}}

-  * `htmlEscape` and `htmlUnescape` template functions {{<gh 2287>}}

-  * `time` converts a timestamp string into a time.Time structure {{<gh 2329>}}

-### Enhancements

-* Render the shortcodes as late as possible {{<gh 0xed0985404db4630d1b9d3ad0b7e41fb186ae0112>}}

-* Remove unneeded casts in page.getParam {{<gh 2186 >}}

-* Automatic page date fallback {{<gh 2239>}}

-* Enable safeHTMLAttr {{<gh 2234>}}

-* Add TODO list support for markdown {{<gh 2296>}}

-* Make absURL and relURL accept any type {{<gh 2352>}}

-* Suppress 'missing static' error {{<gh 2344>}}

-* Make summary, wordcount etc. more efficient {{<gh 2378>}}

-* Better error reporting in `hugo convert` {{<gh 2440>}}

-* Reproducible builds thanks to govendor {{<gh 2461>}}

-### Fixes

-* Fix shortcode in markdown headers {{<gh 2210 >}}

-* Explicitly bind livereload to hugo server port {{<gh 2205>}}

-* Fix Emojify for certain text patterns {{<gh 2198>}}

-* Normalize file name to NFC {{<gh 2259>}}

-* Ignore emacs temp files {{<gh 2266>}}

-* Handle symlink change event {{<gh 2273>}}

-* Fix panic when using URLize {{<gh 2274>}}

-* `hugo import jekyll`: Fixed target path location check {{<gh 2293>}}

-* Return all errors from casting in templates {{<gh 2356>}}

-* Fix paginator counter on x86-32 {{<gh 2420>}}

-* Fix half-broken self-closing shortcodes {{<gh 2499>}}

-****

-## **0.16.0** June 6th 2016

-Hugo 0.16 is our best and biggest release ever. The Hugo community has

-outdone itself with continued performance improvements,

-[beautiful themes](http://themes.gohugo.io) for all types of sites from project

-sites to documentation to blogs to portfolios, and increased stability.

-This release represents **over 550 contributions by over 110 contributors** to

-the main Hugo code base. Since last release Hugo has **gained 3500 stars, 90

-contributors and 23 additional themes.**

-This release celebrates 3 years since  {{< gh "@spf13" >}} wrote the first lines

-of Hugo. During those 3 years Hugo has accomplished some major milestones

-including...

-* 10,000+ stars on GitHub

-* 320+ contributors

-* 90+ themes

-* 1000s of happy websites

-* Many subprojects like {{< gh "@spf13/cobra">}}, {{< gh "@spf13/viper">}} and

-  {{< gh "@spf13/afero">}} which have experienced broad usage across the Go

-  ecosystem.

-{{< gh "@bep" >}} led the development of Hugo for the 3rd consecutive release

-with nearly half of the contributions to 0.16 in addition to his considerable

-contributions as lead maintainer. {{< gh "@anthonyfok" >}}, {{< gh

-"@DigitalCraftsman" >}}, {{< gh "@MooreReason" >}} all made significant

-contributions. A special thanks to {{< gh "@abourget " >}} for his considerable

-work on multilingual support. Due to its broad impact we wanted to spend more

-time testing it and it will be included in Hugo's next release.

-### Highlights

-**Partial Builds:** Prior to this release Hugo would always reread and rebuild

-the entire site. This release introduces support for reactive site building

-while watching (`hugo server`). Hugo will watch the filesystem for changes and

-only re-read the changed files. Depending on the files change Hugo will

-intelligently re-render only the needed portion of the site. Performance gains

-depend on the operation performed and size of the site. In our testing build

-times decreased anywhere from 10% to 99%.

-**Template Improvements:** Template improvements continue to be a mainstay of each Hugo release. Hugo 0.16 adds support for the new `block` keyword introduced in Go 1.6 -- think base templates with default sections -- as well as many new template functions.

-**Polish:** As Hugo matures releases will inevitably contain fewer huge new features. This release represents hundreds of small improvements across ever facet of Hugo which will make for a much better experience for all of our users. Worth mentioning here is the curious bug where live reloading didn't work in some editors on OS X, including the popular TextMate 2. This is now fixed. Oh, and now any error will exit with an error code, a big thing for automated deployments.

-### New Features

-* Support reading configuration variables from the OS environment {{<gh 2090 >}}

-* Add emoji support {{<gh 1892>}}

-* Add `themesDir` option to configuration {{<gh 1556>}}

-* Add support for Go 1.6 `block` keyword in templates {{<gh 1832>}}

-* Partial static sync {{<gh 1644>}}

-* Source file based relative linking (a la GitHub) {{<gh 0x0f6b334b6715253b030c4e783b88e911b6e53e56>}}

-*  Add `ByLastmod` sort function to pages. {{<gh 0xeb627ca16de6fb5e8646279edd295a8bf0f72bf1 >}}

-* New templates functions:

-	* `readFile` {{<gh 1551 >}}

-    * `countwords` and `countrunes` {{<gh 1440>}}

-    * `default` {{<gh 1943>}}

-    * `hasPrefix` {{<gh 1243>}}

-    * `humanize` {{<gh 1818>}}

-    * `jsonify` {{<gh 0x435e996c4fd48e9009ffa9f83a19fb55f0777dbd>}}

-    * `md5` and `sha1` {{<gh 1932>}}

-    * `replaceRE` {{<gh 1845>}}

-    * `findRE` {{<gh 2048>}}

-    * `shuffle` {{<gh 1942>}}

-    * `slice` {{<gh 1902>}}

-    * `plainify` {{<gh 1915>}}

-### Enhancements

-* Hugo now exits with error code on any error. This is a big thing for

-  automated deployments. {{<gh 740 >}}

-* Print error when `/index.html` is zero-length {{<gh 947>}}

-* Enable dirname and filename bash autocompletion for more flags {{<gh

-  0x666ddd237791b56fd048992dca9a27d1af50a10e>}}

-* Improve error handling in commands {{<gh 1502>}}

-* Add sanity checks for `hugo import jekyll` {{<gh 1625 >}}

-* Add description to `Page.Params` {{<gh 1484>}}

-* Add async version of Google Analytics internal template {{<gh 1711>}}

-* Add autostart option to YouTube shortcode {{<gh 1784>}}

-* Set Date and Lastmod for main home page {{<gh 1903>}}

-* Allow URL with extension in frontmatter {{<gh 1923>}}

-* Add list support in Scratch {{<gh

-  0xeaba04e82bdfc5d4c29e970f11b4aab9cc0efeaa>}}

-* Add file option to gist shortcode {{<gh 1955>}}

-* Add config layout and content directory CLI options {{<gh 1698>}}

-* Add boolean value comparison to `where` template function {{<gh

-  0xf3c74c9db484c8961e70cb3458f9e41e7832fa12>}}

-* Do not write to to cache when `ignoreCache` is set  {{<gh 2067>}}

-* Add option to disable rendering of 404 page  {{<gh 2037>}}

-* Mercurial is no longer needed to build Hugo {{<gh 2062 >}}

-* Do not create `robots.txt` by default {{<gh 2049>}}

-* Disable syntax guessing for PygmentsCodeFences by default.  To enable syntax

-  guessing again, add the following to your config file:

-  `PygmentsCodeFencesGuessSyntax = true` {{<gh 2034>}}

-* Make `ByCount` sort consistently {{<gh 1930>}}

-* Add `Scratch` to shortcode {{<gh 2000>}}

-* Add support for symbolic links for content, layout, static, theme  {{<gh 1855 >}}

-* Add '+' as one of the valid characters in URLs specified in the front matter

-  {{<gh 1290 >}}

-* Make alias redirect output URLs relative when `RelativeURLs = true` {{<gh 2093 >}}

-* Hugo injects meta generator tag on homepage if missing {{<gh 2182 >}}

-### Fixes

-* Fix file change watcher for TextMate 2 and friends on OS X {{<gh 1053 >}}

-* Make dynamic reloading of config file reliable on all platform {{<gh 1684 >}}

-* Hugo now works on Linux/arm64 {{<gh 1772 >}}

-* `plainIDAnchors` now defaults to `true`  {{<gh 2057>}}

-* Win32 and ARM builds fixed {{<gh 1716>}}

-* Copy static dir files without theme's static dir {{<gh 1656>}}

-* Make `noTimes` command flag work {{<gh 1657>}}

-* Change most global CLI flags into local ones {{<gh 1624>}}

-* Remove transformation of menu URLs {{<gh 1239>}}

-* Do not fail on unknown Jekyll file {{<gh 1705>}}

-* Use absolute path when editing with editor {{<gh 1589>}}

-* Fix hugo server "Watching for changes" path display {{<gh 1721>}}

-* Do not strip special characters out of URLs {{<gh 1292>}}

-* Fix `RSSLink` when uglyURLs are enabled {{<gh 175>}}

-* Get BaseURL from viper in server mode {{<gh 1821>}}

-* Fix shortcode handling in RST {{<gh 1904>}}

-* Use default sitemap configuration for homepage {{<gh 1304>}}

-* Exit if specific port is unavailable in server mode {{<gh 1901>}}

-* Fix regression in "section menus for lazy blogger" {{<gh 2065>}}

-****

-## **0.15.0**  November 25, 2015

-The v0.15.0 Hugo release brings a lot of polish to Hugo. Exactly 6 months after

-the 0.14 release, Hugo has seen massive growth and changes. Most notably, this

-is Hugo's first release under the Apache 2.0 license. With this license change

-we hope to expand the great community around Hugo and make it easier for our

-many users to contribute.  This release represents over **377 contributions by

-87 contributors** to the main Hugo repo and hundreds of improvements to the

-libraries Hugo uses. Hugo also launched a [new theme

-showcase](http://themes.gohugo.io) and participated in

-[Hacktoberfest](https://hacktoberfest.digitalocean.com).

-Hugo now has:

-* 6700 (+2700) stars on GitHub

-* 235 (+75) contributors

-* 65 (+30) themes

-**Template Improvements:** This release takes Hugo to a new level of speed and

-usability. Considerable work has been done adding features and performance to

-the template system which now has full support of Ace, Amber and Go Templates.

-**Hugo Import:** Have a Jekyll site, but dreaming of porting it to Hugo? This

-release introduces a new `hugo import jekyll`command that makes this easier

-than ever.

-**Performance Improvements:** Just when you thought Hugo couldn't get any faster,

-Hugo continues to improve in speed while adding features. Notably Hugo 0.15

-introduces the ability to render and serve directly from memory resulting in

-30%+ lower render times.

-Huge thanks to all who participated in this release. A special thanks to

-{{< gh "@bep" >}} who led the development of Hugo this release again,

-{{< gh "@anthonyfok" >}},

-{{< gh "@eparis" >}},

-{{< gh "@tatsushid" >}} and

-{{< gh "@DigitalCraftsman" >}}.

-### New features

-* new `hugo import jekyll` command. {{< gh 1469 >}}

-* The new `Param` convenience method on `Page` and `Node` can be used to get the most specific parameter value for a given key. {{< gh 1462 >}}

-* Several new information elements have been added to `Page` and `Node`:

-    * `RuneCount`: The number of [runes](http://blog.golang.org/strings) in the content, excluding any whitespace. This may be a good alternative to `.WordCount`  for Japanese and other CJK languages where a word-split by spaces makes no sense.  {{< gh 1266 >}}

-	* `RawContent`: Raw Markdown as a string. One use case may be of embedding remarkjs.com slides.

-	* `IsHome`: tells the truth about whether you're on the home page or not.

-### Improvements

-* `hugo server` now builds ~30%+ faster by rendering to memory instead of disk. To get the old behavior, start the server with `--renderToDisk=true`.

-* Hugo now supports dynamic reloading of the config file when watching.

-* We now use a custom-built `LazyFileReader` for reading file contents, which means we don't read media files in `/content` into memory anymore -- and file reading is now performed in parallel on multicore PCs. {{< gh 1181 >}}

-* Hugo is now built with `Go 1.5` which, among many other improvements, have fixed the last known data race in Hugo. {{< gh 917 >}}

-* Paginator now also supports page groups. {{< gh 1274 >}}

-* Markdown improvements:

-    * Hugo now supports GitHub-flavoured markdown code fences for highlighting for `md`-files (Blackfriday rendered markdown) and `mmark` files (MMark rendered markdown). {{< gh 362 1258 >}}

-    * Several new Blackfriday options are added:

-        * Option to disable Blackfriday's `Smartypants`.

-        * Option for Blackfriday to open links in a new window/tab. {{< gh 1220 >}}

-        * Option to disable Blackfriday's LaTeX style dashes {{< gh 1231 >}}

-        * Definition lists extension support.

-* `Scratch` now has built-in `map` support.

-* We now fall back to `link title` for the default page sort. {{< gh 1299 >}}

-* Some notable new configuration options:

-	*  `IgnoreFiles` can be set with a list of Regular Expressions that matches files to be ignored during build. {{< gh 1189 >}}

-	* `PreserveTaxonomyNames`, when set to `true`, will preserve what you type as the taxonomy name both in the folders created and the taxonomy `key`, but it will be normalized for the URL.  {{< gh 1180 >}}

-* `hugo gen` can now generate man files, bash auto complete and markdown documentation

-* Hugo will now make suggestions when a command is mistyped

-* Shortcodes now have a boolean `.IsNamedParams` property. {{< gh 1597 >}}

-### New Template Features

-* All template engines:

-	* The new `dict` function that could be used to pass maps into a template. {{< gh 1463 >}}

-	* The new `pluralize` and `singularize` template funcs.

-	* The new `base64Decode` and `base64Encode` template funcs.

-	* The `sort` template func now accepts field/key chaining arguments and pointer values. {{< gh 1330 >}}

-	* Several fixes for `slicestr` and `substr`, most importantly, they now have full `utf-8`-support. {{< gh 1190 1333 1347 >}}

-	* The new `last` template function allows the user to select the last `N` items of a slice. {{< gh 1148 >}}

-	* The new `after` func allows the user to select the items after the `Nth` item. {{< gh 1200 >}}

-	* Add `time.Time` type support to the `where`, `ge`, `gt`, `le`, and `lt` template functions.

-	* It is now possible to use constructs like `where Values ".Param.key" nil` to filter pages that doesn't have a particular parameter. {{< gh 1232 >}}

-	* `getJSON`/`getCSV`: Add retry on invalid content. {{< gh 1166 >}}

-	* 	The new `readDir` func lists local files. {{< gh 1204 >}}

-    * The new `safeJS` function allows the embedding of content into JavaScript contexts in Go templates.

-    * Get the main site RSS link from any page by accessing the `.Site.RSSLink` property. {{< gh 1566 >}}

-* Ace templates:

-	* Base templates now also works in themes. {{< gh 1215 >}}.

-	* And now also on Windows. {{< gh 1178 >}}

-* Full support for Amber templates including all template functions.

-* A built-in template for Google Analytics. {{< gh 1505 >}}

-* Hugo is now shipped with new built-in shortcodes: {{< gh 1576 >}}

-  * `youtube` for YouTube videos

-  * `vimeo` for Vimeo videos

-  * `gist` for GitHub gists

-  * `tweet` for Twitter Tweets

-  * `speakerdeck` for Speakerdeck slides

-### Bugfixes

-* Fix data races in page sorting and page reversal. These operations are now also cached. {{< gh 1293 >}}

-* `page.HasMenuCurrent()` and `node.HasMenuCurrent()` now work correctly in multi-level nested menus.

-* Support `Fish and Chips` style section titles. Previously, this would end up as  `Fish And Chips`. Now, the first character is made toupper, but the rest are preserved as-is. {{< gh 1176 >}}

-* Hugo now removes superfluous p-tags around shortcodes. {{< gh 1148 >}}

-### Notices

-* `hugo server` will watch by default now.

-* Some fields and methods were deprecated in `0.14`. These are now removed, so the error message isn't as friendly if you still use the old values. So please change:

-	*   `getJson` to `getJSON`, `getCsv` to `getCSV`, `safeHtml` to

-  `safeHTML`, `safeCss` to `safeCSS`, `safeUrl` to `safeURL`, `Url` to `URL`,

-  `UrlPath` to `URLPath`, `BaseUrl` to `BaseURL`, `Recent` to `Pages`.

-### Known Issues

-Using the Hugo v0.15 32-bit Windows or ARM binary, running `hugo server` would crash or hang due to a [memory alignment issue](https://golang.org/pkg/sync/atomic/#pkg-note-BUG) in [Afero](https://github.com/spf13/afero).  The bug was discovered shortly after the v0.15.0 release and has since been [fixed](https://github.com/spf13/afero/pull/23) by {{< gh "@tpng" >}}.  If you encounter this bug, you may either compile Hugo v0.16-DEV from source, or use the following solution/workaround:

-* **64-bit Windows users: Please use [hugo_0.15_windows_amd64.zip](https://github.com/gohugoio/hugo/releases/download/v0.15/hugo_0.15_windows_amd64.zip)** (amd64 == x86-64).  It is only the 32-bit hugo_0.15_windows_386.zip that crashes/hangs (see {{< gh 1621 >}} and {{< gh 1628 >}}).

-* **32-bit Windows and ARM users: Please run `hugo server --renderToDisk` as a workaround** until Hugo v0.16 is released (see [“hugo server” returns runtime error on armhf](https://discourse.gohugo.io/t/hugo-server-returns-runtime-error-on-armhf/2293) and {{< gh 1716 >}}).

-----

-## **0.14.0** May 25, 2015

-The v0.14.0 Hugo release brings of the most demanded features to Hugo. The

-foundation of Hugo is stabilizing nicely and a lot of polish has been added.

-We’ve expanded support for additional content types with support for AsciiDoc,

-Restructured Text, HTML and Markdown. Some of these types depend on external

-libraries as there does not currently exist native support in Go. We’ve tried

-to make the experience as seamless as possible. Look for more improvements here

-in upcoming releases.

-A lot of work has been done to improve the user experience, with extra polish

-to the Windows experience. Hugo errors are more helpful overall and Hugo now

-can detect if it’s being run in Windows Explorer and provide additional

-instructions to run it via the command prompt.

-The Hugo community continues to grow. Hugo has over 4000 stars on github, 165

-contributors, 35 themes and 1000s of happy users. It is now the 5th most

-popular static site generator (by Stars) and has the 3rd largest contributor

-community.

-This release represents over **240 contributions by 36 contributors** to the main

-Hugo codebase.

-Big shout out to {{< gh "@bep" >}} who led the development of Hugo

-this release, {{< gh "@anthonyfok" >}},

-{{< gh "@eparis" >}},

-{{< gh "@SchumacherFM" >}},

-{{< gh "@RickCogley" >}} &

-{{< gh "@mdhender" >}} for their significant contributions

-and {{< gh "@tatsushid" >}} for his continuous improvements

-to the templates. Also a big thanks to all the theme creators. 11 new themes

-have been added since last release and the [hugoThemes repo now has previews of

-all of

-them](https://github.com/gohugoio/hugoThemes/blob/master/README.md#theme-list).

-Hugo also depends on a lot of other great projects. A big thanks to all of our dependencies including:

-[cobra](https://github.com/spf13/cobra),

-[viper](https://github.com/spf13/viper),

-[blackfriday](https://github.com/russross/blackfriday),

-[pflag](https://github.com/spf13/pflag),

-[HugoThemes](https://github.com/gohugoio/hugothemes),

-[BurntSushi](https://github.com/BurntSushi/toml),

-[goYaml](https://github.com/go-yaml/yaml/tree/v2), and the Go standard library.

-## New features

-* Support for all file types in content directory.

-    * If dedicated file type handler isn’t found it will be copied to the destination.

-* Add `AsciiDoc` support using external helpers.

-* Add experimental support for [`Mmark`](https://github.com/miekg/mmark) markdown processor

-* Bash autocomplete support via `genautocomplete` command

-* Add section menu support for a [Section Menu for "the Lazy Blogger"]({{< relref "extras/menus.md#section-menu-for-the-lazy-blogger" >}})

-* Add support for `Ace` base templates

-* Adding `RelativeURLs = true` to site config will now make all the relative URLs relative to the content root.

-* New template functions:

-  * `getenv`

-  * The string functions `substr` and `slicestr`

-  * `seq`, a sequence generator very similar to its Gnu counterpart

-  * `absURL` and `relURL`, both of which takes the `BaseURL` setting into account

-## Improvements

-* Highlighting with `Pygments` is now cached to disk -- expect a major speed boost if you use it!

-* More Pygments highlighting options, including `line numbers`

-* Show help information to Windows users who try to double click on `hugo.exe`.

-* Add `bind` flag to `hugo server` to set the interface to which the server will bind

-* Add support for `canonifyURLs` in `srcset`

-* Add shortcode support for HTML (content) files

-* Allow the same `shortcode` to  be used with or without inline content

-* Configurable RSS output filename

-## Bugfixes

-* Fix panic with paginator and zero pages in result set.

-* Fix crossrefs on Windows.

-* Fix `eq` and `ne` template functions when used with a raw number combined with the result of `add`, `sub` etc.

-* Fix paginator with uglyURLs

-* Fix {{< gh 998 >}}, supporting UTF8 characters in Permalinks.

-## Notices

-* To get variable and function names in line with the rest of the Go community,

-  a set of variable and function names has been deprecated: These will still

-  work in 0.14, but will be removed in 0.15. What to do should be obvious by

-  the build log; `getJson` to `getJSON`, `getCsv` to `getCSV`, `safeHtml` to

-  `safeHTML`, `safeCss` to `safeCSS`, `safeUrl` to `safeURL`, `Url` to `URL`,

-  `UrlPath` to `URLPath`, `BaseUrl` to `BaseURL`, `Recent` to `Pages`,

-  `Indexes` to `Taxonomies`.

-----

-## **0.13.0** Feb 21, 2015

-The v0.13.0 release is the largest Hugo release to date. The release introduced

-some long sought after features (pagination, sequencing, data loading, tons of

-template improvements) as well as major internal improvements. In addition to

-the code changes, the Hugo community has grown significantly and now has over

-3000 stars on github, 134 contributors, 24 themes and 1000s of happy users.

-This release represents **448 contributions by 65 contributors**

-A special shout out to {{< gh "@bep" >}} and

-{{< gh "@anthonyfok" >}} for their new role as Hugo

-maintainers and their tremendous contributions this release.

-### New major features

-* Support for [data files](/extras/datafiles/) in [YAML](http://yaml.org/),

-  [JSON](http://www.json.org/), or [TOML](https://github.com/toml-lang/toml)

-  located in the `data` directory ({{< gh 885 >}})

-* Support for [dynamic content](/extras/dynamiccontent/) by loading JSON & CSV

-  from remote sources via GetJson and GetCsv in short codes or other layout

-  files ({{< gh 748 >}})

-* [Pagination support](/extras/pagination/) for home page, sections and

-  taxonomies ({{< gh 750 >}})

-* Universal sequencing support

-    * A new, generic Next/Prev functionality is added to all lists of pages

-      (sections, taxonomies, etc.)

-    * Add in-section [Next/Prev](/templates/variables/) content pointers

-* `Scratch` -- [a "scratchpad"](/extras/scratch) for your node- and page-scoped

-  variables

-* [Cross Reference](/extras/crossreferences/) support to easily link documents

-  together with the ref and relref shortcodes.

-* [Ace](http://ace.yoss.si/) template engine support ({{< gh 541 >}})

-* A new [shortcode](/extras/shortcodes/) token of `{{</* */>}}` (raw HTML)

-  alongside the existing `{{%/* */%}}` (Markdown)

-* A top level `Hugo` variable (on Page & Node) is added with various build

-  information

-* Several new ways to order and group content:

-    * `ByPublishDate`

-    * `GroupByPublishDate(format, order)`

-    * `GroupByParam(key, order)`

-    * `GroupByParamDate(key, format, order)`

-* Hugo has undergone a major refactoring, with a new handler system and a

-  generic file system. This sounds and is technical, but will pave the way for

-  new features and make Hugo even speedier

-### Notable enhancements to existing features

-* The [shortcode](/extras/shortcodes/) handling is rewritten for speed and

-  better error messages.

-* Several improvements to the [template functions](/templates/functions/):

-    * `where` is now even more powerful and accepts SQL-like syntax with the

-      operators `==`, `eq`; `!=`, `<>`, `ne`; `>=`, `ge`; `>`, `gt`; `<=`,

-      `le`; `<`, `lt`; `in`, `not in`

-    * `where` template function now also accepts dot chaining key argument

-      (e.g. `"Params.foo.bar"`)

-* New template functions:

-    * `apply`

-    * `chomp`

-    * `delimit`

-    * `sort`

-    * `markdownify`

-    * `in` and `intersect`

-    * `trim`

-    * `replace`

-    * `dateFormat`

-* Several [configurable improvements related to Markdown

-  rendering](/overview/configuration/#configure-blackfriday-rendering:a66b35d20295cb764719ac8bd35837ec):

-    * Configuration of footnote rendering

-    * Optional support for smart angled quotes, e.g. `"Hugo"` → «Hugo»

-    * Enable descriptive header IDs

-* URLs in XML output is now correctly canonified ({{< gh 725 728 >}}, and part

-  of {{< gh 789 >}})

-### Other improvements

-* Internal change to use byte buffer pool significantly lowering memory usage

-  and providing measurable performance improvements overall

-* Changes to docs:

-    * A new [Troubleshooting](/troubleshooting/overview/) section is added

-    * It's now searchable through Google Custom Search ({{< gh 753 >}})

-    * Some new great tutorials:

-        * [Automated deployments with

-          Wercker](/tutorials/automated-deployments/)

-        * [Creating a new theme](/tutorials/creating-a-new-theme/)

-* [`hugo new`](/content/archetypes/) now copies the content in addition to the front matter

-* Improved unit test coverage

-* Fixed a lot of Windows-related path issues

-* Improved error messages for template and rendering errors

-* Enabled soft LiveReload of CSS and images ({{< gh 490 >}})

-* Various fixes in RSS feed generation ({{< gh 789 >}})

-* `HasMenuCurrent` and `IsMenuCurrent` is now supported on Nodes

-* A bunch of [bug fixes](https://github.com/gohugoio/hugo/commits/master)

-----

-## **0.12.0** Sept 1, 2014

-A lot has happened since Hugo v0.11.0 was released. Most of the work has been

-focused on polishing the theme engine and adding critical functionality to the

-templates.

-This release represents over 90 code commits from 28 different contributors.

-  * 10 [new themes](https://github.com/gohugoio/hugoThemes) created by the community

-  * Fully themable [Partials](/templates/partials/)

-  * [404 template](/templates/404/) support in themes

-  * [Shortcode](/extras/shortcodes/) support in themes

-  * [Views](/templates/views/) support in themes

-  * Inner [shortcode](/extras/shortcodes/) content now treated as Markdown

-  * Support for header ids in Markdown (# Header {#myid})

-  * [Where](/templates/list/) template function to filter lists of content, taxonomies, etc.

-  * [GroupBy](/templates/list/) & [GroupByDate](/templates/list/) methods to group pages

-  * Taxonomy [pages list](/taxonomies/methods/) now sortable, filterable, limitable & groupable

-  * General cleanup to taxonomies & documentation to make it more clear and consistent

-  * [Showcase](/showcase/) returned and has been expanded

-  * Pretty links now always have trailing slashes

-  * [BaseUrl](/overview/configuration/) can now include a subdirectory

-  * Better feedback about draft & future post rendering

-  * A variety of improvements to [the website](http://gohugo.io/)

-----

-## **0.11.0** May 28, 2014

-This release represents over 110 code commits from 29 different contributors.

-  * Considerably faster... about 3 - 4x faster on average

-  * [LiveReload](/extras/livereload/). Hugo will automatically reload the browser when the build is complete

-  * Theme engine w/[Theme Repository](https://github.com/gohugoio/hugoThemes)

-  * [Menu system](/extras/menus/) with support for active page

-  * [Builders](/extras/builders/) to quickly create a new site, content or theme

-  * [XML sitemap](/templates/sitemap/) generation

-  * [Integrated Disqus](/extras/comments/) support

-  * Streamlined [template organization](/templates/overview/)

-  * [Brand new docs site](http://gohugo.io/)

-  * Support for publishDate which allows for posts to be dated in the future

-  * More [sort](/content/ordering/) options

-  * Logging support

-  * Much better error handling

-  * More informative verbose output

-  * Renamed Indexes > [Taxonomies](/taxonomies/overview/)

-  * Renamed Chrome > [Partials](/templates/partials/)

-----

-## **0.10.0** March 1, 2014

-This release represents over 110 code commits from 29 different contributors.

-  * [Syntax highlighting](/extras/highlighting/) powered by pygments (**slow**)

-  * Ability to [sort content](/content/ordering/) many more ways

-  * Automatic [table of contents](/extras/toc/) generation

-  * Support for Unicode URLs, aliases and indexes

-  * Configurable per-section [permalink](/extras/permalinks/) pattern support

-  * Support for [paired shortcodes](/extras/shortcodes/)

-  * Shipping with some [shortcodes](/extras/shortcodes/) (highlight & figure)

-  * Adding [canonify](/extras/urls/) option to keep urls relative

-  * A bunch of [additional template functions](/layout/functions/)

-  * Watching very large sites now works on Mac

-  * RSS generation improved. Limited to 50 items by default, can limit further in [template](/layout/rss/)

-  * Boolean params now supported in [frontmatter](/content/front-matter/)

-  * Launched website [showcase](/showcase/). Show off your own hugo site!

-  * A bunch of [bug fixes](https://github.com/gohugoio/hugo/commits/master)

-----

-## **0.9.0** November 15, 2013

-This release represents over 220 code commits from 22 different contributors.

-  * New [command based interface](/overview/usage/) similar to git (`hugo server -s ./`)

-  * Amber template support

-  * [Aliases](/extras/aliases/) (redirects)

-  * Support for top level pages (in addition to homepage)

-  * Complete overhaul of the documentation site

-  * Full Windows support

-  * Better index support including [ordering by content weight](/content/ordering/)

-  * Add params to site config, available in .Site.Params from templates

-  * Friendlier json support

-  * Support for html & xml content (with frontmatter support)

-  * Support for [summary](/content/summaries/) content divider (<code>&lt;!&#45;&#45;more&#45;&#45;&gt;</code>)

-  * HTML in [summary](/content/summaries/) (when using divider)

-  * Added ["Minutes to Read"](/layout/variables/) functionality

-  * Support for a custom 404 page

-  * Cleanup of how content organization is handled

-  * Loads of unit and performance tests

-  * Integration with travis ci

-  * Static directory now watched and copied on any addition or modification

-  * Support for relative permalinks

-  * Fixed watching being triggered multiple times for the same event

-  * Watch now ignores temp files (as created by Vim)

-  * Configurable number of posts on [homepage](/layout/homepage/)

-  * [Front matter](/content/front-matter/) supports multiple types (int, string, date, float)

-  * Indexes can now use a default template

-  * Addition of truncated bool to content to determine if should show 'more' link

-  * Support for [linkTitles](/layout/variables/)

-  * Better handling of most errors with directions on how to resolve

-  * Support for more date / time formats

-  * Support for go 1.2

-  * Support for `first` in templates

-----

-## **0.8.0** August 2, 2013

-This release represents over 65 code commits from 6 different contributors.

-  * Added support for pretty urls (filename/index.html vs filename.html)

-  * Hugo supports a destination directory

-  * Will efficiently sync content in static to destination directory

-  * Cleaned up options.. now with support for short and long options

-  * Added support for TOML

-  * Added support for YAML

-  * Added support for Previous & Next

-  * Added support for indexes for the indexes

-  * Better Windows compatibility

-  * Support for series

-  * Adding verbose output

-  * Loads of bugfixes

-----

-## **0.7.0** July 4, 2013

-  * Hugo now includes a simple server

-  * First public release

-----

-## **0.6.0** July 2, 2013

-  * Hugo includes an example documentation site which it builds

-----

-## **0.5.0** June 25, 2013

-  * Hugo is quite usable and able to build spf13.com

--- a/content/showcase/2626info.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-05-03T17:20:59+09:00

-description: "Personal blog of Masashi Tsuru"

-license: ""

-licenseLink: ""

-sitelink: http://2626.info/

-tags:

-- personal

-- blog

-thumbnail: /img/2626info-tn.png

-title: 2626.info

----

--- a/content/showcase/antzucaro.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-02-03T20:00:00Z

-description: Ant Zucaro's Blog

-license: GPL

-licenseLink: ""

-sitelink: http://antzucaro.com/

-sourceLink: https://github.com/antzucaro/az.com

-tags:

-- personal

-- blog

-- foundation

-thumbnail: /img/antzucaro-tn.jpg

-title: Ant Zucaro

----

--- a/content/showcase/appernetic.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2016-04-26

-date: 2016-04-26T13:33:33Z

-description: Appernetic.io blog

-license: MIT

-licenseLink: https://github.com/appernetic/hugo-bootstrap-premium/blob/master/LICENSE.md

-sitelink: https://blog.appernetic.io/

-sourceLink: https://github.com/appernetic/hugo-bootstrap-premium

-tags:

-- company

-- blog

-- bootstrap

-thumbnail: /img/apperneticioblog.png

-title: Appernetic

----

--- a/content/showcase/arresteddevops.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2015-11-20

-date: 2015-11-20T01:46:33-06:00

-description: "Arrested DevOps is a podcast focusing on trends in the DevOps space"

-license: "apache2"

-licenseLink: "https://github.com/arresteddevops/ado-hugo/blob/master/LICENSE.md"

-sitelink: https://www.arresteddevops.com/

-sourceLink: https://github.com/arresteddevops/ado-hugo

-tags:

-- podcast

-- bootstrap

-thumbnail: /img/arresteddevops-tn.png

-title: arresteddevops

----

--- a/content/showcase/asc.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-01-22T07:32:00Z

-description: ""

-license: CC-BY-SA

-licenseLink: ""

-sitelink: http://andrewcodispoti.com/

-sourceLink: https://gitlab.com/acodispo/andrewcodispoti-com

-tags:

-- personal

-- bootstrap

-thumbnail: /img/asc-tn.jpg

-title: Andrew S Codispoti

----

--- a/content/showcase/astrochili.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-07-31T11:22:32+03:00

-description: "Personal website"

-license: ""

-licenseLink: ""

-sitelink: http://romansilin.com/

-sourceLink: https://github.com/astrochili/astrochili.github.io

-tags:

-- personal

-- blog

-thumbnail: /img/astrochili-tn.png

-title: Roman Silin

----

--- a/content/showcase/aydoscom.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2016-04-23T13:23:00Z

-description: "web applications"

-license: ""

-licenseLink: ""

-sitelink: https://aydos.com/

-tags:

-- web applications

-thumbnail: /img/aydoscom.png

-title: aydos.com

----

--- a/content/showcase/balaramadurai.net.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2016-11-17T12:27:18+05:30

-description: "Dr. Bala Ramadurai, Professor & Consultant in Innovation, Design Thinking and Tech Forecasting"

-license: ""

-licenseLink: ""

-sitelink: http://balaramadurai.net

-tags:

-- personal

-- blog

-thumbnail: /img/balaramadurai-net-tn.jpg

-title: Dr. Bala Ramadurai | Professor & Consultant in Innovation, Design Thinking and Tech Forecasting

----

--- a/content/showcase/barricade.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-04-15T14:14:28+01:00

-description: "Barricade is an early warning system against hackers."

-license: ""

-licenseLink: ""

-sitelink: https://barricade.io

-tags:

-- company

-- security

-thumbnail: /img/barricade-tn.png

-title: Barricade

----

--- a/content/showcase/bepsays.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-05-26

-date: 2013-11-01T07:32:00Z

-description: "bep's blog"

-license: ""

-licenseLink: ""

-sitelink: http://bepsays.com/

-sourceLink: "https://github.com/bep/bepsays.com"

-tags:

-- personal

-- blog

-thumbnail: /img/bepsays-tn.png

-title: bepsays.com

----

--- a/content/showcase/bharathpalavalli.com.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2017-03-15T07:32:00Z

-description: "Bharath M. Palavalli"

-license: ""

-licenseLink: ""

-sitelink: http://bharathpalavalli.com

-sourceLink: https://github.com/bmp/bharathmp-hugo/tree/gh-pages

-tags:

-- personal

-- website

-thumbnail: /img/bharathpalavalli-tn.png

-title: bharathpalavalli.com

----

--- a/content/showcase/bugtrackers.io.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-lastmod: 2015-10-27

-date: 2015-10-27T09:02:00Z

-description: bugtrackers.io provides stories of digital crafters. It shows people behind bits, pixels and bug reports. bugtrackers.io is your resource for web development.

-sitelink: https://www.bugtrackers.io/

-tags:

-- blog

-- community

-- interviews

-thumbnail: /img/bugtrackersio-tn.jpg

-title: bugtrackers.io

----

--- a/content/showcase/bullion-investor.md

+++ /dev/null

@@ -1,22 +1,0 @@

----

-date: 2017-02-11T10:30:00+02:00

-description: "German language GOLD REPORT. Tips, tricks, news & glossary on coins, bullion bars and precious-metals investments."

-sitelink: https://www.bullion-investor.com/report/

-tags:

-- 'gold price'

-- blog

-- coins

-- deutschland

-- finance

-- germany

-- gold

-- investment

-- news

-- numismatics

-- palladium

-- platinum

-- report

-- silver

-thumbnail: /img/bullion-investor-com.png

-title: GOLDREPORT — Gold, Silver & Numismatics News

----

\ No newline at end of file

--- a/content/showcase/camunda-blog.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-11-30

-date: 2015-12-01T04:20:00Z

-description: "Camunda BPM Team Blog"

-license: "Apache 2.0"

-licenseLink: "https://github.com/camunda/blog.camunda.org#license"

-sitelink: http://blog.camunda.org/

-sourceLink: https://github.com/camunda/blog.camunda.org

-tags:

-- company

-- blog

-thumbnail: /img/camunda-blog.png

-title: Camunda Blog

----

--- a/content/showcase/camunda-docs.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-11-30

-date: 2015-12-01T04:20:00Z

-description: "Camunda BPM Documentation"

-license: MIT

-licenseLink: "https://github.com/camunda/camunda-docs-theme#licence"

-sitelink: http://docs.camunda.org/

-sourceLink: https://github.com/camunda/camunda-docs-theme

-tags:

-- company

-- documentation

-thumbnail: /img/camunda-docs.png

-title: Camunda Docs

----

--- a/content/showcase/carnivorousplants.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2017-05-13T11:00:00Z

-description: "Tools, guides, and interactive resources for growers of all carnivorous plant species."

-license: ""

-licenseLink: ""

-sitelink: https://www.carnivorousplants.co.uk/

-tags:

-- blog

-- education

-thumbnail: /img/carnivorousplants-tn.png

-title: CarnivorousPlants.co.uk

----

--- a/content/showcase/cdnoverview.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-02-17T15:19:08+01:00

-description: "Overview and comparison of CDNs, their features and prices"

-license: ""

-licenseLink: ""

-sitelink: https://www.cdnoverview.com/

-tags:

-- bootstrap

-- portfolio

-- tech

-thumbnail: /img/cdnoverview-tn.png

-title: cdnoverview.com

----

--- a/content/showcase/chinese-grammar.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-lastmod: 2015-08-21

-date: 2015-08-23

-description: Chinese grammar lessons

-sitelink: https://www.chineseboost.com/grammar/

-sourceLink: https://github.com/hughgrigg/chineseboost-articles

-tags:

-- learning

-- education

-thumbnail: /img/chinese-grammar-tn.png

-title: Chinese Grammar

----

--- a/content/showcase/chingli.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-lastmod: 2015-12-19

-date: 2014-08-26T11:20:02-04:00

-description: "chingli’s personal blog"

-sitelink: http://www.chingli.com/

-tags:

-- personal

-- blog

-thumbnail: /img/chingli-tn.jpg

-title: <span lang="zh-CN">青砾</span> (chingli)

----

--- a/content/showcase/chipsncookies.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2016-04-14

-date: 2015-07-08T14:02:16+02:00

-description: "personal blog and portfolio of Samuel Debruyn"

-license: ""

-licenseLink: ""

-sitelink: https://chipsncookies.com

-sourceLink: https://github.com/SamuelDebruyn/chipsncookies-site

-tags:

-- personal

-- blog

-thumbnail: /img/chipsncookies-tn.png

-title: Chips 'n' Cookies

----

--- a/content/showcase/christianmendoza.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2017-06-30

-date: 2016-10-16T13:30:47-04:00

-description: "Personal site"

-license: ""

-licenseLink: ""

-sitelink: https://www.christianmendoza.me/

-sourceLink: https://github.com/christianmendoza/christianmendoza.me

-tags:

-- personal

-- profile

-thumbnail: /img/christianmendoza-tn.jpg

-title: christianmendoza.me

----

--- a/content/showcase/cinegyopen.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2016-09-05T23:23:18+02:00

-description: "Cinegy Open documentation project"

-license: ""

-licenseLink: ""

-sitelink: https://open.cinegy.com/

-sourceLink:

-tags:

-- documentation

-thumbnail: /img/cinegyopen-tn.png

-title: Cinegy Open

----

\ No newline at end of file

--- a/content/showcase/clearhaus.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-10-21T12:37:00+02:00

-description: "Online Acquiring · Accept Visa & MasterCard within 1-3 days"

-license: ""

-licenseLink: ""

-sitelink: https://www.clearhaus.com/

-tags:

-  - company

-  - fintech

-  - payments

-  - acquirer

-thumbnail: /img/clearhaus-tn.png

-title: Clearhaus

----

--- a/content/showcase/cloudshark.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-03-27T09:45:00Z

-description: CloudShark Appliance homepage and documentation

-license: ""

-licenseLink: ""

-sitelink: https://appliance.cloudshark.org/

-tags:

-- company

-- documentation

-- foundation

-thumbnail: /img/cloudshark-tn.jpg

-title: CloudShark

----

--- a/content/showcase/coding-journal.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2015-12-23

-date: 2015-12-23T11:42:00+01:00

-description: blog, portfolio

-license: ""

-licenseLink: ""

-sitelink: http://blog.kulman.sk/

-sourceLink: https://github.com/igorkulman/coding-journal

-tags:

-- blog

-- portfolio

-thumbnail: /img/codingjournal-tn.png

-title: Coding Journal

----

--- a/content/showcase/consequently.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-02-11

-date: 2015-02-11T13:21:27+11:00

-description: "consequently.org, Greg Restall's personal website"

-license: ""

-licenseLink: ""

-sitelink: http://consequently.org

-sourceLink: "https://github.com/consequently/consequently-hugo"

-tags:

-- academic

-- blog

-- kube

-thumbnail: /img/consequently.jpg

-title: consequently.org

----

--- a/content/showcase/ctlcompiled.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-07-25T13:45:09-04:00

-description: "CompilED is a collection of reflections and comments by the software developers at Columbia’s Center for Teaching and Learning (CTL). These views are rooted in our professional and personal experiences developing educational technology."

-license: "Creative Commons Attribution-ShareAlike 3.0 United States."

-licenseLink: "https://creativecommons.org/licenses/by-sa/3.0/us/"

-sitelink: https://compiled.ctl.columbia.edu/

-tags:

-- edtech

-- technology

-- blog

-thumbnail: /img/ctlcompiled-tn.png

-title: CompilED at CTL

----

--- a/content/showcase/danmux.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T10:55:23-04:00

-description: ""

-license: MIT

-licenseLink: ""

-sitelink: http://danmux.com/

-sourceLink: https://github.com/danmux/danmux-hugo

-tags:

-- personal

-- blog

-thumbnail: /img/danmux-tn.jpg

-title: Danmux

----

--- a/content/showcase/datapipelinearchitect.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-02-04T18:30:07-05:00

-description: "Professional website at datapipelinearchitect.com"

-sitelink: http://datapipelinearchitect.com/

-tags:

-- company

-- tech

-- blog

-- website

-thumbnail: /img/datapipelinearchitect-tn.jpg

-title: Data Pipeline Architect

----

--- a/content/showcase/davidepetilli.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-05-25

-date: 2013-11-01T07:32:00Z

-description: ""

-license: MIT

-licenseLink: ""

-sitelink: http://davidepetilli.com

-tags:

-- personal

-- photography

-- portfolio

-- blog

-thumbnail: /img/davidepetilli-tn.jpg

-title: Davide Petilli

----

--- a/content/showcase/davidrallen.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2016-02-03T11:49:07-05:00

-description: "Personal website for David Allen"

-license: "MIT"

-licenseLink: "https://opensource.org/licenses/MIT"

-sitelink: http://davidrallen.com/

-sourceLink: https://github.com/doctorallen/davidrallen.com

-tags:

-- personal

-- blog

-- tech

-thumbnail: /img/davidrallen-tn.png

-title: David Allen

----

--- a/content/showcase/davidyates.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-09-10T07:07:39+02:00

-description: "David Yates"

-license: ""

-licenseLink: ""

-sitelink: https://davidyat.es/

-tags:

-- personal

-- blog

-thumbnail: /img/davidyates-tn.png

-title: David Yates

----

--- a/content/showcase/dbzman-online.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2017-01-02T07:32:00Z

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://dbzman-online.eu/

-sourceLink: https://github.com/Dbzman/dbzman-online.eu

-tags:

-- personal

-- blog

-- portfolio

-thumbnail: /img/dbzman-online-tn.png

-title: Dbzman-Online

----

--- a/content/showcase/devmonk.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T11:31:02-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: https://devmonk.com/

-sourceLink: https://github.com/peteraba/devmonk.com

-tags:

-- educational

-- video

-thumbnail: /img/devmonk-tn.jpg

-title: devmonk

----

--- a/content/showcase/dmitriid.com.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-10-19T16:52:28+02:00

-description: "Personal blog"

-license: "CC BY-NC 4.0"

-licenseLink: ""

-sitelink: http://dmitriid.com/

-sourceLink: https://github.com/dmitriid/dmitriid.com

-tags:

-- personal

-- blog

-thumbnail: /img/dmitriid.com.png

-title: dmitriid.com

----

--- a/content/showcase/emilyhorsman.com.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-lastmod: 2016-01-09

-date: 2016-01-09T01:00:10Z

-description: Personal homepage

-sitelink: https://emilyhorsman.com/

-sourceLink: https://github.com/emilyhorsman/buttercup

-tags:

-- personal

-- blog

-thumbnail: /img/emilyhorsman.com-tn.jpg

-title: emilyhorsman.com

----

--- a/content/showcase/enjoyablerecipes.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-date: 2017-03-07T07:32:00Z

-description: "Indian Recipes Blog"

-license: ""

-licenseLink: ""

-sitelink: https://enjoyable.recipes/

-sourceLink: https://github.com/shubhojyoti/enjoyablerecipes-hugo

-tags:

-- personal

-- blog

-- recipes

-- zurb-foundation

-thumbnail: /img/enjoyablerecipes-tn.png

-title: Enjoyable Recipes

----

--- a/content/showcase/esaezgil.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-date: 2017-04-02T07:32:00Z

-description: "Personal blog of Enrique Saez Gil - esaezgil"

-license: ""

-licenseLink: ""

-sitelink: https://esaezgil.com

-sourceLink: https://github.com/esaezgil/esaezgil.github.io

-tags:

-- personal

-- technical blog

-- software

-- open source

-thumbnail: /img/esaezgil_com-tn.png

-title: esaezgil.com

----

--- a/content/showcase/esolia-com.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-08-08

-date: 2015-07-07T04:32:00Z

-description: Tokyo IT service provider eSolia Inc's Hugo-powered website.

-license: MIT

-licenseLink: ""

-sitelink: http://esolia.com/

-sourceLink: https://github.com/eSolia/eSolia

-tags:

-- company

-- esolia

-- rickcogley

-- japan

-thumbnail: /img/esolia_com-tn.png

-title: eSolia.com

----

--- a/content/showcase/esolia-pro.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-08-08

-date: 2015-07-07T04:32:00Z

-description: Tokyo IT service provider eSolia Inc's eSolia.pro blog site, powered by Hugo.

-license: MIT

-licenseLink: ""

-sitelink: http://esolia.pro/

-sourceLink: https://github.com/eSolia/eSolia.pro

-tags:

-- company

-- esolia

-- rickcogley

-- japan

-thumbnail: /img/esolia_pro-tn.png

-title: eSolia.pro

----

--- a/content/showcase/eurie.md

+++ /dev/null

@@ -1,11 +1,0 @@

----

-date: 2016-10-15T23:30:59+09:00

-description: "User guide for euire Desk"

-license: ""

-licenseLink: ""

-sitelink: https://docs.eurie.io

-tags:

-- documentation

-thumbnail: /img/docs.eurie.io-tn.png

-title: eurie Desk docs

----

--- a/content/showcase/fale.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2016-03-01

-date: 2016-03-01T12:38:00Z

-description: Fabio Alessandro Locati personal blog.

-license: AGPLv3

-licenseLink: ""

-sitelink: http://fale.io/

-sourceLink: https://github.com/fale/fale.io

-tags:

-- personal

-- blog

-thumbnail: /img/fale-tn.png

-title: fale.io

----

--- a/content/showcase/firstnameclub.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2017-03-31T22:36:12+03:00

-description: "Multilingual website. Size 20GB, build time 25 mins. Cloudflare, s3, bootstrap 4"

-license: ""

-licenseLink: ""

-sitelink: https://firstname.club

-sourceLink:

-tags:

-- data

-- website

-thumbnail: /img/firstnameclub.png

-title: firstname club

----

--- a/content/showcase/fixatom.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-10-17T16:19:24+08:00

-description: "a personal blog"

-license: ""

-licenseLink: ""

-sitelink: https://fixatom.com/

-tags:

-- personal

-- blog

-thumbnail: /img/fixatom-tn.png

-title: Atom

----

--- a/content/showcase/furqansoftware.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2017-05-24T06:19:40Z

-description: "Official company website"

-sitelink: https://furqansoftware.com/

-tags:

-- company

-- website

-- blog

-- tech

-thumbnail: /img/furqansoftware-tn.png

-title: Furqan Software

----

--- a/content/showcase/fxsitecompat.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-09-08

-date: 2014-08-26T19:40:00-04:00

-description: Multilingual, community documentation and blog site

-license: ""

-licenseLink: ""

-sitelink: https://www.fxsitecompat.com/

-sourceLink: https://github.com/fxsitecompat/www.fxsitecompat.com

-tags:

-- community

-- documentation

-- translation

-thumbnail: /img/fxsitecompat-tn.png

-title: Firefox Site Compatibility

----

--- a/content/showcase/gntech.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2016-02-13T21:47:27+01:00

-description: "Projects, music and drawings, the personal web page of Gustav Näslund"

-license: ""

-licenseLink: ""

-sitelink: http://www.gntech.se/

-tags:

-- personal

-- blog

-- projects

-- music

-- drawings

-thumbnail: /img/gntech-tn.png

-title: gntech.se

----

--- a/content/showcase/gogb.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-lastmod: 2015-05-25

-date: 2013-11-01T07:32:00Z

-description: ""

-license: MIT

-licenseLink: ""

-sitelink: http://getgb.io

-tags:

-- project

-thumbnail: /img/gogb-tn.jpg

-title: GoGB

----

--- a/content/showcase/goin5minutes.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-lastmod: 2015-11-20

-date: 2015-11-20T20:46:00Z

-description: "Code for Go in 5 Minutes Screencasts"

-license: "Apache License 2.0"

-licenseLink: "https://github.com/arschles/go-in-5-minutes/blob/master/LICENSE"

-sitelink: http://www.goin5minutes.com/

-sourceLink: https://github.com/arschles/go-in-5-minutes/tree/master/www

-tags:

-- screencasts

-thumbnail: /img/goin5minutes-tn.png

-title: Go in 5 minutes

----

\ No newline at end of file

--- a/content/showcase/h10n.me.md

+++ /dev/null

@@ -1,11 +1,0 @@

----

-date: 2016-03-05T14:30:21+01:00

-description: "Personal profile page of Horst Gutmann"

-sitelink: http://h10n.me/

-sourceLink: https://github.com/zerok/h10n.me

-tags:

-- personal

-- profile

-thumbnail: /img/h10n.me-tn.png

-title: h10n.me

----

--- a/content/showcase/heimatverein-niederjosbach.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2017-01-02T07:32:00Z

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://heimatverein-niederjosbach.de/

-sourceLink: https://github.com/Dbzman/heimatverein-niederjosbach.de

-tags:

-- association

-- gallery

-thumbnail: /img/heimatverein-niederjosbach-tn.png

-title: Niederjosbacher Heimat- und Geschichtsverein 2007 e.V.

----

--- a/content/showcase/horeaporutiu.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2017-06-22T07:32:00Z

-description: ""

-license: ""

-licenseLink: ""

-sitelink: https://horeaporutiu.github.io/

-sourceLink: https://github.com/horeaporutiu/hugo-horeaporutiu

-tags:

-- personal

-- blog

-thumbnail: /img/horeaporutiu-tn.jpg

-title: horeaporutiu.github.io

----

--- a/content/showcase/hugo.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2013-07-01T07:32:00Z

-description: This site

-license: Simpl

-licenseLink: ""

-sitelink: http://gohugo.io/

-sourceLink: https://github.com/gohugoio/hugo/tree/master/docs

-tags:

-- documentation

-- bootstrap

-thumbnail: /img/hugo-tn.jpg

-title: Hugo

----

--- a/content/showcase/invincible.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2017-07-01T01:11:00Z

-description: "The Invincible: The tale of a disillusioned prince"

-license: "Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License"

-licenseLink: "https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode"

-sitelink: https://invincible.site/

-sourceLink: https://github.com/shazic/the_invincible

-tags:

-- personal

-- blog

-- graphic novel

-thumbnail: /img/invincible-tn.jpg

-title: Invincible

----

--- a/content/showcase/invision.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2017-01-28T12:04:00Z

-description: InVision Engineering Blog

-license: ""

-licenseLink: ""

-sitelink: http://engineering.invisionapp.com

-tags:

-- company

-- blog

-- engineering

-thumbnail: /img/invision-tn.png

-title: InVision Engineering Blog

----

--- a/content/showcase/jamescampbell.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2016-06-06T14:42:59-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: https://jamescampbell.us/

-sourceLink: https://github.com/jamesacampbell/causes-and-effects-hugo

-tags:

-- personal

-- blog

-thumbnail: /img/jamescampbell-tn.png

-title: jamescampbell.us

----

--- a/content/showcase/jorgennilsson.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2016-02-11T23:41:27+01:00

-description: "Personal web site and blog of digital director Jorgen Nilsson"

-license: ""

-licenseLink: ""

-sitelink: http://jorgennilsson.com/

-tags:

-- personal

-- blog

-thumbnail: /img/jorgennilsson-tn.png

-title: jorgennilsson.com

----

--- a/content/showcase/kieranhealy.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-02-27T20:35:00Z

-description: Kieran Healy's Website

-license: ""

-licenseLink: ""

-sitelink: http://kieranhealy.org/

-sourceLink: https://github.com/kjhealy/kieranhealy.hugo

-tags:

-- personal

-- blog

-- academic

-thumbnail: /img/kjhealy-tn.jpg

-title: Kieran Healy

----

--- a/content/showcase/klingt-net.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2016-05-15T23:18:16+02:00

-description: "klingt.net is the personal homepage of Andreas Linz."

-license: ""

-licenseLink: ""

-sitelink: https://klingt.net/

-sourceLink: https://github.com/klingtnet/klingt.net

-tags:

-- personal

-- blog

-- programming

-thumbnail: /img/klingt-net-tn.png

-title: klingt net

----

--- a/content/showcase/launchcode5.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-11-01T07:32:00Z

-description: Corporate Site for Launchcode Software Studios

-license: Copyright Launchcode Software Studios

-licenseLink: ""

-sitelink: http://www.launchcode5.com/

-sourceLink: https://github.com/Launchcode5/launchcode5.com

-tags:

-- bootstrap

-thumbnail: /img/launchcode-tn.jpg

-title: Launchcode Software Studios

----

--- a/content/showcase/leepenney.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2016-01-24

-date: 2016-01-24T16:10:00Z

-description: Site of author Lee Penney

-license: MIT

-licenseLink: ""

-sitelink: http://leepenney.com/

-tags:

-- personal

-- website

-thumbnail: /img/leepenney-tn.jpg

-title: Lee Penney

----

--- a/content/showcase/leowkahman.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2016-07-24T00:00:00+08:00

-description: "Leow Kah Man - Tech Blog"

-license: ""

-licenseLink: ""

-sitelink: https://www.leowkahman.com/

-tags:

-- personal

-- blog

-thumbnail: /img/leowkahman-tn.png

-title: Leow Kah Man - Tech Blog

----

\ No newline at end of file

--- a/content/showcase/lk4d4.darth.io.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-25T18:59:30-04:00

-description: Alexandr Morozov

-license: ""

-licenseLink: ""

-sitelink: http://lk4d4.darth.io/

-sourceLink: https://github.com/LK4D4/lk4d4.darth.io

-tags:

-- personal

-- blog

-thumbnail: /img/lk4d4-tn.jpg

-title: lk4d4.darth.io

----

--- a/content/showcase/losslesslife.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-11-15

-date: 2015-11-15T11:20:00-08:00

-description: "Losslesslife covers everything high-end and audiophile headphones. Headphones and headphone amplifiers, accessories, how-to guides, and reviews."

-sitelink: http://pages.losslesslife.com/

-tags:

-- headphones

-- electronics

-- technical

-- reviews

-- education

-- audiophile

-thumbnail: /img/losslesslife-tn.png

-title: LosslessLife

----

--- a/content/showcase/lucumt.info.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2017-03-12T13:14:14+08:00

-description: "Personal blog of Rosen Lu"

-license: ""

-licenseLink: ""

-sitelink: http://lucumt.info/posts

-sourceLink: https://github.com/lucumt/ghblog

-tags:

-- personal

-- blog

-thumbnail: /img/lucumt.info.png

-title: 飞狐的部落格

----

--- a/content/showcase/mariosanchez.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2015-06-20

-date: 2015-06-20

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://mariosanchez.org/

-sourceLink: https://github.com/mariobox/Hugo-Source

-tags:

-- personal

-- blog

-thumbnail: /img/mariosanchez-tn.jpg

-title: mariosanchez.org

----

--- a/content/showcase/mayan-edms.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-06-13T19:38:56-04:00

-description: "Free Open Source Document Management System"

-license: "Apache 2.0"

-licenseLink: ""

-sitelink: http://www.mayan-edms.com/

-sourceLink: https://gitlab.com/mayan-edms/website

-tags:

-- paperless

-- floss

-thumbnail: /img/mayan-edms-tn.png

-title: Mayan EDMS

----

--- a/content/showcase/michaelwhatcott.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T11:47:11-04:00

-description: ""

-license: Simpl-2.0

-licenseLink: ""

-sitelink: http://michaelwhatcott.com/

-sourceLink: https://bitbucket.org/mdwhatcott/michaelwhatcott.com-boilerplate/src

-tags:

-- personal

-- blog

-thumbnail: /img/michaelwhatcott-tn.jpg

-title: michaelwhatcott

----

--- a/content/showcase/mongodb-eng-journal.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-03-09T14:14:16-05:00

-description: "The MongoDB Engineering Journal -- for builders, by builders."

-license: ""

-licenseLink: ""

-sitelink: http://engineering.mongodb.com/

-tags:

-- engineering

-- blog

-thumbnail: /img/mongodb-eng-tn.png

-title: The Mongodb Engineering Journal

----

--- a/content/showcase/mtbhomer.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-06-19T11:38:39+02:00

-description: "Personal website Martijn ten Bhömer"

-license: ""

-licenseLink: ""

-sitelink: https://www.mtbhomer.com/

-sourceLink: https://github.com/mtbhomer/web-portfolio

-tags:

-- personal

-- portfolio

-- design

-thumbnail: /img/mtbhomer-tn.png

-title: mtbhomer.com

----

--- a/content/showcase/myearworms.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2017-03-08T07:32:00Z

-description: "All the songs that get stuck in my head"

-license: ""

-licenseLink: ""

-sitelink: https://myearworms.com/

-sourceLink: https://github.com/jaydreyer/myearworms

-tags:

-- personal

-- blog

-- music

-thumbnail: /img/myearworms-tn.jpg

-title: My Earworms

----

--- a/content/showcase/neavey.net.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-12-21T21:19:46Z

-description: "Adventure Miles - A personal travel blog."

-license: "MIT"

-licenseLink: "https://raw.githubusercontent.com/patrickn/neaveynet-hugo/master/LICENSE.md"

-sitelink: http://neavey.net/

-sourceLink: https://github.com/patrickn/neaveynet-hugo

-tags:

-- personal

-- travel

-- blog

-thumbnail: /img/neavey-tn.jpg

-title: neavey.net

----

--- a/content/showcase/nickoneill.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T12:15:48-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://blog.nickoneill.name/

-sourceLink: https://github.com/nickoneill/blog.nickoneill.name

-tags:

-- personal

-- blog

-thumbnail: /img/nickoneill-tn.jpg

-title: authenticgeek

----

--- a/content/showcase/ninjaducks.in.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2015-10-24

-date: 2015-10-24T14:06:00+05:30

-description: Personal blog

-license: ""

-licenseLink: ""

-sitelink: http://ninjaducks.in

-sourceLink: https://github.com/shivanshuag/shivanshuag.github.io/tree/new

-tags:

-- personal

-- blog

-thumbnail: /img/ninjaducks-tn.png

-title: ninjaducks.in

----

--- a/content/showcase/ninya.io.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T09:47:00-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://blog.ninya.io/

-sourceLink: https://github.com/ninya-io/ninya-io.github.io/tree/dev

-tags:

-- project

-- blog

-thumbnail: /img/ninya-tn.jpg

-title: ninya.io

----

--- a/content/showcase/nodesk.md

+++ /dev/null

@@ -1,11 +1,0 @@

----

-lastmod: 2015-08-26

-date: 2015-08-26T22:33:00Z

-description: "NoDesk | All Things Digital Nomad"

-sitelink: http://nodesk.co/

-tags:

-- digital nomad

-- web

-thumbnail: /img/nodesk-tn.png

-title: nodesk.co

----

--- a/content/showcase/novelist-xyz.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-05-22T17:54:51+08:00

-description: "Peter Y. Chuang - Novelist, Short Story Writer"

-license: ""

-licenseLink: ""

-sitelink: https://novelist.xyz

-sourceLink: https://github.com/peterychuang/peterychuang.github.io/tree/source

-tags:

-- personal

-- blog

-thumbnail: /img/novelist-xyz.png

-title: Peter Y. Chuang

----

--- a/content/showcase/npf.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-08-21T12:21:18-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://npf.io/

-sourceLink: https://github.com/natefinch/npf

-tags:

-- personal

-- blog

-thumbnail: /img/npf-tn.jpg

-title: npf.io

----

--- a/content/showcase/nutspubcrawl.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2017-06-03T07:32:00Z

-description: ""

-license: ""

-licenseLink: ""

-sitelink: https://nutspubcrawl.com/

-sourceLink: https://github.com/jeremielondon/nuts-hugo

-tags:

-- company

-- multilingual

-- London

-thumbnail: /img/nutspubcrawl.jpg

-title: Nutspubcrawl.com

----

--- a/content/showcase/ocul-maps.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2017-05-09T11:04:33-04:00

-description: "The Ontario Council of University Libraries Historical Topographic Maps Digitization Project"

-license: ""

-licenseLink: ""

-sitelink: http://ocul.on.ca/topomaps

-sourcelink: https://github.com/scholarsportal/historical-topos

-tags:

-- education

-- project

-- multilingual

-thumbnail: /img/ocul-maps.png

-title: OCUL topographic maps

----

--- a/content/showcase/petanikode.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2017-01-10T07:32:00Z

-description: "Programmer Pengguna Linux"

-license: ""

-licenseLink: ""

-sitelink: http://petanikode.com/

-tags:

-- programming

-- blog

-thumbnail: /img/petanikode.png

-title: Petani Kode

----

--- a/content/showcase/peteraba.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T11:30:57-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: https://peteraba.com/

-sourceLink: https://github.com/peteraba/peteraba.com

-tags:

-- personal

-- blog

-thumbnail: /img/peteraba-tn.jpg

-title: peteraba

----

--- a/content/showcase/picturingjordan.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2017-01-22T17:32:00Z

-description: "Sharing Jordan with the world — one picture at a time."

-license: "Creative Commons Attribution 4.0 International"

-licenseLink: https://creativecommons.org/licenses/by-sa/4.0/

-sitelink: https://picturingjordan.com/

-sourceLink: https://github.com/alanorth/picturingjordan.com

-tags:

-- personal

-- blog

-thumbnail: /img/picturingjordan-tn.png

-title: picturingjordan.com

----

--- a/content/showcase/promotive.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2017-02-21T12:26:26+01:00

-description: "Corporate website a event management agency"

-license: ""

-licenseLink: ""

-sitelink: https://promotive.es

-tags:

-- company

-- corporate

-- spanish

-- event management

-- bootstrap

-thumbnail: /img/promotive.png

-title: Promotive

----

--- a/content/showcase/rahulrai.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-10-04T21:01:18+01:00

-description: "My Take on Cloud"

-license: ""

-licenseLink: ""

-sitelink: https://rahulrai.in

-sourceLink: https://github.com/moonytheloony/Blog-Web

-tags:

-- personal

-- blog

-thumbnail: /img/rahulrai_in-tn.png

-title: My Take on Cloud

----

--- a/content/showcase/rakutentech.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2016-01-20

-date: 2016-01-20T07:32:00Z

-description: ""

-license: MIT

-licenseLink: ""

-sitelink: http://techblog.rakuten.co.jp/

-tags:

-- company

-- blog

-thumbnail: /img/rakutentech-tn.png

-title: Rakuten Tech Blog

----

--- a/content/showcase/rdegges.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-08-05T15:33:56-07:00

-description: "The personal website of Randall Degges."

-license: "Unlicense"

-licenseLink: "http://unlicense.org/"

-sitelink: https://www.rdegges.com/

-sourceLink: https://github.com/rdegges/rdegges-www

-tags:

-- personal

-- blog

-thumbnail: /img/rdegges-tn.png

-title: Randall Degges

----

--- a/content/showcase/readtext.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-lastmod: 2015-11-16

-date: 2015-11-16T08:36:00Z

-description: Restored text files

-sitelink: http://readtext.org/

-tags:

-- textfiles

-- reading

-thumbnail: /img/readtext-tn.png

-title: ReadText

----

--- a/content/showcase/richardsumilang.md

+++ /dev/null

@@ -1,17 +1,0 @@

----

-lastmod: 2015-09-08

-date: 2015-09-07T00:12:00-07:00

-description: "Personal website dedicated to electronics, programming, and reviews."

-license: "MIT"

-licenseLink: "https://opensource.org/licenses/MIT"

-sitelink: http://richardsumilang.com/

-sourceLink: https://github.com/richardsumilang-blog

-tags:

-- personal

-- blog

-- technical

-- electronics

-- reviews

-thumbnail: /img/richardsumilang-tn.png

-title: Richard Sumilang - Top Secret Labs

----

--- a/content/showcase/rick-cogley-info.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2016-02-01

-date: 2015-05-20T04:32:00Z

-description: Rick Cogley's personal site, powered by Hugo.

-license: MIT

-licenseLink: ""

-sitelink: http://rick.cogley.info/

-sourceLink: https://github.com/RickCogley/RCC-Hugo2015

-tags:

-- personal

-- blog

-- rickcogley

-- japan

-thumbnail: /img/rick_cogley_info-tn.jpg

-title: rick.cogley.info

----

--- a/content/showcase/ridingbytes.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-10-01

-date: 2015-09-27T00:00:00Z

-description: Official Company Website

-license: ""

-licenseLink: ""

-sitelink: http://ridingbytes.com/

-tags:

-- company

-- website

-- blog

-- tech

-thumbnail: /img/ridingbytes-tn.png

-title: RIDING BYTES

----

--- a/content/showcase/robertbasic.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2016-03-26

-date: 2016-03-26T17:47:40+01:00

-description: "Robert Basic is a web developer from Serbia."

-license: ""

-licenseLink: ""

-sitelink: http://robertbasic.com/

-sourceLink: https://github.com/robertbasic/robertbasic.com-hugo

-tags:

-- personal

-- blog

-thumbnail: /img/robertbasic-tn.png

-title: Robert Basic's blog

----

--- a/content/showcase/sanjay-saxena.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2017-04-13T07:32:00Z

-description: ""

-license: ""

-licenseLink: ""

-sitelink: https://sanjay-saxena.github.io

-sourceLink: https://github.com/sanjay-saxena/sanjay-saxena-hugo

-tags:

-- personal

-- blog

-thumbnail: /img/sanjay-saxena-tn.png

-title: sanjay-saxena.github.io

----

--- a/content/showcase/scottcwilson.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-08-08

-date: 2015-07-21T10:00:00Z

-description: Personal portfolio, created with Hugo

-license: MIT

-licenseLink: ""

-sitelink: http://scottcwilson.github.io/

-sourceLink: https://github.com/scottcwilson/hugosite

-tags:

-- personal

-- blog

-thumbnail: /img/scottcwilson-tn.png

-title: scottcwilson.com

----

--- a/content/showcase/shapeshed.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-10-10T07:32:00Z

-description: Personal blog.

-license: ""

-licenseLink: ""

-sitelink: http://shapeshed.com/

-sourceLink: https://github.com/shapeshed/shapeshed.com

-tags:

-- personal

-- blog

-thumbnail: /img/shapeshed-tn.png

-title: shapeshed.com

----

--- a/content/showcase/shelan.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2016-02-07

-date: 2016-02-07T10:30:00Z

-description: Shelan's Blog

-license: MIT

-licenseLink: ""

-sitelink: http://shelan.org/

-sourceLink: https://github.com/shelan/my-hugo-site

-tags:

-- personal

-- blog

-thumbnail: /img/shelan-tn.png

-title: shelan.org

----

\ No newline at end of file

--- a/content/showcase/siba.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-date: 2017-08-01T08:12:00Z

-description: "All-in-One Intelligent Bot for Business"

-license: ""

-licenseLink: ""

-sitelink: http://siba.ai/

-tags:

-- corporate

-- saas

-- software

-- chatbot

-- blog

-thumbnail: /img/siba-tn.png

-title: Siba Chatbot

----

--- a/content/showcase/silvergeko.md

+++ /dev/null

@@ -1,12 +1,0 @@

----

-date: 2016-03-28T14:16:59+02:00

-description: "Custom theme of small italian software house"

-license: ""

-licenseLink: ""

-sitelink: http://silvergeko.it/

-tags:

-- profesional

-thumbnail: /img/silvergeko.jpg

-title: Silvergeko

----

--- a/content/showcase/softinio.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2016-03-11

-date: 2015-11-29T07:16:53-05:00

-description: Salar Rahmanian Blog

-license: MIT

-licenseLink: https://raw.githubusercontent.com/softinio/softinio.com/master/LICENSE

-sitelink: http://www.softinio.com/

-sourceLink: https://github.com/softinio/softinio.com

-tags:

-- personal

-- technical

-- blog

-thumbnail: /img/softinio-tn.png

-title: Salar Rahmanian

----

--- a/content/showcase/spf13.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2013-07-01T07:32:00Z

-description: The first Hugo powered website.

-license: MIT

-licenseLink: ""

-sitelink: http://spf13.com/

-sourceLink: https://github.com/spf13/spf13.com

-tags:

-- personal

-- blog

-thumbnail: /img/spf13-tn.jpg

-title: spf13.com

----

--- a/content/showcase/steambap.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-07-28T07:32:00Z

-description: Weilin's blog

-license: MIT

-licenseLink: ""

-sitelink: http://weilinshi.org/

-sourceLink: https://github.com/steambap/weilinshi.org

-tags:

-- personal

-- blog

-thumbnail: /img/steambap.png

-title: weilinshi

----

--- a/content/showcase/stefano.chiodino.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-date: 2016-05-21T21:25:25+01:00

-description: "Personal site + blog"

-license: ""

-licenseLink: ""

-sitelink: https://stefano.chiodino.uk/

-sourceLink: https://github.com/Draga/go-web

-tags:

-- personal

-- blog

-thumbnail: /img/stefano.chiodino-tn.jpg

-title: stefano.chiodino.uk

----

--- a/content/showcase/stou.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-11-23T01:28:16+07:00

-description: "Rasmus Stougaard"

-license: ""

-licenseLink: ""

-sitelink: http://stou.dk/

-sourceLink: "https://github.com/stou/stou.github.io"

-tags:

-- personal

-- blog

-thumbnail: /img/stou-tn.png

-title: stou.dk

----

--- a/content/showcase/szymonkatra.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-07-10

-date: 2015-07-10T16:15:00+01:00

-description: Szymon Katra

-license: ""

-licenseLink: ""

-sitelink: http://szymonkatra.github.io/

-sourceLink: https://github.com/SzymonKatra/SzymonKatra.github.io/tree/master/hugo_project

-tags:

-- personal

-- blog

-thumbnail: /img/szymonkatra-tn.png

-title: szymonkatra.github.io

----

--- a/content/showcase/techmadeplain.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-05-22T19:54:00Z

-description: Tech Coaching site

-license: ""

-licenseLink: ""

-sitelink: http://techmadeplain.com/

-tags:

-- personal

-- blog

-thumbnail: /img/techmadeplain-tn.jpg

-title: Tech Made Plain

----

--- a/content/showcase/tendermint.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T09:34:42-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://tendermint.com/

-sourceLink: https://github.com/tendermint/tendermint.github.io

-tags:

-- project

-thumbnail: /img/tendermint-tn.jpg

-title: tendermint

----

--- a/content/showcase/thecodeking.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-10-09T23:06:16+01:00

-description: "Personal site for articles and projects."

-license: ""

-licenseLink: ""

-sitelink: http://thecodeking.co.uk

-tags:

-- personal

-- blog

-thumbnail: /img/thecodeking-tn.jpg

-title: thecodeking

----

--- a/content/showcase/thehome.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2015-08-08

-date: 2014-12-27T20:00:00+07:00

-description: "Tom Helmer Hansen"

-license: ""

-licenseLink: ""

-sitelink: http://www.thehome.dk/

-sourceLink: "https://github.com/tomhelmer/website-source"

-tags:

-- personal

-- blog

-thumbnail: /img/thehome-tn.png

-title: thehome.dk

----

--- a/content/showcase/thislittleduck.md

+++ /dev/null

@@ -1,11 +1,0 @@

----

-date: 2017-06-04T21:30:00+10:00

-description: "Software company website"

-sitelink: https://thislittleduck.com

-tags:

-- business

-- portfolio

-thumbnail: /img/thislittleduck-tn.png

-title: This Little Duck

----

--- a/content/showcase/tibobeijen.nl.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2017-03-18T11:30:00Z

-description: "Blog of programmer Tibo Beijen"

-license: ""

-licenseLink: ""

-sitelink: https://www.tibobeijen.nl/

-sourceLink: https://github.com/TBeijen/tbnl-hugo

-tags:

-- personal

-- programming

-- blog

-thumbnail: /img/tibobeijen-nl-tn.png

-title: tibobeijen.nl

----

--- a/content/showcase/ttsreader.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-date: 2017-05-19T07:32:00Z

-description: "Online Text to Speech App and Content"

-license: ""

-licenseLink: ""

-sitelink: http://ttsreader.com/

-tags:

-- text to speech

-- app

-- blog

-- showcase

-- company

-thumbnail: /img/ttsreader-tn.png

-title: TTSReader

----

--- a/content/showcase/tutorialonfly.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2016-04-15

-date: 2016-04-15T01:28:16+08:00

-description: "Tutorialonfly.com provide free tutorials in gitbook version online and pdf,epub,mobi etc for offline read, it's a great website built on hugo, thanks spf13 who created hugo"

-license: ""

-licenseLink: ""

-sitelink: https://tutorialonfly.com/

-tags:

-- tutorials

-- free

-- ebook download

-- fast

-thumbnail: /img/tutorialonfly-tn.jpg

-title: Tutorialonfly

----

\ No newline at end of file

--- a/content/showcase/tutswiki.md

+++ /dev/null

@@ -1,19 +1,0 @@

----

-lastmod: 2017-05-23

-date: 2017-05-23T07:33:00Z

-description: "Collaborative tutorials for the internet"

-license: ""

-licenseLink: ""

-sitelink: https://tutswiki.com/

-sourceLink: https://github.com/TutsWiki/source

-tags:

-- tutorial

-- wiki

-- computer science

-- programming

-- documentation

-- books

-thumbnail: /img/tutswiki-tn.jpg

-title: TutsWiki.com

----

--- a/content/showcase/ucsb.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2014-11-25

-date: 2014-08-26T14:12:55-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://philosophy.ucsb.edu/

-sourceLink: https://github.com/ucsbphil/philweb

-tags:

-- education

-thumbnail: /img/ucsb-tn.jpg

-title: ucsb

----

--- a/content/showcase/upbeat.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-06-12T11:57:53+02:00

-description: "Blog by Rocchi Cesare"

-license: ""

-licenseLink: ""

-sitelink: http://upbeat.it/

-sourceLink:

-tags:

-- personal

-- blog

-thumbnail: /img/upbeat.png

-title: upbeat

----

--- a/content/showcase/vamp.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-08-08

-date: 2014-06-26T15:45:00Z

-description: Vamp.io microservices platform homepage and documentation

-license: "Apache 2"

-licenseLink: ""

-sitelink: http://vamp.io/

-tags:

-- tech

-- documentation

-- company

-- api

-thumbnail: /img/vamp_landingpage-tn.png

-title: Vamp.io

----

--- a/content/showcase/viglug.org.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2016-03-01

-date: 2016-03-01T11:20:00Z

-description: ViGLug.org is the website of the Linux User Group of Milan Est (Italy)

-license: "AGPLv3"

-licenseLink: ""

-sitelink: http://viglug.org/

-tags:

-- tech

-- linux

-- user group

-thumbnail: /img/viglug-tn.png

-title: Viglug.org

----

--- a/content/showcase/vurt.co.md

+++ /dev/null

@@ -1,15 +1,0 @@

----

-lastmod: 2014-08-26

-date: 2014-08-26T12:09:39-04:00

-description: ""

-license: ""

-licenseLink: ""

-sitelink: http://vurt.co.uk/

-sourceLink: https://github.com/gilesp/vurtcouk

-tags:

-- personal

-- blog

-thumbnail: /img/vurt.co-tn.jpg

-title: vurt.co.uk

----

--- a/content/showcase/worldtowriters.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2017-05-12

-date: 2017-05-12T22:00:00Z

-description: "A translation service agency site"

-license: MIT

-licenseLink: ""

-sitelink: https://worldtowriters.com

-tags:

-- company

-- translation

-thumbnail: /img/worldtowriters-com.jpg

-title: World to Writers translation site

----

--- a/content/showcase/yslow-rules.md

+++ /dev/null

@@ -1,16 +1,0 @@

----

-lastmod: 2015-08-08

-date: 2014-04-07T10:45:00Z

-description: Community project of YSlow rules translations

-license: MIT License

-licenseLink: https://raw.github.com/checkmyws/yslow-rules/master/LICENSE

-sitelink: http://checkmyws.github.io/yslow-rules/

-sourceLink: https://github.com/checkmyws/yslow-rules

-tags:

-- community

-- documentation

-- translation

-thumbnail: /img/yslow-rules-tn.png

-title: YSlow Rules

----

--- a/content/showcase/ysqi.md

+++ /dev/null

@@ -1,13 +1,0 @@

----

-date: 2016-03-25T09:05:49+08:00

-description: "虞双齐个人博客"

-license: "MIT"

-licenseLink: "https://opensource.org/licenses/MIT"

-sitelink: https://www.yushuangqi.com/

-sourceLink: https://github.com/ysqi/yushuangqi.com/

-tags:

-- personal

-- blog

-thumbnail: /img/ysqi-blog.png

-title: yushuangqi-blog

----

--- a/content/showcase/yulinling.net.md

+++ /dev/null

@@ -1,14 +1,0 @@

----

-lastmod: 2015-12-19

-date: 2015-09-09T21:42:00-04:00

-description: Multilingual, blog

-license: ""

-licenseLink: ""

-sitelink: https://yulinling.net/

-sourceLink: https://bitbucket.org/lynxiayel/yulinling_source_public

-tags:

-- blog

-- documentation

-thumbnail: /img/yulinling-tn.jpg

-title: <span lang="zh-CN">语林灵</span> (Yulinling)

----

--- a/content/taxonomies/displaying.md

+++ /dev/null

@@ -1,137 +1,0 @@

----

-aliases:

-- /indexes/displaying/

-lastmod: 2016-06-29

-date: 2013-07-01

-linktitle: Displaying

-menu:

-  main:

-    parent: taxonomy

-next: /taxonomies/templates

-prev: /taxonomies/usage

-title: Displaying Taxonomies

-weight: 20

-toc: true

----

-There are four common ways you can display the data in your

-taxonomies in addition to the automatic taxonomy pages created by hugo

-using the [list templates](/templates/list/):

-1. For a given piece of content, you can list the terms attached

-2. For a given piece of content, you can list other content with the same

-   term

-3. You can list all terms for a taxonomy

-4. You can list all taxonomies (with their terms)

-## 1. Displaying taxonomy terms assigned to this content

-Within your content templates, you may wish to display

-the taxonomies that that piece of content is assigned to.

-Because we are leveraging the front matter system to

-define taxonomies for content, the taxonomies assigned to

-each content piece are located in the usual place

-(.Params.`plural`).

-### Example

-    <ul id="tags">

-      {{ range .Params.tags }}

-        <li><a href="{{ "/tags/" | relLangURL }}{{ . | urlize }}">{{ . }}</a> </li>

-      {{ end }}

-    </ul>

-If you want to list taxonomies inline, you will have to take

-care of optional plural ending in the title (if multiple taxonomies),

-as well as commas. Let's say we have a taxonomy "directors" such as

-`directors: [ "Joel Coen", "Ethan Coen" ]` in the TOML-format front matter.

-To list such taxonomy use the following:

-### Example

-    {{ if .Params.directors }}

-      <strong>Director{{ if gt (len .Params.directors) 1 }}s{{ end }}:</strong>

-      {{ range $index, $director := .Params.directors }}{{ if gt $index 0 }}, {{ end }}<a href="{{ "/directors/" | relURL }}{{ . | urlize }}">{{ . }}</a>{{ end }}

-    {{ end }}

-Alternatively, you may use the [delimit]({{< relref "templates/functions.md#delimit" >}})

-template function as a shortcut if the taxonomies should just be listed

-with a separator.  See {{< gh 2143 >}} on GitHub for discussion.

-## 2. Listing content with the same taxonomy term

-First, you may be asking why you would use this. If you are using a

-taxonomy for something like a series of posts, this is exactly how you

-would do it. It’s also an quick and dirty way to show some related

-content.

-### Example

-    <ul>

-      {{ range .Site.Taxonomies.series.golang }}

-        <li><a href="{{ .Page.RelPermalink }}">{{ .Page.Title }}</a></li>

-      {{ end }}

-    </ul>

-## 3. Listing all content in a given taxonomy

-This would be very useful in a sidebar as “featured content”. You could

-even have different sections of “featured content” by assigning

-different terms to the content.

-### Example

-    <section id="menu">

-        <ul>

-            {{ range $key, $taxonomy := .Site.Taxonomies.featured }}

-            <li> {{ $key }} </li>

-            <ul>

-                {{ range $taxonomy.Pages }}

-                <li hugo-nav="{{ .RelPermalink}}"><a href="{{ .Permalink}}"> {{ .LinkTitle }} </a> </li>

-                {{ end }}

-            </ul>

-            {{ end }}

-        </ul>

-    </section>

-## 4. Rendering a Site's Taxonomies

-If you wish to display the list of all keys for a taxonomy, you can find retrieve

-them from the `.Site` variable which is available on every page.

-This may take the form of a tag cloud, a menu or simply a list.

-The following example displays all tag keys:

-### Example

-    <ul id="all-tags">

-      {{ range $name, $taxonomy := .Site.Taxonomies.tags }}

-        <li><a href="{{ "/tags/" | relLangURL }}{{ $name | urlize }}">{{ $name }}</a></li>

-      {{ end }}

-    </ul>

-### Complete Example

-This example will list all taxonomies, each of their keys and all the content assigned to each key.

-    <section>

-      <ul>

-        {{ range $taxonomyname, $taxonomy := .Site.Taxonomies }}

-          <li><a href="{{ "/" | relLangURL}}{{ $taxonomyname | urlize }}">{{ $taxonomyname }}</a>

-            <ul>

-              {{ range $key, $value := $taxonomy }}

-              <li> {{ $key }} </li>

-                    <ul>

-                    {{ range $value.Pages }}

-                        <li hugo-nav="{{ .RelPermalink}}"><a href="{{ .Permalink}}"> {{ .LinkTitle }} </a> </li>

-                    {{ end }}

-                    </ul>

-              {{ end }}

-            </ul>

-          </li>

-        {{ end }}

-      </ul>

-    </section>

--- a/content/taxonomies/methods.md

+++ /dev/null

@@ -1,69 +1,0 @@

----

-lastmod: 2015-12-23

-date: 2014-05-26

-linktitle: Structure & Methods

-menu:

-  main:

-    parent: taxonomy

-next: /extras/aliases

-prev: /taxonomies/ordering

-title: Using Taxonomies

-weight: 75

----

-Hugo makes a set of values and methods available on the various Taxonomy structures.

-## Taxonomy Methods

-A Taxonomy is a `map[string]WeightedPages`.

-.Get(term)

-: Returns the WeightedPages for a term.

-.Count(term)

-: The number of pieces of content assigned to this term.

-.Alphabetical

-: Returns an OrderedTaxonomy (slice) ordered by Term.

-.ByCount

-: Returns an OrderedTaxonomy (slice) ordered by number of entries.

-## OrderedTaxonomy

-Since Maps are unordered, an OrderedTaxonomy is a special structure that has a defined order.

-```go

-[]struct {

-	Name          string

-	WeightedPages WeightedPages

-}

-```

-Each element of the slice has:

-.Term

-: The Term used.

-.WeightedPages

-: A slice of Weighted Pages.

-.Count

-: The number of pieces of content assigned to this term.

-.Pages

-: All Pages assigned to this term. All [list methods](/templates/list/) are available to this.

-## WeightedPages

-WeightedPages is simply a slice of WeightedPage.

-```go

-type WeightedPages []WeightedPage

-```

-.Count(term)

-: The number of pieces of content assigned to this term.

-.Pages

-: Returns a slice of pages, which then can be ordered using any of the [list methods](/templates/list/).

--- a/content/taxonomies/ordering.md

+++ /dev/null

@@ -1,80 +1,0 @@

----

-aliases:

-- /indexes/ordering/

-lastmod: 2015-12-23

-date: 2013-07-01

-linktitle: Ordering

-menu:

-  main:

-    identifier: Ordering Taxonomies

-    parent: taxonomy

-next: /taxonomies/methods

-prev: /taxonomies/templates

-title: Ordering Taxonomies

-weight: 60

-toc: true

----

-Hugo provides the ability to both:

- 1. Order the way the keys for a taxonomy are displayed

- 2. Order the way taxonomyed content appears

-## Ordering Taxonomies

-Taxonomies can be ordered by either alphabetical key or by the number of content pieces assigned to that key.

-### Order Alphabetically Example

-    <ul>

-    {{ $data := .Data }}

-    {{ range $key, $value := .Data.Taxonomy.Alphabetical }}

-    <li><a href="{{ .Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $value.Name | urlize }}"> {{ $value.Name }} </a> {{ $value.Count }} </li>

-    {{ end }}

-    </ul>

-### Order by Popularity Example

-    <ul>

-    {{ $data := .Data }}

-    {{ range $key, $value := .Data.Taxonomy.ByCount }}

-    <li><a href="{{ .Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $value.Name | urlize }}"> {{ $value.Name }} </a> {{ $value.Count }} </li>

-    {{ end }}

-    </ul>

-[See Also Taxonomy Lists]({{< relref "templates/list.md" >}})

-## Ordering Content within Taxonomies

-Hugo uses both **Date** and **Weight** to order content within taxonomies.

-Each piece of content in Hugo can optionally be assigned a date.

-It can also be assigned a weight for each taxonomy it is assigned to.

-When iterating over content within taxonomies the default sort is first by weight then by date. This means that if the weights for two pieces of content are the same, than the more recent content will be displayed first. The default weight for any piece of content is 0.

-### Assigning Weight

-Content can be assigned weight for each taxonomy that it's assigned to.

-```toml

-+++

-tags = [ "a", "b", "c" ]

-tags_weight = 22

-categories = ["d"]

-title = "foo"

-categories_weight = 44

-+++

-Front Matter with weighted tags and categories

-```

-The convention is `taxonomyname_weight`.

-In the above example, this piece of content has a weight of 22 which applies to the sorting when rendering the pages assigned to the "a", "b" and "c" values of the 'tag' taxonomy.

-It has also been assigned the weight of 44 when rendering the 'd' category.

-With this the same piece of content can appear in different positions in different taxonomies.

-Currently taxonomies only support the default ordering of content which is weight -> date.

--- a/content/taxonomies/overview.md

+++ /dev/null

@@ -1,95 +1,0 @@

----

-aliases:

-- /indexes/overview/

-- /doc/indexes/

-- /extras/indexes

-lastmod: 2015-08-04

-date: 2013-07-01

-linktitle: Overview

-menu:

-  main:

-    identifier: taxonomy overview

-    parent: taxonomy

-next: /taxonomies/usage

-prev: /templates/404

-title: Taxonomy Overview

-weight: 10

----

-Hugo includes support for user-defined groupings of content called

-taxonomies.[^1] Taxonomies give us a way to classify our content so we can

-demonstrate relationships in a variety of logical ways.

-[^1]: Taxonomies were called *indexes* in Hugo prior to v0.11.

-The default taxonomies for Hugo are *tags* and *categories*. These

-taxonomies are common to many website systems (e.g. WordPress, Drupal,

-Jekyll). Unlike all of those systems, Hugo makes it trivial to customize

-the taxonomies you will be using for your site however you wish. Another

-good use for taxonomies is to group a set of posts into a series. Other

-common uses would include *categories*, *tags*, *groups*, *series* and many

-more.

-When taxonomies are used (and templates are provided), Hugo will

-automatically create pages listing all of the taxonomies, their terms

-and all of the content attached to those terms.

-## Definitions

-**Taxonomy:** A categorization that can be used to classify content

-**Term:** A key within that taxonomy

-**Value:** A piece of content assigned to that Term

-## Example

-For example, if I was writing about movies, I may want the following

-taxonomies:

-* Actors

-* Directors

-* Studios

-* Genre

-* Year

-* Awards

-I would then specify in each movie’s front-matter the specific terms for

-each of those taxonomies. Hugo would then automatically create pages for

-each Actor, Director, Studio, Genre, Year and Award listing all of the

-Movies that matched that specific Actor, Director, etc.

-### Taxonomy Organization

-Let’s use an example to demonstrate the different labels in action.

-From the perspective of the taxonomy, it could be visualized as:

-    Actor                    <- Taxonomy

-        Bruce Willis         <- Term

-            The Six Sense    <- Content

-            Unbreakable      <- Content

-            Moonrise Kingdom <- Content

-        Samuel L. Jackson    <- Term

-            Unbreakable      <- Content

-            The Avengers     <- Content

-            xXx              <- Content

-From the perspective of the content, it would appear differently, though

-the data and labels used are the same:

-    Unbreakable                 <- Content

-        Actors                  <- Taxonomy

-            Bruce Willis        <- Term

-            Samuel L. Jackson   <- Term

-        Director                <- Taxonomy

-            M. Night Shyamalan  <- Term

-        ...

-    Moonrise Kingdom            <- Content

-        Actors                  <- Taxonomy

-            Bruce Willis        <- Term

-            Bill Murray         <- Term

-        Director                <- Taxonomy

-            Wes Anderson        <- Term

-        ...

--- a/content/taxonomies/templates.md

+++ /dev/null

@@ -1,40 +1,0 @@

----

-aliases:

-- /indexes/templates/

-lastmod: 2014-05-29

-date: 2013-07-01

-linktitle: Templates

-menu:

-  main:

-    parent: taxonomy

-next: /taxonomies/ordering

-prev: /templates/displaying

-title: Taxonomy Templates

-weight: 30

----

-Taxonomy templates should be placed in the folder `layouts/taxonomy`.

-When Taxonomy term template is provided for a Taxonomy, a section is rendered for it at `/SINGULAR/`. (eg. `/tag/` or `/category/`)

-There are two different templates that the use of taxonomies will require you to provide:

-### All content attached to taxonomy

-A [taxonomy terms template](/templates/terms/) is a template which has access to all the full Taxonomy structure.

-This Template is commonly used to generate the list of terms for a given template.

-#### layouts/taxonomy/SINGULAR.terms.html

-For example: `tag.terms.html`, `category.terms.html`, or your custom Taxonomy: `actor.terms.html`

-### All content attached to term

-A [list template](/templates/list/) is used to automatically generate pages for each unique term found.

-#### layouts/taxonomy/SINGULAR.html

-For example: `tag.html`, `category.html`, or your custom Taxonomy: `actor.html`

-Terms are rendered at `SINGULAR/TERM/`. (eg. `/tag/book/` or `/category/news/`)

--- a/content/taxonomies/usage.md

+++ /dev/null

@@ -1,109 +1,0 @@

----

-lastmod: 2015-12-23

-date: 2014-05-26

-linktitle: Usage

-toc: true

-menu:

-  main:

-    parent: taxonomy

-next: /taxonomies/displaying

-prev: /taxonomies/overview

-title: Using Taxonomies

-weight: 15

----

-## Defining taxonomies for a site

-Taxonomies must be defined in the site configuration before they can be

-used throughout the site. You need to provide both the plural and

-singular labels for each taxonomy.

-Here is an example configuration in TOML and YAML

-that specifies three taxonomies (the default two, plus `series`).

-Notice the format is <code><strong>singular key</strong> = &quot;<em>plural value</em>&quot;</code> for TOML,

-or <code><strong>singular key</strong>: &quot;<em>plural value</em>&quot;</code> for YAML:

-<table class="table">

-<thead>

-<tr>

-<th>config.toml excerpt:</th><th>config.yaml excerpt:</th>

-</tr>

-</thead>

-<tbody>

-<tr valign="top">

-<td><pre><code class="language-toml">[taxonomies]

-tag = "tags"

-category = "categories"

-series = "series"

-</code></pre></td>

-<td><pre><code class="language-yaml">taxonomies:

-  tag: "tags"

-  category: "categories"

-  series: "series"

-</code></pre></td>

-</tr>

-</tbody>

-</table>

-## Assigning taxonomy values to content

-Once an taxonomy is defined at the site level, any piece of content

-can be assigned to it regardless of content type or section.

-Assigning content to an taxonomy is done in the front matter.

-Simply create a variable with the *plural* name of the taxonomy

-and assign all terms you want to apply to this content.

-## Preserving taxonomy values

-By default, taxonomy names are hyphenated, lower-cased and normalized, and then

-fixed and titleized on the archive page.

-However, if you want to have a taxonomy value with special characters

-such as `Gérard Depardieu` instead of `Gerard Depardieu`,

-you need to set the `preserveTaxonomyNames` [site configuration](/overview/configuration/) variable to `true`.

-Hugo will then preserve special characters in taxonomy values

-but will still titleize the values for titles and normalize them in URLs.

-Note that if you use `preserveTaxonomyNames` and intend to manually construct URLs to the archive pages,

-you will need to pass the taxonomy values through the `urlize` template function.

-## Front Matter Example (in TOML)

-```toml

-+++

-title = "Hugo: A fast and flexible static site generator"

-tags = [ "Development", "Go", "fast", "Blogging" ]

-categories = [ "Development" ]

-series = [ "Go Web Dev" ]

-slug = "hugo"

-project_url = "https://github.com/gohugoio/hugo"

-+++

-```

-## Front Matter Example (in JSON)

-```json

-{

-    "title": "Hugo: A fast and flexible static site generator",

-    "tags": [

-        "Development",

-        "Go",

-        "fast",

-        "Blogging"

-    ],

-    "categories" : [

-        "Development"

-    ],

-    "series" : [

-        "Go Web Dev"

-    ],

-    "slug": "hugo",

-    "project_url": "https://github.com/gohugoio/hugo"

-}

-```

-## Add content file with frontmatter

-See [Source Organization]({{< relref "overview/source-directory.md#content-for-home-page-and-other-list-pages" >}}).

--- a/content/templates/404.md

+++ b/content/templates/404.md

@@ -1,55 +1,57 @@

---

-aliases:

-- /layout/404/

-lastmod: 2015-12-30

-date: 2013-08-21

-linktitle: "Custom 404 page"

+title: Custom 404 Page

+linktitle: 404 Page

+description: If you know how to create a single page template, you have unlimited options for creating a custom 404.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-31

+categories: [templates]

+#tags: [404, page not found]

 menu:

-  main:

-    parent: layout

-next: /taxonomies/overview

-notoc: true

-next: /templates/debugging

-prev: /templates/sitemap

-title: 404.html Templates

-weight: 100

+  docs:

+    parent: "templates"

+    weight: 120

+weight: 120	#rem

+draft: false

+aliases: [/templates/404/]

+toc: false

---

-When using Hugo with [GitHub Pages](http://pages.github.com/), you can provide

-your own template for a [custom 404 error page](https://help.github.com/articles/custom-404-pages/)

-by creating a 404.html template file in your `/layouts` folder.

-When Hugo generates your site, the `404.html` file will be placed in the root.

+When using Hugo with [GitHub Pages](http://pages.github.com/), you can provide your own template for a [custom 404 error page](https://help.github.com/articles/custom-404-pages/) by creating a 404.html template file in your `/layouts` folder. When Hugo generates your site, the `404.html` file will be placed in the root.

-404 pages will have all the regular [page

-variables](/layout/variables/) available to use in the templates.

+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 `.Data.Pages`.

-    ▾ layouts/

-        404.html

+```bash

+▾ layouts/

+    404.html

+```

 ## 404.html

 This is a basic example of a 404.html template:

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    <section id="main">

+{{% code file="layouts/404.html" download="404.html" %}}

+```html

+{{ define "main"}}

+    <main id="main">

       <div>

-       <h1 id="title">{{ .Title }}</h1>

+       <h1 id="title"><a href="{{ "/" | relURL }}">Go Home</a></h1>

       </div>

-    </section>

+    </main>

+{{ end }}

+```

+{{% /code %}}

-    {{ partial "footer.html" . }}

+## Automatic Loading

-### Automatic Loading

 Your 404.html file can be set to load automatically when a visitor enters a mistaken URL path, dependent upon the web serving environment you are using. For example:

-* _GitHub Pages_ - it's automatic.

-* _Apache_ - one way is to specify `ErrorDocument 404 /404.html` in an `.htaccess` file in the root of your site.

-* _Nginx_ - you might specify `error_page   404  =  /404.html;` in your `nginx.conf` file.

-* _Amazon AWS S3_ - when setting a bucket up for static web serving, you can specify the error file.

-* _Caddy Server_ - using `errors { 404 /404.html }`. [Details here](https://caddyserver.com/docs/errors)

+* [GitHub Pages](/hosting-and-deployment/hosting-on-github/). The 404 page is automatic.

+* Apache. You can specify `ErrorDocument 404 /404.html` in an `.htaccess` file in the root of your site.

+* Nginx. You might specify `error_page 404 /404.html;` in your `nginx.conf` file.

+* Amazon AWS S3. When setting a bucket up for static web serving, you can specify the error file from within the S3 GUI.

+* Caddy Server. Using `errors { 404 /404.html }`. [Details here](https://caddyserver.com/docs/errors)

+[pagevars]: /variables/page/

\ No newline at end of file

--- /dev/null

+++ b/content/templates/_index.md

@@ -1,0 +1,19 @@

+---

+title: Templates

+linktitle: Templates Overview

+description: Go templating, template types and lookup order, shortcodes, and data.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+menu:

+  docs:

+    parent: "templates"

+    weight: 01

+weight: 01	#rem

+categories: [templates]

+#tags: []

+draft: false

+aliases: [/templates/overview/,/templates/content]

+toc: false

+notesforauthors:

+---

--- a/content/templates/ace.md

+++ /dev/null

@@ -1,58 +1,0 @@

----

-aliases:

-- /doc/templates/ace

-- /layout/templates/ace

-- /layout/ace/

-lastmod: 2015-08-04

-date: 2014-04-20

-linktitle: Ace templates

-menu:

-  main:

-    parent: layout

-next: /templates/functions

-prev: /templates/go-templates

-title: Ace Templates

-weight: 17

----

-In addition to [Go templates](/templates/go-templates) and [Amber](/templates/amber) templates, Hugo supports the powerful Ace templates.

-For template documentation, follow the links from the [Ace project](https://github.com/yosssi/ace).

-* Ace templates must be named with the ace-suffix, e.g. `list.ace`

-* It's possible to use both Go templates and Ace templates side-by-side, and include one into the other

-* Full Go template syntax support, including all the useful helper funcs

-* Partials can be included both with the Ace and the Go template syntax:

-	* `= include partials/foo.html .`[^ace-theme]

-	* `{{ partial "foo" . }}`

-One noticeable difference between Ace and the others is the inheritance support through [base and inner templates](https://github.com/yosssi/ace/tree/master/examples/base_inner_template).

-In Hugo the base template will be chosen with the same ruleset as for [Go templates](/templates/blocks/).

-.:

-index.ace

-./blog:

-single.ace

-baseof.ace

-./_default:

-baseof.ace  list.ace  single.ace  single-baseof.ace

-```

-Some examples for the layout files above:

-* Home page: `./index.ace` +  `./_default/baseof.ace`

-* Single page in the `blog` section: `./blog/single.ace` +  `./blog/baseof.ace`

-* Single page in another section: `./_default/single.ace` +  `./_default/single-baseof.ace`

-* Taxonomy page in any section: `./_default/list.ace` +  `./_default/baseof.ace`

-**Note:** In most cases one `baseof.ace` in `_default` will suffice.

-**Note:** An Ace template without a reference to a base section, e.g. `= content`, will be handled as a standalone template.

-[^ace-theme]: Note that the `html` suffix is needed, even if the filename is suffixed `ace`. This does not work from inside a theme, see [issue 763](https://github.com/gohugoio/hugo/issues/763).

--- /dev/null

+++ b/content/templates/alternatives.md

@@ -1,0 +1,77 @@

+---

+title: Alternative Templating Languages

+linktitle: Alternative Templating

+description: In addition to Go templates, Hugo supports the powerful Ace templating from @yosssi and Amber templating from @eknkc.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-20

+categories: [templates]

+#tags: [amber,ace,templating languages]

+menu:

+  docs:

+    parent: "templates"

+    weight: 170

+weight: 170

+sections_weight: 170

+draft: false

+aliases: [/templates/ace/,/templates/amber/]

+toc: true

+---

+## Ace Templates

+For template documentation, follow the links from the [Ace project](https://github.com/yosssi/ace).

+* Ace templates must be named with the ace-suffix; e.g., `list.ace`

+* It's possible to use both Go templates and Ace templates side by side and even include one into the other

+* Full Go template syntax support, including all the useful helper [template functions][]

+* Partials can be included both with the Ace and the Go template syntax. For example, the following two will have the same output in Ace:

+    * `= include partials/foo.html .`

+    * `{{ partial "foo" . }}`

+One noticeable difference between Ace and the other templating engines in Hugo is [Ace's inheritance support through base and inner templates][aceinheritance].

+In Hugo, the Ace base template will be chosen with the same rule set as for [Go base templates][].

+```bash

+.:

+index.ace

+./blog:

+single.ace

+baseof.ace

+./_default:

+baseof.ace  list.ace  single.ace  single-baseof.ace

+```

+{{% note %}}

+Note that the `html` suffix is needed even if the filename is suffixed `ace`. This does not work from inside a theme ([issue #763](https://github.com/gohugoio/hugo/issues/763)).

+{{% /note %}}

+Some examples for the layout files above:

+* Home page: `./index.ace` +  `./_default/baseof.ace`

+* Single page in the `blog` section: `./blog/single.ace` +  `./blog/baseof.ace`

+* Single page in another section: `./_default/single.ace` +  `./_default/single-baseof.ace`

+* Taxonomy page in any section: `./_default/list.ace` +  `./_default/baseof.ace`

+{{% note %}}

+In most cases, one `baseof.ace` in `_default` will suffice. An Ace template without a reference to a base section (e.g., `= content`) will be handled as a standalone template.

+{{% /note %}}

+## Amber Templates

+For Amber template documentation, follow the links from the [Amber project][].

+* Amber templates must be named with the Amber suffix; e.g., `list.amber`

+* Partials in Amber or HTML can be included with the Amber template syntax:

+    * `import ../partials/test.html `

+    * `import ../partials/test_a.amber `

+[aceinheritance]: https://github.com/yosssi/ace/tree/master/examples/base_inner_template

+[Amber Project]: https://github.com/eknkc/amber

+[template functions]: /functions/

+[Go templates]: /templates/introduction/

+[Go base templates]: /templates/base/

\ No newline at end of file

--- a/content/templates/amber.md

+++ /dev/null

@@ -1,27 +1,0 @@

----

-aliases:

-- /doc/templates/amber

-- /layout/templates/amber

-- /layout/amber/

-lastmod: 2015-11-05

-date: 2015-07-20

-linktitle: Amber templates

-menu:

-  main:

-    parent: layout

-next: /templates/functions

-prev: /templates/go-templates

-title: Amber Templates

-weight: 18

----

-Amber templates are another template type which Hugo supports, in addition to [Go templates](/templates/go-templates) and [Ace templates]({{< relref "templates/ace.md" >}}) templates.

-For template documentation, follow the links from the [Amber project](https://github.com/eknkc/amber)

-* Amber templates must be named with the amber-suffix, e.g. `list.amber`

-* Partials in Amber or HTML can be included with the Amber template syntax:

-	* `import ../partials/test.html `

-	* `import ../partials/test_a.amber `

--- /dev/null

+++ b/content/templates/base.md

@@ -1,0 +1,136 @@

+---

+title: Base Templates and Blocks

+linktitle:

+description: The base and block constructs allow you to define the outer shell of your master templates (i.e., the chrome of the page).

+godocref: https://golang.org/pkg/text/template/#example_Template_block

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates,fundamentals]

+#tags: [blocks,base]

+menu:

+  docs:

+    parent: "templates"

+    weight: 20

+weight: 20

+sections_weight: 20

+draft: false

+aliases: [/templates/blocks/,/templates/base-templates-and-blocks/]

+toc: true

+---

+The `block` keyword allows you to define the outer shell of your pages' one or more master template(s) and then fill in or override portions as necessary.

+## Base Template Lookup Order

+The [lookup order][lookup] for base templates is as follows:

+1. `/layouts/section/<TYPE>-baseof.html`

+2. `/themes/<THEME>/layouts/section/<TYPE>-baseof.html`

+3. `/layouts/<TYPE>/baseof.html`

+4. `/themes/<THEME>/layouts/<TYPE>/baseof.html`

+5. `/layouts/section/baseof.html`

+6. `/themes/<THEME>/layouts/section/baseof.html`

+7. `/layouts/_default/post-baseof.html`

+8. `/themes/<THEME>/layouts/_default/post-baseof.html`

+9. `/layouts/_default/baseof.html`

+10. `/themes/<THEME>/layouts/_default/baseof.html`

+Variables are denoted by capitalized text set within `<>`. Note that Hugo's default behavior is for `type` to inherit from `section` unless otherwise specified.

+### Example Base Template Lookup Order

+As an example, let's assume your site is using a theme called "mytheme" when rendering the section list for a `post` section. Hugo picks `layout/section/post.html` as the template for [rendering the section][]. The `{{define}}` block in this template tells Hugo that the template is an extension of a base template.

+Here is the lookup order for the `post` base template:

+1. `/layouts/section/post-baseof.html`

+2. `/themes/mytheme/layouts/section/post-baseof.html`

+3. `/layouts/post/baseof.html`

+4. `/themes/mytheme/layouts/post/baseof.html`

+5. `/layouts/section/baseof.html`

+6. `/themes/mytheme/layouts/section/baseof.html`

+7. `/layouts/_default/post-baseof.html`

+8. `/themes/mytheme/layouts/_default/post-baseof.html`

+9. `/layouts/_default/baseof.html`

+10. `/themes/mytheme/layouts/_default/baseof.html`

+## Define the Base Template

+The following defines a simple base template at `_default/baseof.html`. As a default template, it is the shell from which all your pages will be rendered unless you specify another `*baseof.html` closer to the beginning of the lookup order.

+{{% code file="layouts/_default/baseof.html" download="baseof.html" %}}

+```html

+<!DOCTYPE html>

+<html>

+  <head>

+    <meta charset="utf-8">

+    <title>{{ block "title" . }}

+      <!-- Blocks may include default content. -->

+      {{ .Site.Title }}

+    {{ end }}</title>

+  </head>

+  <body>

+    <!-- Code that all your templates share, like a header -->

+    {{ block "main" . }}

+      <!-- The part of the page that begins to differ between templates -->

+    {{ end }}

+    {{ block "footer" . }}

+    <!-- More shared code, perhaps a footer but that can be overridden if need be in  -->

+    {{ end }}

+  </body>

+</html>

+```

+{{% /code %}}

+## Override the Base Template

+From the above base template, you can define a [default list template][hugolists]. The default list template will inherit all of the code defined above and can then implement its own `"main"` block from:

+{{% code file="layouts/_default/list.html" download="list.html" %}}

+```html

+{{ define "main" }}

+  <h1>Posts</h1>

+  {{ range .Data.Pages }}

+    <article>

+      <h2>{{ .Title }}</h2>

+      {{ .Content }}

+    </article>

+  {{ end }}

+{{ end }}

+```

+{{% /code %}}

+This replaces the contents of our (basically empty) "main" block with something useful for the list template. In this case, we didn't define a `"title"` block, so the contents from our base template remain unchanged in lists.

+{{% warning %}}

+Code that you put outside the block definitions *can* break your layout. This even includes HTML comments. For example:

+```html

+<!-- Seemingly harmless HTML comment..that will break your layout at build -->

+{{ define "main" }}

+...your code here

+{{ end }}

+```

+[See this thread from the Hugo discussion forums.](https://discourse.gohugo.io/t/baseof-html-block-templates-and-list-types-results-in-empty-pages/5612/6)

+{{% /warning %}}

+The following shows how you can override both the `"main"` and `"title"` block areas from the base template with code unique to your [default single page template][singletemplate]:

+{{% code file="layouts/_default/single.html" download="single.html" %}}

+```html

+{{ define "title" }}

+  <!-- This will override the default value set in baseof.html; i.e., "{{.Site.Title}}" in the original example-->

+  {{ .Title }} &ndash; {{ .Site.Title }}

+{{ end }}

+{{ define "main" }}

+  <h1>{{ .Title }}</h1>

+  {{ .Content }}

+{{ end }}

+```

+{{% /code %}}

+[hugolists]: /templates/lists

+[lookup]: /templates/lookup-order/

+[rendering the section]: /templates/section-templates/

+[singletemplate]: /templates/single-page-templates/

--- a/content/templates/blocks.md

+++ /dev/null

@@ -1,110 +1,0 @@

----

-date: 2016-03-29T21:26:20-05:00

-menu:

-  main:

-    parent: layout

-prev: /templates/views/

-next: /templates/partials/

-title: Block Templates

-weight: 80

----

-The `block` keyword in Go templates allows you to define the outer shell of your pages one or more master template(s), filling in or overriding portions as necessary.

-## Base template lookup

-In version `0.20` Hugo introduced custom [Output Formats]({{< relref "extras/output-formats.md" >}}), all of which can have their own templates that also can use a base template if needed.

-This introduced two new terms relevant in the lookup of the templates, the media type's `Suffix` and the output format's `Name`.

-Given the above, Hugo tries to use the most specific base tamplate it finds:

-1. /layouts/_current-path_/_template-name_-baseof.[output-format].[suffix], e.g. list-baseof.amp.html.

-1. /layouts/_current-path_/_template-name_-baseof.[suffix], e.g. list-baseof.html.

-2. /layouts/_current-path_/baseof.[output-format].[suffix], e.g baseof.amp.html

-2. /layouts/_current-path_/baseof.[suffix], e.g baseof.html

-3. /layouts/_default/_template-name_-baseof.[output-format].[suffix] e.g. list-baseof.amp.html.

-3. /layouts/_default/_template-name_-baseof.[suffix], e.g. list-baseof.html.

-4. /layouts/_default/baseof.[output-format].[suffix]

-4. /layouts/_default/baseof.[suffix]

-For each of the steps above, it will first look in the project, then, if theme is set, in the theme's layouts folder. Hugo picks the first base template found.

-As an example, with a site using the theme `exampletheme`, when rendering the section list for the section `post` for the output format `Calendar`. Hugo picks the `section/post.calendar.ics` as the template and this template has a `define` section that indicates it needs a base template. This is then the lookup order:

-1. `/layouts/section/post-baseof.calendar.ics`

-1. `/layouts/section/post-baseof.ics`

-2.  `/themes/exampletheme/layouts/section/post-baseof.calendar.ics`

-2.  `/themes/exampletheme/layouts/section/post-baseof.ics`

-3.  `/layouts/section/baseof.calendar.ics`

-3.  `/layouts/section/baseof.ics`

-4. `/themes/exampletheme/layouts/section/baseof.calendar.ics`

-4. `/themes/exampletheme/layouts/section/baseof.ics`

-5.  `/layouts/_default/post-baseof.calendar.ics`

-5.  `/layouts/_default/post-baseof.ics`

-6.  `/themes/exampletheme/layouts/_default/post-baseof.calendar.ics`

-6.  `/themes/exampletheme/layouts/_default/post-baseof.ics`

-7.   `/layouts/_default/baseof.calendar.ics`

-7.   `/layouts/_default/baseof.ics`

-8. `/themes/exampletheme/layouts/_default/baseof.calendar.ics`

-8. `/themes/exampletheme/layouts/_default/baseof.ics`

-## Define the base template

-Let's define a simple base template (`_default/baseof.html`), a shell from which all our pages will start.

-```html

-<!DOCTYPE html>

-<html>

-  <head>

-    <meta charset="utf-8">

-    <title>{{ block "title" . }}

-      <!-- Blocks may include default content. -->

-      {{ .Site.Title }}

-    {{ end }}</title>

-  </head>

-  <body>

-    <!-- Code that all your templates share, like a header -->

-    {{ block "main" . }}

-      <!-- The part of the page that begins to differ between templates -->

-    {{ end }}

-    <!-- More shared code, perhaps a footer -->

-  </body>

-</html>

-```

-## Overriding the base

-Your [default list template]({{< relref "templates/list.md" >}}) (`_default/list.html`) will inherit all of the code defined in the base template. It could then implement its own "main" block from the base template above like so:

-```html

-<!-- Note the lack of Go's context "dot" when defining blocks -->

-{{ define "main" }}

-  <h1>Posts</h1>

-  {{ range .Data.Pages }}

-    <article>

-      <h2>{{ .Title }}</h2>

-      {{ .Content }}

-    </article>

-  {{ end }}

-{{ end }}

-```

-This replaces the contents of our (basically empty) "main" block with something useful for the list template. In this case, we didn't define a "title" block so the contents from our base template remain unchanged in lists.

-In our [default single template]({{< relref "templates/content.md" >}}) (`_default/single.html`), let's implement both blocks:

-```html

-{{ define "title" }}

-  {{ .Title }} &ndash; {{ .Site.Title }}

-{{ end }}

-{{ define "main" }}

-  <h1>{{ .Title }}</h1>

-  {{ .Content }}

-{{ end }}

-```

-This overrides both block areas from the base template with code unique to our single template.

--- a/content/templates/content.md

+++ /dev/null

@@ -1,167 +1,0 @@

----

-aliases:

-- /layout/content/

-lastmod: 2015-05-22

-date: 2013-07-01

-linktitle: Single Content

-menu:

-  main:

-    parent: layout

-next: /templates/list

-prev: /templates/variables

-title: Single Content Template

-weight: 30

-toc: true

----

-The primary view of content in Hugo is the single view. Hugo, for every

-Markdown file provided, will render it with a single template.

-## Which Template will be rendered?

-Hugo uses a set of rules to figure out which template to use when

-rendering a specific page.

-Hugo will use the following prioritized list. If a file isn’t present,

-then the next one in the list will be used. This enables you to craft

-specific layouts when you want to without creating more templates

-than necessary. For most sites, only the `_default` file at the end of

-the list will be needed.

-Users can specify the `type` and `layout` in the [front-matter](/content/front-matter/). `Section`

-is determined based on the content file’s location. If `type` is provided,

-it will be used instead of `section`.

-### Single Page

-* /layouts/`TYPE`/`LAYOUT`.html

-* /layouts/`SECTION`/`LAYOUT`.html

-* /layouts/`TYPE`/single.html

-* /layouts/`SECTION`/single.html

-* /layouts/_default/single.html

-* /themes/`THEME`/layouts/`TYPE`/`LAYOUT`.html

-* /themes/`THEME`/layouts/`SECTION`/`LAYOUT`.html

-* /themes/`THEME`/layouts/`TYPE`/single.html

-* /themes/`THEME`/layouts/`SECTION`/single.html

-* /themes/`THEME`/layouts/_default/single.html

-## Example Single Template File

-Content pages are of the type "page" and have all the [page

-variables](/layout/variables/) and [site

-variables](/templates/variables/) available to use in the templates.

-In the following examples we have created two different content types as well as

-a default content type.

-The default content template to be used in the event that a specific

-template has not been provided for that type. The default type works the

-same as the other types, but the directory must be called "\_default".

-    ▾ layouts/

-      ▾ _default/

-          single.html

-      ▾ post/

-          single.html

-      ▾ project/

-          single.html

-### post/single.html

-This content template is used for [spf13.com](http://spf13.com/).

-It makes use of [partial templates](/templates/partials/)

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    {{ $baseURL := .Site.BaseURL }}

-    <section id="main">

-      <h1 id="title">{{ .Title }}</h1>

-      <div>

-            <article id="content">

-               {{ .Content }}

-            </article>

-      </div>

-    </section>

-    <aside id="meta">

-        <div>

-        <section>

-          <h4 id="date"> {{ .Date.Format "Mon Jan 2, 2006" }} </h4>

-          <h5 id="wc"> {{ .FuzzyWordCount }} Words </h5>

-        </section>

-        <ul id="categories">

-          {{ range .Params.topics }}

-            <li><a href="{{ $baseURL }}/topics/{{ . | urlize }}">{{ . }}</a> </li>

-          {{ end }}

-        </ul>

-        <ul id="tags">

-          {{ range .Params.tags }}

-            <li> <a href="{{ $baseURL }}/tags/{{ . | urlize }}">{{ . }}</a> </li>

-          {{ end }}

-        </ul>

-        </div>

-        <div>

-            {{ if .Prev }}

-              <a class="previous" href="{{.Prev.Permalink}}"> {{.Prev.Title}}</a>

-            {{ end }}

-            {{ if .Next }}

-              <a class="next" href="{{.Next.Permalink}}"> {{.Next.Title}}</a>

-            {{ end }}

-        </div>

-    </aside>

-    {{ partial "disqus.html" . }}

-    {{ partial "footer.html" . }}

-### project/single.html

-This content template is used for [spf13.com](http://spf13.com/).

-It makes use of [partial templates](/templates/partials/)

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    {{ $baseURL := .Site.BaseURL }}

-    <section id="main">

-      <h1 id="title">{{ .Title }}</h1>

-      <div>

-            <article id="content">

-               {{ .Content }}

-            </article>

-      </div>

-    </section>

-    <aside id="meta">

-        <div>

-        <section>

-          <h4 id="date"> {{ .Date.Format "Mon Jan 2, 2006" }} </h4>

-          <h5 id="wc"> {{ .FuzzyWordCount }} Words </h5>

-        </section>

-        <ul id="categories">

-          {{ range .Params.topics }}

-          <li><a href="{{ $baseURL }}/topics/{{ . | urlize }}">{{ . }}</a> </li>

-          {{ end }}

-        </ul>

-        <ul id="tags">

-          {{ range .Params.tags }}

-            <li> <a href="{{ $baseURL }}/tags/{{ . | urlize }}">{{ . }}</a> </li>

-          {{ end }}

-        </ul>

-        </div>

-    </aside>

-    {{if isset .Params "project_url" }}

-    <div id="ribbon">

-        <a href="{{ index .Params "project_url" }}" rel="me">Fork me on GitHub</a>

-    </div>

-    {{ end }}

-    {{ partial "footer.html" . }}

-Notice how the project/single.html template uses an additional parameter unique

-to this template. This doesn't need to be defined ahead of time. If the key is

-present in the front matter than it can be used in the template. To

-easily generate new content of this type with these keys ready use

-[content archetypes](/content/archetypes/).

--- /dev/null

+++ b/content/templates/data-templates.md

@@ -1,0 +1,255 @@

+---

+title: Data Templates

+linktitle:

+description: In addition to Hugo's built-in variables, you can specify your own custom data in templates or shortcodes that pull from both local and dynamic sources.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-03-12

+categories: [templates]

+#tags: [data,dynamic,csv,json,toml,yaml]

+menu:

+  docs:

+    parent: "templates"

+    weight: 80

+weight: 80

+sections_weight: 80

+draft: false

+aliases: [/extras/datafiles/,/extras/datadrivencontent/,/doc/datafiles/]

+toc: true

+---

+<!-- begin data files -->

+Hugo supports loading data from YAML, JSON, and TOML files located in the `data` directory in the root of your Hugo project.

+## The Data Folder

+The `data` folder is where you can store additional data for Hugo to use when generating your site. Data files aren't used to generate standalone pages; rather, they're meant to be supplemental to content files. This feature can extend the content in case your front matter fields grow out of control. Or perhaps you want to show a larger dataset in a template (see example below). In both cases, it's a good idea to outsource the data in their own files.

+These files must be YAML, JSON, or TOML files (using the `.yml`, `.yaml`, `.json`, or `toml` extension). The data will be accessible as a `map` in the `.Site.Data` variable.

+## Data Files in Themes

+Data Files can also be used in [Hugo themes][themes] but note that theme data files follow the same logic as other template files in the [Hugo lookup order][lookup] (i.e., given two files with the same name and relative path, the file in the root project `data` directory will override the file in the `themes/<THEME>/data` directory).

+Therefore, theme authors should take care to not include data files that could be easily overwritten by a user who decides to [customize a theme][customize]. For theme-specific data items that shouldn't be overridden, it can be wise to prefix the folder structure with a namespace; e.g. `mytheme/data/<THEME>/somekey/...`. To check if any such duplicate exists, run hugo with the `-v` flag.

+The keys in the map created with data templates from data files will be a dot-chained set of `path`, `filename`, and `key` in file (if applicable).

+This is best explained with an example:

+## Example: Jaco Pastorius' Solo Discography

+[Jaco Pastorius](http://en.wikipedia.org/wiki/Jaco_Pastorius_discography) was a great bass player, but his solo discography is short enough to use as an example. [John Patitucci](http://en.wikipedia.org/wiki/John_Patitucci) is another bass giant.

+The example below is a bit contrived, but it illustrates the flexibility of data Files. This example uses TOML as its file format with the two following data files:

+* `data/jazz/bass/jacopastorius.toml`

+* `data/jazz/bass/johnpatitucci.toml`

+`jacopastorius.toml` contains the content below. `johnpatitucci.toml` contains a similar list:

+```

+discography = [

+"1974 – Modern American Music … Period! The Criteria Sessions",

+"1974 – Jaco",

+"1976 - Jaco Pastorius",

+"1981 - Word of Mouth",

+"1981 - The Birthday Concert (released in 1995)",

+"1982 - Twins I & II (released in 1999)",

+"1983 - Invitation",

+"1986 - Broadway Blues (released in 1998)",

+"1986 - Honestly Solo Live (released in 1990)",

+"1986 - Live In Italy (released in 1991)",

+"1986 - Heavy'n Jazz (released in 1992)",

+"1991 - Live In New York City, Volumes 1-7.",

+"1999 - Rare Collection (compilation)",

+"2003 - Punk Jazz: The Jaco Pastorius Anthology (compilation)",

+"2007 - The Essential Jaco Pastorius (compilation)"

+]

+```

+The list of bass players can be accessed via `.Site.Data.jazz.bass`, a single bass player by adding the filename without the suffix, e.g. `.Site.Data.jazz.bass.jacopastorius`.

+You can now render the list of recordings for all the bass players in a template:

+```html

+{{ range $.Site.Data.jazz.bass }}

+   {{ partial "artist.html" . }}

+{{ end }}

+```

+And then in the `partial/artist.html`:

+```

+<ul>

+{{ range .discography }}

+  <li>{{ . }}</li>

+{{ end }}

+</ul>

+```

+Discover a new favorite bass player? Just add another `.toml` file in the same directory.

+## Example: Accessing Named Values in a Data File

+Assume you have the following YAML structure in your `User0123.yml` data file located directly in `data/`:

+```

+Name: User0123

+"Short Description": "He is a **jolly good** fellow."

+Achievements:

+  - "Can create a Key, Value list from Data File"

+  - "Learns Hugo"

+  - "Reads documentation"

+```

+You can use the following code to render the `Short Description` in your layout::

+```

+<div>Short Description of {{.Site.Data.User0123.Name}}: <p>{{ index .Site.Data.User0123 "Short Description" | markdownify }}</p></div>

+```

+Note the use of the [`markdownify` template function][markdownify]. This will send the description through the Blackfriday Markdown rendering engine.

+<!-- begin "Data-drive Content" page -->

+## Data-Driven Content

+In addition to the [data files](/extras/datafiles/) feature, Hugo also a "data-driven content" feature, which lets you load any [JSON](http://www.json.org/) or [CSV](http://en.wikipedia.org/wiki/Comma-separated_values) file from nearly any resource.

+Data-driven content currently consists of two functions, `getJSON` and `getCSV`, which are available in all template files.

+## Implementation details

+### Call the Functions with a URL

+In your template, call the functions like this:

+```golang

+{{ $dataJ := getJSON "url" }}

+{{ $dataC := getCSV "separator" "url" }}

+```

+If you use a prefix or postfix for the URL, the functions accept [variadic arguments][variadic]:

+```

+{{ $dataJ := getJSON "url prefix" "arg1" "arg2" "arg n" }}

+{{ $dataC := getCSV  "separator" "url prefix" "arg1" "arg2" "arg n" }}

+```

+The separator for `getCSV` must be put in the first position and can only be one character long.

+All passed arguments will be joined to the final URL:

+```html

+{{ $urlPre := "https://api.github.com" }}

+{{ $gistJ := getJSON $urlPre "/users/GITHUB_USERNAME/gists" }}

+```

+This will resolve internally to the following:

+```html

+{{ $gistJ := getJSON "https://api.github.com/users/GITHUB_USERNAME/gists" }}

+```

+Finally, you can range over an array. This example will output the

+first 5 gists for a GitHub user:

+```html

+<ul>

+  {{ $urlPre := "https://api.github.com" }}

+  {{ $gistJ := getJSON $urlPre "/users/GITHUB_USERNAME/gists" }}

+  {{ range first 5 $gistJ }}

+    {{ if .public }}

+      <li><a href="{{ .html_url }}" target="_blank">{{ .description }}</a></li>

+    {{ end }}

+  {{ end }}

+</ul>

+```

+### Example for CSV files

+For `getCSV`, the one-character-long separator must be placed in the first position followed by the URL. The following is an example of creating an HTML table in a [partial template][partials] from a published CSV:

+{{% code file="layouts/partials/get-csv.html" %}}

+```html

+  <table>

+    <thead>

+      <tr>

+      <th>Name</th>

+      <th>Position</th>

+      <th>Salary</th>

+      </tr>

+    </thead>

+    <tbody>

+    {{ $url := "http://a-big-corp.com/finance/employee-salaries.csv" }}

+    {{ $sep := "," }}

+    {{ range $i, $r := getCSV $sep $url }}

+      <tr>

+        <td>{{ index $r 0 }}</td>

+        <td>{{ index $r 1 }}</td>

+        <td>{{ index $r 2 }}</td>

+      </tr>

+    {{ end }}

+    </tbody>

+  </table>

+```

+{{% /code %}}

+The expression `{{index $r number}}` must be used to output the nth-column from the current row.

+### Cache URLs

+Each downloaded URL will be cached in the default folder `$TMPDIR/hugo_cache/`. The variable `$TMPDIR` will be resolved to your system-dependent temporary directory.

+With the command-line flag `--cacheDir`, you can specify any folder on your system as a caching directory.

+You can also set `cacheDir` in the [main configuration file][config].

+If you don't like caching at all, you can fully disable caching with the command line flag `--ignoreCache`.

+### Authentication When Using REST URLs

+Currently, you can only use those authentication methods that can be put into an URL. [OAuth][] and other authentication methods are not implemented.

+### Load Local files

+To load local files with `getJSON` and `getCSV`, the source files must reside within Hugo's working directory. The file extension does not matter, but the content does.

+It applies the same output logic as above in [Calling the Functions with a URL](#calling-the-functions-with-a-url).

+## LiveReload with Data Files

+There is no chance to trigger a [LiveReload][] when the content of a URL changes. However, when a *local* file changes (i.e., `data/*` and `themes/<THEME>/data/*`), a LiveReload will be triggered. Symlinks are not supported. Note too that because downloading of data takes a while, Hugo stops processing your Markdown files until the data download has completed.

+{{% warning "URL Data and LiveReload" %}}

+If you change any local file and the LiveReload is triggered, Hugo will read the data-driven (URL) content from the cache. If you have disabled the cache (i.e., by running the server with `hugo server --ignoreCache`), Hugo will re-download the content every time LiveReload triggers. This can create *huge* traffic. You may reach API limits quickly.

+{{% /warning %}}

+## Examples of Data-driven Content

+- Photo gallery JSON powered: [https://github.com/pcdummy/hugo-lightslider-example](https://github.com/pcdummy/hugo-lightslider-example)

+- GitHub Starred Repositories [in a post](https://github.com/SchumacherFM/blog-cs/blob/master/content%2Fposts%2Fgithub-starred.md) using data-driven content in a [custom short code](https://github.com/SchumacherFM/blog-cs/blob/master/layouts%2Fshortcodes%2FghStarred.html).

+## Specs for Data Formats

+* [TOML Spec][toml]

+* [YAML Spec][yaml]

+* [JSON Spec][json]

+* [CSV Spec][csv]

+[config]: /getting-started/configuration/

+[csv]: https://tools.ietf.org/html/rfc4180

+[customize]: /themes/customizing/

+[json]: /documents/ecma-404-json-spec.pdf

+[LiveReload]: /getting-started/usage/#livereload

+[lookup]: /templates/lookup-order/

+[markdownify]: /functions/markdownify/

+[OAuth]: http://en.wikipedia.org/wiki/OAuth

+[partials]: /templates/partials/

+[themes]: /themes/

+[toml]: https://github.com/toml-lang/toml

+[variadic]: http://en.wikipedia.org/wiki/Variadic_function

+[vars]: /variables/

+[yaml]: http://yaml.org/spec/

\ No newline at end of file

--- a/content/templates/debugging.md

+++ /dev/null

@@ -1,62 +1,0 @@

----

-aliases:

-- /doc/debugging/

-- /layout/debugging/

-lastmod: 2015-05-25

-date: 2015-05-22

-linktitle: Debugging

-menu:

-  main:

-    parent: layout

-prev: /templates/404

-title: Template Debugging

-weight: 110

----

-# Template Debugging

-Here are some snippets you can add to your template to answer some common questions.

-These snippets use the `printf` function available in all Go templates.  This function is

-an alias to the Go function, [fmt.Printf](http://golang.org/pkg/fmt/).

-### What variables are available in this context?

-You can use the template syntax, `$.`, to get the top-level template context

-from anywhere in your template.  This will print out all the values under, `.Site`.

-    {{ printf "%#v" $.Site }}

-This will print out the value of `.Permalink`:

-    {{ printf "%#v" .Permalink }}

-This will print out a list of all the variables scoped to the current context

-(a.k.a. The dot, "`.`").

-    {{ printf "%#v" . }}

-When writing a [Homepage](/templates/homepage), what does one of the pages

-you're looping through look like?

-```

-{{ range .Data.Pages }}

-    {{/* The context, ".", is now a Page */}}

-    {{ printf "%#v" . }}

-{{ end }}

-```

-### Why do I have no variables defined?

-Check that you are passing variables in the `partial` function. For example

-```

-{{ partial "header" }}

-```

-will render the header partial, but the header partial will not have access to any variables. You need to pass variables explicitly. For example:

-```

-{{ partial "header" . }}

-```

--- /dev/null

+++ b/content/templates/files.md

@@ -1,0 +1,118 @@

+---

+title: Local File Templates

+linktitle: Local File Templates

+description: Hugo's `readerDir` and `readFile` functions make it easy to traverse your project's directory structure and write file contents to your templates.

+godocref: https://golang.org/pkg/os/#FileInfo

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [files,directories]

+menu:

+  docs:

+    parent: "templates"

+    weight: 110

+weight: 110

+sections_weight: 110

+draft: false

+aliases: [/extras/localfiles/,/templates/local-files/]

+toc: true

+---

+## Traverse Local Files

+With Hugo's [`readDir` and `readFile` template functions][reads], you can traverse your website's files on your server.

+## Use `readDir`

+The [`readDir` function][reads] returns an array of [`os.FileInfo`][osfileinfo]. It takes the file's `path` as a single string argument. This path can be to any directory of your website (i.e., as found on your server's file system).

+Whether the path is absolute or relative does not matter because---at least for `readDir`---the root of your website (typically `./public/`) in effect becomes both:

+1. The file system root

+2. The current working directory

+### `readDir` Example: List Directory Files

+This shortcode creates a link to each of the files in a directory---display as the file's basename---along with the file's size in bytes.

+{{% code file="layouts/shortcodes/directoryindex.html" download="directoryindex.html" %}}

+```html

+{{< readfile file="/themes/gohugoioTheme/layouts/shortcodes/directoryindex.html" >}}

+```

+{{% /code %}}

+You can then call the shortcode as follows inside of your content's markup:

+```html

+{{</* directoryindex path="/static/css" pathURL="/css" */>}}

+```

+The above shortcode [is part of the code for the Hugo docs][dirindex]. Here it lists this site's CSS files:

+{{< directoryindex path="/themes/gohugoioTheme/static/dist" pathURL="/css" >}}

+{{% note "Slashes are Important" %}}

+The initial slash `/` in `pathURL` is important in the `directoryindex` shortcode. Otherwise, `pathURL` becomes relative to the current web page.

+{{% /note %}}

+## Use `readFile`

+The [`readfile` function][reads] reads a file from disk and converts it into a string to be manipulated by other Hugo functions or added as-is. `readFile` takes the file, including path, as an argument passed to the function.

+To use the `readFile` function in your templates, make sure the path is relative to your *Hugo project's root directory*:

+```html

+{{ readFile "/content/templates/local-file-templates" }}

+```

+### `readFile` Example: Add a Project File to Content

+As `readFile` is a function, it is only available to you in your templates and not your content. However, we can create a simple [shortcode template][sct] that calls `readFile`, passes the first argument through the function, and then allows an optional second argument to send the file through the Blackfriday markdown processor. The pattern for adding this shortcode to your content will be as follows:

+```

+{{</* readfile file="/path/to/local/file.txt" markdown="true" */>}}

+```

+{{% warning %}}

+If you are going to create [custom shortcodes](/templates/shortcode-templates/) with `readFile` for a theme, note that usage of the shortcode will refer to the project root and *not* your `themes` directory.

+{{% /warning %}}

+Here is the templating for our new `readfile` shortcode:

+{{% code file="layouts/shortcodes/readfile.html" download="readfile.html" %}}

+```

+{{< readfile file="/themes/gohugoioTheme/layouts/shortcodes/readfile.html">}}

+```

+{{% /code %}}

+This `readfile` shortcode is [also part of the Hugo docs][readfilesource]. So is [`testing.txt`][testfile], which we will call in this example by passing it into our new `readfile` shortcode as follows:

+```

+{{</* readfile file="/content/readfiles/testing.txt" */>}}

+```

+The output "string" for this shortcode declaration will be the following:

+```markdown

+{{< readfile file="/content/readfiles/testing.txt" >}}

+```

+However, if we want Hugo to pass this string through Blackfriday, we should add the `markdown="true"` optional parameter:

+```html

+{{</* readfile file="/content/readfiles/testing.txt" markdown="true" */>}}

+```

+And here is the result as [called directly in the Hugo docs][] and rendered for display:

+{{< readfile file="/content/readfiles/testing.txt" markdown="true">}}

+[called directly in the Hugo docs]: https://github.com/gohugoio/hugo/blob/master/docs/content/templates/files.md

+[dirindex]: https://github.com/gohugoio/hugo/blob/master/docs/layouts/shortcodes/directoryindex.html

+[osfileinfo]: https://golang.org/pkg/os/#FileInfo

+[reads]: /functions/readfile/

+[sc]: /content-management/shortcodes/

+[sct]: /templates/shortcode-templates/

+[readfilesource]: https://github.com/gohugoio/hugo/blob/master/

+[testfile]: https://github.com/gohugoio/hugo/blob/master/docs/testfile

--- a/content/templates/functions.md

+++ /dev/null

@@ -1,1088 +1,0 @@

----

-aliases:

-- /layout/functions/

-lastmod: 2015-09-20

-date: 2013-07-01

-linktitle: Functions

-toc: true

-menu:

-  main:

-    parent: layout

-next: /templates/variables

-prev: /templates/go-templates

-title: Hugo Template Functions

-weight: 20

----

-Hugo uses the excellent Go html/template library for its template engine.

-It is an extremely lightweight engine that provides a very small amount of

-logic. In our experience, it is just the right amount of logic to be able

-to create a good static website.

-Go templates are lightweight but extensible. Hugo has added the following

-functions to the basic template logic.

-(Go itself supplies built-in functions, including comparison operators

-and other basic tools; these are listed in the

-[Go template documentation](http://golang.org/pkg/text/template/#hdr-Functions).)

-## General

-### default

-Checks whether a given value is set and returns a default value if it is not.

-"Set" in this context means non-zero for numeric types and times;

-non-zero length for strings, arrays, slices, and maps;

-any boolean or struct value; or non-nil for any other types.

-e.g.

-    {{ index .Params "font" | default "Roboto" }} → default is "Roboto"

-    {{ default "Roboto" (index .Params "font") }} → default is "Roboto"

-### delimit

-Loops through any array, slice or map and returns a string of all the values separated by the delimiter. There is an optional third parameter that lets you choose a different delimiter to go between the last two values.

-Maps will be sorted by the keys, and only a slice of the values will be returned, keeping a consistent output order.

-Works on [lists](/templates/list/), [taxonomies](/taxonomies/displaying/), [terms](/templates/terms/), [groups](/templates/list/)

-e.g.

-    // Front matter

-    +++

-    tags: [ "tag1", "tag2", "tag3" ]

-    +++

-    // Used anywhere in a template

-    Tags: {{ delimit .Params.tags ", " }}

-    // Outputs Tags: tag1, tag2, tag3

-    // Example with the optional "last" parameter

-    Tags: {{ delimit .Params.tags ", " " and " }}

-    // Outputs Tags: tag1, tag2 and tag3

-### dict

-Creates a dictionary `(map[string, interface{})`, expects parameters added in value:object fashion.

-Invalid combinations like keys that are not strings or uneven number of parameters, will result in an exception thrown.

-Useful for passing maps to partials when adding to a template.

-e.g. Pass into "foo.html" a map with the keys "important, content"

-    {{$important := .Site.Params.SomethingImportant }}

-    {{range .Site.Params.Bar}}

-        {{partial "foo" (dict "content" . "important" $important)}}

-    {{end}}

-"foo.html"

-    Important {{.important}}

-    {{.content}}

-or create a map on the fly to pass into

-    {{partial "foo" (dict "important" "Smiles" "content" "You should do more")}}

-### slice

-`slice` allows you to create an array (`[]interface{}`) of all arguments that you pass to this function.

-One use case is the concatenation of elements in combination with `delimit`:

-```html

-{{ delimit (slice "foo" "bar" "buzz") ", " }}

-<!-- returns the string "foo, bar, buzz" -->

-```

-### shuffle

-`shuffle` returns a random permutation of a given array or slice, e.g.

-```html

-{{ shuffle (seq 1 5) }}

-<!-- returns [2 5 3 1 4] -->

-{{ shuffle (slice "foo" "bar" "buzz") }}

-<!-- returns [buzz foo bar] -->

-```

-### echoParam

-Prints a parameter if it is set.

-e.g. `{{ echoParam .Params "project_url" }}`

-### eq

-Returns true if the parameters are equal.

-e.g.

-    {{ if eq .Section "blog" }}current{{ end }}

-### first

-Slices an array to only the first _N_ elements.

-Works on [lists](/templates/list/), [taxonomies](/taxonomies/displaying/), [terms](/templates/terms/), [groups](/templates/list/)

-e.g.

-    {{ range first 10 .Data.Pages }}

-        {{ .Render "summary" }}

-    {{ end }}

-### jsonify

-Encodes a given object to JSON.

-e.g.

-    {{ dict "title" .Title "content" .Plain | jsonify }}

-### last

-Slices an array to only the last _N_ elements.

-Works on [lists](/templates/list/), [taxonomies](/taxonomies/displaying/), [terms](/templates/terms/), [groups](/templates/list/)

-e.g.

-    {{ range last 10 .Data.Pages }}

-        {{ .Render "summary" }}

-    {{ end }}

-### after

-Slices an array to only the items after the <em>N</em>th item. Use this in combination

-with `first` to use both halves of an array split at item _N_.

-Works on [lists](/templates/list/), [taxonomies](/taxonomies/displaying/), [terms](/templates/terms/), [groups](/templates/list/)

-e.g.

-    {{ range after 10 .Data.Pages }}

-        {{ .Render "title" }}

-    {{ end }}

-### getenv

-Returns the value of an environment variable.

-Takes a string containing the name of the variable as input. Returns

-an empty string if the variable is not set, otherwise returns the

-value of the variable. Note that in Unix-like environments, the

-variable must also be exported in order to be seen by `hugo`.

-e.g.

-    {{ getenv "HOME" }}

-### in

-Checks if an element is in an array (or slice) and returns a boolean.

-The elements supported are strings, integers and floats (only float64 will match as expected).

-In addition, it can also check if a substring exists in a string.

-e.g.

-    {{ if in .Params.tags "Git" }}Follow me on GitHub!{{ end }}

-or

-    {{ if in "this string contains a substring" "substring" }}Substring found!{{ end }}

-### intersect

-Given two arrays (or slices), this function will return the common elements in the arrays.

-The elements supported are strings, integers and floats (only float64).

-A useful example of this functionality is a 'similar posts' block.

-Create a list of links to posts where any of the tags in the current post match any tags in other posts.

-e.g.

-    <ul>

-    {{ $page_link := .Permalink }}

-    {{ $tags := .Params.tags }}

-    {{ range .Site.Pages }}

-        {{ $page := . }}

-        {{ $has_common_tags := intersect $tags .Params.tags | len | lt 0 }}

-        {{ if and $has_common_tags (ne $page_link $page.Permalink) }}

-            <li><a href="{{ $page.Permalink }}">{{ $page.Title }}</a></li>

-        {{ end }}

-    {{ end }}

-    </ul>

-### union

-Given two arrays (or slices) A and B, this function will return a new array that contains the elements or objects that belong to either A or to B or to both. The elements supported are strings, integers and floats (only float64).

-```

-{{ union (slice 1 2 3) (slice 3 4 5) }}

-<!-- returns [1 2 3 4 5] -->

-{{ union (slice 1 2 3) nil }}

-<!-- returns [1 2 3] -->

-{{ union nil (slice 1 2 3) }}

-<!-- returns [1 2 3] -->

-{{ union nil nil }}

-<!-- returns an error because both arrays/slices have to be of the same type -->

-```

-### isset

-Returns true if the parameter is set.

-Takes either a slice, array or channel and an index or a map and a key as input.

-e.g. `{{ if isset .Params "project_url" }} {{ index .Params "project_url" }}{{ end }}`

-### seq

-Creates a sequence of integers. It's named and used as GNU's seq.

-Some examples:

-* `3` => `1, 2, 3`

-* `1 2 4` => `1, 3`

-* `-3` => `-1, -2, -3`

-* `1 4` => `1, 2, 3, 4`

-* `1 -2` => `1, 0, -1, -2`

-### sort

-Sorts maps, arrays and slices, returning a sorted slice.

-A sorted array of map values will be returned, with the keys eliminated.

-There are two optional arguments, which are `sortByField` and `sortAsc`.

-If left blank, sort will sort by keys (for maps) in ascending order.

-Works on [lists](/templates/list/), [taxonomies](/taxonomies/displaying/), [terms](/templates/terms/), [groups](/templates/list/)

-e.g.

-    // Front matter

-    +++

-    tags: [ "tag3", "tag1", "tag2" ]

-    +++

-    // Site config

-    +++

-    [params.authors]

-      [params.authors.Derek]

-        "firstName"  = "Derek"

-        "lastName"   = "Perkins"

-      [params.authors.Joe]

-        "firstName"  = "Joe"

-        "lastName"   = "Bergevin"

-      [params.authors.Tanner]

-        "firstName"  = "Tanner"

-        "lastName"   = "Linsley"

-    +++

-    // Use default sort options - sort by key / ascending

-    Tags: {{ range sort .Params.tags }}{{ . }} {{ end }}

-    // Outputs Tags: tag1 tag2 tag3

-    // Sort by value / descending

-    Tags: {{ range sort .Params.tags "value" "desc" }}{{ . }} {{ end }}

-    // Outputs Tags: tag3 tag2 tag1

-    // Use default sort options - sort by value / descending

-    Authors: {{ range sort .Site.Params.authors }}{{ .firstName }} {{ end }}

-    // Outputs Authors: Derek Joe Tanner

-    // Use default sort options - sort by value / descending

-    Authors: {{ range sort .Site.Params.authors "lastName" "desc" }}{{ .lastName }} {{ end }}

-    // Outputs Authors: Perkins Linsley Bergevin

-### where

-Filters an array to only elements containing a matching value for a given field.

-Works on [lists](/templates/list/), [taxonomies](/taxonomies/displaying/), [terms](/templates/terms/), [groups](/templates/list/)

-e.g.

-    {{ range where .Data.Pages "Section" "post" }}

-       {{ .Content }}

-    {{ end }}

-It can be used with dot chaining second argument to refer a nested element of a value.

-e.g.

-    // Front matter on some pages

-    +++

-    series: golang

-    +++

-    {{ range where .Site.Pages "Params.series" "golang" }}

-       {{ .Content }}

-    {{ end }}

-It can also be used with an operator like `!=`, `>=`, `in` etc. Without an operator (like above), `where` compares a given field with a matching value in a way like `=` is specified.

-e.g.

-    {{ range where .Data.Pages "Section" "!=" "post" }}

-       {{ .Content }}

-    {{ end }}

-Following operators are now available

-- `=`, `==`, `eq`: True if a given field value equals a matching value

-- `!=`, `<>`, `ne`: True if a given field value doesn't equal a matching value

-- `>=`, `ge`: True if a given field value is greater than or equal to a matching value

-- `>`, `gt`: True if a given field value is greater than a matching value

-- `<=`, `le`: True if a given field value is lesser than or equal to a matching value

-- `<`, `lt`: True if a given field value is lesser than a matching value

-- `in`: True if a given field value is included in a matching value. A matching value must be an array or a slice

-- `not in`: True if a given field value isn't included in a matching value. A matching value must be an array or a slice

-- `intersect`: True if a given field value that is a slice / array of strings or integers contains elements in common with the matching value. It follows the same rules as the intersect function.

-*`intersect` operator, e.g.:*

-    {{ range where .Site.Pages ".Params.tags" "intersect" .Params.tags }}

-      {{ if ne .Permalink $.Permalink }}

-        {{ .Render "summary" }}

-      {{ end }}

-    {{ end }}

-*`where` and `first` can be stacked, e.g.:*

-    {{ range first 5 (where .Data.Pages "Section" "post") }}

-       {{ .Content }}

-    {{ end }}

-### Unset field

-Filter only work for set fields. To check whether a field is set or exist, use operand `nil`.

-This can be useful to filter a small amount of pages from a large pool. Instead of set field on all pages, you can set field on required pages only.

-Only following operators are available for `nil`

-- `=`, `==`, `eq`: True if the given field is not set.

-- `!=`, `<>`, `ne`: True if the given field is set.

-e.g.

-    {{ range where .Data.Pages ".Params.specialpost" "!=" nil }}

-       {{ .Content }}

-    {{ end }}

-### uniq

-Takes in a slice or array and returns a slice with subsequent duplicate elements removed.

-    {{ uniq (slice 1 2 3 2) }}

-    {{ slice 1 2 3 2 | uniq }}

-    <!-- both return [1 2 3] -->

-## Files

-### readDir

-Gets a directory listing from a directory relative to the current project working dir.

-So, If the project working dir has a single file named `README.txt`:

-`{{ range (readDir ".") }}{{ .Name }}{{ end }}` → "README.txt"

-### readFile

-Reads a file from disk and converts it into a string. Note that the filename must be relative to the current project working dir.

- So, if you have a file with the name `README.txt` in the root of your project with the content `Hugo Rocks!`:

- `{{readFile "README.txt"}}` → `"Hugo Rocks!"`

-### imageConfig

-Parses the image and returns the height, width and color model.

-e.g.

-```

-{{ with (imageConfig "favicon.ico") }}

-favicon.ico: {{.Width}} x {{.Height}}

-{{ end }}

-```

-## Math

-<table class="table table-bordered">

-<thead>

-<tr>

-<th>Function</th>

-<th>Description</th>

-<th>Example</th>

-</tr>

-</thead>

-<tbody>

-<tr>

-<td><code>add</code></td>

-<td>Adds two integers.</td>

-<td><code>{{add 1 2}}</code> → 3</td>

-</tr>

-<tr>

-<td><code>div</code></td>

-<td>Divides two integers.</td>

-<td><code>{{div 6 3}}</code> → 2</td>

-</tr>

-<tr>

-<td><code>mod</code></td>

-<td>Modulus of two integers.</td>

-<td><code>{{mod 15 3}}</code> → 0</td>

-</tr>

-<tr>

-<td><code>modBool</code></td>

-<td>Boolean of modulus of two integers.  <code>true</code> if modulus is 0.</td>

-<td><code>{{modBool 15 3}}</code> → true</td>

-</tr>

-<tr>

-<td><code>mul</code></td>

-<td>Multiplies two integers.</td>

-<td><code>{{mul 2 3}}</code> → 6</td>

-</tr>

-<tr>

-<td><code>sub</code></td>

-<td>Subtracts two integers.</td>

-<td><code>{{sub 3 2}}</code> → 1</td>

-</tr>

-</tbody>

-</table>

-## Numbers

-### int

-Creates an `int`.

-e.g.

-* `{{ int "123" }}` → 123

-### lang.NumFmt

-`NumFmt` formats a number with the given precision using the *decimal*,

-*grouping*, and *negative* options.  The `options` parameter is a

-string consisting of `<negative> <decimal> <grouping>`.  The default

-`options` value is `- . ,`.

-Note that numbers are rounded up at 5 or greater.

-So, with precision set to 0, 1.5 becomes `2`, and 1.4 becomes `1`.

-```

-{{ lang.NumFmt 2 12345.6789 }} → 12,345.68

-{{ lang.NumFmt 2 12345.6789 "- , ." }} → 12.345,68

-{{ lang.NumFmt 0 -12345.6789 "- . ," }} → -12,346

-{{ lang.NumFmt 6 -12345.6789 "- ." }} → -12345.678900

-{{ -98765.4321 | lang.NumFmt 2 }} → -98,765.43

-```

-## Strings

-### printf

-Format a string using the standard `fmt.Sprintf` function. See [the go

-doc](https://golang.org/pkg/fmt/) for reference.

-A

-e.g., `{{ i18n ( printf "combined_%s" $var ) }}` or `{{ printf "formatted %.2f" 3.1416 }}`

-### chomp

-Removes any trailing newline characters. Useful in a pipeline to remove newlines added by other processing (including `markdownify`).

-e.g., `{{chomp "<p>Blockhead</p>\n"}}` → `"<p>Blockhead</p>"`

-### dateFormat

-Converts the textual representation of the datetime into the other form or returns it of Go `time.Time` type value.

-These are formatted with the layout string.

-e.g. `{{ dateFormat "Monday, Jan 2, 2006" "2015-01-21" }}` → "Wednesday, Jan 21, 2015"

-### emojify

-Runs the string through the Emoji emoticons processor. The result will be declared as "safe" so Go templates will not filter it.

-See the [Emoji cheat sheet](http://www.emoji-cheat-sheet.com/) for available emoticons.

-e.g. `{{ "I :heart: Hugo" | emojify }}`

-### highlight

-Takes a string of code and a language, uses Pygments to return the syntax highlighted code in HTML.

-Used in the [highlight shortcode](/extras/highlighting/).

-### htmlEscape

-HtmlEscape returns the given string with the critical reserved HTML codes escaped,

-such that `&` becomes `&amp;` and so on. It escapes only: `<`, `>`, `&`, `'` and `"`.

-Bear in mind that, unless content is passed to `safeHTML`, output strings are escaped

-usually by the processor anyway.

-e.g.

-`{{ htmlEscape "Hugo & Caddy > Wordpress & Apache" }} → "Hugo &amp; Caddy &gt; Wordpress &amp; Apache"`

-### htmlUnescape

-HtmlUnescape returns the given string with html escape codes un-escaped. This

-un-escapes more codes than `htmlEscape` escapes, including `#` codes and pre-UTF8

-escapes for accented characters. It defers completely to the Go `html.UnescapeString`

-function, so functionality is consistent with that codebase.

-Remember to pass the output of this to `safeHTML` if fully unescaped characters

-are desired, or the output will be escaped again as normal.

-e.g.

-`{{ htmlUnescape "Hugo &amp; Caddy &gt; Wordpress &amp; Apache" }} → "Hugo & Caddy > Wordpress & Apache"`

-### humanize

-Humanize returns the humanized version of an argument with the first letter capitalized.

-If the input is either an int64 value or the string representation of an integer, humanize returns the number with the proper ordinal appended.

-e.g.

-```

-{{humanize "my-first-post"}} → "My first post"

-{{humanize "myCamelPost"}} → "My camel post"

-{{humanize "52"}} → "52nd"

-{{humanize 103}} → "103rd"

-```

-### lower

-Converts all characters in string to lowercase.

-e.g. `{{lower "BatMan"}}` → "batman"

-### markdownify

-Runs the string through the Markdown processor. The result will be declared as "safe" so Go templates will not filter it.

-e.g. `{{ .Title | markdownify }}`

-### plainify

-Strips any HTML and returns the plain text version.

-e.g. `{{ "<b>BatMan</b>" | plainify }}` → "BatMan"

-### pluralize

-Pluralize the given word with a set of common English pluralization rules.

-e.g. `{{ "cat" | pluralize }}` → "cats"

-### findRE

-Returns a list of strings that match the regular expression. By default all matches will be included. The number of matches can be limited with an optional third parameter.

-The example below returns a list of all second level headers (`<h2>`) in the content:

-    {{ findRE "<h2.*?>(.|\n)*?</h2>" .Content }}

-We can limit the number of matches in that list with a third parameter. Let's say we want to have at most one match (or none if no substring matched):

-    {{ findRE "<h2.*?>(.|\n)*?</h2>" .Content 1 }}

-    <!-- returns ["<h2 id="#foo">Foo</h2>"] -->

-`findRE` allows us to build an automatically generated table of contents that could be used for a simple scrollspy:

-    {{ $headers := findRE "<h2.*?>(.|\n)*?</h2>" .Content }}

-    {{ if ge (len $headers) 1 }}

-        <ul>

-        {{ range $headers }}

-            <li>

-                <a href="#{{ . | plainify | urlize }}">

-                    {{ . | plainify }}

-                </a>

-            </li>

-        {{ end }}

-        </ul>

-    {{ end }}

-First, we try to find all second-level headers and generate a list if at least one header was found. `plainify` strips the HTML and `urlize` converts the header into a valid URL.

-### replace

-Replaces all occurrences of the search string with the replacement string.

-e.g. `{{ replace "Batman and Robin" "Robin" "Catwoman" }}` → "Batman and Catwoman"

-### replaceRE

-Replaces all occurrences of a regular expression with the replacement pattern.

-e.g. `{{ replaceRE "^https?://([^/]+).*" "$1" "http://gohugo.io/docs" }}` → "gohugo.io"

-e.g. `{{ "http://gohugo.io/docs" | replaceRE "^https?://([^/]+).*" "$1" }}` → "gohugo.io"

-### safeHTML

-Declares the provided string as a "safe" HTML document fragment

-so Go html/template will not filter it.  It should not be used

-for HTML from a third-party, or HTML with unclosed tags or comments.

-Example: Given a site-wide `config.toml` that contains this line:

-    copyright = "© 2015 Jane Doe.  <a href=\"http://creativecommons.org/licenses/by/4.0/\">Some rights reserved</a>."

-`{{ .Site.Copyright | safeHTML }}` would then output:

-> © 2015 Jane Doe.  <a href="http://creativecommons.org/licenses/by/4.0/">Some rights reserved</a>.

-However, without the `safeHTML` function, html/template assumes

-`.Site.Copyright` to be unsafe, escaping all HTML tags,

-rendering the whole string as plain-text like this:

-<blockquote>

-<p>© 2015 Jane Doe.  &lt;a href=&#34;http://creativecommons.org/licenses/by/4.0/&#34;&gt;Some rights reserved&lt;/a&gt;.</p>

-</blockquote>

-### safeHTMLAttr

-Declares the provided string as a "safe" HTML attribute

-from a trusted source, for example, ` dir="ltr"`,

-so Go html/template will not filter it.

-Example: Given a site-wide `config.toml` that contains this menu entry:

-    [[menu.main]]

-        name = "IRC: #golang at freenode"

-        url = "irc://irc.freenode.net/#golang"

-* `<a href="{{ .URL }}">` ⇒ `<a href="#ZgotmplZ">` (Bad!)

-* `<a {{ printf "href=%q" .URL | safeHTMLAttr }}>` ⇒ `<a href="irc://irc.freenode.net/#golang">` (Good!)

-### safeCSS

-Declares the provided string as a known "safe" CSS string

-so Go html/templates will not filter it.

-"Safe" means CSS content that matches any of:

-1. The CSS3 stylesheet production, such as `p { color: purple }`.

-2. The CSS3 rule production, such as `a[href=~"https:"].foo#bar`.

-3. CSS3 declaration productions, such as `color: red; margin: 2px`.

-4. The CSS3 value production, such as `rgba(0, 0, 255, 127)`.

-Example: Given `style = "color: red;"` defined in the front matter of your `.md` file:

-* `<p style="{{ .Params.style | safeCSS }}">…</p>` ⇒ `<p style="color: red;">…</p>` (Good!)

-* `<p style="{{ .Params.style }}">…</p>` ⇒ `<p style="ZgotmplZ">…</p>` (Bad!)

-Note: "ZgotmplZ" is a special value that indicates that unsafe content reached a

-CSS or URL context.

-### safeJS

-Declares the provided string as a known "safe" Javascript string so Go

-html/templates will not escape it.  "Safe" means the string encapsulates a known

-safe EcmaScript5 Expression, for example, `(x + y * z())`. Template authors

-are responsible for ensuring that typed expressions do not break the intended

-precedence and that there is no statement/expression ambiguity as when passing

-an expression like `{ foo:bar() }\n['foo']()`, which is both a valid Expression

-and a valid Program with a very different meaning.

-Example: Given `hash = "619c16f"` defined in the front matter of your `.md` file:

-* `<script>var form_{{ .Params.hash | safeJS }};…</script>` ⇒ `<script>var form_619c16f;…</script>` (Good!)

-* `<script>var form_{{ .Params.hash }};…</script>` ⇒ `<script>var form_"619c16f";…</script>` (Bad!)

-### singularize

-Singularize the given word with a set of common English singularization rules.

-e.g. `{{ "cats" | singularize }}` → "cat"

-### slicestr

-Slicing in `slicestr` is done by specifying a half-open range with two indices, `start` and `end`.

-For example, 1 and 4 creates a slice including elements 1 through 3.

-The `end` index can be omitted; it defaults to the string's length.

-e.g.

-* `{{slicestr "BatMan" 3}}` → "Man"

-* `{{slicestr "BatMan" 0 3}}` → "Bat"

-### truncate

-Truncate a text to a max length without cutting words or leaving unclosed HTML tags. Since Go templates are HTML-aware, truncate will handle normal strings vs HTML strings intelligently. It's important to note that if you have a raw string that contains HTML tags that you want treated as HTML, you will need to convert the string to HTML using the safeHTML template function before sending the value to truncate; otherwise, the HTML tags will be escaped by truncate.

-e.g.

-* `{{ "this is a text" | truncate 10 " ..." }}` → `this is a ...`

-* `{{ "<em>Keep my HTML</em>" | safeHTML | truncate 10 }}` → `<em>Keep my …</em>`

-* `{{ "With [Markdown](#markdown) inside." | markdownify | truncate 10 }}` → `With <a href='#markdown'>Markdown …</a>`

-### split

-Split a string into substrings separated by a delimiter.

-e.g.

-* `{{split "tag1,tag2,tag3" "," }}` → ["tag1" "tag2" "tag3"]

-### string

-Creates a `string`.

-e.g.

-* `{{string "BatMan"}}` → "BatMan"

-### substr

-Extracts parts of a string, beginning at the character at the specified

-position, and returns the specified number of characters.

-It normally takes two parameters: `start` and `length`.

-It can also take one parameter: `start`, i.e. `length` is omitted, in which case

-the substring starting from start until the end of the string will be returned.

-To extract characters from the end of the string, use a negative start number.

-In addition, borrowing from the extended behavior described at http://php.net/substr,

-if `length` is given and is negative, then that many characters will be omitted from

-the end of string.

-e.g.

-* `{{substr "BatMan" 0 -3}}` → "Bat"

-* `{{substr "BatMan" 3 3}}` → "Man"

-### hasPrefix

-HasPrefix tests whether a string begins with prefix.

-* `{{ hasPrefix "Hugo" "Hu" }}` → true

-### title

-Converts all characters in string to titlecase.

-e.g. `{{title "BatMan"}}` → "Batman"

-### trim

-Returns a slice of the string with all leading and trailing characters contained in cutset removed.

-e.g. `{{ trim "++Batman--" "+-" }}` → "Batman"

-### upper

-Converts all characters in string to uppercase.

-e.g. `{{upper "BatMan"}}` → "BATMAN"

-### countwords

-`countwords` tries to convert the passed content to a string and counts each word

-in it. The template functions works similar to [.WordCount]({{< relref "templates/variables.md#page-variables" >}}).

-```html

-{{ "Hugo is a static site generator." | countwords }}

-<!-- outputs a content length of 6 words.  -->

-```

-### countrunes

-Alternatively to counting all words , `countrunes` determines the number  of runes in the content and excludes any whitespace. This can become useful if you have to deal with

-CJK-like languages.

-```html

-{{ "Hello, 世界" | countrunes }}

-<!-- outputs a content length of 8 runes. -->

-```

-### md5

-`md5` hashes the given input and returns its MD5 checksum.

-```html

-{{ md5 "Hello world, gophers!" }}

-<!-- returns the string "b3029f756f98f79e7f1b7f1d1f0dd53b" -->

-```

-This can be useful if you want to use Gravatar for generating a unique avatar:

-```html

-<img src="https://www.gravatar.com/avatar/{{ md5 "[email protected]" }}?s=100&d=identicon">

-```

-### sha1

-`sha1` hashes the given input and returns its SHA1 checksum.

-```html

-{{ sha1 "Hello world, gophers!" }}

-<!-- returns the string "c8b5b0e33d408246e30f53e32b8f7627a7a649d4" -->

-```

-### sha256

-`sha256` hashes the given input and returns its SHA256 checksum.

-```html

-{{ sha256 "Hello world, gophers!" }}

-<!-- returns the string "6ec43b78da9669f50e4e422575c54bf87536954ccd58280219c393f2ce352b46" -->

-```

-## Internationalization

-### i18n

-This translates a piece of content based on your `i18n/en-US.yaml`

-(and friends) files. You can use the [go-i18n](https://github.com/nicksnyder/go-i18n) tools to manage your translations.  The translations can exist in both the theme and at the root of your repository.

-e.g.: `{{ i18n "translation_id" }}`

-For more information about string translations, see [Translation of strings]({{< relref "content/multilingual.md#translation-of-strings">}}).

-### T

-`T` is an alias to `i18n`. E.g. `{{ T "translation_id" }}`.

-## Times

-### time

-`time` converts a timestamp string into a [`time.Time`](https://godoc.org/time#Time) structure so you can access its fields. E.g.

-* `{{ time "2016-05-28" }}` → "2016-05-28T00:00:00Z"

-* `{{ (time "2016-05-28").YearDay }}` → 149

-* `{{ mul 1000 (time "2016-05-28T10:30:00.00+10:00").Unix }}` → 1464395400000 (Unix time in milliseconds)

-### now

-`now` returns the current local time as a [`time.Time`](https://godoc.org/time#Time).

-## URLs

-### absLangURL, relLangURL

-These are similar to the `absURL` and `relURL` relatives below, but will add the correct language prefix when the site is configured with more than one language.

-So for a site  `baseURL` set to `http://mysite.com/hugo/` and the current language is `en`:

-* `{{ "blog/" | absLangURL }}` → "http://mysite.com/hugo/en/blog/"

-* `{{ "blog/" | relLangURL }}` → "/hugo/en/blog/"

-### absURL, relURL

-Both `absURL` and `relURL` considers the configured value of `baseURL`, so given a `baseURL` set to `http://mysite.com/hugo/`:

-* `{{ "mystyle.css" | absURL }}` → "http://mysite.com/hugo/mystyle.css"

-* `{{ "mystyle.css" | relURL }}` → "/hugo/mystyle.css"

-* `{{ "http://gohugo.io/" | relURL }}` →  "http://gohugo.io/"

-* `{{ "http://gohugo.io/" | absURL }}` →  "http://gohugo.io/"

-The last two examples may look funky, but is useful if you, say, have a list of images, some of them hosted externally, some locally:

-```

-<script type="application/ld+json">

-{

-    "@context" : "http://schema.org",

-    "@type" : "BlogPosting",

-    "image" : {{ apply .Params.images "absURL" "." }}

-}

-</script>

-```

-The above also exploits the fact that the Go template parser JSON-encodes objects inside `script` tags.

-**Note:** These functions are smart about missing slashes, but will not add one to the end if not present.

-### ref, relref

-Looks up a content page by relative path or logical name to return the permalink (`ref`) or relative permalink (`relref`). Requires a `Page` object (usually satisfied with `.`). Used in the [`ref` and `relref` shortcodes]({{% ref "extras/crossreferences.md" %}}).

-e.g. {{ ref . "about.md" }}

-### safeURL

-Declares the provided string as a "safe" URL or URL substring (see [RFC 3986][]).

-A URL like `javascript:checkThatFormNotEditedBeforeLeavingPage()` from a trusted

-source should go in the page, but by default dynamic `javascript:` URLs are

-filtered out since they are a frequently exploited injection vector.

-[RFC 3986]: http://tools.ietf.org/html/rfc3986

-Without `safeURL`, only the URI schemes `http:`, `https:` and `mailto:`

-are considered safe by Go.  If any other URI schemes, e.g.&nbsp;`irc:` and

-`javascript:`, are detected, the whole URL would be replaced with

-`#ZgotmplZ`.  This is to "defang" any potential attack in the URL,

-rendering it useless.

-Example: Given a site-wide `config.toml` that contains this menu entry:

-    [[menu.main]]

-        name = "IRC: #golang at freenode"

-        url = "irc://irc.freenode.net/#golang"

-The following template:

-    <ul class="sidebar-menu">

-      {{ range .Site.Menus.main }}

-      <li><a href="{{ .URL }}">{{ .Name }}</a></li>

-      {{ end }}

-    </ul>

-would produce `<li><a href="#ZgotmplZ">IRC: #golang at freenode</a></li>`

-for the `irc://…` URL.

-To fix this, add ` | safeURL` after `.URL` on the 3rd line, like this:

-      <li><a href="{{ .URL | safeURL }}">{{ .Name }}</a></li>

-With this change, we finally get `<li><a href="irc://irc.freenode.net/#golang">IRC: #golang at freenode</a></li>`

-as intended.

-### urlize

-Takes a string and sanitizes it for usage in URLs, converts spaces to "-".

-e.g. `<a href="/tags/{{ . | urlize }}">{{ . }}</a>`

-### querify

-Takes a set of key-value pairs and returns a [query string](https://en.wikipedia.org/wiki/Query_string) that can be appended to a URL. E.g.

-    <a href="https://www.google.com?{{ (querify "q" "test" "page" 3) | safeURL }}">Search</a>

-will be rendered as

-    <a href="https://www.google.com?page=3&q=test">Search</a>

-## Content Views

-### Render

-Takes a view to render the content with.  The view is an alternate layout, and should be a file name that points to a template in one of the locations specified in the documentation for [Content Views](/templates/views).

-This function is only available on a piece of content, and in list context.

-This example could render a piece of content using the content view located at `/layouts/_default/summary.html`:

-    {{ range .Data.Pages }}

-        {{ .Render "summary"}}

-    {{ end }}

-## Advanced

-### apply

-Given a map, array, or slice, returns a new slice with a function applied over it. Expects at least three parameters, depending on the function being applied. The first parameter is the sequence to operate on; the second is the name of the function as a string, which must be in the Hugo function map (generally, it is these functions documented here). After that, the parameters to the applied function are provided, with the string `"."` standing in for each element of the sequence the function is to be applied against. An example is in order:

-    +++

-    names: [ "Derek Perkins", "Joe Bergevin", "Tanner Linsley" ]

-    +++

-    {{ apply .Params.names "urlize" "." }} → [ "derek-perkins", "joe-bergevin", "tanner-linsley" ]

-This is roughly equivalent to:

-    {{ range .Params.names }}{{ . | urlize }}{{ end }}

-However, it isn’t possible to provide the output of a range to the `delimit` function, so you need to `apply` it. A more complete example should explain this. Let's say you have two partials for displaying tag links in a post,  "post/tag/list.html" and "post/tag/link.html", as shown below.

-    <!-- post/tag/list.html -->

-    {{ with .Params.tags }}

-    <div class="tags-list">

-      Tags:

-      {{ $len := len . }}

-      {{ if eq $len 1 }}

-        {{ partial "post/tag/link" (index . 0) }}

-      {{ else }}

-        {{ $last := sub $len 1 }}

-        {{ range first $last . }}

-          {{ partial "post/tag/link" . }},

-        {{ end }}

-        {{ partial "post/tag/link" (index . $last) }}

-      {{ end }}

-    </div>

-    {{ end }}

-    <!-- post/tag/link.html -->

-    <a class="post-tag post-tag-{{ . | urlize }}" href="/tags/{{ . | urlize }}">{{ . }}</a>

-This works, but the complexity of "post/tag/list.html" is fairly high; the Hugo template needs to perform special behaviour for the case where there’s only one tag, and it has to treat the last tag as special. Additionally, the tag list will be rendered something like "Tags: tag1 , tag2 , tag3" because of the way that the HTML is generated and it is interpreted by a browser.

-This is Hugo. We have a better way. If this were your "post/tag/list.html" instead, all of those problems are fixed automatically (this first version separates all of the operations for ease of reading; the combined version will be shown after the explanation).

-    <!-- post/tag/list.html -->

-    {{ with .Params.tags }}

-    <div class="tags-list">

-      Tags:

-      {{ $sort := sort . }}

-      {{ $links := apply $sort "partial" "post/tag/link" "." }}

-      {{ $clean := apply $links "chomp" "." }}

-      {{ delimit $clean ", " }}

-    </div>

-    {{ end }}

-In this version, we are now sorting the tags, converting them to links with "post/tag/link.html", cleaning off stray newlines, and joining them together in a delimited list for presentation. That can also be written as:

-    <!-- post/tag/list.html -->

-    {{ with .Params.tags }}

-    <div class="tags-list">

-      Tags:

-      {{ delimit (apply (apply (sort .) "partial" "post/tag/link" ".") "chomp" ".") ", " }}

-    </div>

-    {{ end }}

-`apply` does not work when receiving the sequence as an argument through a pipeline.

-***

-### base64Encode and base64Decode

-`base64Encode` and `base64Decode` let you easily decode content with a base64 encoding and vice versa through pipes. Let's take a look at an example:

-    {{ "Hello world" | base64Encode }}

-    <!-- will output "SGVsbG8gd29ybGQ=" and -->

-    {{ "SGVsbG8gd29ybGQ=" | base64Decode }}

-    <!-- becomes "Hello world" again. -->

-You can also pass other datatypes as argument to the template function which tries

-to convert them. Now we use an integer instead of a string:

-    {{ 42 | base64Encode | base64Decode }}

-    <!-- will output "42". Both functions always return a string. -->

-**Tip:** Using base64 to decode and encode becomes really powerful if we have to handle

-responses of APIs.

-    {{ $resp := getJSON "https://api.github.com/repos/gohugoio/hugo/readme"  }}

-    {{ $resp.content | base64Decode | markdownify }}

-The response of the GitHub API contains the base64-encoded version of the [README.md](https://github.com/gohugoio/hugo/blob/master/README.md) in the Hugo repository. Now we can decode it and parse the Markdown. The final output will look similar to the rendered version on GitHub.

-***

-### partialCached

-See [Template Partials]({{< relref "templates/partials.md#cached-partials" >}}) for an explanation of the `partialCached` template function.

-## .Site.GetPage

-Every `Page` has a `Kind` attribute 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` looks up an index page of a given `Kind` and `path`. This method may support regular pages in the future, but currently it is a convenient way of getting the index pages, such as the home page or a section, from a template:

-    {{ with .Site.GetPage "section" "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 isn't found.

-The valid page kinds are: *home, section, taxonomy and taxonomyTerm.*

--- a/content/templates/go-templates.md

+++ /dev/null

@@ -1,443 +1,0 @@

----

-aliases:

-- /layout/go-templates/

-- /layouts/go-templates/

-lastmod: 2015-11-30

-date: 2013-07-01

-menu:

-  main:

-    parent: layout

-next: /templates/ace

-prev: /templates/overview

-title: Go Template Primer

-weight: 15

-toc: true

----

-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for

-its template engine. It is an extremely lightweight engine that provides a very

-small amount of logic. In our experience it is just the right amount of

-logic to be able to create a good static website. If you have used other

-template systems from different languages or frameworks, you will find a lot of

-similarities in Go templates.

-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]

-go into more depth and cover features that aren't mentioned here.

-## Introduction to Go Templates

-Go templates provide an extremely simple template language. It adheres to the

-belief that only the most basic of logic belongs in the template or view layer.

-One consequence of this simplicity is that Go templates parse very quickly.

-A unique characteristic of Go templates is they are content aware. Variables and

-content will be sanitized depending on the context of where they are used. More

-details can be found in the [Go docs][gohtmltemplate].

-## Basic Syntax

-Go lang templates are HTML files with the addition of variables and

-functions.

-**Go variables and functions are accessible within {{ }}**

-Accessing a predefined variable "foo":

-    {{ foo }}

-**Parameters are separated using spaces**

-Calling the `add` function with input of 1, 2:

-    {{ add 1 2 }}

-**Methods and fields are accessed via dot notation**

-Accessing the Page Parameter "bar"

-    {{ .Params.bar }}

-**Parentheses can be used to group items together**

-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}

-## Variables

-Each Go template has a struct (object) made available to it. In Hugo, each

-template is passed page struct. More details are available on the

-[variables](/layout/variables/) page.

-A variable is accessed by referencing the variable name.

-    <title>{{ .Title }}</title>

-Variables can also be defined and referenced.

-    {{ $address := "123 Main St."}}

-    {{ $address }}

-## Functions

-Go template ships with a few functions which provide basic functionality. The Go

-template system also provides a mechanism for applications to extend the

-available functions with their own. [Hugo template

-functions](/layout/functions/) provide some additional functionality we believe

-are useful for building websites. Functions are called by using their name

-followed by the required parameters separated by spaces. Template

-functions cannot be added without recompiling Hugo.

-**Example 1: Adding numbers**

-    {{ add 1 2 }}

-**Example 2: Comparing numbers**

-    {{ lt 1 2 }}

-(There are more boolean operators, detailed in the

-[template documentation](http://golang.org/pkg/text/template/#hdr-Functions).)

-## Includes

-When including another template, you will pass to it the data it will be

-able to access. To pass along the current context, please remember to

-include a trailing dot. The templates location will always be starting at

-the /layout/ directory within Hugo.

-**Example:**

-    {{ template "partials/header.html" . }}

-And, starting with Hugo v0.12, you may also use the `partial` call

-for [partial templates](/templates/partials/):

-    {{ partial "header.html" . }}

-## Logic

-Go templates provide the most basic iteration and conditional logic.

-### Iteration

-Just like in Go, the Go templates make heavy use of `range` to iterate over

-a map, array or slice. The following are different examples of how to use

-range.

-**Example 1: Using Context**

-    {{ range array }}

-        {{ . }}

-    {{ end }}

-**Example 2: Declaring value variable name**

-    {{range $element := array}}

-        {{ $element }}

-    {{ end }}

-**Example 2: Declaring key and value variable name**

-    {{range $index, $element := array}}

-        {{ $index }}

-        {{ $element }}

-    {{ end }}

-### Conditionals

-`if`, `else`, `with`, `or` & `and` provide the framework for handling conditional

-logic in Go Templates. Like `range`, each statement is closed with `end`.

-Go Templates treat the following values as false:

-* false

-* 0

-* any array, slice, map, or string of length zero

-**Example 1: `if`**

-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}

-**Example 2: `if` … `else`**

-    {{ if isset .Params "alt" }}

-        {{ index .Params "alt" }}

-    {{else}}

-        {{ index .Params "caption" }}

-    {{ end }}

-**Example 3: `and` & `or`**

-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}

-**Example 4: `with`**

-An alternative way of writing "`if`" and then referencing the same value

-is to use "`with`" instead. `with` rebinds the context `.` within its scope,

-and skips the block if the variable is absent.

-The first example above could be simplified as:

-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}

-**Example 5: `if` … `else if`**

-    {{ if isset .Params "alt" }}

-        {{ index .Params "alt" }}

-    {{ else if isset .Params "caption" }}

-        {{ index .Params "caption" }}

-    {{ end }}

-## Pipes

-One of the most powerful components of Go templates is the ability to

-stack actions one after another. This is done by using pipes. Borrowed

-from Unix pipes, the concept is simple, each pipeline's output becomes the

-input of the following pipe.

-Because of the very simple syntax of Go templates, the pipe is essential

-to being able to chain together function calls. One limitation of the

-pipes is that they only can work with a single value and that value

-becomes the last parameter of the next pipeline.

-A few simple examples should help convey how to use the pipe.

-**Example 1:**

-    {{ shuffle (seq 1 5) }}

-is the same as

-    {{ (seq 1 5) | shuffle }}

-**Example 2:**

-    {{ index .Params "disqus_url" | html }}

-Access the page parameter called "disqus_url" and escape the HTML.

-The `index` function is a [Go][] built-in, and you can read about it [here][gostdlibpkgtexttemplate]. `index`:

-> ...returns the result of indexing its first argument by the following arguments. Thus "index x 1 2 3" is, in Go syntax, `x[1][2][3]`. Each indexed item must be a map, slice, or array.

-**Example 3:**

-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr") }}

-    Stuff Here

-    {{ end }}

-Could be rewritten as

-    {{ if isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" }}

-    Stuff Here

-    {{ end }}

-### Internet Explorer conditional comments using Pipes

-By default, Go Templates remove HTML comments from output. This has the unfortunate side effect of removing Internet Explorer conditional comments. As a workaround, use something like this:

-    {{ "<!--[if lt IE 9]>" | safeHTML }}

-      <script src="html5shiv.js"></script>

-    {{ "<![endif]-->" | safeHTML }}

-Alternatively, use the backtick (`` ` ``) to quote the IE conditional comments, avoiding the tedious task of escaping every double quotes (`"`) inside, as demonstrated in the [examples](http://golang.org/pkg/text/template/#hdr-Examples) in the Go text/template documentation, e.g.:

-```

-{{ `<!--[if lt IE 7]><html class="no-js lt-ie9 lt-ie8 lt-ie7"><![endif]-->` | safeHTML }}

-```

-## Context (a.k.a. the dot)

-The most easily overlooked concept to understand about Go templates is that `{{ . }}`

-always refers to the current context. In the top level of your template, this

-will be the data set made available to it. Inside of a iteration, however, it will have

-the value of the current item. When inside of a loop, the context has changed:

-`{{ . }}` will no longer refer to the data available to the entire page. If you need

-to

-access this from within the loop, you will likely want to do one of the following:

-1. Set it to a variable instead of depending on the context.  For example:

-        {{ $title := .Site.Title }}

-        {{ range .Params.tags }}

-          <li>

-            <a href="{{ $baseURL }}/tags/{{ . | urlize }}">{{ . }}</a>

-            - {{ $title }}

-          </li>

-        {{ end }}

-    Notice how once we have entered the loop the value of `{{ . }}` has changed. We

-    have defined a variable outside of the loop so we have access to it from within

-    the loop.

-2. Use `$.` to access the global context from anywhere.

-   Here is an equivalent example:

-        {{ range .Params.tags }}

-          <li>

-            <a href="{{ $baseURL }}/tags/{{ . | urlize }}">{{ . }}</a>

-            - {{ $.Site.Title }}

-          </li>

-        {{ end }}

-    This is because `$`, a special variable, is set to the starting value

-    of `.` the dot by default,

-    a [documented feature](http://golang.org/pkg/text/template/#hdr-Variables)

-    of Go text/template.  Very handy, eh?

-    > However, this little magic would cease to work if someone were to

-    > mischievously redefine `$`, e.g. `{{ $ := .Site }}`.

-    > *(No, don't do it!)*

-    > You may, of course, recover from this mischief by using `{{ $ := . }}`

-    > in a global context to reset `$` to its default value.

-## Whitespace

-Go 1.6 includes the ability to trim the whitespace from either side of a Go tag by including a hyphen (`-`) and space immediately beside the corresponding `{{` or `}}` delimiter.

-For instance, the following Go template:

-```html

-<div>

-  {{ .Title }}

-</div>

-```

-will include the newlines and horizontal tab in its HTML output:

-```html

-<div>

-  Hello, World!

-</div>

-```

-whereas using

-```html

-<div>

-  {{- .Title -}}

-</div>

-```

-in that case will output simply `<div>Hello, World!</div>`.

-Go considers the following characters as whitespace: space, horizontal tab, carriage return and newline.

-# Hugo Parameters

-Hugo provides the option of passing values to the template language

-through the site configuration (for sitewide values), or through the meta

-data of each specific piece of content. You can define any values of any

-type (supported by your front matter/config format) and use them however

-you want to inside of your templates.

-## Using Content (page) Parameters

-In each piece of content, you can provide variables to be used by the

-templates. This happens in the [front matter](/content/front-matter/).

-An example of this is used in this documentation site. Most of the pages

-benefit from having the table of contents provided. Sometimes the TOC just

-doesn't make a lot of sense. We've defined a variable in our front matter

-of some pages to turn off the TOC from being displayed.

-Here is the example front matter:

-```

----

-title: "Permalinks"

-lastmod: 2015-11-30

-date: "2013-11-18"

-aliases:

-  - "/doc/permalinks/"

-groups: ["extras"]

-groups_weight: 30

-notoc: true

----

-```

-Here is the corresponding code inside of the template:

-      {{ if not .Params.notoc }}

-        <div id="toc" class="well col-md-4 col-sm-6">

-        {{ .TableOfContents }}

-        </div>

-      {{ end }}

-## Using Site (config) Parameters

-In your top-level configuration file (e.g., `config.yaml`) you can define site

-parameters, which are values which will be available to you in partials.

-For instance, you might declare:

-```yaml

-params:

-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."

-  TwitterUser: "spf13"

-  SidebarRecentLimit: 5

-```

-Within a footer layout, you might then declare a `<footer>` which is only

-provided if the `CopyrightHTML` parameter is provided, and if it is given,

-you would declare it to be HTML-safe, so that the HTML entity is not escaped

-again.  This would let you easily update just your top-level config file each

-January 1st, instead of hunting through your templates.

-```

-{{if .Site.Params.CopyrightHTML}}<footer>

-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHTML}}</div>

-</footer>{{end}}

-```

-An alternative way of writing the "`if`" and then referencing the same value

-is to use "`with`" instead. With rebinds the context `.` within its scope,

-and skips the block if the variable is absent:

-```

-{{with .Site.Params.TwitterUser}}<span class="twitter">

-<a href="https://twitter.com/{{.}}" rel="author">

-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"

- alt="Twitter"></a>

-</span>{{end}}

-```

-Finally, if you want to pull "magic constants" out of your layouts, you can do

-so, such as in this example:

-```

-<nav class="recent">

-  <h1>Recent Posts</h1>

-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Pages}}

-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>

-  {{end}}</ul>

-</nav>

-```

-# Template example: Show only upcoming events

-Go allows you to do more than what's shown here.  Using Hugo's

-[`where`](/templates/functions/#where) function and Go built-ins, we can list

-only the items from `content/events/` whose date (set in the front matter) is in

-the future:

-    <h4>Upcoming Events</h4>

-    <ul class="upcoming-events">

-    {{ range where .Data.Pages.ByDate "Section" "events" }}

-      {{ if ge .Date.Unix .Now.Unix }}

-        <li><span class="event-type">{{ .Type | title }} —</span>

-          {{ .Title }}

-          on <span class="event-date">

-          {{ .Date.Format "2 January at 3:04pm" }}</span>

-          at {{ .Params.place }}

-        </li>

-      {{ end }}

-    {{ end }}

-[go]: http://golang.org/

-[gohtmltemplate]: http://golang.org/pkg/html/template/

-[gostdlibpkgtexttemplate]: http://golang.org/pkg/text/template/

--- a/content/templates/homepage.md

+++ b/content/templates/homepage.md

@@ -1,81 +1,81 @@

---

-aliases:

-- /layout/homepage/

-lastmod: 2015-08-04

-date: 2013-07-01

+title: Homepage Template

+linktitle: Homepage Template

+description: The homepage of a website is often formatted differently than the other pages. For this reason, Hugo makes it easy for you to define your new site's homepage as a unique template.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [homepage]

 menu:

-  main:

-    parent: layout

-next: /templates/terms

-notoc: true

-prev: /templates/list

-title: Homepage

-weight: 50

+  docs:

+    parent: "templates"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+aliases: [/layout/homepage/,/templates/homepage-template/]

+toc: true

---

-The home page of a website is often formatted differently than the other

-pages. In Hugo you can define your own homepage template.

+Homepage is a `Page` and therefore has all the [page variables][pagevars] and [site variables][sitevars] available for use.

-Homepage is a `Page` and have all the [page

-variables](/templates/variables/) and [site

-variables](/templates/variables/) available to use in the templates.

+{{% note "The Only Required Template" %}}

+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 %}}

-*This 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 when using a single page site.*

+## Homepage Template Lookup Order

-In addition to the standard page variables, the homepage has access to

-all site content accessible from `.Data.Pages`. Details on how to use the

-list of pages can be found in the [Lists Template](/templates/list/).

+The [lookup order][lookup] for the homepage template is as follows:

-Note that a home page can also have a content file with frontmatter,  see [Source Organization]({{< relref "overview/source-directory.md#content-for-home-page-and-other-list-pages" >}}).

+1. `/layouts/index.html`

+2. `/layouts/_default/list.html`

+3. `/themes/<THEME>/layouts/index.html`

+4. `/themes/<THEME>/layouts/_default/list.html`

-## Which Template will be rendered?

-Hugo uses a set of rules to figure out which template to use when

-rendering a specific page.

+## Add Content and Front Matter to the Homepage

-Hugo will use the following prioritized list. If a file isn’t present,

-then the next one in the list will be used. This enables you to craft

-specific layouts when you want to without creating more templates

-than necessary. For most sites, only the \_default file at the end of

-the list will be needed.

+The homepage, similar to other [list pages in Hugo][lists], accepts content and front matter from an `_index.md` file. This file should live at the root of your `content` folder (i.e., `content/_index.md`). You can then add body copy and metadata to your homepage the way you would any other content file.

-* /layouts/index.html

-* /layouts/\_default/list.html

-* /layouts/\_default/single.html

-* /themes/`THEME`/layouts/index.html

-* /themes/`THEME`/layouts/\_default/list.html

-* /themes/`THEME`/layouts/\_default/single.html

+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.

-## Example index.html

-This content template is used for [spf13.com](http://spf13.com/).

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

-It makes use of [partial templates](/templates/partials/) and uses a similar approach as a [List](/templates/list/).

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

-    <!DOCTYPE html>

-    <html class="no-js" lang="en-US" prefix="og: http://ogp.me/ns# fb: http://ogp.me/ns/fb#">

-    <head>

-        <meta charset="utf-8">

+## Example Homepage Template

-        {{ partial "meta.html" . }}

+The following is an example of a homepage template that uses [partial][partials], [base][] templates, and a content file at `content/_index.md` to populate the `{{.Title}}` and `{{Content}}` [page variables][pagevars].

-        <base href="{{ .Site.BaseURL }}">

-        <title>{{ .Site.Title }}</title>

-        <link rel="canonical" href="{{ .Permalink }}">

-        <link href="{{ .RSSLink }}" rel="alternate" type="application/rss+xml" title="{{ .Site.Title }}" />

-        {{ partial "head_includes.html" . }}

-    </head>

-    <body lang="en">

-    {{ partial "subheader.html" . }}

-    <section id="main">

+{{% code file="layouts/index.html" download="index.html" %}}

+```html

+{{ define "main" }}

+    <main aria-role="main">

+      <header class="homepage-header">

+        <h1>{{.Title}}</h1>

+        {{ with .Params.subtitle }}

+        <span class="subtitle">{{.}}</span>

+        {{ end }}

+      </header>

+      <div class="homepage-content">

+        <!-- Note that the content for index.html, as a sort of list page, will pull from content/_index.md -->

+        {{.Content}}

+      </div>

       <div>

+        <!-- Note that .Data.Pages is the equivalent of .Site.Pages on the homepage template. -->

         {{ range first 10 .Data.Pages }}

             {{ .Render "summary"}}

         {{ end }}

       </div>

-    </section>

+    </main>

+{{ end }}

+```

+{{% /code %}}

-    {{ partial "footer.html" . }}

+[base]: /templates/base/

+[contentorg]: /content-management/organization/

+[lists]: /templates/lists/

+[lookup]: /templates/lookup-order/

+[pagevars]: /variables/page/

+[partials]: /templates/partials/

+[sitevars]: /variables/site/

--- /dev/null

+++ b/content/templates/internal.md

@@ -1,0 +1,137 @@

+---

+title: Internal Templates

+linktitle: Internal Templates

+description: Hugo ships with a group of boilerplate templates that cover the most common use cases for static websites.

+date: 2017-03-06

+publishdate: 2017-03-06

+lastmod: 2017-03-06

+categories: [templates]

+#tags: [internal, analytics,]

+menu:

+  docs:

+    parent: "templates"

+    weight: 168

+weight: 168

+sections_weight: 168

+draft: false

+aliases: []

+toc: true

+wip: true

+---

+<!-- reference: https://discourse.gohugo.io/t/lookup-order-for-partials/5705/6

+code: https://github.com/gohugoio/hugo/blob/e445c35d6a0c7f5fc2f90f31226cd1d46e048bbc/tpl/template_embedded.go#L147 -->

+{{% warning %}}

+While the following internal templates are called similar to partials, they do *not* observe the partial template lookup order.

+{{% /warning %}}

+## Google Analytics

+Hugo ships with internal templates for Google Analytics tracking, including both synchronous and asynchronous tracking codes.

+### Configure Google Analytics

+Provide your tracking id in your configuration file:

+```toml

+googleAnalytics = "UA-123-45"

+```

+```yml

+googleAnalytics: "UA-123-45"

+```

+### Use the Google Analytics Template

+You can then include the Google Analytics internal template:

+```golang

+{{ template "_internal/google_analytics.html" . }}

+```

+```golang

+{{ template "_internal/google_analytics_async.html" . }}

+```

+## Disqus

+Hugo also ships with an internal template for [Disqus comments][disqus], a popular commenting system for both static and dynamic websites. In order to effectively use Disqus, you will need to secure a Disqus "shortname" by [signing up for the free service][disqussignup].

+### Configure Disqus

+To use Hugo's Disqus template, you first need to set a single value in your site's `config.toml` or `config.yml`:

+```toml

+disqusShortname = "yourdiscussshortname"

+```

+```yaml

+disqusShortname: "yourdiscussshortname"

+```

+You also have the option to set the following in the front matter for a given piece of content:

+* `disqus_identifier`

+* `disqus_title`

+* `disqus_url`

+### Use the Disqus Template

+To add Disqus, include the following line in templates where you want your comments to appear:

+```golang

+{{ template "_internal/disqus.html" . }}

+```

+### Conditional Loading of Disqus Comments

+Users have noticed that enabling Disqus comments when running the Hugo web server on `localhost` (i.e. via `hugo server`) causes the creation of unwanted discussions on the associated Disqus account.

+You can create the following `layouts/partials/disqus.html`:

+{{% code file="layouts/partials/disqus.html" download="disqus.html" %}}

+```html

+<div id="disqus_thread"></div>

+<script type="text/javascript">

+(function() {

+    // Don't ever inject Disqus on localhost--it creates unwanted

+    // discussions from 'localhost:1313' on your Disqus account...

+    if (window.location.hostname == "localhost")

+        return;

+    var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;

+    var disqus_shortname = '{{ .Site.DisqusShortname }}';

+    dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';

+    (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);

+})();

+</script>

+<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>

+<a href="http://disqus.com/" class="dsq-brlink">comments powered by <span class="logo-disqus">Disqus</span></a>

+```

+{{% /code %}}

+The `if` statement skips the initialization of the Disqus comment injection when you are running on `localhost`.

+You can then render your custom Disqus partial template as follows:

+```golang

+{{ partial "disqus.html" . }}

+```

+```

+_internal/_default/robots.txt

+_internal/_default/rss.xml

+_internal/_default/sitemap.xml

+_internal/_default/sitemapindex.xml

+_internal/disqus.html

+_internal/google_news.html

+_internal/google_analytics.html

+_internal/google_analytics_async.html

+_internal/opengraph.html

+_internal/pagination.html

+_internal/schema.html

+_internal/twitter_cards.html

+```

--- /dev/null

+++ b/content/templates/introduction.md

@@ -1,0 +1,498 @@

+---

+title: Introduction to Hugo Templating

+linktitle: Introduction

+description: Hugo uses Go's `html/template` and `text/template` libraries as the basis for the templating.

+godocref: https://golang.org/pkg/html/template/

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-25

+categories: [templates,fundamentals]

+#tags: [go]

+menu:

+  docs:

+    parent: "templates"

+    weight: 10

+weight: 10

+sections_weight: 10

+draft: false

+aliases: [/templates/introduction/,/layouts/introduction/,/layout/introduction/, /templates/go-templates/]

+toc: true

+---

+{{% note %}}

+The following is only a primer on Go templates. For an in-depth look into Go templates, check the official [Go docs](http://golang.org/pkg/html/template/).

+{{% /note %}}

+Go templates provide an extremely simple template language that adheres to the belief that only the most basic of logic belongs in the template or view layer.

+## Basic Syntax

+Golang templates are HTML files with the addition of [variables][variables] and [functions][functions]. Golang template variables and functions are accessible within `{{ }}`.

+### Access a Predefined Variable

+```golang

+{{ foo }}

+```

+Parameters for functions are separated using spaces. The following example calls the `add` function with inputs of `1` and `2`:

+```golang

+{{ add 1 2 }}

+```

+#### Methods and Fields are Accessed via dot Notation

+Accessing the Page Parameter `bar` defined in a piece of content's [front matter][].

+```golang

+{{ .Params.bar }}

+```

+#### Parentheses Can be Used to Group Items Together

+```golang

+{{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}

+```

+## Variables

+Each Go template gets a data object. In Hugo, each template is passed a `Page`. See [variables][] for more information.

+This is how you access a `Page` variable from a template:

+```golang

+<title>{{ .Title }}</title>

+```

+Values can also be stored in custom variables and referenced later:

+```golang

+{{ $address := "123 Main St."}}

+{{ $address }}

+```

+{{% warning %}}

+Variables defined inside `if` conditionals and similar are not visible on the outside. See [https://github.com/golang/go/issues/10608](https://github.com/golang/go/issues/10608).

+Hugo has created a workaround for this issue in [Scratch](/functions/scratch).

+{{% /warning %}}

+## Functions

+Go templates only ship with a few basic functions but also provide a mechanism for applications to extend the original set.

+[Hugo template functions][functions] provide additional functionality specific to building websites. Functions are called by using their name followed by the required parameters separated by spaces. Template functions cannot be added without recompiling Hugo.

+### Example 1: Adding Numbers

+```golang

+{{ add 1 2 }}

+=> 3

+```

+### Example 2: Comparing Numbers

+```golang

+{{ lt 1 2 }}

+=> true (i.e., since 1 is less than 2)

+```

+Note that both examples make us of Go template's [math functions][].

+{{% note "Additional Boolean Operators" %}}

+There are more boolean operators than those listed in the Hugo docs in the [Golang template documentation](http://golang.org/pkg/text/template/#hdr-Functions).

+{{% /note %}}

+## Includes

+When including another template, you will pass to it the data it will be

+able to access. To pass along the current context, please remember to

+include a trailing dot. The templates location will always be starting at

+the `/layout/` directory within Hugo.

+### Template and Partial Examples

+```golang

+{{ template "partials/header.html" . }}

+```

+Starting with Hugo v0.12, you may also use the `partial` call

+for [partial templates][partials]:

+```golang

+{{ partial "header.html" . }}

+```

+## Logic

+Go templates provide the most basic iteration and conditional logic.

+### Iteration

+Just like in Go, the Go templates make heavy use of `range` to iterate over

+a map, array, or slice. The following are different examples of how to use

+range.

+#### Example 1: Using Context

+```golang

+{{ range array }}

+    {{ . }}

+{{ end }}

+```

+#### Example 2: Declaring Value => Variable name

+```golang

+{{range $element := array}}

+    {{ $element }}

+{{ end }}

+```

+#### Example 3: Declaring Key-Value Variable Name

+```golang

+{{range $index, $element := array}}

+   {{ $index }}

+   {{ $element }}

+{{ end }}

+```

+### Conditionals

+`if`, `else`, `with`, `or`, and `and` provide the framework for handling conditional logic in Go Templates. Like `range`, each statement is closed with an `{{end}}`.

+Go Templates treat the following values as false:

+* false

+* 0

+* any zero-length array, slice, map, or string

+#### Example 1: `if`

+```golang

+{{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}

+```

+#### Example 2: `if` … `else`

+```golang

+{{ if isset .Params "alt" }}

+    {{ index .Params "alt" }}

+{{else}}

+    {{ index .Params "caption" }}

+{{ end }}

+```

+#### Example 3: `and` & `or`

+```golang

+{{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}

+```

+#### Example 4: `with`

+An alternative way of writing "`if`" and then referencing the same value

+is to use "`with`" instead. `with` rebinds the context `.` within its scope

+and skips the block if the variable is absent.

+The first example above could be simplified as:

+```golang

+{{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}

+```

+#### Example 5: `if` … `else if`

+```golang

+{{ if isset .Params "alt" }}

+    {{ index .Params "alt" }}

+{{ else if isset .Params "caption" }}

+    {{ index .Params "caption" }}

+{{ end }}

+```

+## Pipes

+One of the most powerful components of Go templates is the ability to stack actions one after another. This is done by using pipes. Borrowed from Unix pipes, the concept is simple: each pipeline's output becomes the input of the following pipe.

+Because of the very simple syntax of Go templates, the pipe is essential to being able to chain together function calls. One limitation of the pipes is that they can only work with a single value and that value becomes the last parameter of the next pipeline.

+A few simple examples should help convey how to use the pipe.

+### Example 1: `shuffle`

+The following two examples are functionally the same:

+```golang

+{{ shuffle (seq 1 5) }}

+```

+```golang

+{{ (seq 1 5) | shuffle }}

+```

+### Example 2: `index`

+The following accesses the page parameter called "disqus_url" and escapes the HTML. This example also uses the [`index` function][index], which is built into Go templates:

+```golang

+{{ index .Params "disqus_url" | html }}

+```

+### Example 3: `or` with `isset`

+```golang

+{{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr") }}

+Stuff Here

+{{ end }}

+```

+Could be rewritten as

+```golang

+{{ if isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" }}

+Stuff Here

+{{ end }}

+```

+### Example 4: Internet Explorer Conditional Comments

+By default, Go Templates remove HTML comments from output. This has the unfortunate side effect of removing Internet Explorer conditional comments. As a workaround, use something like this:

+```golang

+{{ "<!--[if lt IE 9]>" | safeHTML }}

+  <script src="html5shiv.js"></script>

+{{ "<![endif]-->" | safeHTML }}

+```

+Alternatively, you can use the backtick (`` ` ``) to quote the IE conditional comments, avoiding the tedious task of escaping every double quotes (`"`) inside, as demonstrated in the [examples](http://golang.org/pkg/text/template/#hdr-Examples) in the Go text/template documentation:

+```

+{{ `<!--[if lt IE 7]><html class="no-js lt-ie9 lt-ie8 lt-ie7"><![endif]-->` | safeHTML }}

+```

+## Context (aka "the dot")

+The most easily overlooked concept to understand about Go templates is that `{{ . }}` always refers to the current context. In the top level of your template, this will be the data set made available to it. Inside of an iteration, however, it will have the value of the current item in the loop; i.e., `{{ . }}` will no longer refer to the data available to the entire page. If you need to access page-level data (e.g., page params set in front matter) from within the loop, you will likely want to do one of the following:

+### 1. Define a Variable Independent of Context

+The following shows how to define a variable independent of the context.

+{{% code file="tags-range-with-page-variable.html" %}}

+```html

+{{ $title := .Site.Title }}

+<ul>

+{{ range .Params.tags }}

+    <li>

+        <a href="/tags/{{ . | urlize }}">{{ . }}</a>

+        - {{ $title }}

+    </li>

+{{ end }}

+</ul>

+```

+{{% /code %}}

+{{% note %}}

+Notice how once we have entered the loop (i.e. `range`), the value of `{{ . }}` has changed. We have defined a variable outside of the loop (`{{$title}}`) that we've assigned a value so that we have access to the value from within the loop as well.

+{{% /note %}}

+### 2. Use `$.` to Access the Global Context

+`$` has special significance in your templates. `$` is set to the starting value of `.` ("the dot") by default. This is a [documented feature of Go text/template][dotdoc]. This means you have access to the global context from anywhere. Here is an equivalent example of the preceding code block but now using `$` to grab `.Site.Title` from the global context:

+{{% code file="range-through-tags-w-global.html" %}}

+```hbs

+<ul>

+{{ range .Params.tags }}

+  <li>

+    <a href="/tags/{{ . | urlize }}">{{ . }}</a>

+            - {{ $.Site.Title }}

+  </li>

+{{ end }}

+</ul>

+```

+{{% /code %}}

+{{% warning "Don't Redefine the Dot" %}}

+The built-in magic of `$` would cease to work if someone were to mischievously redefine the special character; e.g. `{{ $ := .Site }}`. *Don't do it.* You may, of course, recover from this mischief by using `{{ $ := . }}` in a global context to reset `$` to its default value.

+{{% /warning %}}

+## Whitespace

+Go 1.6 includes the ability to trim the whitespace from either side of a Go tag by including a hyphen (`-`) and space immediately beside the corresponding `{{` or `}}` delimiter.

+For instance, the following Go template will include the newlines and horizontal tab in its HTML output:

+```html

+<div>

+  {{ .Title }}

+</div>

+```

+Which will output:

+```html

+<div>

+  Hello, World!

+</div>

+```

+Leveraging the `-` in the following example will remove the extra white space surrounding the `.Title` variable and remove the newline:

+```html

+<div>

+  {{- .Title -}}

+</div>

+```

+Which then outputs:

+```html

+<div>Hello, World!</div>

+```

+Go considers the following characters whitespace:

+* <kbd>space</kbd>

+* horizontal <kbd>tab</kbd>

+* carriage <kbd>return</kbd>

+* newline

+## Hugo Parameters

+Hugo provides the option of passing values to your template layer through your [site configuration][config] (i.e. for site-wide values) or through the metadata of each specific piece of content (i.e. the [front matter][]). You can define any values of any type and use them however you want in your templates, as long as the values are supported by the front matter format specified via `metaDataFormat` in your configuration file.

+## Use Content (`Page`) Parameters

+You can provide variables to be used by templates in individual content's [front matter][].

+An example of this is used in the Hugo docs. Most of the pages benefit from having the table of contents provided, but sometimes the table of contents doesn't make a lot of sense. We've defined a `notoc` variable in our front matter that will prevent a table of contents from rendering when specifically set to `true`.

+Here is the example front matter:

+```yaml

+---

+title: Roadmap

+lastmod: 2017-03-05

+date: 2013-11-18

+notoc: true

+---

+```

+Here is an example of corresponding code that could be used inside a `toc.html` [partial template][partials]:

+{{% code file="layouts/partials/toc.html" download="toc.html" %}}

+```html

+{{ if not .Params.notoc }}

+<aside>

+  <header>

+    <a href="#{{.Title | urlize}}">

+    <h3>{{.Title}}</h3>

+    </a>

+  </header>

+  {{.TableOfContents}}

+</aside>

+<a href="#" id="toc-toggle"></a>

+{{end}}

+```

+{{% /code %}}

+We want the *default* behavior to be for pages to include a TOC unless otherwise specified. This template checks to make sure that the `notoc:` field in this page's front matter is not `true`.

+## Use Site Configuration Parameters

+You can arbitrarily define as many site-level parameters as you want in your [site's configuration file][config]. These parameters are globally available in your templates.

+For instance, you might declare the following:

+{{% code file="config.yaml" %}}

+```yaml

+params:

+  copyrighthtml: "Copyright &#xA9; 2017 John Doe. All Rights Reserved."

+  twitteruser: "spf13"

+  sidebarrecentlimit: 5

+```

+{{% /code %}}

+Within a footer layout, you might then declare a `<footer>` that is only rendered if the `copyrighthtml` parameter is provided. If it *is* provided, you will then need to declare the string is safe to use via the [`safeHTML` function][safehtml] so that the HTML entity is not escaped again. This would let you easily update just your top-level config file each January 1st, instead of hunting through your templates.

+```html

+{{if .Site.Params.copyrighthtml}}<footer>

+<div class="text-center">{{.Site.Params.CopyrightHTML | safeHTML}}</div>

+</footer>{{end}}

+```

+An alternative way of writing the "`if`" and then referencing the same value is to use [`with`][with] instead. `with` rebinds the context (`.`) within its scope and skips the block if the variable is absent:

+{{% code file="layouts/partials/twitter.html" %}}

+```html

+{{with .Site.Params.twitteruser}}

+<div>

+  <a href="https://twitter.com/{{.}}" rel="author">

+  <img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}" alt="Twitter"></a>

+</div>

+{{end}}

+```

+{{% /code %}}

+Finally, you can pull "magic constants" out of your layouts as well. The following uses the [`first`][first] function, as well as the [`.RelPermalink`][relpermalink] page variable and the [`.Site.Pages`][sitevars] site variable.

+```html

+<nav>

+  <h1>Recent Posts</h1>

+  <ul>

+  {{- range first .Site.Params.SidebarRecentLimit .Site.Pages -}}

+    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>

+  {{- end -}}

+  </ul>

+</nav>

+```

+## Example: Show Only Upcoming Events

+Go allows you to do more than what's shown here. Using Hugo's [`where` function][where] and Go built-ins, we can list only the items from `content/events/` whose date (set in a content file's [front matter][]) is in the future. The following is an example [partial template][partials]:

+{{% code file="layouts/partials/upcoming-events.html" download="upcoming-events.html" %}}

+```html

+<h4>Upcoming Events</h4>

+<ul class="upcoming-events">

+{{ range where .Data.Pages.ByDate "Section" "events" }}

+  {{ if ge .Date.Unix .Now.Unix }}

+    <li>

+    <!-- add span for event type -->

+      <span>{{ .Type | title }} —</span>

+      {{ .Title }} on

+    <!-- add span for event date -->

+      <span>{{ .Date.Format "2 January at 3:04pm" }}</span>

+      at {{ .Params.place }}

+    </li>

+  {{ end }}

+{{ end }}

+</ul>

+```

+{{% /code %}}

+[`where` function]: /functions/where/

+[config]: /getting-started/configuration/

+[dotdoc]: http://golang.org/pkg/text/template/#hdr-Variables

+[first]: /functions/first/

+[front matter]: /content-management/front-matter/

+[functions]: /functions/ "See the full list of Hugo's templating functions with a quick start reference guide and basic and advanced examples."

+[Go html/template]: http://golang.org/pkg/html/template/ "Godocs references for Golang's html templating"

+[gohtmltemplate]: http://golang.org/pkg/html/template/ "Godocs references for Golang's html templating"

+[index]: /functions/index/

+[math functions]: /functions/math/

+[partials]: /templates/partials/ "Link to the partial templates page inside of the templating section of the Hugo docs"

+[relpermalink]: /variables/page/

+[safehtml]: /functions/safehtml/

+[sitevars]: /variables/site/

+[variables]: /variables/ "See the full extent of page-, site-, and other variables that Hugo make available to you in your templates."

+[where]: /functions/where/

+[with]: /functions/with/

+[godocsindex]: http://golang.org/pkg/text/template/ "Godocs page for index function"

--- a/content/templates/list.md

+++ /dev/null

@@ -1,437 +1,0 @@

----

-aliases:

-- /layout/indexes/

-lastmod: 2015-08-04

-date: 2013-07-01

-linktitle: List of Content

-menu:

-  main:

-    parent: layout

-next: /templates/homepage

-prev: /templates/content

-title: Content List Template

-weight: 40

-toc: true

----

-A list template is any template that will be used to render multiple pieces of

-content in a single HTML page (with the exception of the [homepage](/layout/homepage/) which has a

-dedicated template).

-We are using the term list in its truest sense, a sequential arrangement

-of material, especially in alphabetical or numerical order. Hugo uses

-list templates to render anyplace where content is being listed such as

-taxonomies and sections.

-## Which Template will be rendered?

-Hugo uses a set of rules to figure out which template to use when

-rendering a specific page.

-Hugo will use the following prioritized list. If a file isn’t present,

-then the next one in the list will be used. This enables you to craft

-specific layouts when you want to without creating more templates

-than necessary. For most sites only the \_default file at the end of

-the list will be needed.

-### Section Lists

-A Section will be rendered at /`SECTION`/ (e.g.&nbsp;http://spf13.com/project/)

-* /layouts/section/`SECTION`.html

-*  /layouts/`SECTION`/list.html

-* /layouts/\_default/section.html

-* /layouts/\_default/list.html

-* /themes/`THEME`/layouts/section/`SECTION`.html

-* /themes/`THEME`/layouts/`SECTION`/list.html

-* /themes/`THEME`/layouts/\_default/section.html

-* /themes/`THEME`/layouts/\_default/list.html

-Note that a sections list page can also have a content file with frontmatter,  see [Source Organization]({{< relref "overview/source-directory.md#content-for-home-page-and-other-list-pages" >}}).

-### Taxonomy Lists

-A Taxonomy will be rendered at /`PLURAL`/`TERM`/ (e.g.&nbsp;http://spf13.com/topics/golang/) from:

-* /layouts/taxonomy/`SINGULAR`.html (e.g.&nbsp;`/layouts/taxonomy/topic.html`)

-* /layouts/\_default/taxonomy.html

-* /layouts/\_default/list.html

-* /themes/`THEME`/layouts/taxonomy/`SINGULAR`.html

-* /themes/`THEME`/layouts/\_default/taxonomy.html

-* /themes/`THEME`/layouts/\_default/list.html

-Note that a taxonomy list page can also have a content file with frontmatter,  see [Source Organization]({{< relref "overview/source-directory.md#content-for-home-page-and-other-list-pages" >}}).

-### Section RSS

-A Section’s RSS will be rendered at /`SECTION`/index.xml (e.g.&nbsp;http://spf13.com/project/index.xml)

-*Hugo ships with its own [RSS 2.0][] template. In most cases this will

-be sufficient, and an RSS template will not need to be provided by the

-user.*

-Hugo provides the ability for you to define any RSS type you wish, and

-can have different RSS files for each section and taxonomy.

-* /layouts/section/`SECTION`.rss.xml

-* /layouts/\_default/rss.xml

-* /themes/`THEME`/layouts/section/`SECTION`.rss.xml

-* /themes/`THEME`/layouts/\_default/rss.xml

-### Taxonomy RSS

-A Taxonomy’s RSS will be rendered at /`PLURAL`/`TERM`/index.xml (e.g.&nbsp;http://spf13.com/topics/golang/index.xml)

-*Hugo ships with its own [RSS 2.0][] template. In most cases this will

-be sufficient, and an RSS template will not need to be provided by the

-user.*

-Hugo provides the ability for you to define any RSS type you wish, and

-can have different RSS files for each section and taxonomy.

-* /layouts/taxonomy/`SINGULAR`.rss.xml

-* /layouts/\_default/rss.xml

-* /themes/`THEME`/layouts/taxonomy/`SINGULAR`.rss.xml

-* /themes/`THEME`/layouts/\_default/rss.xml

-## Variables

-A list page is a `Page` and have all the [page variables](/templates/variables/)

-and [site variables](/templates/variables/) available to use in the templates.

-Taxonomy pages will additionally have:

-**.Data.`Singular`** The taxonomy itself.<br>

-## Example List Template Pages

-### Example section template (post.html)

-This content template is used for [spf13.com](http://spf13.com/).

-It makes use of [partial templates](/templates/partials/). All examples use a

-[view](/templates/views/) called either "li" or "summary" which this example site

-defined.

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    <section id="main">

-      <div>

-       <h1 id="title">{{ .Title }}</h1>

-            <ul id="list">

-                {{ range .Data.Pages }}

-                    {{ .Render "li"}}

-                {{ end }}

-            </ul>

-      </div>

-    </section>

-    {{ partial "footer.html" . }}

-### Example taxonomy template (tag.html)

-This content template is used for [spf13.com](http://spf13.com/).

-It makes use of [partial templates](/templates/partials/). All examples use a

-[view](/templates/views/) called either "li" or "summary" which this example site

-defined.

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    <section id="main">

-      <div>

-       <h1 id="title">{{ .Title }}</h1>

-        {{ range .Data.Pages }}

-            {{ .Render "summary"}}

-        {{ end }}

-      </div>

-    </section>

-    {{ partial "footer.html" . }}

-## Ordering Content

-In the case of Hugo, each list will render the content based on metadata provided in the [front

-matter](/content/front-matter/). See [ordering content](/content/ordering/) for more information.

-Here are a variety of different ways you can order the content items in

-your list templates:

-### Order by Weight -> Date (default)

-    {{ range .Data.Pages }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by Weight -> Date

-    {{ range .Data.Pages.ByWeight }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by Date

-    {{ range .Data.Pages.ByDate }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by PublishDate

-    {{ range .Data.Pages.ByPublishDate }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .PublishDate.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by ExpiryDate

-    {{ range .Data.Pages.ByExpiryDate }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .ExpiryDate.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by Lastmod

-    {{ range .Data.Pages.ByLastmod }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by Length

-    {{ range .Data.Pages.ByLength }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by Title

-    {{ range .Data.Pages.ByTitle }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by LinkTitle

-    {{ range .Data.Pages.ByLinkTitle }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .LinkTitle }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-### Order by Parameter

-Order based on the specified frontmatter parameter. Pages without that

-parameter will use the site's `.Site.Params` default. If the parameter is not

-found at all in some entries, those entries will appear together at the end

-of the ordering.

-The below example sorts a list of posts by their rating.

-    {{ range (.Data.Pages.ByParam "rating") }}

-      <!-- ... -->

-    {{ end }}

-If the frontmatter field of interest is nested beneath another field, you can

-also get it:

-    {{ range (.Data.Pages.ByParam "author.last_name") }}

-      <!-- ... -->

-    {{ end }}

-### Reverse Order

-Can be applied to any of the above. Using Date for an example.

-    {{ range .Data.Pages.ByDate.Reverse }}

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-    {{ end }}

-## Grouping Content

-Hugo provides some grouping functions for list pages. You can use them to

-group pages by Section, Type, Date etc.

-Here are a variety of different ways you can group the content items in

-your list templates:

-### Grouping by Page field

-    {{ range .Data.Pages.GroupBy "Section" }}

-    <h3>{{ .Key }}</h3>

-    <ul>

-        {{ range .Pages }}

-        <li>

-        <a href="{{ .Permalink }}">{{ .Title }}</a>

-        <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-        </li>

-        {{ end }}

-    </ul>

-    {{ end }}

-### Grouping by Page date

-    {{ range .Data.Pages.GroupByDate "2006-01" }}

-    <h3>{{ .Key }}</h3>

-    <ul>

-        {{ range .Pages }}

-        <li>

-        <a href="{{ .Permalink }}">{{ .Title }}</a>

-        <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-        </li>

-        {{ end }}

-    </ul>

-    {{ end }}

-### Grouping by Page publish date

-    {{ range .Data.Pages.GroupByPublishDate "2006-01" }}

-    <h3>{{ .Key }}</h3>

-    <ul>

-        {{ range .Pages }}

-        <li>

-        <a href="{{ .Permalink }}">{{ .Title }}</a>

-        <div class="meta">{{ .PublishDate.Format "Mon, Jan 2, 2006" }}</div>

-        </li>

-        {{ end }}

-    </ul>

-    {{ end }}

-### Grouping by Page param

-    {{ range .Data.Pages.GroupByParam "param_key" }}

-    <h3>{{ .Key }}</h3>

-    <ul>

-        {{ range .Pages }}

-        <li>

-        <a href="{{ .Permalink }}">{{ .Title }}</a>

-        <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-        </li>

-        {{ end }}

-    </ul>

-    {{ end }}

-### Grouping by Page param in date format

-    {{ range .Data.Pages.GroupByParamDate "param_key" "2006-01" }}

-    <h3>{{ .Key }}</h3>

-    <ul>

-        {{ range .Pages }}

-        <li>

-        <a href="{{ .Permalink }}">{{ .Title }}</a>

-        <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-        </li>

-        {{ end }}

-    </ul>

-    {{ end }}

-### Reversing Key Order

-The ordering of the groups is performed by keys in alphanumeric order (A–Z,

-1–100) and in reverse chronological order (newest first) for dates.

-While these are logical defaults, they are not always the desired order. There

-are two different syntaxes to change the order; they both work the same way, so

-it’s really just a matter of preference.

-#### Reverse method

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

-    ...

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

-    ...

-#### Providing the (alternate) direction

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

-    ...

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

-    ...

-### Ordering Pages within Group

-Because Grouping returns a key and a slice of pages, all of the ordering methods listed above are available.

-In this example, I’ve ordered the groups in chronological order and the content

-within each group in alphabetical order by title.

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

-    <h3>{{ .Key }}</h3>

-    <ul>

-        {{ range .Pages.ByTitle }}

-        <li>

-        <a href="{{ .Permalink }}">{{ .Title }}</a>

-        <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-        </li>

-        {{ end }}

-    </ul>

-    {{ end }}

-## Filtering & Limiting 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 like the `limit` keyword in SQL. It reduces the array to only the

-first _N_ elements. It takes the array and number of elements as input.

-    {{ range first 10 .Data.Pages }}

-        {{ .Render "summary" }}

-    {{ end }}

-### `where`

-`where` works in a similar manner to the `where` keyword in SQL. It selects all

-elements of the slice that match the provided field and value. It takes three

-arguments: 'array or slice of maps or structs', 'key or field name' and 'match

-value'.

-    {{ range where .Data.Pages "Section" "post" }}

-       {{ .Content }}

-    {{ end }}

-### `first` & `where` Together

-Using both together can be very powerful.

-    {{ range first 5 (where .Data.Pages "Section" "post") }}

-       {{ .Content }}

-    {{ end }}

-If `where` or `first` receives invalid input or a field name that doesn’t exist,

-it will return an error and stop site generation.

-These are both template functions and work on not only

-[lists](/templates/list/), but [taxonomies](/taxonomies/displaying/),

-[terms](/templates/terms/) and [groups](/templates/list/).

-[RSS 2.0]: http://cyber.law.harvard.edu/rss/rss.html "RSS 2.0 Specification"

--- /dev/null

+++ b/content/templates/lists.md

@@ -1,0 +1,651 @@

+---

+title: Lists of Content in Hugo

+linktitle: List Page Templates

+description: Lists have a specific meaning and usage in Hugo when it comes to rendering your site homepage, section page, taxonomy list, or taxonomy terms list.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [lists,sections,rss,taxonomies,terms]

+menu:

+  docs:

+    parent: "templates"

+    weight: 22

+weight: 22

+sections_weight: 22

+draft: false

+aliases: [/templates/list/,/layout/indexes/]

+toc: true

+---

+## What is a List Page Template?

+A list page template is a template used to render multiple pieces of content in a single HTML page. The exception to this rule is the homepage, which is still a list but has its own [dedicated template][homepage].

+Hugo uses the term *list* in its truest sense; i.e. a sequential arrangement of material, especially in alphabetical or numerical order. Hugo uses list templates on any output HTML page where content is traditionally listed:

+* [Taxonomy terms pages][taxterms]

+* [Taxonomy list pages][taxlists]

+* [Section list pages][sectiontemps]

+* [RSS][rss]

+The idea of a list page comes from the [hierarchical mental model of the web][mentalmodel] and is best demonstrated visually:

+![Image demonstrating a hierarchical website sitemap.](/images/site-hierarchy.svg)

+## List Defaults

+### Default Templates

+Since section lists and taxonomy lists (N.B., *not* [taxonomy terms lists][taxterms]) are both *lists* with regards to their templates, both have the same terminating default of `_default/list.html` or `themes/<THEME>/layouts/_default/list.html` in their lookup order. In addition, both [section lists][sectiontemps] and [taxonomy lists][taxlists] have their own default list templates in `_default`:

+#### Default Section Templates

+1. `layouts/_default/section.html`

+2. `layouts/_default/list.html`

+#### Default Taxonomy List Templates

+1. `layouts/_default/taxonomy.html`

+2. `themes/<THEME>/layouts/_default/taxonomy.html`

+## Add Content and Front Matter to List Pages

+Since v0.18, [everything in Hugo is a `Page`][bepsays]. This means list pages and the homepage can have associated content files (i.e. `_index.md`) that contain page metadata (i.e., front matter) and content.

+This new model allows you to include list-specific front matter via `.Params` and also means that list templates (e.g., `layouts/_default/list.html`) have access to all [page variables][pagevars].

+{{% note %}}

+It is important to note that all `_index.md` content files will render according to a *list* template and not according to a [single page template](/templates/single-page-templates/).

+{{% /note %}}

+### Example Project Directory

+The following is an example of a typical Hugo project directory's content:

+```bash

+.

+...

+├── content

+|   ├── post

+|   |   ├── _index.md

+|   |   ├── post-01.md

+|   |   └── post-02.md

+|   └── quote

+|   |   ├── quote-01.md

+|   |   └── quote-02.md

+...

+```

+Using the above example, let's assume you have the following in `content/post/_index.md`:

+{{% code file="content/post/_index.md" %}}

+```yaml

+---

+title: My Golang Journey

+date: 2017-03-23

+publishdate: 2017-03-24

+---

+I decided to start learning Golang in March 2017.

+Follow my journey through this new blog.

+```

+{{% /code %}}

+You can now access this `_index.md`'s' content in your list template:

+{{% code file="layouts/_default/list.html" download="list.html" %}}

+```html

+{{ define "main" }}

+<main>

+    <article>

+        <header>

+            <h1>{{.Title}}</h1>

+        </header>

+        <!-- "{{.Content}}" pulls from the markdown content of the corresponding _inde.xmd -->

+        {{.Content}}

+    </article>

+    <ul>

+    <!-- Ranges through content/post/*.md -->

+    {{ range .Data.Pages }}

+        <li>

+            <a href="{{.Permalink}}">{{.Date.Format "2006-01-02"}} | {{.Title}}</a

+        </li>

+    {{ end }}

+    </ul>

+</main>

+{{ end }}

+```

+{{% /code %}}

+This above will output the following HTML:

+{{% code file="yoursite.com/post/index.html" copy="false" %}}

+```html

+<!--top of your baseof code-->

+<main>

+    <article>

+        <header>

+            <h1>My Golang Journey</h1>

+        </header>

+        <p>I decided to start learning Golang in March 2017.</p>

+        <p>Follow my journey through this new blog.</p>

+    </article>

+    <ul>

+        <li><a href="/post/post-01/">Post 1</a></li>

+        <li><a href="/post/post-02/">Post 2</a></li>

+    </ul>

+</main>

+<!--bottom of your baseof-->

+```

+{{% /code %}}

+### List Pages Without `_index.md`

+You do *not* have to create an `_index.md` file for every list page (i.e. section, taxonomy, taxonomy terms, etc) or the homepage. If Hugo does not find an `_index.md` within the respective content section when rendering a list template, the page will be created but with no `{{.Content}}` and only the default values for `.Title` etc.

+Using this same `layouts/_default/list.html` template and applying it to the the `quotes` section above will render the following output. Note that `quotes` does not have an `_index.md` file to pull from:

+{{% code file="yoursite.com/quote/index.html" copy="false" %}}

+```html

+<!--baseof-->

+<main>

+    <article>

+        <header>

+        <!-- Hugo assumes that .Title is the name of the section since there is no _index.md content file from which to pull a "title:" field -->

+            <h1>Quotes</h1>

+        </header>

+    </article>

+    <ul>

+        <li><a href="https://yoursite.com/quote/quotes-01/">Quote 1</a></li>

+        <li><a href="https://yoursite.com/quote/quotes-02/">Quote 2</a></li>

+    </ul>

+</main>

+<!--baseof-->

+```

+{{% /code %}}

+{{% note %}}

+The default behavior of Hugo is to pluralize list titles; hence the inflection of the `quote` section to "Quotes" when called with the `.Title` [page variable](/variables/page/). You can change this via the `pluralizeListTitles` directive in your [site configuration](/getting-started/configuration/).

+{{% /note %}}

+## Example List Templates

+### Section Template

+This list template has been modified slightly from a template originally used in [spf13.com](http://spf13.com/). It makes use of [partial templates][partials] for the chrome of the rendered page rather than using a [base template][base] The examples that follow also use the [content view templates][views] `li.html` or `summary.html`.

+{{% code file="layouts/section/post.html" %}}

+```html

+{{ partial "header.html" . }}

+{{ partial "subheader.html" . }}

+<main>

+  <div>

+   <h1>{{ .Title }}</h1>

+        <ul>

+        <!-- Renders the li.html content view for each content/post/*.md -->

+            {{ range .Data.Pages }}

+                {{ .Render "li"}}

+            {{ end }}

+        </ul>

+  </div>

+</main>

+{{ partial "footer.html" . }}

+```

+{{% /code %}}

+### Taxonomy Template

+{{% code file="layouts/_default/taxonomies.html" download="taxonomies.html" %}}

+```html

+{{ define "main" }}

+<main>

+  <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 }}

+        {{ .Render "summary"}}

+    {{ end }}

+  </div>

+</main>

+{{ end }}

+```

+{{% /code %}}

+## Order Content

+Hugo lists render the content based on metadata you provide in [front matter][]. In addition to sane defaults, Hugo also ships with multiple methods to make quick work of ordering content inside list templates:

+### Default List Ordering: Weight > Date

+{{% code file="layouts/partials/default-order.html" %}}

+```html

+<ul>

+    {{ range .Data.Pages }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Weight

+{{% code file="layouts/partials/by-weight.html" %}}

+```html

+<ul>

+    {{ range .Data.Pages.ByWeight }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Date

+{{% code file="layouts/partials/by-date.html" %}}

+```html

+<ul>

+    <!-- orders content according to the "date" field in front matter -->

+    {{ range .Data.Pages.ByDate }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Publish Date

+{{% code file="layouts/partials/by-publish-date.html" %}}

+```html

+<ul>

+    <!-- orders content according to the "publishdate" field in front matter -->

+    {{ range .Data.Pages.ByPublishDate }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Expiration Date

+{{% code file="layouts/partials/by-expiry-date.html" %}}

+```html

+<ul>

+    {{ range .Data.Pages.ByExpiryDate }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Last Modified Date

+{{% code file="layouts/partials/by-last-mod.html" %}}

+```html

+<ul>

+    <!-- orders content according to the "lastmod" field in front matter -->

+    {{ range .Data.Pages.ByLastmod }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Length

+{{% code file="layouts/partials/by-length.html" %}}

+```html

+<ul>

+    <!-- orders content according to content length in ascending order (i.e., the shortest content will be listed first) -->

+    {{ range .Data.Pages.ByLength }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Title

+{{% code file="layouts/partials/by-title.html" %}}

+```html

+<ul>

+    <!-- ranges through content in ascending order according to the "title" field set in front matter -->

+    {{ range .Data.Pages.ByTitle }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Link Title

+{{% code file="layouts/partials/by-link-title.html" %}}

+```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 }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .LinkTitle }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Parameter

+Order based on the specified front matter parameter. Content that does not have the specified front matter field  will use the site's `.Site.Params` default. If the parameter is not found at all in some entries, those entries will appear together at the end of the ordering.

+{{% code file="layouts/partials/by-rating.html" %}}

+```html

+<!-- Ranges through content according to the "rating" field set in front matter -->

+{{ range (.Data.Pages.ByParam "rating") }}

+  <!-- ... -->

+{{ end }}

+```

+{{% /code %}}

+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" %}}

+```html

+{{ range (.Data.Pages.ByParam "author.last_name") }}

+  <!-- ... -->

+{{ end }}

+```

+{{% /code %}}

+### Reverse Order

+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" %}}

+```html

+<ul>

+    {{ range .Data.Pages.ByDate.Reverse }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+## Group Content

+Hugo provides some functions for grouping pages by Section, Type, Date, etc.

+### By Page Field

+{{% code file="layouts/partials/by-page-field.html" %}}

+```html

+<!-- Groups content according to content section. The ".Key" in this instance will be the section's title. -->

+{{ range .Data.Pages.GroupBy "Section" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+In the above example, you may want `{{.Title}}` to point the `title` field you have added to your `_index.md` file instead. You can access this value using the [`.GetPage` function][getpage]:

+{{% code file="layouts/partials/by-page-field.html" %}}

+```html

+<!-- Groups content according to content section.-->

+{{ range .Data.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>

+{{ else }}

+<!-- If no _index.md is available, ".Key" defaults to the section title and filters to title casing -->

+<h3>{{ .Key | title }}</h3>

+{{ end }}

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Date

+{{% code file="layouts/partials/by-page-date.html" %}}

+```html

+<!-- Groups content by month according to the "date" field in front matter -->

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

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Publish Date

+{{% code file="layouts/partials/by-page-publish-date.html" %}}

+```html

+<!-- Groups content by month according to the "publishdate" field in front matter -->

+{{ range .Data.Pages.GroupByPublishDate "2006-01" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .PublishDate.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Page Parameter

+{{% code file="layouts/partials/by-page-param.html" %}}

+```html

+<!-- Groups content according to the "param_key" field in front matter -->

+{{ range .Data.Pages.GroupByParam "param_key" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Page Parameter in Date Format

+The following template takes grouping by `date` a step further and uses Golang's layout string. See the [`Format` function][] for more examples of how to use Golang's layout string to format dates in Hugo.

+{{% code file="layouts/partials/by-page-param-as-date.html" %}}

+```html

+<!-- Groups content by month according to the "param_key" field in front matter -->

+{{ range .Data.Pages.GroupByParamDate "param_key" "2006-01" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### Reverse Key Order

+Ordering of groups is performed by keys in alphanumeric order (A–Z, 1–100) and in reverse chronological order (i.e., with the newest first) for dates.

+While these are logical defaults, they are not always the desired order. There are two different syntaxes to change Hugo's default ordering for groups, both of which work the same way.

+#### 1. Adding the Reverse Method

+```html

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

+```

+```html

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

+```

+#### 2. Providing the Alternate Direction

+```html

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

+```

+```html

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

+```

+### Order Within Groups

+Because Grouping returns a `{{.Key}}` and a slice of pages, all of the ordering methods listed above are available.

+Here is the ordering for the example that follows:

+1. Content is grouped by month according to the `date` field in front matter.

+2. Groups are listed in ascending order (i.e., the oldest groups first)

+3. Pages within each respective group are ordered alphabetically according to the `title`.

+{{% code file="layouts/partials/by-group-by-page.html" %}}

+```html

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

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages.ByTitle }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+## Filter and Limiting Lists

+Sometimes you only want to list a subset of the available content. A common is to only display “Posts” on blog's homepage. You can accomplish this with the `where` function.

+### `where`

+`where` works in a similar manner to the [`where` keyword in SQL][wherekeyword]. It selects all elements of the array or slice that match the provided field and value. `where` takes three arguments:

+1. `array` *or* `slice of maps or structs`

+2. `key` *or* `field name`

+3. `match value`

+{{% code file="layouts/_default/.html" %}}

+```html

+{{ range where .Data.Pages "Section" "post" }}

+   {{ .Content }}

+{{ end }}

+```

+{{% /code %}}

+You can see more examples in the [functions documentation for `where`][wherefunction].

+### `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" %}}

+```html

+{{ range first 10 .Data.Pages }}

+  {{ .Render "summary" }}

+{{ end }}

+```

+{{% /code %}}

+### `first` and `where` Together

+Using `first` and `where` together can be very powerful:

+{{% code file="first-and-where-together.html" %}}

+```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 }}

+   {{ .Content }}

+{{ end }}

+```

+{{% /code %}}

+[base]: /templates/base/

+[bepsays]: http://bepsays.com/en/2016/12/19/hugo-018/

+[directorystructure]: /getting-started/directory-structure/

+[`Format` function]: /functions/format/

+[front matter]: /content-management/front-matter/

+[getpage]: /functions/getpage/

+[homepage]: /templates/homepage/

+[homepage]: /templates/homepage/

+[limitkeyword]: https://www.techonthenet.com/sql/select_limit.php

+[mentalmodel]: http://webstyleguide.com/wsg3/3-information-architecture/3-site-structure.html

+[pagevars]: /variables/page/

+[partials]: /templates/partials/

+[RSS 2.0]: http://cyber.law.harvard.edu/rss/rss.html "RSS 2.0 Specification"

+[rss]: /templates/rss/

+[sections]: /content-management/sections/

+[sectiontemps]: /templates/section-templates/

+[sitevars]: /variables/site/

+[taxlists]: /templates/taxonomy-templates/#taxonomy-list-templates/

+[taxterms]: /templates/taxonomy-templates/#taxonomy-terms-templates/

+[taxvars]: /variables/taxonomy/

+[views]: /templates/views/

+[wherefunction]: /functions/where/

+[wherekeyword]: https://www.techonthenet.com/sql/where.php

\ No newline at end of file

--- /dev/null

+++ b/content/templates/lookup-order.md

@@ -1,0 +1,197 @@

+---

+title: Hugo's Lookup Order

+linktitle: Template Lookup Order

+description: The lookup order is a prioritized list used by Hugo as it traverses your files looking for the appropriate corresponding file to render your content.

+godocref:

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-05-25

+categories: [templates,fundamentals]

+#tags: [lookup]

+menu:

+  docs:

+    parent: "templates"

+    weight: 15

+  quicklinks:

+weight: 15

+sections_weight: 15

+draft: false

+aliases: [/templates/lookup/]

+toc: true

+---

+Before creating your templates, it's important to know how Hugo looks for files within your project's [directory structure][].

+Hugo uses a prioritized list called the **lookup order** as it traverses your `layouts` folder in your Hugo project *looking* for the appropriate template to render your content.

+The template lookup order is an inverted cascade: if template A isn’t present or specified, Hugo will look to template B. If template B isn't present or specified, Hugo will look for template C...and so on until it reaches the `_default/` directory for your project or theme. In many ways, the lookup order is similar to the programming concept of a [switch statement without fallthrough][switch].

+The power of the lookup order is that it enables you to craft specific layouts and keep your templating [DRY][].

+{{% note %}}

+Most Hugo websites will only need the default template files at the end of the lookup order (i.e. `_default/*.html`).

+{{% /note %}}

+## Lookup Orders

+The respective lookup order for each of Hugo's templates has been defined throughout the Hugo docs:

+* [Homepage Template][home]

+* [Base Templates][base]

+* [Section Page Templates][sectionlookup]

+* [Taxonomy List Templates][taxonomylookup]

+* [Taxonomy Terms Templates][termslookup]

+* [Single Page Templates][singlelookup]

+* [RSS Templates][rsslookup]

+* [Shortcode Templates][sclookup]

+## Template Lookup Examples

+The lookup order is best illustrated through examples. The following shows you the process Hugo uses for finding the appropriate template to render your [single page templates][], but the concept holds true for all templates in Hugo.

+1. The project is using the theme `mytheme` (specified in the project's [configuration][config]).

+2. The layouts and content directories for the project are as follows:

+```bash

+.

+├── content

+│   ├── events

+│   │   ├── _index.md

+│   │   └── my-first-event.md

+│   └── posts

+│       ├── my-first-post.md

+│       └── my-second-post.md

+├── layouts

+│   ├── _default

+│   │   └── single.html

+│   ├── posts

+│   │   └── single.html

+│   └── reviews

+│       └── reviewarticle.html

+└── themes

+    └── mytheme

+        └── layouts

+            ├── _default

+            │   ├── list.html

+            │   └── single.html

+            └── posts

+                ├── list.html

+                └── single.html

+```

+Now we can look at the front matter for the three content (i.e.`.md`) files.

+{{% note  %}}

+Only three of the four markdown files in the above project are subject to the *single* page lookup order. `_index.md` is a specific `kind` in Hugo. Whereas `my-first-post.md`, `my-second-post.md`, and `my-first-event.md` are all of kind `page`, all `_index.md` files in a Hugo project are used to add content and front matter to [list pages](/templates/lists/). In this example, `events/_index.md` will render according to its [section template](/templates/section-templates/) and respective lookup order.

+{{% /note %}}

+### Example: `my-first-post.md`

+{{% code file="content/posts/my-first-post.md" copy="false" %}}

+```yaml

+---

+title: My First Post

+date: 2017-02-19

+description: This is my first post.

+---

+```

+{{% /code %}}

+When building your site, Hugo will go through the lookup order until it finds what it needs for `my-first-post.md`:

+1. ~~`/layouts/UNSPECIFIED/UNSPECIFIED.html`~~

+2. ~~`/layouts/posts/UNSPECIFIED.html`~~

+3. ~~`/layouts/UNSPECIFIED/single.html`~~

+4. <span class="yes">`/layouts/posts/single.html`</span>

+  <br><span class="break">BREAK</span>

+5. <span class="na">`/layouts/_default/single.html`</span>

+6. <span class="na">`/themes/<THEME>/layouts/UNSPECIFIED/UNSPECIFIED.html`</span>

+7. <span class="na">`/themes/<THEME>/layouts/posts/UNSPECIFIED.html`</span>

+8. <span class="na">`/themes/<THEME>/layouts/UNSPECIFIED/single.html`</span>

+9. <span class="na">`/themes/<THEME>/layouts/posts/single.html`</span>

+10. <span class="na">`/themes/<THEME>/layouts/_default/single.html`</span>

+Notice the term `UNSPECIFIED` rather than `UNDEFINED`. If you don't tell Hugo the specific type and layout, it makes assumptions based on sane defaults. `my-first-post.md` does not specify a content `type` in its front matter. Therefore, Hugo assumes the content `type` and `section` (i.e. `posts`, which is defined by file location) are one in the same. ([Read more on sections][sections].)

+`my-first-post.md` also does not specify a `layout` in its front matter. Therefore, Hugo assumes that `my-first-post.md`, which is of type `page` and a *single* piece of content, should default to the next occurrence of a `single.html` template in the lookup (#4).

+### Example: `my-second-post.md`

+{{% code file="content/posts/my-second-post.md" copy="false" %}}

+```yaml

+---

+title: My Second Post

+date: 2017-02-21

+description: This is my second post.

+type: review

+layout: reviewarticle

+---

+```

+{{% /code %}}

+Here is the way Hugo traverses the single-page lookup order for `my-second-post.md`:

+1. <span class="yes">`/layouts/review/reviewarticle.html`</span>

+  <br><span class="break">BREAK</span>

+2. <span class="na">`/layouts/posts/reviewarticle.html`</span>

+3. <span class="na">`/layouts/review/single.html`</span>

+4. <span class="na">`/layouts/posts/single.html`</span>

+5. <span class="na">`/layouts/_default/single.html`</span>

+6. <span class="na">`/themes/<THEME>/layouts/review/reviewarticle.html`</span>

+7. <span class="na">`/themes/<THEME>/layouts/posts/reviewarticle.html`</span>

+8. <span class="na">`/themes/<THEME>/layouts/review/single.html`</span>

+9. <span class="na">`/themes/<THEME>/layouts/posts/single.html`</span>

+10. <span class="na">`/themes/<THEME>/layouts/_default/single.html`</span>

+The front matter in `my-second-post.md` specifies the content `type` (i.e. `review`) as well as the `layout` (i.e. `reviewarticle`). Hugo finds the layout it needs at the top level of the lookup (#1) and does not continue to search through the other templates.

+{{% note "Type and not Types" %}}

+Notice that the directory for the template for `my-second-post.md` is `review` and not `reviews`. This is because *type is always singular when defined in front matter*.

+{{% /note%}}

+### Example: `my-first-event.md`

+{{% code file="content/events/my-first-event.md" copy="false" %}}

+```yaml

+---

+title: My First

+date: 2017-02-21

+description: This is an upcoming event..

+---

+```

+{{% /code %}}

+Here is the way Hugo traverses the single-page lookup order for `my-first-event.md`:

+1. ~~`/layouts/UNSPECIFIED/UNSPECIFIED.html`~~

+2. ~~`/layouts/events/UNSPECIFIED.html`~~

+3. ~~`/layouts/UNSPECIFIED/single.html`~~

+4. ~~`/layouts/events/single.html`~~

+5. <span class="yes">`/layouts/_default/single.html`</span>

+<br><span class="break">BREAK</span>

+6. <span class="na">`/themes/<THEME>/layouts/UNSPECIFIED/UNSPECIFIED.html`</span>

+7. <span class="na">`/themes/<THEME>/layouts/events/UNSPECIFIED.html`</span>

+8. <span class="na">`/themes/<THEME>/layouts/UNSPECIFIED/single.html`</span>

+9. <span class="na">`/themes/<THEME>/layouts/events/single.html`</span>

+10. <span class="na">`/themes/<THEME>/layouts/_default/single.html`</span>

+{{% note %}}

+`my-first-event.md` is significant because it demonstrates the role of the lookup order in Hugo themes. Both the root project directory *and* the `mytheme` themes directory have a file at `_default/single.html`. Understanding this order allows you to [customize Hugo themes](/themes/customizing/) by creating template files with identical names in your project directory that step in front of theme template files in the lookup. This allows you to customize the look and feel of your website while maintaining compatibility with the theme's upstream.

+{{% /note %}}

+[base]: /templates/base/#base-template-lookup-order

+[config]: /getting-started/configuration/

+[directory structure]: /getting-started/directory-structure/

+[DRY]: https://en.wikipedia.org/wiki/Don%27t_repeat_yourself

+[home]: /templates/homepage/#homepage-template-lookup-order

+[rsslookup]: /templates/rss/#rss-template-lookup-order

+[sclookup]: /templates/shortcode-templates/#shortcode-template-lookup-order

+[sections]: /content-management/sections/

+[sectionlookup]: /templates/section-templates/#section-template-lookup-order

+[single page templates]: /templates/single-page-templates/

+[singlelookup]: /templates/single-page-templates/#single-page-template-lookup-order

+[switch]: https://en.wikipedia.org/wiki/Switch_statement#Fallthrough

+[taxonomylookup]: /templates/taxonomy-templates/#taxonomy-list-template-lookup-order

+[termslookup]: /templates/taxonomy-templates/#taxonomy-terms-template-lookup-order

--- /dev/null

+++ b/content/templates/menu-templates.md

@@ -1,0 +1,107 @@

+---

+title: Menu Templates

+linktitle: Menu Templates

+description: Menus are a powerful but simple feature for content management but can be easily manipulated in your templates to meet your design needs.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [lists,sections,menus]

+menu:

+  docs:

+    parent: "templates"

+    weight: 130

+weight: 130

+sections_weight: 130

+draft: false

+aliases: [/templates/menus/]

+toc: false

+---

+Hugo makes no assumptions about how your rendered HTML will be

+structured. Instead, it provides all of the functions you will need to be

+able to build your menu however you want.

+The following is an example:

+{{% code file="layouts/partials/sidebar.html" download="sidebar.html" %}}

+```html

+<!-- sidebar start -->

+<aside>

+    <div id="sidebar" class="nav-collapse">

+        <!-- sidebar menu start-->

+        <ul class="sidebar-menu">

+          {{ $currentPage := . }}

+          {{ range .Site.Menus.main }}

+              {{ if .HasChildren }}

+            <li class="sub-menu{{if $currentPage.HasMenuCurrent "main" . }} active{{end}}">

+            <a href="javascript:;" class="">

+                {{ .Pre }}

+                <span>{{ .Name }}</span>

+                <span class="menu-arrow arrow_carrot-right"></span>

+            </a>

+            <ul class="sub">

+                {{ range .Children }}

+                <li{{if $currentPage.IsMenuCurrent "main" . }} class="active"{{end}}><a href="{{.URL}}"> {{ .Name }} </a> </li>

+                {{ end }}

+            </ul>

+          {{else}}

+            <li>

+            <a href="{{.URL}}">

+                {{ .Pre }}

+                <span>{{ .Name }}</span>

+            </a>

+          {{end}}

+          </li>

+          {{end}}

+            <li> <a href="https://github.com/gohugoio/hugo/issues" target="blank">Questions and Issues</a> </li>

+            <li> <a href="#" target="blank">Edit this Page</a> </li>

+        </ul>

+        <!-- sidebar menu end-->

+    </div>

+</aside>

+<!--sidebar end-->

+```

+{{% /code %}}

+{{% note "`absLangURL` and `relLangURL`" %}}

+Use the [`absLangUrl`](/functions/abslangurl) or [`relLangUrl`](/functions/rellangurl) functions if your theme makes use of the [multilingual feature](/content-management/multilingual/). In contrast to `absURL` and `relURL`, these two functions add the correct language prefix to the url.

+{{% /note %}}

+## Section Menu for Lazy Bloggers

+To enable this menu, add the following to your site `config`:

+```toml

+SectionPagesMenu = "main"

+```

+The menu name can be anything, but take a note of what it is.

+This will create a menu with all the sections as menu items and all the sections' pages as "shadow-members". The _shadow_ implies that the pages isn't represented by a menu-item themselves, but this enables you to create a top-level menu like this:

+```html

+<nav class="sidebar-nav">

+    {{ $currentPage := . }}

+    {{ range .Site.Menus.main }}

+    <a class="sidebar-nav-item{{if or ($currentPage.IsMenuCurrent "main" .) ($currentPage.HasMenuCurrent "main" .) }} active{{end}}" href="{{.URL}}">{{ .Name }}</a>

+    {{ end }}

+</nav>

+```

+In the above, the menu item is marked as active if on the current section's list page or on a page in that section.

+The above is all that's needed. But if you want custom menu items, e.g. changing weight or name, you can define them manually in the site config, i.e. `config.toml`:

+```toml

+[[menu.main]]

+    name = "This is the blog section"

+    weight = -110

+    identifier = "blog"

+    url = "/blog/"

+```

+{{% note %}}

+The `identifier` *must* match the section name.

+{{% /note %}}

--- /dev/null

+++ b/content/templates/ordering-and-grouping.md

@@ -1,0 +1,425 @@

+---

+title: Ordering and Grouping Hugo Lists

+linktitle: List Ordering and Grouping

+description: You can group or order your content in both your templating and content front matter.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: []

+menu:

+  docs:

+    parent: "templates"

+    weight: 27

+weight: 27

+sections_weight: 27

+draft: true

+aliases: [/templates/ordering/,/templates/grouping/]

+toc: true

+notes: This was originally going to be a separate page on the new docs site but it now makes more sense to keep everything within the templates/lists page. - rdwatters, 2017-03-12.

+---

+In Hugo, A list template is any template that will be used to render multiple pieces of content in a single HTML page.

+## Example List Templates

+### Section Template

+This list template is used for [spf13.com](http://spf13.com/). It makes use of [partial templates][partials]. All examples use a [view](/templates/views/) called either "li" or "summary."

+{{% code file="layouts/section/post.html" %}}

+```html

+{{ partial "header.html" . }}

+{{ partial "subheader.html" . }}

+<section id="main">

+  <div>

+   <h1 id="title">{{ .Title }}</h1>

+        <ul id="list">

+            {{ range .Data.Pages }}

+                {{ .Render "li"}}

+            {{ end }}

+        </ul>

+  </div>

+</section>

+{{ partial "footer.html" . }}

+```

+{{% /code %}}

+### Taxonomy Template

+{{% code file="layouts/_default/taxonomies.html" download="taxonomies.html" %}}

+```html

+{{ define "main" }}

+<section id="main">

+  <div>

+   <h1 id="title">{{ .Title }}</h1>

+    {{ range .Data.Pages }}

+        {{ .Render "summary"}}

+    {{ end }}

+  </div>

+</section>

+{{ end }}

+```

+{{% /code %}}

+## Order Content

+Hugo lists render the content based on metadata provided in the [front matter](/content-management/front-matter/)..

+Here are a variety of different ways you can order the content items in

+your list templates:

+### Default: Weight > Date

+{{% code file="layouts/partials/order-default.html" %}}

+```html

+<ul class="pages">

+    {{ range .Data.Pages }}

+        <li>

+            <h1><a href="{{ .Permalink }}">{{ .Title }}</a></h1>

+            <time>{{ .Date.Format "Mon, Jan 2, 2006" }}</time>

+        </li>

+    {{ end }}

+</ul>

+```

+{{% /code %}}

+### By Weight

+{{% code file="layouts/partials/by-weight.html" %}}

+```html

+{{ range .Data.Pages.ByWeight }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Date

+{{% code file="layouts/partials/by-date.html" %}}

+```html

+{{ range .Data.Pages.ByDate }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Publish Date

+{{% code file="layouts/partials/by-publish-date.html" %}}

+```html

+{{ range .Data.Pages.ByPublishDate }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .PublishDate.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Expiration Date

+{{% code file="layouts/partials/by-expiry-date.html" %}}

+```html

+{{ range .Data.Pages.ByExpiryDate }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .ExpiryDate.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Last Modified Date

+{{% code file="layouts/partials/by-last-mod.html" %}}

+```html

+{{ range .Data.Pages.ByLastmod }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Length

+{{% code file="layouts/partials/by-length.html" %}}

+```html

+{{ range .Data.Pages.ByLength }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Title

+{{% code file="layouts/partials/by-title.html" %}}

+```html

+{{ range .Data.Pages.ByTitle }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Link Title

+{{% code file="layouts/partials/by-link-title.html" %}}

+```html

+{{ range .Data.Pages.ByLinkTitle }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .LinkTitle }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+{{ end }}

+```

+{{% /code %}}

+### By Parameter

+Order based on the specified front matter parameter. Content that does not have the specified front matter field  will use the site's `.Site.Params` default. If the parameter is not found at all in some entries, those entries will appear together at the end of the ordering.

+The below example sorts a list of posts by their rating.

+{{% code file="layouts/partials/by-rating.html" %}}

+```html

+{{ range (.Data.Pages.ByParam "rating") }}

+  <!-- ... -->

+{{ end }}

+```

+{{% /code %}}

+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" %}}

+```html

+{{ range (.Data.Pages.ByParam "author.last_name") }}

+  <!-- ... -->

+{{ end }}

+```

+{{% /code %}}

+### Reverse Order

+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" %}}

+```html

+{{ range .Data.Pages.ByDate.Reverse }}

+<li>

+<a href="{{ .Permalink }}">{{ .Title }}</a>

+<div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+</li>

+{{ end }}

+```

+{{% /code %}}

+## Group Content

+Hugo provides some functions for grouping pages by Section, Type, Date, etc.

+### By Page Field

+{{% code file="layouts/partials/by-page-field.html" %}}

+```html

+{{ range .Data.Pages.GroupBy "Section" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Page date

+{{% code file="layouts/partials/by-page-date.html" %}}

+```html

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

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Page publish date

+{{% code file="layouts/partials/by-page-publish-date.html" %}}

+```html

+{{ range .Data.Pages.GroupByPublishDate "2006-01" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .PublishDate.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Page Param

+{{% code file="layouts/partials/by-page-param.html" %}}

+```html

+{{ range .Data.Pages.GroupByParam "param_key" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### By Page Param in Date Format

+{{% code file="layouts/partials/by-page-param-as-date.html" %}}

+```html

+{{ range .Data.Pages.GroupByParamDate "param_key" "2006-01" }}

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+### Reverse Key Order

+The ordering of the groups is performed by keys in alphanumeric order (A–Z, 1–100) and in reverse chronological order (newest first) for dates.

+While these are logical defaults, they are not always the desired order. There are two different syntaxes to change the order, both of which work the same way. You can use your preferred syntax.

+#### Reverse Method

+```html

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

+```

+```html

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

+```

+#### Provide the Alternate Direction

+```html

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

+```

+```html

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

+```

+### Order Within Groups

+Because Grouping returns a `{{.Key}}` and a slice of pages, all of the ordering methods listed above are available.

+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" %}}

+```html

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

+<h3>{{ .Key }}</h3>

+<ul>

+    {{ range .Pages.ByTitle }}

+    <li>

+    <a href="{{ .Permalink }}">{{ .Title }}</a>

+    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+    </li>

+    {{ end }}

+</ul>

+{{ end }}

+```

+{{% /code %}}

+## Filter and Limiting Lists

+Sometimes you only want to list a subset of the available content. A common request is to only display “Posts” on the homepage. You can accomplish this with the `where` function.

+### `where`

+`where` works in a similar manner to the `where` keyword in SQL. It selects all elements of the array or slice that match the provided field and value. `where` takes three arguments:

+1. `array` or a `slice of maps or structs`

+2. `key` or `field name`

+3. `match value`

+{{% code file="layouts/_default/.html" %}}

+```html

+{{ range where .Data.Pages "Section" "post" }}

+   {{ .Content }}

+{{ end }}

+```

+{{% /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" %}}

+```html

+{{ range first 10 .Data.Pages }}

+  {{ .Render "summary" }}

+{{ end }}

+```

+{{% /code %}}

+### `first` and `where` Together

+Using `first` and `where` together can be very powerful:

+{{% code file="first-and-where-together.html" %}}

+```html

+{{ range first 5 (where .Data.Pages "Section" "post") }}

+   {{ .Content }}

+{{ end }}

+```

+{{% /code %}}

+[views]: /templates/views/

--- /dev/null

+++ b/content/templates/output-formats.md

@@ -1,0 +1,211 @@

+---

+title: Custom Output Formats

+linktitle: Custom Output Formats

+description: Hugo can output content in multiple formats, including calendar events, e-book formats, Google AMP, and JSON search indexes, or any custom text format.

+date: 2017-03-22

+publishdate: 2017-03-22

+lastmod: 2017-03-22

+categories: [templates]

+#tags: ["amp","outputs","rss"]

+menu:

+  docs:

+    parent: "templates"

+    weight: 18

+weight: 18

+sections_weight: 18

+draft: false

+aliases: [/templates/outputs/,/extras/output-formats/,/content-management/custom-outputs/]

+toc: true

+---

+This page describes how to properly configure your site with the media types and output formats, as well as where to create your templates for your custom outputs.

+## Media Types

+A [media type][] (also known as *MIME type* and *content type*) is a two-part identifier for file formats and format contents transmitted on the Internet.

+This is the full set of built-in media types in Hugo:

+{{< datatable "media" "types" "Type" "Suffix" >}}

+**Note:**

+* It is possible to add custom media types or change the defaults; e.g., if you want to change the suffix for `text/html` to `asp`.

+* The `Suffix` is the value that will be used for URLs and filenames for that media type in Hugo.

+* The `Type` is the identifier that must be used when defining new/custom `Output Formats` (see below).

+* The full set of media types will be registered in Hugo's built-in development server to make sure they are recognized by the browser.

+To add or modify a media type, define it in a `mediaTypes` section in your [site configuration][config], either for all sites or for a given language.

+Example in `config.toml`:

+```toml

+[mediaTypes]

+  [mediaTypes."text/enriched"]

+  suffix = "enr"

+  [mediaTypes."text/html"]

+  suffix = "asp"

+```

+The above example adds one new media type, `text/enriched`, and changes the suffix for the built-in `text/html` media type.

+## Output Formats

+Given a media type and some additional configuration, you get an `Output Format`:

+This is the full set of Hugo's built-in output formats:

+{{< datatable "output" "formats" "Name" "MediaType" "Path" "BaseName" "Rel" "Protocol" "IsPlainText" "IsHTML" "NoUgly">}}

+* A page can be output in as many output formats as you want, and you can have an infinite amount of output formats defined **as long as they resolve to a unique path on the file system**. In the above table, the best example of this is `AMP` vs. `HTML`. `AMP` has the value `amp` for `Path` so it doesn't overwrite the `HTML` version; e.g. we can now have both `/index.html` and `/amp/index.html`.

+* The `MediaType` must match the `Type` of an already defined media type.

+* You can define new output formats or redefine built-in output formats; e.g., if you want to put `AMP` pages in a different path.

+To add or modify an output format, define it in an `outputFormats` section in your site's [configuration file](/templates/configuration/), either for all sites or for a given language.

+```toml

+[outputFormats.MyEnrichedFormat]

+mediaType = "text/enriched"

+baseName = "myindex"

+isPlainText = true

+protocol = "bep://"

+```

+The above example is fictional, but if used for the homepage on a site with `baseURL` `http://example.org`, it will produce a plain text homepage with the URL `bep://example.org/myindex.enr`.

+### Configure Output Formats

+The following is the full list of configuration options for output formats and their default values:

+`Name`

+: the output format identifier. This is used to define what output format(s) you want for your pages.

+`MediaType`

+: this must match the `Type` of a defined media type.

+`Path`

+: sub path to save the output files.

+`BaseName`

+: the base filename for the list filenames (homepage, etc.). **Default:** `index`.

+`Rel`

+: can be used to create `rel` values in `link` tags. **Default:** `alternate`.

+`Protocol`

+: will replace the "http://" or "https://" in your `baseURL` for this output format.

+`IsPlainText`

+: use Go's plain text templates parser for the templates. **Default:** `false`.

+`IsHTML`

+: used in situations only relevant for `HTML`-type formats; e.g., page aliases.

+`NoUgly`

+: used to turn off ugly URLs If `uglyURLs` is set to `true` in your site. **Default:** `false`.

+`NotAlternative`

+: enable if it doesn't make sense to include this format in an `AlternativeOutputFormats` format listing on `Page` (e.g., with `CSS`). Note that we use the term *alternative* and not *alternate* here, as it does not necessarily replace the other format. **Default:** `false`.

+## Output Formats for Pages

+A `Page` in Hugo can be rendered to multiple representations on the file system. By default, all pages will render as `HTML` with some of them also as `RSS` (homepage, sections, etc.).

+This can be changed by defining an `outputs` list of output formats in either the `Page` front matter or in the site configuration (either for all sites or per language).

+Example from site `config.toml`:

+```toml

+[outputs]

+  home = ["HTML", "AMP", "RSS"]

+  page = ["HTML"]

+```

+Example from site `config.yml`:

+```yml

+outputs:

+  home: ["HTML", "AMP", "RSS"]

+  page: ["HTML"]

+```

+* The output definition is per `Page` `Kind` (i.e, `page`, `home`, `section`, `taxonomy`, or `taxonomyTerm`).

+* The names used must match the `Name` of a defined `Output Format`.

+* Any `Kind` without a definition will default to `HTML`.

+* These can be overridden per `Page` in the front matter of content files.

+* Output formats are case insensitive.

+The following is an example of `YAML` front matter in a content file that defines output formats for the rendered `Page`:

+```yaml

+---

+date: "2016-03-19"

+outputs:

+- html

+- amp

+- json

+---

+```

+## Link to Output Formats

+Each `Page` has both an `.OutputFormats` (all formats, including the current) and an `.AlternativeOutputFormats` variable, the latter of which is useful for creating a `link rel` list in your site's `<head>`:

+```

+{{ range .AlternativeOutputFormats -}}

+<link rel="{{ .Rel }}" type="{{ .MediaType.Type }}" href="{{ .Permalink | safeURL }}">

+{{ end -}}

+```

+Note that `.Permalink` and `.RelPermalink` on `Page` will return the first output format defined for that page (usually `HTML` if nothing else is defined).

+This is how you link to a given output format:

+```

+{{ with  .OutputFormats.Get "json" -}}

+<a href="{{ .Permalink }}">{{ .Name }}</a>

+{{- end }}

+```

+From content files, you can use the [`ref` or `relref` shortcodes](/content-management/shortcodes/#ref-and-relref):

+```

+[Neat]({{</* ref "blog/neat.md" "amp" */>}})

+[Who]({{</* relref "about.md#who" "amp" */>}})

+```

+## Templates for Your Output Formats

+A new output format needs a corresponding template in order to render anything useful.

+{{% note %}}

+The key distinction for Hugo versions 0.20 and newer is that Hugo looks at an output format's `Name` and MediaType's `Suffix` when choosing the template used to render a given `Page`.

+{{% /note %}}

+The following table shows examples of different output formats, the suffix used, and Hugo's respective template [lookup order][]. All of the examples in the table can:

+* Use a [base template][base].

+* Include [partial templates][partials]

+{{< datatable "output" "layouts" "Example" "OutputFormat" "Suffix" "Template Lookup Order" >}}

+Hugo will now also detect the media type and output format of partials, if possible, and use that information to decide if the partial should be parsed as a plain text template or not.

+Hugo will look for the name given, so you can name it whatever you want. But if you want it treated as plain text, you should use the file suffix and, if needed, the name of the Output Format. The pattern is as follows:

+```

+[partial name].[OutputFormat].[suffix]

+```

+The partial below is a plain text template (Outpuf Format is `CSV`, and since this is the only output format with the suffix `csv`, we don't need to include the Output Format's `Name`):

+```

+{{ partial "mytextpartial.csv" . }}

+```

+[base]: /templates/base/

+[config]: /getting-started/configuration/

+[lookup order]: /templates/lookup/

+[media type]: https://en.wikipedia.org/wiki/Media_type

+[partials]: /templates/partials/

--- a/content/templates/overview.md

+++ /dev/null

@@ -1,76 +1,0 @@

----

-aliases:

-- /doc/templates/

-- /layout/templates/

-- /layout/overview/

-lastmod: 2015-05-22

-date: 2013-07-01

-linktitle: Overview

-menu:

-  main:

-    parent: layout

-next: /templates/go-templates

-prev: /themes/creation

-title: Hugo Templates

-weight: 10

-toc: true

----

-Hugo uses the excellent Go html/template library for its template engine.

-It is an extremely lightweight engine that provides a very small amount of

-logic. In our experience it is just the right amount of logic to be able

-to create a good static website.

-While Hugo has a number of different template roles, most complete

-websites can be built using just a small number of template files.

-Please don’t be afraid of the variety of different template roles. They

-enable Hugo to build very complicated sites. Most sites will only

-need to create a [/layouts/\_default/single.html](/templates/content/) & [/layouts/\_default/list.html](/templates/list/)

-If you are new to Go's templates, the [Go Template Primer](/layout/go-templates/)

-is a great place to start.

-If you are familiar with Go’s templates, Hugo provides some [additional

-template functions](/templates/functions/) and [variables](/templates/variables/) you will want to be familiar

-with.

-## Primary Template roles

-There are 3 primary kinds of templates that Hugo works with.

-### [Single](/templates/content/)

-Render a single piece of content

-### [List](/templates/list/)

-Page that list multiple pieces of content

-### [Homepage](/templates/homepage/)

-The homepage of your site

-## Supporting Template Roles (optional)

-Hugo also has additional kinds of templates all of which are optional

-### [Partial Templates](/templates/partials/)

-Common page parts to be included in the above mentioned templates

-### [Content Views](/templates/views/)

-Different ways of rendering a (single) content type

-### [Taxonomy Terms](/templates/terms/)

-A list of the terms used for a specific taxonomy, e.g. a Tag cloud

-## Other Templates (generally unnecessary)

-### [RSS](/templates/rss/)

-Used to render all rss documents

-### [Sitemap](/templates/sitemap/)

-Used to render the XML sitemap

-### [404](/templates/404/)

-This template will create a 404.html page used when hosting on GitHub Pages

-### [Alias](/extras/aliases/#customizing)

-This template will override the default page used to create aliases of pages.

--- /dev/null

+++ b/content/templates/pagination.md

@@ -1,0 +1,155 @@

+---

+title: Pagination

+linktitle: Pagination

+description: Hugo supports pagination for your homepage, section pages, and taxonomies.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [lists,sections,pagination]

+menu:

+  docs:

+    parent: "templates"

+    weight: 140

+weight: 140

+sections_weight: 140

+draft: false

+aliases: [/extras/pagination,/doc/pagination/]

+toc: true

+---

+The real power of Hugo pagination shines when combined with the [`where` function][where] and its SQL-like operators: [`first`][], [`last`][], and [`after`][]. You can even [order the content][lists] the way you've become used to with Hugo.

+## Configure Pagination

+Pagination can be configured in your [site configuration][configuration]:

+`Paginate`

+: default = `10`. This setting can be overridden within the template.

+`PaginatePath`

+: default = `page`. Allows you to set a different path for your pagination pages.

+Setting `Paginate` to a positive value will split the list pages for the homepage, sections and taxonomies into chunks of that size. But note that the generation of the pagination pages for sections, taxonomies and homepage is *lazy* --- the pages will not be created if not referenced by a `.Paginator` (see below).

+`PaginatePath` is used to adapt the `URL` to the pages in the paginator (the default setting will produce URLs on the form `/page/1/`.

+## List Paginator Pages

+{{% warning %}}

+`.Paginator` is provided to help you build a pager menu. This feature is currently only supported on homepage and list pages (i.e., taxonomies and section lists).

+{{% /warning %}}

+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 }}`.

+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 }}`

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

+```

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

+```

+## Build the navigation

+The `.Paginator` contains enough information to build a paginator interface.

+The easiest way to add this to your pages is to include the built-in template (with `Bootstrap`-compatible styles):

+```html

+{{ template "_internal/pagination.html" . }}

+```

+{{% note "When to Create `.Paginator`" %}}

+If you use any filters or ordering functions to create your `.Paginator` *and* you want the navigation buttons to be shown before the page listing, you must create the `.Paginator` before it's used.

+{{% /note %}}

+The following example shows how to create `.Paginator` before its used:

+```html

+{{ $paginator := .Paginate (where .Data.Pages "Type" "post") }}

+{{ template "_internal/pagination.html" . }}

+{{ range $paginator.Pages }}

+   {{ .Title }}

+{{ end }}

+```

+Without the `where` filter, the above example is even simpler:

+```html

+{{ template "_internal/pagination.html" . }}

+{{ range .Paginator.Pages }}

+   {{ .Title }}

+{{ end }}

+```

+If you want to build custom navigation, you can do so using the `.Paginator` object, which includes the following properties:

+`PageNumber`

+: The current page's number in the pager sequence

+`URL`:

+The relative URL to the current pager

+`Pages`:

+The pages in the current pager

+`NumberOfElements`

+: The number of elements on this page

+`HasPrev`

+: Whether there are page(s) before the current

+`Prev`

+: The pager for the previous page

+`HasNext`

+: Whether there are page(s) after the current

+`Next`

+: The pager for the next page

+`First`

+: The pager for the first page

+`Last`

+: The pager for the last page

+`Pagers`

+: A list of pagers that can be used to build a pagination menu

+`PageSize`

+: Size of each pager

+`TotalPages`

+: The number of pages in the paginator

+`TotalNumberOfElements`

+: The number of elements on all pages in this paginator

+## Additional information

+The pages are built on the following form (`BLANK` means no value):

+```

+[SECTION/TAXONOMY/BLANK]/index.html

+[SECTION/TAXONOMY/BLANK]/page/1/index.html => redirect to  [SECTION/TAXONOMY/BLANK]/index.html

+[SECTION/TAXONOMY/BLANK]/page/2/index.html

+....

+```

+[`first`]: /functions/first/

+[`last`]: /functions/last/

+[`after`]: /functions/after/

+[configuration]: /getting-started/configuration/

+[lists]: /templates/lists/

+[where]: /functions/where/

\ No newline at end of file

--- a/content/templates/partials.md

+++ b/content/templates/partials.md

@@ -1,146 +1,171 @@

---

-aliases:

-- /layout/chrome/

-lastmod: 2016-01-01

-date: 2013-07-01

-menu:

-  main:

-    parent: layout

-next: /templates/rss

-prev: /templates/blocks/

 title: Partial Templates

-weight: 80

+linktitle: Partial Templates

+description: Partials are smaller, context-aware components in your list and page templates that can be used economically to keep your templating DRY.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [lists,sections,partials]

+menu:

+  docs:

+    parent: "templates"

+    weight: 90

+weight: 90

+sections_weight: 90

+draft: false

+aliases: [/templates/partial/,/layout/chrome/,/extras/analytics/]

 toc: true

---

-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 subdirectories like `/layouts/partials/post/tag`.

+## Partial Template Lookup Order

-Partials are especially important for themes as it gives users an opportunity

-to overwrite just a small part of your theme, while maintaining future compatibility.

+Partial templates---like [single page templates][singletemps] and [list page templates][listtemps]---have a specific [lookup order][]. However, partials are simpler in that Hugo will only check in two places:

-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.

+1. `layouts/partials/*<PARTIALNAME>.html`

+2. `themes/<THEME>/layouts/partials/*<PARTIALNAME>.html`

-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.

+This allows a theme's end user to copy a partial's contents into a file of the same name for [further customization][customize].

-    ▾ layouts/

-      ▾ partials/

-          header.html

-          footer.html

+## Use Partials in your Templates

-## Partial vs Template

+All partials for your Hugo project are located in a single `layouts/partials` directory. For better organization, you can create multiple subdirectories within `partials` as well:

-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.

+```

+.

+└── layouts

+    └── partials

+        ├── footer

+        │   ├── scripts.html

+        │   └── site-footer.html

+        ├── head

+        │   ├── favicons.html

+        │   ├── metadata.html

+        │   ├── prerender.html

+        │   └── twitter.html

+        └── header

+            ├── site-header.html

+            └── site-nav.html

+```

-With the addition of the theme system in v0.11, it became apparent that a theme

-& override-aware partial was needed.

+All partials are called within your templates using the following pattern:

-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.

+```

+{{ partial "<PATH>/<PARTIAL>.html" . }}

+```

-## Example header.html

-This header template is used for [spf13.com](http://spf13.com/):

+{{% note %}}

+One of the most common mistakes with new Hugo users is failing to pass a context to the partial call. In the pattern above, note how "the dot" (`.`) is required as the second argument to give the partial context. You can read more about "the dot" in the [Hugo templating introduction](/templates/introduction/).

+{{% /note %}}

-    <!DOCTYPE html>

-    <html class="no-js" lang="en-US" prefix="og: http://ogp.me/ns# fb: http://ogp.me/ns/fb#">

-    <head>

-        <meta charset="utf-8">

+As shown in the above example directory structure, you can nest your directories within `partials` for better source organization. You only need to call the nested partial's path relative to the `partials` directory:

-        {{ partial "meta.html" . }}

+```golang

+{{ partial "header/site-header.html" . }}

+{{ partial "footer/scripts.html" . }}

+```

-        <base href="{{ .Site.BaseURL }}">

-        <title> {{ .Title }} : spf13.com </title>

-        <link rel="canonical" href="{{ .Permalink }}">

-        {{ if .RSSLink }}<link href="{{ .RSSLink }}" rel="alternate" type="application/rss+xml" title="{{ .Title }}" />{{ end }}

+{{% note %}}

+Before v0.12, Hugo used the `template` call to include partial templates. When using Hugo v0.12 and newer, be sure to use the `{{ partial "<PATH>/<PARTIAL>.html" . }}` syntax. The old approach will still work but has fewer benefits.

+{{% /note %}}

-        {{ partial "head_includes.html" . }}

-    </head>

-    <body lang="en">

+### Variable Scoping

-## Example footer.html

-This footer template is used for [spf13.com](http://spf13.com/):

+The second argument in a partial call is the variable being passed down. The above examples are passing the `.`, which tells the template receiving the partial to apply the current [context][context].

-    <footer>

-      <div>

-        <p>

-        &copy; 2013-14 Steve Francia.

-        <a href="http://creativecommons.org/licenses/by/3.0/" title="Creative Commons Attribution">Some rights reserved</a>;

-        please attribute properly and link back. Hosted by <a href="http://servergrove.com">ServerGrove</a>.

-        </p>

-      </div>

-    </footer>

-    <script type="text/javascript">

+This means the partial will *only* be able to access those variables. The partial is isolated and *has no access to the outer scope*. From within the partial, `$.Var` is equivalent to `.Var`.

-      var _gaq = _gaq || [];

-      _gaq.push(['_setAccount', 'UA-XYSYXYSY-X']);

-      _gaq.push(['_trackPageview']);

+### Cached Partials

-      (function() {

-        var ga = document.createElement('script');

-        ga.src = ('https:' == document.location.protocol ? 'https://ssl' :

-            'http://www') + '.google-analytics.com/ga.js';

-        ga.setAttribute('async', 'true');

-        document.documentElement.firstChild.appendChild(ga);

-      })();

+The [`partialCached` template function][partialcached] can offer significant performance gains for complex templates that don't need to be re-rendered on every invocation. The simplest usage is as follows:

-    </script>

-    </body>

-    </html>

+```

+{{ partialCached "footer.html" . }}

+```

-To reference a partial template stored in a subfolder, e.g. `/layouts/partials/post/tag/list.html`, call it this way:

+You can also pass additional parameters to `partialCached` to create *variants* of the cached partial.

-     {{ partial "post/tag/list" . }}

+For example, you can tell Hugo to only render the partial `footer.html` once per section:

-Note that the subdirectories you create under /layouts/partials can be named whatever you like.

+```

+{{ partialCached "footer.html" . .Section }}

+```

-For more examples of referencing these templates, see

-[single content templates](/templates/content/),

-[list templates](/templates/list/) and

-[homepage templates](/templates/homepage/).

+If you need to pass additional parameters to create unique variants, you can pass as many variant parameters as you need:

+```

+{{ partialCached "footer.html" . .Params.country .Params.province }}

+```

-## Variable scoping

+Note that the variant parameters are not made available to the underlying partial template. They are only use to create a unique cache key.

-As you might have noticed, `partial` calls receive two parameters.

+### Example `header.html`

-1. The first is the name of the partial and determines the file

-location to be read.

-2. The second is the variables to be passed down to the partial.

+The following `header.html` partial template is used for [spf13.com](http://spf13.com/):

-This means that the partial will _only_ be able to access those variables. It is

-isolated and has no access to the outer scope. From within the

-partial, `$.Var` is equivalent to `.Var`

+{{% code file="layouts/partials/header.html" download="header.html" %}}

+```html

+<!DOCTYPE html>

+<html class="no-js" lang="en-US" prefix="og: http://ogp.me/ns# fb: http://ogp.me/ns/fb#">

+<head>

+    <meta charset="utf-8">

-## Cached Partials

+    {{ partial "meta.html" . }}

-The `partialCached` template function can offer significant performance gains

-for complex templates that don't need to be rerendered upon every invocation.

-The simplest usage is as follows:

+    <base href="{{ .Site.BaseURL }}">

+    <title> {{ .Title }} : spf13.com </title>

+    <link rel="canonical" href="{{ .Permalink }}">

+    {{ if .RSSLink }}<link href="{{ .RSSLink }}" rel="alternate" type="application/rss+xml" title="{{ .Title }}" />{{ end }}

-    {{ partialCached "footer.html" . }}

+    {{ partial "head_includes.html" . }}

+</head>

+<body lang="en">

+```

+{{% /code %}}

-You can also pass additional parameters to `partialCached` to create *variants* of the cached partial.

-For example, say you have a complex partial that should be identical when rendered for pages within the same section.

-You could use a variant based upon section so that the partial is only rendered once per section:

+{{% note %}}

+The `header.html` example partial was built before the introduction of block templates to Hugo. Read more on [base templates and blocks](/templates/base/) for defining the outer chrome or shell of your master templates (i.e., your site's head, header, and footer). You can even combine blocks and partials for added flexibility.

+{{% /note %}}

-    {{ partialCached "footer.html" . .Section }}

+### Example `footer.html`

-If you need to pass additional parameters to create unique variants,

-you can pass as many variant parameters as you need:

+The following `footer.html` partial template is used for [spf13.com](http://spf13.com/):

-    {{ partialCached "footer.html" . .Params.country .Params.province }}

+{{% code file="layouts/partials/footer.html" download="footer.html" %}}

+```html

+<footer>

+  <div>

+    <p>

+    &copy; 2013-14 Steve Francia.

+    <a href="http://creativecommons.org/licenses/by/3.0/" title="Creative Commons Attribution">Some rights reserved</a>;

+    please attribute properly and link back. Hosted by <a href="http://servergrove.com">ServerGrove</a>.

+    </p>

+  </div>

+</footer>

+<script type="text/javascript">

-Note that the variant parameters are not made available to the underlying partial template.

-They are only use to create a unique cache key.

+  var _gaq = _gaq || [];

+  _gaq.push(['_setAccount', 'UA-XYSYXYSY-X']);

+  _gaq.push(['_trackPageview']);

+  (function() {

+    var ga = document.createElement('script');

+    ga.src = ('https:' == document.location.protocol ? 'https://ssl' :

+        'http://www') + '.google-analytics.com/ga.js';

+    ga.setAttribute('async', 'true');

+    document.documentElement.firstChild.appendChild(ga);

+  })();

+</script>

+</body>

+</html>

+```

+{{% /code %}}

+[context]: /templates/introduction/ "The most easily overlooked concept to understand about Go templating is how the dot always refers to the current context."

+[customize]: /themes/customizing/ "Hugo provides easy means to customize themes as long as users are familiar with Hugo's template lookup order."

+[listtemps]: /templates/lists/ "To effectively leverage Hugo's system, see how Hugo handles list pages, where content for sections, taxonomies, and the homepage are listed and ordered."

+[lookup order]: /templates/lookup-order/ "To keep your templating dry, read the documentation on Hugo's lookup order."

+[partialcached]: /functions/partialcached/ "Use the partial cached function to improve build times in cases where Hugo can cache partials that don't need to be rendered with every page."

+[singletemps]: /templates/single-page-templates/ "The most common form of template in Hugo is the single content template. Read the docs on how to create templates for individual pages."

+[themes]: /themes/

\ No newline at end of file

--- /dev/null

+++ b/content/templates/robots.md

@@ -1,0 +1,56 @@

+---

+title: Robots.txt File

+linktitle: Robots.txt

+description: Hugo can generate a customized robots.txt in the same way as any other template.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [robots,search engines]

+menu:

+  docs:

+    parent: "templates"

+    weight: 165

+weight: 165

+sections_weight: 165

+draft: false

+aliases: [/extras/robots-txt/]

+toc: false

+---

+To create your robots.txt as a template, first set the `enableRobotsTXT` value to `true` in your [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: *

+```

+## Robots.txt Template Lookup Order

+The [lookup order][lookup] for the `robots.txt` template is as follows:

+* `/layouts/robots.txt`

+* `/themes/<THEME>/layout/robots.txt`

+{{% note %}}

+If you do not want Hugo to create a default `robots.txt` or leverage the `robots.txt` template, you can hand code your own and place the file in `static`. Remember that everything in the [static directory](/getting-started/directory-structure/) is copied over as-is when Hugo builds your site.

+{{% /note %}}

+## Robots.txt Template Example

+The following is an example `robots.txt` layout:

+{{% code file="layouts/robots.txt" download="robots.txt" %}}

+```http

+User-agent: *

+{{range .Data.Pages}}

+Disallow: {{.RelPermalink}}

+{{end}}

+```

+{{% /code %}}

+This template disallows all the pages of the site by creating one `Disallow` entry for each page.

+[config]: /getting-started/configuration/

+[lookup]: /templates/lookup-order/

+[robots]: http://www.robotstxt.org/

\ No newline at end of file

--- a/content/templates/rss.md

+++ b/content/templates/rss.md

@@ -1,130 +1,142 @@

---

-aliases:

-- /layout/rss/

-lastmod: 2015-08-04

-date: 2015-05-19

-linktitle: RSS

+title: RSS Templates

+linktitle: RSS Templates

+description: Hugo ships with its own RSS 2.0 template that requires almost no configuration, or you can create your own RSS templates.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [rss, xml]

+categories: [templates]

 menu:

-  main:

-    parent: layout

-next: /templates/sitemap

-notoc: one

-prev: /templates/partials

-title: RSS (feed) Templates

-weight: 90

+  docs:

+    parent: "templates"

+    weight: 150

+weight: 150

+sections_weight: 150

+draft: false

+aliases: [/templates/rss/]

 toc: true

---

-Like all other templates, you can use a single RSS template to generate all of your RSS feeds, or you can create a specific template for each individual feed.

+## RSS Template Lookup Order

-*Unlike other Hugo templates*, Hugo ships with its own [RSS 2.0 template](#the-embedded-rss-xml:eceb479b7b3b2077408a2878a29e1320). In most cases this will be sufficient, and an RSS template will not need to be provided by the user. But you can provide an rss template if you like, as you can see in the next section.

+You can use a single RSS template to generate all of your RSS feeds or create a specific template for each individual feed.

+1. `/layouts/section/<section>.rss.xml`

+2. `/layouts/_default/rss.xml`

+3. `/themes/<theme>/layouts/section/<section>.rss.xml`

+4. `/themes/<theme>/layouts/_default/rss.xml`

+{{% note "Hugo Ships with an RSS Template" %}}

+Hugo ships with its own [RSS 2.0 template](#the-embedded-rss-xml). The embedded template will be sufficient for most use cases.

+{{% /note %}}

 RSS pages are of the type `Page` and have all the [page variables](/layout/variables/) available to use in the templates.

-## Which Template will be rendered?

-Hugo uses a set of rules to figure out which template to use when rendering a specific page.

+### Section RSS

-Hugo will use the following prioritized list. If a file isn’t present, then the next one in the list will be used. This enables you to craft specific layouts when you want to without creating more templates than necessary. For most sites only the `\_default` file at the end of the list will be needed.

+A [section’s][section] RSS will be rendered at `/<SECTION>/index.xml` (e.g., http://spf13.com/project/index.xml).

+Hugo provides the ability for you to define any RSS type you wish and can have different RSS files for each section and taxonomy.

+## Lookup Order for RSS Templates

 ### Main RSS

-* /layouts/rss.xml

-* /layouts/\_default/rss.xml

-* [Embedded rss.xml](#the-embedded-rss-xml:eceb479b7b3b2077408a2878a29e1320)

+1. `/layouts/rss.xml`

+2. `/layouts/_default/rss.xml`

+3.  Embedded rss.xml

 ### Section RSS

-* /layouts/section/`SECTION`.rss.xml

-* /layouts/\_default/rss.xml

-* /themes/`THEME`/layouts/section/`SECTION`.rss.xml

-* /themes/`THEME`/layouts/\_default/rss.xml

-* [Embedded rss.xml](#the-embedded-rss-xml:eceb479b7b3b2077408a2878a29e1320)

+1. `/layouts/section/<SECTION>.rss.xml`

+2. `/layouts/_default/rss.xml`

+3. `/themes/<THEME>/layouts/section/<SECTION>.rss.xml`

+4. `/themes/<THEME>/layouts/_default/rss.xml`

+5. Embedded rss.xml

 ### Taxonomy RSS

-* /layouts/taxonomy/`SINGULAR`.rss.xml

-* /layouts/\_default/rss.xml

-* /themes/`THEME`/layouts/taxonomy/`SINGULAR`.rss.xml

-* /themes/`THEME`/layouts/\_default/rss.xml

-* [Embedded rss.xml](#the-embedded-rss-xml:eceb479b7b3b2077408a2878a29e1320)

+1. `/layouts/taxonomy/<SINGULAR>.rss.xml`

+2. `/layouts/_default/rss.xml`

+3. `/themes/<THEME>/layouts/taxonomy/<SINGULAR>.rss.xml`

+4. `/themes/<THEME>/layouts/_default/rss.xml`

+5. Embedded rss.xml

-### Taxonomy Terms RSS

+## Configure RSS

-* /layouts/taxonomy/`SINGULAR`.terms.rss.xml

-* /layouts/\_default/rss.xml

-* /themes/`THEME`/layouts/taxonomy/`SINGULAR`.terms.rss.xml

-* /themes/`THEME`/layouts/\_default/rss.xml

-* [Embedded rss.xml](#the-embedded-rss-xml:eceb479b7b3b2077408a2878a29e1320)

+By default, Hugo will create an unlimited number of RSS entries. You can limit the number of articles included in the built-in RSS templates by assigning a numeric value to `rssLimit:` field in your project's [`config` file][config].

+The following values will also be included in the RSS output if specified in your site’s configuration:

-## Configuring RSS

+```toml

+languageCode = "en-us"

+copyright = "This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License."

-If the following values are specified in the site’s config file (`config.toml`), then they will be included in the RSS output. Example values are provided.

+[author]

+    name = "My Name Here"

+```

-    languageCode = "en-us"

-    copyright = "This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License."

-    [author]

-        name = "My Name Here"

-        email = "[email protected]"

-### Limiting the Number of Items

-By default, the RSS feed is limited to **15** items.

-You may override the default by using the `rssLimit` [site configuration variable](/overview/configuration/).

 ## The Embedded rss.xml

 This is the default RSS template that ships with Hugo. It adheres to the [RSS 2.0 Specification][RSS 2.0].

-    <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

-      <channel>

-        <title>{{ if eq  .Title  .Site.Title }}{{ .Site.Title }}{{ else }}{{ with .Title }}{{.}} on {{ end }}{{ .Site.Title }}{{ end }}</title>

-        <link>{{ .Permalink }}</link>

-        <description>Recent content {{ if ne  .Title  .Site.Title }}{{ with .Title }}in {{.}} {{ end }}{{ end }}on {{ .Site.Title }}</description>

-        <generator>Hugo -- gohugo.io</generator>{{ with .Site.LanguageCode }}

-        <language>{{.}}</language>{{end}}{{ with .Site.Author.email }}

-        <managingEditor>{{.}}{{ with $.Site.Author.name }} ({{.}}){{end}}</managingEditor>{{end}}{{ with .Site.Author.email }}

-        <webMaster>{{.}}{{ with $.Site.Author.name }} ({{.}}){{end}}</webMaster>{{end}}{{ with .Site.Copyright }}

-        <copyright>{{.}}</copyright>{{end}}{{ if not .Date.IsZero }}

-        <lastBuildDate>{{ .Date.Format "Mon, 02 Jan 2006 15:04:05 -0700" | safeHTML }}</lastBuildDate>{{ end }}

-        <atom:link href="{{.Permalink}}" rel="self" type="application/rss+xml" />

-        {{ range .Data.Pages }}

-        <item>

-          <title>{{ .Title }}</title>

-          <link>{{ .Permalink }}</link>

-          <pubDate>{{ .Date.Format "Mon, 02 Jan 2006 15:04:05 -0700" | safeHTML }}</pubDate>

-          {{ with .Site.Author.email }}<author>{{.}}{{ with $.Site.Author.name }} ({{.}}){{end}}</author>{{end}}

-          <guid>{{ .Permalink }}</guid>

-          <description>{{ .Summary | html }}</description>

-        </item>

-        {{ end }}

-      </channel>

-    </rss>

+```xml

+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

+  <channel>

+    <title>{{ with .Title }}{{.}} on {{ end }}{{ .Site.Title }}</title>

+    <link>{{ .Permalink }}</link>

+    <description>Recent content {{ with .Title }}in {{.}} {{ end }}on {{ .Site.Title }}</description>

+    <generator>Hugo -- gohugo.io</generator>{{ with .Site.LanguageCode }}

+    <language>{{.}}</language>{{end}}{{ with .Site.Author.email }}

+    <managingEditor>{{.}}{{ with $.Site.Author.name }} ({{.}}){{end}}</managingEditor>{{end}}{{ with .Site.Author.email }}

+    <webMaster>{{.}}{{ with $.Site.Author.name }} ({{.}}){{end}}</webMaster>{{end}}{{ with .Site.Copyright }}

+    <copyright>{{.}}</copyright>{{end}}{{ if not .Date.IsZero }}

+    <lastBuildDate>{{ .Date.Format "Mon, 02 Jan 2006 15:04:05 -0700" | safeHTML }}</lastBuildDate>{{ end }}

+    <atom:link href="{{.URL}}" rel="self" type="application/rss+xml" />

+    {{ range first 15 .Data.Pages }}

+    <item>

+      <title>{{ .Title }}</title>

+      <link>{{ .Permalink }}</link>

+      <pubDate>{{ .Date.Format "Mon, 02 Jan 2006 15:04:05 -0700" | safeHTML }}</pubDate>

+      {{ with .Site.Author.email }}<author>{{.}}{{ with $.Site.Author.name }} ({{.}}){{end}}</author>{{end}}

+      <guid>{{ .Permalink }}</guid>

+      <description>{{ .Content | html }}</description>

+    </item>

+    {{ end }}

+  </channel>

+</rss>

+```

-**Important**: _Hugo will automatically add the following header line to this file on render… please don't include this in the template as it's not valid HTML._

-~~~css

+{{% warning "XML Header" %}}

+Hugo will automatically add the following header line to this file on render. Please do *not* include this in the template as it's not valid HTML.

+```xml

 <?xml version="1.0" encoding="utf-8" standalone="yes" ?>

-~~~

+```

+{{% /warning %}}

-## Referencing your RSS Feed in `<head>`

+## Reference your RSS Feed in `<head>`

 In your `header.html` template, you can specify your RSS feed in your `<head></head>` tag like this:

-~~~html

+```html

 {{ if .RSSLink }}

-  <link href="{{ .RSSLink }}" rel="alternate feed" type="application/rss+xml" title="{{ .Site.Title }}" />

+  <link href="{{ .RSSLink }}" rel="alternate" type="application/rss+xml" title="{{ .Site.Title }}" />

+  <link href="{{ .RSSLink }}" rel="feed" type="application/rss+xml" title="{{ .Site.Title }}" />

 {{ end }}

-~~~

+```

-... with the autodiscovery link specified by the line with `rel="alternate"`.

+...with the auto-discovery link specified by the line with `rel="alternate"`.

 The `.RSSLink` will render the appropriate RSS feed URL for the section, whether it's everything, posts in a section, or a taxonomy.

-**N.b.**, if you reference your RSS link, be sure to specify the mime type with `type="application/rss+xml"`.

+If you reference your RSS link, be sure to specify the MIME type with `type="application/rss+xml"`.

-~~~html

+```html

 <a href="{{ .URL }}" type="application/rss+xml" target="_blank">{{ .SomeText }}</a>

-~~~

+```

+[config]: /getting-started/configuration/

+[embedded]: #the-embedded-rss-xml

 [RSS 2.0]: http://cyber.law.harvard.edu/rss/rss.html "RSS 2.0 Specification"

+[section]: /content-management/sections/

--- /dev/null

+++ b/content/templates/section-templates.md

@@ -1,0 +1,126 @@

+---

+title: Section Page Templates

+linktitle: Section Templates

+description: Templates used for section pages are **lists** and therefore have all the variables and methods available to list pages.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [lists,sections]

+menu:

+  docs:

+    parent: "templates"

+    weight: 40

+weight: 40

+sections_weight: 40

+draft: false

+aliases: [/templates/sections/]

+toc: true

+---

+## Add Content and Front Matter to Section Templates

+To effectively leverage section page templates, you should first understand Hugo's [content organization](/content-management/organization/) and, specifically, the purpose of `_index.md` for adding content and front matter to section and other list pages.

+## Section Template Lookup Order

+The [lookup order][lookup] for section templates is as follows:

+1. `/layouts/section/<SECTION>.html`

+2. `/layouts/<SECTION>/list.html`

+3. `/layouts/_default/section.html`

+4. `/layouts/_default/list.html`

+5. `/themes/<THEME>/layouts/section/<SECTION>.html`

+6. `/themes/<THEME>/layouts/<SECTION>/list.html`

+7. `/themes/<THEME>/layouts/_default/section.html`

+8. `/themes/<THEME>/layouts/_default/list.html`

+## `.Site.GetPage` with Sections

+Every `Page` in Hugo has a `.Kind` attribute. `Kind` can easily be combined with the [`where` function][where] in your templates to create kind-specific lists of content. This method is ideal for creating lists, but there are times where you may want to fetch just the index page of a single section via the section's path.

+The [`.GetPage` function][getpage] looks up an index page of a given `Kind` and `path`.

+{{% note %}}

+`.GetPage` is not currently supported to grab single content files but *may* be supported in the future.

+{{% /note %}}

+You can call `.Site.GetPage` with two arguments: `kind` and `kind value`.

+These are the valid values for 'kind':

+1. `home`

+2. `section`

+3. `taxonomy`

+4. `taxonomyTerm`

+## Example: Creating a Default Section Template

+{{% code file="layouts/_default/section.html" download="section.html" %}}

+```html

+{{ define "main" }}

+  <main>

+      {{ .Content }}

+          <ul class="contents">

+          {{ range .Paginator.Pages }}

+              <li>{{.Title}}

+                  <div>

+                    {{ partial "summary.html" . }}

+                  </div>

+              </li>

+          {{ end }}

+          </ul>

+      {{ partial "pagination.html" . }}

+  </main>

+{{ end }}

+```

+{{% /code %}}

+### Example: Using `.Site.GetPage`

+The `.Site.GetPage` example that follows assumes the following project directory structure:

+```bash

+.

+└── content

+    ├── blog

+    │   ├── _index.md # "title: My Hugo Blog" in the front matter

+    │   ├── post-1.md

+    │   ├── post-2.md

+    │   └── post-3.md

+    └── events #Note there is no _index.md file in "events"

+        ├── event-1.md

+        └── event-2.md

+```

+`.Site.GetPage` will return `nil` if no `_index.md` page is found. Therefore, if `content/blog/_index.md` does not exist, the template will output the section name:

+```html

+<h1>{{ with .Site.GetPage "section" "blog" }}{{ .Title }}{{ end }}</h1>

+```

+Since `blog` has a section index page with front matter at `content/blog/_index.md`, the above code will return the following result:

+```html

+<h1>My Hugo Blog</h1>

+```

+If we try the same code with the `events` section, however, Hugo will default to the section title because there is no `content/events/_index.md` from which to pull content and front matter:

+```html

+<h1>{{ with .Site.GetPage "section" "events" }}{{ .Title }}{{ end }}</h1>

+```

+Which then returns the following:

+```html

+<h1>Events</h1>

+```

+[contentorg]: /content-management/organization/

+[getpage]: /functions/getpage/

+[lists]: /templates/lists/

+[lookup]: /templates/lookup-order/

+[where]: /functions/where/

--- /dev/null

+++ b/content/templates/shortcode-templates.md

@@ -1,0 +1,372 @@

+---

+title: Creating Your Own Shortcodes

+linktitle: Shortcode Templates

+description: You can extend Hugo's built-in shortcodes by creating your own using the same templating syntax as that for single and list pages.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [shortcodes]

+menu:

+  docs:

+    parent: "templates"

+    weight: 100

+weight: 100

+sections_weight: 100

+draft: false

+aliases: []

+toc: true

+---

+Shortcodes are a means to consolidate templating into small, reusable snippets that you can embed directly inside of your content. In this sense, you can think of shortcodes as the intermediary between [page and list templates][templates] and [basic content files][].

+{{% note %}}

+Hugo also ships with built-in shortcodes for common use cases. (See [Content Management: Shortcodes](/content-management/shortcodes/).)

+{{% /note %}}

+## Create Custom Shortcodes

+Hugo's built-in shortcodes cover many common, but not all, use cases. Luckily, Hugo provides the ability to easily create custom shortcodes to meet your website's needs.

+### File Placement

+To create a shortcode, place an HTML template in the `layouts/shortcodes` directory of your [source organization][]. Consider the file name carefully since the shortcode name will mirror that of the file but without the `.html` extension. For example, `layouts/shortcodes/myshortcode.html` will be called with either `{{</* myshortcode /*/>}}` or `{{%/* myshortcode /*/%}}` depending on the type of parameters you choose.

+### Shortcode Template Lookup Order

+Shortcode templates have a simple [lookup order][]:

+1. `/layouts/shortcodes/<SHORTCODE>.html`

+2. `/themes/<THEME>/layouts/shortcodes/<SHORTCODE>.html`

+### Positional vs Named Parameters

+You can create shortcodes using the following types of parameters:

+* Positional parameters

+* Named parameters

+* Positional *or* named parameters (i.e, "flexible")

+In shortcodes with positional parameters, the order of the parameters is important. If a shortcode has a single required value (e.g., the `youtube` shortcode below), positional parameters work very well and require less typing from content authors.

+For more complex layouts with multiple or optional parameters, named parameters work best. While less terse, named parameters require less memorization from a content author and can be added in a shortcode declaration in any order.

+Allowing both types of parameters (i.e., a "flexible" shortcode) is useful for complex layouts where you want to set default values that can be easily overridden by users.

+### Access Parameters

+All shortcode parameters can be accessed via the `.Get` method. Whether you pass a key (i.e., string) or a number to the `.Get` method depends on whether you are accessing a named or positional parameter, respectively.

+To access a parameter by name, use the `.Get` method followed by the named parameter as a quoted string:

+```golang

+{{ .Get "class" }}

+```

+To access a parameter by position, use the `.Get` followed by a numeric position, keeping in mind that positional parameters are zero-indexed:

+```golang

+{{ .Get 0 }}

+```

+`with` is great when the output depends on a parameter being set:

+```golang

+{{ with .Get "class"}} class="{{.}}"{{ end }}

+```

+`.Get` can also be used to check if a parameter has been provided. This is

+most helpful when the condition depends on either of the values, or both:

+```golang

+{{ or .Get "title" | .Get "alt" | if }} alt="{{ with .Get "alt"}}{{.}}{{else}}{{.Get "title"}}{{end}}"{{ end }}

+```

+#### `.Inner`

+If a closing shortcode is used, the `.Inner` variable will be populated with all of the content between the opening and closing shortcodes. If a closing shortcode is required, you can check the length of `.Inner` as an indicator of its existence.

+A shortcode with content declared via the `.Inner` variable can also be declared without the inline content and without the closing shortcode by using the self-closing syntax:

+```golang

+{{</* innershortcode /*/>}}

+```

+#### `.Params`

+The `.Params` variable in shortcodes contains the list parameters passed to shortcode for more complicated use cases. You can also access higher-scoped parameters with the following logic:

+`$.Params`

+: these are the parameters passed directly into the shortcode declaration (e.g., a YouTube video ID)

+`$.Page.Params`

+: refers to the page's params; the "page" in this case refers to the content file in which the shortcode is declared (e.g., a `shortcode_color` field in a content's front matter could be accessed via `$.Page.Params.shortcode_color`).

+`$.Page.Site.Params`

+: refers to global variables as defined in your [site's configuration file][config].

+#### `.IsNameParams`

+The `.IsNamedParams` variable checks whether the shortcode declaration uses named parameters and returns a boolean value.

+For example, you could create an `image` shortcode that can take either a `src` named parameter or the first positional parameter, depending on the preference of the content's author. Let's assume the `image` shortcode is called as follows:

+```md

+{{</* image src="images/my-image.jpg"*/>}}

+```

+You could then include the following as part of your shortcode templating:

+```html

+{{ if .IsNamedParams }}

+<img src="{{.Get "src" alt="">

+{{ else }}

+<img src="{{.Get 0}}" alt="">

+{{ end }}.

+```

+See the [example Vimeo shortcode][vimeoexample] below for `.IsNamedParams` in action.

+{{% warning %}}

+While you can create shortcode templates that accept both positional and named parameters, you *cannot* declare shortcodes in content with a mix of parameter types. Therefore, a shortcode declared like `{{</* image src="images/my-image.jpg" "This is my alt text" */>}}` will return an error.

+{{% /warning %}}

+You can also use the variable `.Page` to access all the normal [page variables][pagevars].

+A shortcodes can also be nested. In a nested shortcode, you can access the parent shortcode context with [`.Parent` variable][shortcodesvars]. This can be very useful for inheritance of common shortcode parameters from the root.

+## Custom Shortcode Examples

+The following are examples of the different types of shortcodes you can create via shortcode template files in `/layouts/shortcodes`.

+### Single-word Example: `year`

+Let's assume you would like to keep mentions of your copyright year current in your content files without having to continually review your markdown. Your goal is to be able to call the shortcode as follows:

+```markdown

+{{</* year */>}}

+```

+{{% code file="/layouts/shortcodes/year.html" %}}

+```golang

+{{ .Page.Now.Year }}

+```

+{{% /code %}}

+### Single Positional Example: `youtube`

+Embedded videos are a common addition to markdown content that can quickly become unsightly. The following is the code used by [Hugo's built-in YouTube shortcode][youtubeshortcode]:

+```golang

+{{</* youtube 09jf3ow9jfw */>}}

+```

+Would load the template at `/layouts/shortcodes/youtube.html`:

+{{% code file="/layouts/shortcodes/youtube.html" %}}

+```html

+<div class="embed video-player">

+<iframe class="youtube-player" type="text/html" width="640" height="385" src="http://www.youtube.com/embed/{{ index .Params 0 }}" allowfullscreen frameborder="0">

+</iframe>

+</div>

+```

+{{% /code %}}

+{{% code file="youtube-embed.html" copy="false" %}}

+```html

+<div class="embed video-player">

+    <iframe class="youtube-player" type="text/html"

+        width="640" height="385"

+        src="http://www.youtube.com/embed/09jf3ow9jfw"

+        allowfullscreen frameborder="0">

+    </iframe>

+</div>

+```

+{{% /code %}}

+### Single Named Example: `image`

+Let's say you want to create your own `img` shortcode rather than use Hugo's built-in [`figure` shortcode][figure]. Your goal is to be able to call the shortcode as follows in your content files:

+{{% code file="content-image.md" %}}

+```golang

+{{</* img src="/media/spf13.jpg" title="Steve Francia" */>}}

+```

+{{% /code %}}

+You have created the shortcode at `/layouts/shortcodes/img.html`, which loads the following shortcode template:

+{{% code file="/layouts/shortcodes/img.html" %}}

+```html

+<!-- image -->

+<figure {{ with .Get "class" }}class="{{.}}"{{ end }}>

+    {{ with .Get "link"}}<a href="{{.}}">{{ end }}

+        <img src="{{ .Get "src" }}" {{ if or (.Get "alt") (.Get "caption") }}alt="{{ with .Get "alt"}}{{.}}{{else}}{{ .Get "caption" }}{{ end }}"{{ end }} />

+    {{ if .Get "link"}}</a>{{ end }}

+    {{ if or (or (.Get "title") (.Get "caption")) (.Get "attr")}}

+    <figcaption>{{ if isset .Params "title" }}

+        <h4>{{ .Get "title" }}</h4>{{ end }}

+        {{ if or (.Get "caption") (.Get "attr")}}<p>

+        {{ .Get "caption" }}

+        {{ with .Get "attrlink"}}<a href="{{.}}"> {{ end }}

+            {{ .Get "attr" }}

+        {{ if .Get "attrlink"}}</a> {{ end }}

+        </p> {{ end }}

+    </figcaption>

+    {{ end }}

+</figure>

+<!-- image -->

+```

+{{% /code %}}

+Would be rendered as:

+{{% code file="img-output.html" copy="false" %}}

+```html

+<figure >

+    <img src="/media/spf13.jpg"  />

+    <figcaption>

+        <h4>Steve Francia</h4>

+    </figcaption>

+</figure>

+```

+{{% /code %}}

+### Single Flexible Example: `vimeo`

+```golang

+{{</* vimeo 49718712 */>}}

+{{</* vimeo id="49718712" class="flex-video" */>}}

+```

+Would load the template found at `/layouts/shortcodes/vimeo.html`:

+{{% code file="/layouts/shortcodes/vimeo.html" %}}

+```html

+{{ if .IsNamedParams }}

+  <div class="{{ if .Get "class" }}{{ .Get "class" }}{{ else }}vimeo-container{{ end }}">

+    <iframe src="//player.vimeo.com/video/{{ .Get "id" }}" allowfullscreen></iframe>

+  </div>

+{{ else }}

+  <div class="{{ if len .Params | eq 2 }}{{ .Get 1 }}{{ else }}vimeo-container{{ end }}">

+    <iframe src="//player.vimeo.com/video/{{ .Get 0 }}" allowfullscreen></iframe>

+  </div>

+{{ end }}

+```

+{{% /code %}}

+Would be rendered as:

+{{% code file="vimeo-iframes.html" copy="false" %}}

+```html

+<div class="vimeo-container">

+  <iframe src="//player.vimeo.com/video/49718712" allowfullscreen></iframe>

+</div>

+<div class="flex-video">

+  <iframe src="//player.vimeo.com/video/49718712" allowfullscreen></iframe>

+</div>

+```

+{{% /code %}}

+### Paired Example: `highlight`

+The following is taken from `highlight`, which is a [built-in shortcode][] that ships with Hugo.

+{{% code file="highlight-example.md" %}}

+```markdown

+{{</* highlight html */>}}

+  <html>

+    <body> This HTML </body>

+  </html>

+{{</* /highlight */>}}

+```

+{{% /code %}}

+The template for the `highlight` shortcode uses the following code, which is already included in Hugo:

+```golang

+{{ .Get 0 | highlight .Inner  }}

+```

+The rendered output of the HTML example code block will be as follows:

+{{% code file="syntax-highlighted.html" copy="false" %}}

+```html

+<div class="highlight" style="background: #272822"><pre style="line-height: 125%"><span style="color: #f92672">&lt;html&gt;</span>

+    <span style="color: #f92672">&lt;body&gt;</span> This HTML <span style="color: #f92672">&lt;/body&gt;</span>

+<span style="color: #f92672">&lt;/html&gt;</span>

+</pre></div>

+```

+{{% /code %}}

+{{% note %}}

+The preceding shortcode makes use of a Hugo-specific template function called `highlight`, which uses [Pygments](http://pygments.org) to add syntax highlighting to the example HTML code block. See the [developer tools page on syntax highlighting](/tools/syntax-highlighting/) for more information.

+{{% /note %}}

+### Nested Shortcode: Image Gallery

+Hugo's [`.Parent` shortcode variable][parent] returns a boolean value depending on whether the shortcode in question is called within the context of a *parent* shortcode. This provides an inheritance model for common shortcode parameters.

+The following example is contrived but demonstrates the concept. Assume you have a `gallery` shortcode that expects one named `class` parameter:

+{{% code file="layouts/shortcodes/gallery.html" %}}

+```html

+<div class="{{.Get "class"}}">

+  {{.Inner}}

+</div>

+```

+{{% /code %}}

+You also have an `image` shortcode with a single named `src` parameter that you want to call inside of `gallery` and other shortcodes so that the parent defines the context of each `image`:

+{{% code file="layouts/shortcodes/image.html" %}}

+```html

+{{- $src := .Get "src" -}}

+{{- with .Parent -}}

+  <img src="{{$src}}" class="{{.Get "class"}}-image">

+{{- else -}}

+  <img src="{{$src}}">

+{{- end }}

+```

+{{% /code %}}

+You can then call your shortcode in your content as follows:

+```markdown

+{{</* gallery class="content-gallery" */>}}

+  {{</* img src="/images/one.jpg" */>}}

+  {{</* img src="/images/two.jpg" */>}}

+{{</* /gallery */>}}

+{{</* img src="/images/three.jpg" */>}}

+```

+This will output the following HTML. Note how the first two `image` shortcodes inherit the `class` value of `content-gallery` set with the call to the parent `gallery`, whereas the third `image` only uses `src`:

+```html

+<div class="content-gallery">

+    <img src="/images/one.jpg" class="content-gallery-image">

+    <img src="/images/two.jpg" class="content-gallery-image">

+</div>

+<img src="/images/three.jpg">

+```

+## More Shortcode Examples

+More shortcode examples can be found in the [shortcodes directory for spf13.com][spfscs] and the [shortcodes directory for the Hugo docs][docsshortcodes].

+[basic content files]: /content-management/formats/ "See how Hugo leverages markdown--and other supported formats--to create content for your website."

+[built-in shortcode]: /content-management/shortcodes/

+[config]: /getting-started/configuration/ "Learn more about Hugo's built-in configuration variables as well as how to us your site's configuration file to include global key-values that can be used throughout your rendered website."

+[Content Management: Shortcodes]: /content-management/shortcodes/#using-hugo-s-built-in-shortcodes "Check this section if you are not familiar with the definition of what a shortcode is or if you are unfamiliar with how to use Hugo's built-in shortcodes in your content files."

+[source organization]: /getting-started/directory-structure/#directory-structure-explained "Learn how Hugo scaffolds new sites and what it expects to find in each of your directories."

+[docsshortcodes]: https://github.com/gohugoio/hugo/tree/master/docs/layouts/shortcodes "See the shortcode source directory for the documentation site you're currently reading."

+[figure]: /content-management/shortcodes/#figure

+[hugosc]: /content-management/shortcodes/#using-hugo-s-built-in-shortcodes

+[lookup order]: /templates/lookup-order/ "See the order in which Hugo traverses your template files to decide where and how to render your content at build time"

+[pagevars]: /variables/page/ "See which variables you can leverage in your templating for page vs list templates."

+[parent]: /variables/shortcodes/

+[shortcodesvars]: /variables/shortcodes/ "Certain variables are specific to shortcodes, although most .Page variables can be accessed within your shortcode template."

+[spfscs]: https://github.com/spf13/spf13.com/tree/master/layouts/shortcodes "See more examples of shortcodes by visiting the shortcode directory of the source for spf13.com, the blog of Hugo's creator, Steve Francia."

+[templates]: /templates/ "The templates section of the Hugo docs."

+[vimeoexample]: #single-flexible-example-vimeo

+[youtubeshortcode]: /content-management/shortcodes/#youtube "See how to use Hugo's built-in YouTube shortcode."

\ No newline at end of file

--- /dev/null

+++ b/content/templates/single-page-templates.md

@@ -1,0 +1,107 @@

+---

+title: Single Page Templates

+linktitle:

+description: The primary view of content in Hugo is the single view. Hugo will render every Markdown file provided with a corresponding single template.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-04-06

+categories: [templates]

+#tags: [page]

+menu:

+  docs:

+    parent: "templates"

+    weight: 60

+weight: 60

+sections_weight: 60

+draft: false

+aliases: [/layout/content/]

+toc: true

+---

+## Single Page Template Lookup Order

+You can specify a [content's `type`][content type] and `layout` in a single content file's [front matter][]. However, you cannot specify `section` because this is determined based on file location (see [content section][section]).

+Hugo assumes your content section and content type are the same unless you tell Hugo otherwise by providing a `type` directly in the front matter of a content file. This is why #1 and #3 come before #2 and #4, respectively, in the following lookup order. Values in angle brackets (`<>`) are variable.

+1. `/layouts/<TYPE>/<LAYOUT>.html`

+2. `/layouts/<SECTION>>/<LAYOUT>.html`

+3. `/layouts/<TYPE>/single.html`

+4. `/layouts/<SECTION>/single.html`

+5. `/layouts/_default/single.html`

+6. `/themes/<THEME>/layouts/<TYPE>/<LAYOUT>.html`

+7. `/themes/<THEME>/layouts/<SECTION>/<LAYOUT>.html`

+8. `/themes/<THEME>/layouts/<TYPE>/single.html`

+9. `/themes/<THEME>/layouts/<SECTION>/single.html`

+10. `/themes/<THEME>/layouts/_default/single.html`

+## Example Single Page Templates

+Content pages are of the type `page` and will therefore have all the [page variables][pagevars] and [site variables][] available to use in their templates.

+### `post/single.html`

+This single page template makes use of Hugo [base templates][], the [`.Format` function][] for dates, the [`.WordCount` page variable][pagevars], and ranges through the single content's specific [taxonomies][pagetaxonomy]. [`with`][] is also used to check whether the taxonomies are set in the front matter.

+{{% code file="layouts/post/single.html" download="single.html" %}}

+```html

+{{ define "main" }}

+<section id="main">

+  <h1 id="title">{{ .Title }}</h1>

+  <div>

+        <article id="content">

+           {{ .Content }}

+        </article>

+  </div>

+</section>

+<aside id="meta">

+    <div>

+    <section>

+      <h4 id="date"> {{ .Date.Format "Mon Jan 2, 2006" }} </h4>

+      <h5 id="wordcount"> {{ .WordCount }} Words </h5>

+    </section>

+    {{ with .Params.topics }}

+    <ul id="topics">

+      {{ range . }}

+        <li><a href="{{ "topics" | absURL}}{{ . | urlize }}">{{ . }}</a> </li>

+      {{ end }}

+    </ul>

+    {{ end }}

+    {{ with .Params.tags }}

+    <ul id="tags">

+      {{ range . }}

+        <li> <a href="{{ "tags" | absURL }}{{ . | urlize }}">{{ . }}</a> </li>

+      {{ end }}

+    </ul>

+    {{ end }}

+    </div>

+    <div>

+        {{ with .PrevInSection }}

+          <a class="previous" href="{{.Permalink}}"> {{.Title}}</a>

+        {{ end }}

+        {{ with .NextInSection }}

+          <a class="next" href="{{.Permalink}}"> {{.Title}}</a>

+        {{ end }}

+    </div>

+</aside>

+{{ end }}

+```

+{{% /code %}}

+To easily generate new instances of a content type (e.g., new `.md` files in a section like `project/`) with preconfigured front matter, use [content archetypes][archetypes].

+[archetypes]: /content-management/archetypes/

+[base templates]: /templates/base/

+[config]: /getting-started/configuration/

+[content type]: /content-management/types/

+[directory structure]: /getting-started/directory-structure/

+[dry]: https://en.wikipedia.org/wiki/Don%27t_repeat_yourself

+[`.Format` function]: /functions/format/

+[front matter]: /content-management/front-matter/

+[pagetaxonomy]: /templates/taxonomy-templates/#displaying-a-single-piece-of-content-s-taxonomies

+[pagevars]: /variables/page/

+[partials]: /templates/partials/

+[section]: /content-management/sections/

+[site variables]: /variables/site/

+[spf13]: http://spf13.com/

+[`with`]: /functions/with/

\ No newline at end of file

--- /dev/null

+++ b/content/templates/sitemap-template.md

@@ -1,0 +1,75 @@

+---

+title: Sitemap Template

+# linktitle: Sitemap

+description: Hugo ships with a built-in template file observing the v0.9 of the Sitemap Protocol, but you can override this template if needed.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [sitemap, xml]

+menu:

+  docs:

+    parent: "templates"

+    weight: 160

+weight: 160

+sections_weight: 160

+draft: false

+aliases: [/layout/sitemap/,/templates/sitemap/]

+toc: false

+---

+A single Sitemap template is used to generate the `sitemap.xml` file.

+Hugo automatically comes with this template file. *No work is needed on

+the users' part unless they want to customize `sitemap.xml`.*

+A sitemap is a `Page` and therefore has all the [page variables][pagevars] available to use in this template along with Sitemap-specific ones:

+`.Sitemap.ChangeFreq`

+: The page change frequency

+`.Sitemap.Priority`

+: The priority of the page

+`.Sitemap.Filename`

+: The sitemap filename

+If provided, Hugo will use `/layouts/sitemap.xml` instead of the internal `sitemap.xml` template that ships with Hugo.

+## Hugo’s sitemap.xml

+This template respects the version 0.9 of the [Sitemap Protocol](http://www.sitemaps.org/protocol.html).

+```xml

+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

+  {{ range .Data.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 }}

+    <changefreq>{{ . }}</changefreq>{{ end }}{{ if ge .Sitemap.Priority 0.0 }}

+    <priority>{{ .Sitemap.Priority }}</priority>{{ end }}

+  </url>

+  {{ end }}

+</urlset>

+```

+{{% note %}}

+Hugo will automatically add the following header line to this file

+on render. Please don't include this in the template as it's not valid HTML.

+`<?xml version="1.0" encoding="utf-8" standalone="yes" ?>`

+{{% /note %}}

+## Configure `sitemap.xml`

+Defaults for `<changefreq>`, `<priority>` and `filename` values can be set in the site's config file, e.g.:

+```toml

+[sitemap]

+  changefreq = "monthly"

+  priority = 0.5

+  filename = "sitemap.xml"

+```

+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/

\ No newline at end of file

--- a/content/templates/sitemap.md

+++ /dev/null

@@ -1,75 +1,0 @@

----

-aliases:

-- /layout/sitemap/

-lastmod: 2015-12-10

-date: 2014-05-07

-linktitle: Sitemap

-menu:

-  main:

-    parent: layout

-next: /templates/404

-notoc: true

-prev: /templates/rss

-title: Sitemap Template

-weight: 95

----

-A single Sitemap template is used to generate the `sitemap.xml` file.

-Hugo automatically comes with this template file. **No work is needed on

-the users' part unless they want to customize `sitemap.xml`.**

-A sitemap is a `Page` and have all the [page

-variables](/layout/variables/) available to use in this template

-along with Sitemap-specific ones:

-**.Sitemap.ChangeFreq** The page change frequency<br>

-**.Sitemap.Priority** The priority of the page<br>

-**.Sitemap.Filename** The sitemap filename<br>

-If provided, Hugo will use `/layouts/sitemap.xml` instead of the internal

-one.

-## Hugo’s sitemap.xml

-This template uses the version 0.9 of the [Sitemap

-Protocol](http://www.sitemaps.org/protocol.html) with Google's [hreflang

-attributes](https://support.google.com/webmasters/answer/2620865?hl=en&topic=2370587&ctx=topic)

-for linking to translated content.

-    <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"

-      xmlns:xhtml="http://www.w3.org/1999/xhtml">

-      {{ range .Data.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 }}

-        <changefreq>{{ . }}</changefreq>{{ end }}{{ if ge .Sitemap.Priority 0.0 }}

-        <priority>{{ .Sitemap.Priority }}</priority>{{ end }}{{ if .IsTranslated }}{{ range .Translations }}

-        <xhtml:link

-                    rel="alternate"

-                    hreflang="{{ .Lang }}"

-                    href="{{ .Permalink }}"

-                    />{{ end }}

-        <xhtml:link

-                    rel="alternate"

-                    hreflang="{{ .Lang }}"

-                    href="{{ .Permalink }}"

-                    />{{ end }}

-      </url>

-      {{ end }}

-    </urlset>

-***Important:** Hugo will automatically add the following header line to this file

-on render. Please don't include this in the template as it's not valid HTML.*

-    <?xml version="1.0" encoding="utf-8" standalone="yes" ?>

-## Configuring sitemap.xml

-Defaults for `<changefreq>`, `<priority>` and `filename` values can be set in the site's config file, e.g.:

-    [sitemap]

-      changefreq = "monthly"

-      priority = 0.5

-      filename = "sitemap.xml"

-The same fields can be specified in an individual page's front matter in order to override the value for that page.

--- /dev/null

+++ b/content/templates/taxonomy-templates.md

@@ -1,0 +1,341 @@

+---

+title: Taxonomy Templates

+# linktitle:

+description: Taxonomy templating includes taxonomy list pages, taxonomy terms pages, and using taxonomies in your single page templates.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [taxonomies,metadata,front matter,terms]

+menu:

+  docs:

+    parent: "templates"

+    weight: 50

+weight: 50

+sections_weight: 50

+draft: false

+aliases: [/taxonomies/displaying/,/templates/terms/,/indexes/displaying/,/taxonomies/templates/,/indexes/ordering/, /templates/taxonomies/, /templates/taxonomy/]

+toc: true

+---

+<!-- NOTE! Check on https://github.com/gohugoio/hugo/issues/2826 for shifting of terms' pages to .Data.Pages AND

+https://discourse.gohugo.io/t/how-to-specify-category-slug/4856/15 for original discussion.-->

+Hugo includes support for user-defined groupings of content called **taxonomies**. Taxonomies are classifications that demonstrate logical relationships between content. See [Taxonomies under Content Management](/content-management/taxonomies) if you are unfamiliar with how Hugo leverages this powerful feature.

+Hugo provides multiple ways to use taxonomies throughout your project templates:

+* Order the way the terms for a taxonomy are displayed in a [taxonomy terms template](#taxonomy-terms-template)

+* Order the way content associated with a taxonomy term is displayed in a [taxonomy list template](#taxonomy-list-template)

+* List a single content's taxonomy terms within a [single page template][]

+## Taxonomy List Templates

+Taxonomy list page templates are lists and therefore have all the variables and methods available to [list pages][lists].

+### Taxonomy List Template Lookup Order

+A taxonomy will be rendered at /`PLURAL`/`TERM`/ (e.g., http://spf13.com/topics/golang/) according to the following lookup order:

+1. `/layouts/taxonomy/<SINGULAR>.html`

+2. `/layouts/_default/taxonomy.html`

+3. `/layouts/_default/list.html`

+4. `/themes/<THEME>/layouts/taxonomy/<SINGULAR>.html`

+5. `/themes/<THEME>/layouts/_default/taxonomy.html`

+6. `/themes/<THEME>/layouts/_default/list.html`

+## Taxonomy Terms Template

+### Taxonomy Terms Templates Lookup Order

+A taxonomy terms page will be rendered at `yoursite.com/<PLURALTAXONOMYNAME>`/ (e.g., http://spf13.com/topics/) according to the following lookup order:

+1. `/layouts/taxonomy/<SINGULAR>.terms.html`

+2. `/layouts/_default/terms.html`

+3. `/themes/<THEME>/layouts/taxonomy/<SINGULAR>.terms.html`

+4. `/themes/<THEME>/layouts/_default/terms.html`

+{{% warning "The Taxonomy Terms Template has a Unique Lookup Order" %}}

+If Hugo does not find a terms template in `layout/` or `/themes/<THEME>/layouts/`, Hugo will *not* render a taxonomy terms page.

+{{% /warning %}}

+<!-- Begin /taxonomies/methods/ -->

+Hugo makes a set of values and methods available on the various Taxonomy structures.

+### Taxonomy Methods

+A Taxonomy is a `map[string]WeightedPages`.

+.Get(term)

+: Returns the WeightedPages for a term.

+.Count(term)

+: The number of pieces of content assigned to this term.

+.Alphabetical

+: Returns an OrderedTaxonomy (slice) ordered by Term.

+.ByCount

+: Returns an OrderedTaxonomy (slice) ordered by number of entries.

+### OrderedTaxonomy

+Since Maps are unordered, an OrderedTaxonomy is a special structure that has a defined order.

+```go

+[]struct {

+    Name          string

+    WeightedPages WeightedPages

+}

+```

+Each element of the slice has:

+.Term

+: The Term used.

+.WeightedPages

+: A slice of Weighted Pages.

+.Count

+: The number of pieces of content assigned to this term.

+.Pages

+: All Pages assigned to this term. All [list methods][renderlists] are available to this.

+## WeightedPages

+WeightedPages is simply a slice of WeightedPage.

+```go

+type WeightedPages []WeightedPage

+```

+.Count(term)

+: The number of pieces of content assigned to this term.

+.Pages

+: Returns a slice of pages, which then can be ordered using any of the [list methods][renderlists].

+<!-- Begin /taxonomies/ordering/ -->

+## Order Taxonomies

+Taxonomies can be ordered by either alphabetical key or by the number of content pieces assigned to that key.

+### Order Alphabetically Example

+```html

+<ul>

+  {{ $data := .Data }}

+  {{ range $key, $value := .Data.Taxonomy.Alphabetical }}

+  <li><a href="{{ $.Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $value.Name | urlize }}"> {{ $value.Name }} </a> {{ $value.Count }} </li>

+  {{ end }}

+</ul>

+```

+### Order by Popularity Example

+```html

+<ul>

+  {{ $data := .Data }}

+  {{ range $key, $value := .Data.Taxonomy.ByCount }}

+  <li><a href="{{ $.Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $value.Name | urlize }}"> {{ $value.Name }} </a> {{ $value.Count }} </li>

+  {{ end }}

+</ul>

+```

+<!-- [See Also Taxonomy Lists](/templates/list/) -->

+## Order Content within Taxonomies

+Hugo uses both `date` and `weight` to order content within taxonomies.

+Each piece of content in Hugo can optionally be assigned a date. It can also be assigned a weight for each taxonomy it is assigned to.

+When iterating over content within taxonomies, the default sort is the same as that used for [section and list pages]() first by weight then by date. This means that if the weights for two pieces of content are the same, than the more recent content will be displayed first. The default weight for any piece of content is 0.

+### Assign Weight

+Content can be assigned weight for each taxonomy that it's assigned to.

+```toml

++++

+tags = [ "a", "b", "c" ]

+tags_weight = 22

+categories = ["d"]

+title = "foo"

+categories_weight = 44

++++

+Front Matter with weighted tags and categories

+```

+The convention is `taxonomyname_weight`.

+In the above example, this piece of content has a weight of 22 which applies to the sorting when rendering the pages assigned to the "a", "b" and "c" values of the 'tag' taxonomy.

+It has also been assigned the weight of 44 when rendering the 'd' category.

+With this the same piece of content can appear in different positions in different taxonomies.

+Currently taxonomies only support the default ordering of content which is weight -> date.

+<!-- Begin /taxonomies/templates/ -->

+There are two different templates that the use of taxonomies will require you to provide.

+Both templates are covered in detail in the templates section.

+A [list template](/templates/list/) is any template that will be used to render multiple pieces of content in a single html page. This template will be used to generate all the automatically created taxonomy pages.

+A [taxonomy terms template](/templates/terms/) is a template used to

+generate the list of terms for a given template.

+<!-- Begin /taxonomies/displaying/ -->

+There are four common ways you can display the data in your

+taxonomies in addition to the automatic taxonomy pages created by hugo

+using the [list templates](/templates/list/):

+1. For a given piece of content, you can list the terms attached

+2. For a given piece of content, you can list other content with the same

+   term

+3. You can list all terms for a taxonomy

+4. You can list all taxonomies (with their terms)

+## Display a Single Piece of Content's Taxonomies

+Within your content templates, you may wish to display the taxonomies that piece of content is assigned to.

+Because we are leveraging the front matter system to define taxonomies for content, the taxonomies assigned to each content piece are located in the usual place (i.e., `.Params.<TAXONOMYPLURAL>`).

+### Example: List Tags in a Single Page Template

+```html

+<ul id="tags">

+  {{ range .Params.tags }}

+    <li><a href="{{ "/tags/" | relLangURL }}{{ . | urlize }}">{{ . }}</a> </li>

+  {{ end }}

+</ul>

+```

+If you want to list taxonomies inline, you will have to take care of optional plural endings in the title (if multiple taxonomies), as well as commas. Let's say we have a taxonomy "directors" such as `directors: [ "Joel Coen", "Ethan Coen" ]` in the TOML-format front matter.

+To list such taxonomies, use the following:

+### Example: Comma-delimit Tags in a Single Page Template

+```html

+{{ if .Params.directors }}

+  <strong>Director{{ if gt (len .Params.directors) 1 }}s{{ end }}:</strong>

+  {{ range $index, $director := .Params.directors }}{{ if gt $index 0 }}, {{ end }}<a href="{{ "directors/" | relURL }}{{ . | urlize }}">{{ . }}</a>{{ end }}

+{{ end }}

+```

+Alternatively, you may use the [delimit template function][delimit] as a shortcut if the taxonomies should just be listed with a separator. See {{< gh 2143 >}} on GitHub for discussion.

+## List Content with the Same Taxonomy Term

+If you are using a taxonomy for something like a series of posts, you can list individual pages associated with the same taxonomy. This is also a quick and dirty method for showing related content:

+### Example: Showing Content in Same Series

+```html

+<ul>

+  {{ range .Site.Taxonomies.series.golang }}

+    <li><a href="{{ .Page.RelPermalink }}">{{ .Page.Title }}</a></li>

+  {{ end }}

+</ul>

+```

+## List All content in a Given taxonomy

+This would be very useful in a sidebar as “featured content”. You could even have different sections of “featured content” by assigning different terms to the content.

+### Example: Grouping "Featured" Content

+```html

+<section id="menu">

+    <ul>

+        {{ range $key, $taxonomy := .Site.Taxonomies.featured }}

+        <li> {{ $key }} </li>

+        <ul>

+            {{ range $taxonomy.Pages }}

+            <li hugo-nav="{{ .RelPermalink}}"><a href="{{ .Permalink}}"> {{ .LinkTitle }} </a> </li>

+            {{ end }}

+        </ul>

+        {{ end }}

+    </ul>

+</section>

+```

+## Render a Site's Taxonomies

+If you wish to display the list of all keys for your site's taxonomy, you can retrieve them from the [`.Site` variable][sitevars] available on every page.

+This may take the form of a tag cloud, a menu, or simply a list.

+The following example displays all terms in a site's tags taxonomy:

+### Example: List All Site Tags

+```html

+<ul id="all-tags">

+  {{ range $name, $taxonomy := .Site.Taxonomies.tags }}

+    <li><a href="{{ "/tags/" | relLangURL }}{{ $name | urlize }}">{{ $name }}</a></li>

+  {{ end }}

+</ul>

+```

+### Example: List All Taxonomies, Terms, and Assigned Content

+This example will list all taxonomies and their terms, as well as all the content assigned to each of the terms.

+{{% code file="layouts/partials/all-taxonomies.html" download="all-taxonomies.html" download="all-taxonomies.html" %}}

+```html

+<section>

+  <ul id="all-taxonomies">

+    {{ range $taxonomyname, $taxonomy := .Site.Taxonomies }}

+      <li><a href="{{ "/" | relLangURL}}{{ $taxonomyname | urlize }}">{{ $taxonomyname }}</a>

+        <ul>

+          {{ range $key, $value := $taxonomy }}

+          <li> {{ $key }} </li>

+                <ul>

+                {{ range $value.Pages }}

+                    <li hugo-nav="{{ .RelPermalink}}"><a href="{{ .Permalink}}"> {{ .LinkTitle }} </a> </li>

+                {{ end }}

+                </ul>

+          {{ end }}

+        </ul>

+      </li>

+    {{ end }}

+  </ul>

+</section>

+```

+{{% /code %}}

+## `.Site.GetPage` for Taxonomies

+Because taxonomies are lists, the [`.GetPage` function][getpage] can be used to get all the pages associated with a particular taxonomy term using a terse syntax. The following ranges over the full list of tags on your site and links to each of the individual taxonomy pages for each term without having to use the more fragile URL construction of the "List All Site Tags" example above:

+{{% code file="links-to-all-tags" %}}

+```html

+<ul class="tags">

+  {{ range ($.Site.GetPage "taxonomyTerm" "tags").Pages }}

+   <li><a href="{{ .Permalink }}">{{ .Title}}</a></li>

+  {{ end }}

+</ul>

+```

+{{% /code %}}

+<!--### `.Site.GetPage` Taxonomy List Example

+### `.Site.GetPage` Taxonomy Terms Example -->

+[delimit]: /functions/delimit/

+[getpage]: /functions/getpage/

+[lists]: /templates/lists/

+[renderlists]: /templates/lists/

+[single page template]: /templates/single-page-templates/

+[sitevars]: /variables/site/

--- /dev/null

+++ b/content/templates/template-debugging.md

@@ -1,0 +1,81 @@

+---

+title: Template Debugging

+# linktitle: Template Debugging

+description: You can use Go templates' `printf` function to debug your Hugo  templates. These snippets provide a quick and easy visualization of the variables available to you in different contexts.

+godocref: http://golang.org/pkg/fmt/

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [debugging,troubleshooting]

+menu:

+  docs:

+    parent: "templates"

+    weight: 180

+weight: 180

+sections_weight: 180

+draft: false

+aliases: []

+toc: false

+---

+Here are some snippets you can add to your template to answer some common questions.

+These snippets use the `printf` function available in all Go templates.  This function is an alias to the Go function, [fmt.Printf](http://golang.org/pkg/fmt/).

+## What Variables are Available in this Context?

+You can use the template syntax, `$.`, to get the top-level template context from anywhere in your template. This will print out all the values under, `.Site`.

+```html

+{{ printf "%#v" $.Site }}

+```

+This will print out the value of `.Permalink`:

+```html

+{{ printf "%#v" .Permalink }}

+```

+This will print out a list of all the variables scoped to the current context

+(`.`, aka ["the dot"][tempintro]).

+```html

+{{ printf "%#v" . }}

+```

+When developing a [homepage][], what does one of the pages you're looping through look like?

+```html

+{{ range .Data.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 %}}

+## Why Am I Showing No Defined Variables?

+Check that you are passing variables in the `partial` function:

+```html

+{{ partial "header" }}

+```

+This example will render the header partial, but the header partial will not have access to any contextual variables. You need to pass variables explicitly. For example, note the addition of ["the dot"][tempintro].

+```html

+{{ partial "header" . }}

+```

+The dot (`.`) is considered fundamental to understanding Hugo templating. For more information, see [Introduction to Hugo Templating][tempintro].

+[homepage]: /templates/homepage/

+[tempintro]: /templates/introduction/

\ No newline at end of file

--- a/content/templates/terms.md

+++ /dev/null

@@ -1,176 +1,0 @@

----

-aliases:

-- /indexes/lists/

-- /doc/indexes/

-- /extras/indexes

-lastmod: 2015-09-15

-date: 2014-05-21

-linktitle: Taxonomy Terms

-menu:

-  main:

-    parent: layout

-next: /templates/views

-prev: /templates/homepage

-title: Taxonomy Terms Template

-weight: 60

-toc: true

----

-A unique template is needed to create a list of the terms for a given

-taxonomy. This is different from the [list template](/templates/list/)

-as that template is a list of content, whereas this is a list of meta data.

-Note that a taxonomy terms page can also have a content file with frontmatter,  see [Source Organization]({{< relref "overview/source-directory.md#content-for-home-page-and-other-list-pages" >}}).

-## Which Template will be rendered?

-Hugo uses a set of rules to figure out which template to use when

-rendering a specific page.

-A Taxonomy Terms List will be rendered at /`PLURAL`/

-(e.g. http://spf13.com/topics/)

-from the following prioritized list:

-* /layouts/taxonomy/`SINGULAR`.terms.html (e.g. `/layouts/taxonomy/topic.terms.html`)

-* /layouts/\_default/terms.html

-If a file isn’t present,

-then the next one in the list will be used. This enables you to craft

-specific layouts when you want to without creating more templates

-than necessary. For most sites, only the `_default` file at the end of

-the list will be needed.

-If that neither file is found in either the /layouts or /theme/layouts

-directory, then Hugo will not render the taxonomy terms pages. It is also

-common for people to render taxonomy terms lists on other pages such as

-the homepage or the sidebar (such as a tag cloud) and not have a

-dedicated page for the terms.

-## Variables

-Taxonomy Terms pages are of the type `Page` and have all the

-[page variables](/templates/variables/) and

-[site variables](/templates/variables/)

-available to use in the templates.

-Taxonomy Terms pages will additionally have:

-* **.Data.Singular** The singular name of the taxonomy

-* **.Data.Plural** The plural name of the taxonomy

-* **.Data.Pages** (or as **.Pages**) The taxonomy Terms index pages

-* **.Data.Terms** The taxonomy itself

-* **.Data.Terms.Alphabetical** The Terms alphabetized

-* **.Data.Terms.ByCount** The Terms ordered by popularity

-The last two can also be reversed: **.Data.Terms.Alphabetical.Reverse**, **.Data.Terms.ByCount.Reverse**.

-### Example terms.html files

-This content template is used for [spf13.com](http://spf13.com/).

-It makes use of [partial templates](/templates/partials/). The list of taxonomy

-templates cannot use a [content view](/templates/views/) as they don't display the content, but

-rather information about the content.

-This particular template lists all of the Tags used on

-[spf13.com](http://spf13.com/) and provides a count for the number of pieces of

-content tagged with each tag.

-`.Data.Terms` is a map of terms ⇒ [contents]

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    <section id="main">

-      <div>

-        <h1 id="title">{{ .Title }}</h1>

-        <ul>

-        {{ $data := .Data }}

-        {{ range $key, $value := .Data.Terms }}

-          <li><a href="{{ $.Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $key | urlize }}">{{ $key }}</a> {{ len $value }}</li>

-        {{ end }}

-       </ul>

-      </div>

-    </section>

-    {{ partial "footer.html" . }}

-Another example listing the content for each term (ordered by Date):

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    <section id="main">

-      <div>

-        <h1 id="title">{{ .Title }}</h1>

-        {{ $data := .Data }}

-        {{ range $key,$value := .Data.Terms.ByCount }}

-        <h2><a href="{{ $.Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $value.Name | urlize }}">{{ $value.Name }}</a> {{ $value.Count }}</h2>

-        <ul>

-        {{ range $value.Pages.ByDate }}

-          <li><a href="{{ .Permalink }}">{{ .Title }}</a></li>

-        {{ end }}

-        </ul>

-        {{ end }}

-      </div>

-    </section>

-    {{ partial "footer.html" . }}

-## Ordering

-Hugo can order the term meta data in two different ways. It can be ordered:

-* by the number of contents assigned to that key, or

-* alphabetically.

-### Example terms.html file (alphabetical)

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    <section id="main">

-      <div>

-        <h1 id="title">{{ .Title }}</h1>

-        <ul>

-        {{ $data := .Data }}

-        {{ range $key, $value := .Data.Terms.Alphabetical }}

-          <li><a href="{{ $.Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $value.Name | urlize }}">{{ $value.Name }}</a> {{ $value.Count }}</li>

-        {{ end }}

-        </ul>

-      </div>

-    </section>

-    {{ partial "footer.html" . }}

-### Example terms.html file (ordered by popularity)

-    {{ partial "header.html" . }}

-    {{ partial "subheader.html" . }}

-    <section id="main">

-      <div>

-        <h1 id="title">{{ .Title }}</h1>

-        <ul>

-        {{ $data := .Data }}

-        {{ range $key, $value := .Data.Terms.ByCount }}

-          <li><a href="{{ $.Site.LanguagePrefix }}/{{ $data.Plural }}/{{ $value.Name | urlize }}">{{ $value.Name }}</a> {{ $value.Count }}</li>

-        {{ end }}

-        </ul>

-      </div>

-    </section>

-    {{ partial "footer.html" . }}

-Hugo can also order and paginate the term index pages in all the normal ways.

-### Example terms.html snippet (paginated and ordered by date)

-    <h1 id="title">{{ .Title }}</h1>

-    <ul>

-      {{ range .Paginator.Pages.ByDate.Reverse }}

-        <li><a href="{{ .Permalink }}">{{ .Title }}</a> {{ $.Data.Terms.Count .Data.Term }}</li>

-      {{ end }}

-    </ul>

--- a/content/templates/variables.md

+++ /dev/null

@@ -1,237 +1,0 @@

----

-aliases:

-- /doc/variables/

-- /layout/variables/

-lastmod: 2015-12-08

-date: 2013-07-01

-linktitle: Variables

-menu:

-  main:

-    parent: layout

-next: /templates/content

-prev: /templates/functions

-title: Template Variables

-weight: 20

-toc: true

----

-Hugo makes a set of values available to the templates. Go templates are context based. The following

-are available in the context for the templates.

-## Page Variables

-The following is a list of most of the accessible variables which can be

-defined for a piece of content. Many of these will be defined in the front

-matter, content or derived from file location.

-**See also:** [Scratch](/extras/scratch) for page-scoped writable variables.

-**.Content** The content itself, defined below the front matter.<br>

-**.Data** The data specific to this type of page.<br>

-**.Date** The date the page is associated with.<br>

-**.Description** The description for the page.<br>

-**.Draft** A boolean, `true` if the content is marked as a draft in the front matter.<br>

-**.ExpiryDate** The date where the content is scheduled to expire on.<br>

-**.FuzzyWordCount** The approximate number of words in the content.<br>

-**.Hugo** See [Hugo Variables]({{< relref "#hugo-variables" >}}) below.<br>

-**.IsHome** True if this is the home page.<br>

-**.IsNode** Always false for regular content pages.<br>

-**.IsPage** Always true for regular content pages.<br>

-**.IsTranslated** Whether there are any translations to display.<br>

-**.Keywords** The meta keywords for this content.<br>

-**.Kind** What *kind* of page is this: is one of *page, home, section, taxonomy or taxonomyTerm.* There are also *RSS, sitemap, robotsTXT and 404*, but these will only available during rendering of that kind of page, and not available in any of the `Pages` collections.<br>

-**.Lang** Language taken from the language extension notation.<br>

-**.Language** A language object that points to this the language's definition in the site config.<br>

-**.Lastmod** The date the content was last modified.<br>

-**.LinkTitle** Access when creating links to this content. Will use `linktitle` if set in front matter, else `title`.<br>

-**.Next** Pointer to the following content (based on pub date).<br>

-**.NextInSection** Pointer to the following content within the same section (based on pub date)<br>

-**.Pages** a collection of associated pages. This will be nil for regular content pages. This is an alias for **.Data.Pages**.<br>

-**.Permalink** The Permanent link for this page.<br>

-**.Prev** Pointer to the previous content (based on pub date).<br>

-**.PrevInSection** Pointer to the previous content within the same section (based on pub date). For example, `{{if .PrevInSection}}{{.PrevInSection.Permalink}}{{end}}`.<br>

-**.PublishDate** The date the content is published on.<br>

-**.RSSLink** Link to the taxonomies' RSS link.<br>

-**.RawContent** Raw Markdown content without the metadata header. Useful with [remarkjs.com](http://remarkjs.com)<br>

-**.ReadingTime** The estimated time it takes to read the content in minutes.<br>

-**.Ref** Returns the permalink for a given reference.  Example: `.Ref "sample.md"`. See [cross-references]({{% ref "extras/crossreferences.md" %}}). Does not handle in-page fragments correctly.<br>

-**.RelPermalink** The Relative permanent link for this page.<br>

-**.RelRef** Returns the relative permalink for a given reference.  Example: `RelRef "sample.md"`. See [cross-references]({{% ref "extras/crossreferences.md" %}}). Does not handle in-page fragments.<br>

-**.Section** The [section](/content/sections/) this content belongs to.<br>

-**.Site** See [Site Variables]({{< relref "#site-variables" >}}) below.<br>

-**.Summary** A generated summary of the content for easily showing a snippet in a summary view. Note that the breakpoint can be set manually by inserting <code>&lt;!&#x2d;&#x2d;more&#x2d;&#x2d;&gt;</code> at the appropriate place in the content page.  See [Summaries](/content/summaries/) for more details.<br>

-**.TableOfContents** The rendered table of contents for this content.<br>

-**.Title**  The title for this page.<br>

-**.Translations** A list of translated versions of the current page. See [Multilingual]({{< relref "content/multilingual.md" >}}) for more info.<br>

-**.Truncated** A boolean, `true` if the `.Summary` is truncated.  Useful for showing a "Read more..." link only if necessary.  See [Summaries](/content/summaries/) for more details.<br>

-**.Type** The content [type](/content/types/) (e.g. post).<br>

-**.URL** The relative URL for this page. Note that if `URL` is set directly in frontmatter, that URL is returned as-is.<br>

-**.UniqueID** The MD5-checksum of the content file's path<br>

-**.Weight** Assigned weight (in the front matter) to this content, used in sorting.<br>

-**.WordCount** The number of words in the content.<br>

-## Page Params

-Any other value defined in the front matter, including taxonomies, will be made available under `.Params`.

-For example, the *tags* and *categories* taxonomies are accessed with:

-* **.Params.tags**

-* **.Params.categories**

-**All Params are only accessible using all lowercase characters.**

-This is particularly useful for the introduction of user defined fields in content files. For example, a Hugo website on book reviews could have in the front matter of <code>/content/review/book01.md</code>

-    ---

-	...

-    affiliatelink: "http://www.my-book-link.here"

-	recommendedby: "my Mother"

-    ---

-Which would then be accessible to a template at `/themes/yourtheme/layouts/review/single.html` through `.Params.affiliatelink` and `.Params.recommendedby`, respectively. Two common situations where these could be introduced are as a value of a certain attribute (like `href=""` below) or by itself to be displayed. Sample syntaxes include:

-    <h3><a href={{ printf "%s" $.Params.affiliatelink }}>Buy this book</a></h3>

-	<p>It was recommended by {{ .Params.recommendedby }}.</p>

-which would render

-    <h3><a href="http://www.my-book-link.here">Buy this book</a></h3>

-	<p>It was recommended by my Mother.</p>

-**See also:** [Archetypes]({{% ref "content/archetypes.md" %}}) for consistency of `Params` across pieces of content.

-### Param method

-In Hugo you can declare params both for the site and the individual page. A

-common use case is to have a general value for the site and a more specific

-value for some of the pages (i.e. a header image):

-```

-{{ $.Param "header_image" }}

-```

-The `.Param` method provides a way to resolve a single value whether it's

-in a page parameter or a site parameter.

-When frontmatter contains nested fields, like:

-```

----

-author:

-  given_name: John

-  family_name: Feminella

-  display_name: John Feminella

----

-```

-then `.Param` can access them by concatenating the field names together with a

-dot:

-```

-{{ $.Param "author.display_name" }}

-```

-If your frontmatter contains a top-level key that is ambiguous with a nested

-key, as in the following case,

-```

----

-favorites.flavor: vanilla

-favorites:

-  flavor: chocolate

----

-```

-then the top-level key will be preferred. In the previous example, this

-```

-{{ $.Param "favorites.flavor" }}

-```

-will print `vanilla`, not `chocolate`.

-### Taxonomy Terms Page Variables

-[Taxonomy Terms](/templates/terms/) pages are of the type `Page` and have the following additional variables. These are available in `layouts/_defaults/terms.html` for example.

-**.Data.Singular** The singular name of the taxonomy<br>

-**.Data.Plural** The plural name of the taxonomy<br>

-**.Data.Pages** the list of pages in this taxonomy<br>

-**.Data.Terms** The taxonomy itself<br>

-**.Data.Terms.Alphabetical** The Terms alphabetized<br>

-**.Data.Terms.ByCount** The Terms ordered by popularity<br>

-The last two can also be reversed: **.Data.Terms.Alphabetical.Reverse**, **.Data.Terms.ByCount.Reverse**.

-### Taxonomies elsewhere

-The **.Site.Taxonomies** variable holds all taxonomies defines site-wide.  It is a map of the taxonomy name to a list of its values. For example: "tags" -> ["tag1", "tag2", "tag3"]. Each value, though, is not a string but rather a [Taxonomy variable](#the-taxonomy-variable).

-#### The Taxonomy variable

-The Taxonomy variable, available as **.Site.Taxonomies.tags** for example, contains the list of tags (values) and, for each of those, their corresponding content pages.

-## Site Variables

-Also available is `.Site` which has the following:

-**.Site.BaseURL** The base URL for the site as defined in the site configuration file.<br>

-**.Site.RSSLink** The URL for the site RSS.<br>

-**.Site.Taxonomies** The [taxonomies](/taxonomies/usage/) for the entire site.  Replaces the now-obsolete `.Site.Indexes` since v0.11. Also see section [Taxonomies elsewhere](#taxonomies-elsewhere).<br>

-**.Site.Pages** Array of all content ordered by Date, newest first. `.Site.Pages` replaced `.Site.Recent`, which is no longer supported. This array contains only the pages in the current language.<br>

-**.Site.AllPages** Array of all pages regardless of their translation.<br>

-**.Site.Params** A container holding the values from the `params` section of your site configuration file. For example, a TOML config file might look like this:

-    baseURL = "http://yoursite.example.com/"

-    [params]

-      description = "Tesla's Awesome Hugo Site"

-      author = "Nikola Tesla"

-**.Site.Sections** Top level directories of the site.<br>

-**.Site.Files** All of the source files of the site.<br>

-**.Site.Menus** All of the menus in the site.<br>

-**.Site.Title** A string representing the title of the site.<br>

-**.Site.Author** A map of the authors as defined in the site configuration.<br>

-**.Site.LanguageCode** A string representing the language as defined in the site configuration. This is mostly used to populate the RSS feeds with the right language code.<br>

-**.Site.DisqusShortname** A string representing the shortname of the Disqus shortcode as defined in the site configuration.<br>

-**.Site.GoogleAnalytics** A string representing your tracking code for Google Analytics as defined in the site configuration.<br>

-**.Site.Copyright** A string representing the copyright of your web site as defined in the site configuration.<br>

-**.Site.LastChange** A string representing the date/time of the most recent change to your site, based on the [`date` variable]({{< ref "content/front-matter.md#required-variables" >}}) in the front matter of your content pages.<br>

-**.Site.Permalinks** A string to override the default permalink format. Defined in the site configuration.<br>

-**.Site.BuildDrafts** A boolean (Default: false) to indicate whether to build drafts. Defined in the site configuration.<br>

-**.Site.Data**  Custom data, see [Data Files](/extras/datafiles/).<br>

-**.Site.IsMultiLingual** Whether there are more than one language in this site.<br> See [Multilingual]({{< relref "content/multilingual.md" >}}) for more info.<br>

-**.Site.Language** This indicates which language you are currently rendering the website for.  This is an object with the attributes set in your language definition in your site config.<br>

-**.Site.Language.Lang** The language code of the current locale, e.g. `en`.<br>

-**.Site.Language.Weight** The weight that defines the order in the `.Site.Languages` list.<br>

-**.Site.Language.LanguageName** The full language name, e.g. `English`.<br>

-**.Site.LanguagePrefix** This can be used to prefix  theURLs with whats needed to point to the correct language. It will even work when only one language defined. See also the functions [absLangURL and relLangURL]({{< relref "templates/functions.md#abslangurl-rellangurl" >}}).<br>

-**.Site.Languages** An ordered list (ordered by defined weight) of languages.<br>

-**.Site.RegularPages** A shortcut to the *regular page* collection. Equivalent to `where .Site.Pages "Kind" "page"`.<br>

-## File Variables

-The `.File` variable gives you additional information of a page.

-> **Note:** `.File` is only accessible on *Pages* that has a content page attached to it.

-Available are the following attributes:

-**.File.Path** The original relative path of the page, e.g. `content/posts/foo.en.md`<br>

-**.File.LogicalName** The name of the content file that represents a page, e.g. `foo.en.md`<br>

-**.File.TranslationBaseName** The filename without extension or optional language identifier, e.g. `foo`<br>

-**.File.BaseFileName** The filename without extension, e.g. `foo.en`<br>

-**.File.Ext** or **.File.Extension** The file extension of the content file, e.g. `md`<br>

-**.File.Lang** The language associated with the given file if [Multilingual]({{< relref "content/multilingual.md" >}}) is enabled, e.g. `en`<br>

-**.File.Dir** Given the path `content/posts/dir1/dir2/`, the relative directory path of the content file will be returned, e.g. `posts/dir1/dir2/`<br>

-## Hugo Variables

-Also available is `.Hugo` which has the following:

-**.Hugo.Generator** Meta tag for the version of Hugo that generated the site. Highly recommended to be included by default in all theme headers so we can start to track the usage and popularity of Hugo. Unlike other variables it outputs a **complete** HTML tag, e.g. `<meta name="generator" content="Hugo 0.15" />`<br>

-**.Hugo.Version** The current version of the Hugo binary you are using e.g. `0.13-DEV`<br>

-**.Hugo.CommitHash** The git commit hash of the current Hugo binary e.g. `0e8bed9ccffba0df554728b46c5bbf6d78ae5247`<br>

-**.Hugo.BuildDate** The compile date of the current Hugo binary formatted with RFC 3339 e.g. `2002-10-02T10:00:00-05:00`<br>

--- a/content/templates/views.md

+++ b/content/templates/views.md

@@ -1,129 +1,127 @@

---

-aliases:

-- /templates/views/

-lastmod: 2015-05-22

-date: 2013-07-01

+title: Content View Templates

+# linktitle: Content Views

+description: Hugo can render alternative views of your content, which is especially useful in list and summary views.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [templates]

+#tags: [views]

 menu:

-  main:

-    parent: layout

-next: /templates/blocks

-prev: /templates/terms

-title: Content Views

+  docs:

+    parent: "templates"

+    weight: 70

 weight: 70

+sections_weight: 70

+draft: false

+aliases: []

 toc: true

---

-In addition to the [single content template](/templates/content/), Hugo can render alternative views of

-your content. These are especially useful in [list templates](/templates/list/).

+These alternative **content views** are especially useful in [list templates][lists].

-For example you may want content of every type to be shown on the

-homepage, but only a summary view of it there. Perhaps on a taxonomy

-list page you would only want a bulleted list of your content. Views

-make this very straightforward by delegating the rendering of each

-different type of content to the content itself.

+The following are common use cases for content views:

+* You want content of every type to be shown on the homepage but only with limited [summary views][summaries].

+* You only want a bulleted list of your content on a [taxonomy list page][taxonomylists]. Views make this very straightforward by delegating the rendering of each different type of content to the content itself.

-## Creating a content view

+## Create a Content View

-To create a new view, simply create a template in each of your different

-content type directories with the view name. In the following example, we

-have created a "li" view and a "summary" view for our two content types

-of post and project. As you can see, these sit next to the [single

-content view](/templates/content/) template "single.html". You can even

-provide a specific view for a given type and continue to use the

-\_default/single.html for the primary view.

+To create a new view, create a template in each of your different content type directories with the view name. The following example contains an "li" view and a "summary" view for the `post` and `project` content types. As you can see, these sit next to the [single content view][single] template, `single.html. You can even provide a specific view for a given type and continue to use the `_default/single.html` for the primary view.

-    ▾ layouts/

-      ▾ post/

-          li.html

-          single.html

-          summary.html

-      ▾ project/

-          li.html

-          single.html

-          summary.html

+```bash

+  ▾ layouts/

+    ▾ post/

+        li.html

+        single.html

+        summary.html

+    ▾ project/

+        li.html

+        single.html

+        summary.html

+```

-Hugo also has support for a default content template to be used in the event

-that a specific template has not been provided for that type. The default type

-works the same as the other types, but the directory must be called "_default".

-Content views can also be defined in the "_default" directory.

+Hugo also has support for a default content template to be used in the event that a specific content view template has not been provided for that type. Content views can also be defined in the `_default` directory and will work the same as list and single templates who eventually trickle down to the `_default` directory as a matter of the lookup order.

-    ▾ layouts/

-      ▾ _default/

-          li.html

-          single.html

-          summary.html

+```bash

+▾ layouts/

+  ▾ _default/

+      li.html

+      single.html

+      summary.html

+```

+## Which Template Will be Rendered?

-## Which Template will be rendered?

-Hugo uses a set of rules to figure out which template to use when

-rendering a specific page.

+The following is the [lookup order][lookup] for content views:

-Hugo will use the following prioritized list. If a file isn’t present,

-then the next one in the list will be used. This enables you to craft

-specific layouts when you want to without creating more templates

-than necessary. For most sites only the \_default file at the end of

-the list will be needed.

+1. `/layouts/<TYPE>/<VIEW>.html`

+2. `/layouts/_default/<VIEW>.html`

+3. `/themes/<THEME>/layouts/<TYPE>/<VIEW>.html`

+4. `/themes/<THEME>/layouts/_default/<VIEW>.html`

-* /layouts/`TYPE`/`VIEW`.html

-* /layouts/\_default/`VIEW`.html

-* /themes/`THEME`/layouts/`TYPE`/`VIEW`.html

-* /themes/`THEME`/layouts/\_default/`view`.html

+## Example: Content View Inside a List

+The following example demonstrates how to use content views inside of your [list templates][lists].

-## Example using views

+### `list.html`

-### rendering view inside of a list

+In this example, `.Render` is passed into the template to call the [render function][render]. `.Render` is a special function that instructs content to render itself with the view template provided as the first argument. In this case, the template is going to render the `summary.html` view that follows:

-Using the summary view (defined below) inside of a ([list

-templates](/templates/list/)).

-    <section id="main">

-    <div>

-    <h1 id="title">{{ .Title }}</h1>

-    {{ range .Data.Pages }}

+{{% code file="layouts/_default/list.html" download="list.html" %}}

+```

+<main id="main">

+  <div>

+  <h1 id="title">{{ .Title }}</h1>

+  {{ range .Data.Pages }}

     {{ .Render "summary"}}

-    {{ end }}

-    </div>

-    </section>

+  {{ end }}

+  </div>

+</main>

+```

+{{% /code %}}

-In the above example, you will notice that we have called `.Render` and passed in

-which view to render the content with. `.Render` is a special function available on

-a content which tells the content to render itself with the provided view template.

-In this example, we are not using the li view. To use this we would

-change the render line to `{{ .Render "li" }}`.

+### `summary.html`

+Hugo will pass the entire page object to the following `summary.html` view template. (See [Page Variables][pagevars] for a complete list.)

-### li.html

-Hugo will pass the entire page object to the view template. See [page

-variables](/templates/variables/) for a complete list.

-This content template is used for [spf13.com](http://spf13.com/).

-    <li>

-    <a href="{{ .Permalink }}">{{ .Title }}</a>

-    <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

-    </li>

-### summary.html

-Hugo will pass the entire page object to the view template. See [page

-variables](/templates/variables/) for a complete list.

-This content template is used for [spf13.com](http://spf13.com/).

-    <article class="post">

-    <header>

+{{% code file="layouts/_default/summary.html" download="summary.html" %}}

+```html

+<article class="post">

+  <header>

     <h2><a href='{{ .Permalink }}'> {{ .Title }}</a> </h2>

     <div class="post-meta">{{ .Date.Format "Mon, Jan 2, 2006" }} - {{ .FuzzyWordCount }} Words </div>

-    </header>

+  </header>

+  {{ .Summary }}

+  <footer>

+  <a href='{{ .Permalink }}'><nobr>Read more →</nobr></a>

+  </footer>

+</article>

+```

+{{% /code %}}

-    {{ .Summary }}

-    <footer>

-    <a href='{{ .Permalink }}'><nobr>Read more →</nobr></a>

-    </footer>

-    </article>

+### `li.html`

+Continuing on the previous example, we can change our render function to use a smaller `li.html` view by changing the argument in the call to the `.Render` function (i.e., `{{ .Render "li" }}`).

+{{% code file="layouts/_default/li.html" download="li.html" %}}

+```html

+<li>

+  <a href="{{ .Permalink }}">{{ .Title }}</a>

+  <div class="meta">{{ .Date.Format "Mon, Jan 2, 2006" }}</div>

+</li>

+```

+{{% /code %}}

+[lists]: /templates/lists/

+[lookup]: /templates/lookup-order/

+[pagevars]: /variables/page/

+[render]: /functions/render/

+[single]: /templates/single-page-templates/

+[spf]: http://spf13.com

+[spfsourceli]: https://github.com/spf13/spf13.com/blob/master/layouts/_default/li.html

+[spfsourcesection]: https://github.com/spf13/spf13.com/blob/master/layouts/_default/section.html

+[spfsourcesummary]: https://github.com/spf13/spf13.com/blob/master/layouts/_default/summary.html

+[summaries]: /content-management/summaries/

+[taxonomylists]: /templates/taxonomy-templates/

\ No newline at end of file

--- /dev/null

+++ b/content/themes/_index.md

@@ -1,0 +1,26 @@

+---

+title: Themes

+linktitle: Themes Overview

+description: Install, use, and create Hugo themes.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+menu:

+  docs:

+    parent: "themes"

+    weight: 01

+weight: 01

+sections_weight: 01

+categories: [themes]

+#tags: [themes,introduction,overview]

+draft: false

+aliases: [/themes/overview/]

+toc: false

+---

+Hugo provides a robust theming system that is easy to implement yet feature complete. You can view the themes created by the Hugo community on the [Hugo themes website][hugothemes].

+Hugo themes are powered by the excellent Go template library and are designed to reduce code duplication. They are easy to both customize and keep in synch with the upstream theme.

+[goprimer]: /templates/introduction/

+[hugothemes]: http://themes.gohugo.io/

--- /dev/null

+++ b/content/themes/creating.md

@@ -1,0 +1,87 @@

+---

+title: Creating a Theme

+linktitle: Creating a Theme

+description: The `hugo new theme` command will scaffold the beginnings of a new theme for you to get you on your way.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [themes]

+#tags: [themes, source, organization, directories]

+menu:

+  docs:

+    parent: "themes"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+aliases: [/themes/creation/,/tutorials/creating-a-new-theme/]

+toc: true

+wip: true

+---

+{{% warning "Use Relative Links" %}}

+If you're creating a theme with plans to share it with the community, use relative URLs since users of your theme may not publish from the root of their website. See [relURL](/functions/relurl) and [absURL](/functions/absurl).

+{{% /warning %}}

+Hugo can initialize a new blank theme directory within your existing `themes` using the `hugo new` command:

+```bash

+hugo new theme [name]

+```

+## Theme Components

+A theme consists of templates and static assets such as javascript and css files. Themes can also provide [archetypes][], which are archetypal content types used by the `hugo new` command to scaffold new conte files with preconfigured front matter.

+{{% note "Use the Hugo Generator Tag" %}}

+The [`.Hugo.Generator`](/variables/hugo/) tag is included in all themes featured in the [Hugo Themes Showcase](http://themes.gohugo.io). We ask that you include the generator tag in all sites and themes you create with Hugo to help the core team track Hugo's usage and popularity.

+{{% /note %}}

+## Layouts

+Hugo is built around the concept that things should be as simple as possible.

+Fundamentally, website content is displayed in two different ways, a single

+piece of content and a list of content items. With Hugo, a theme layout starts

+with the defaults. As additional layouts are defined, they are used for the

+content type or section they apply to. This keeps layouts simple, but permits

+a large amount of flexibility.

+## Single Content

+The default single file layout is located at `layouts/_default/single.html`.

+## List of Contents

+The default list file layout is located at `layouts/_default/list.html`.

+## Partial Templates

+Theme creators should liberally use [partial templates](/templates/partials/)

+throughout their theme files. Not only is a good DRY practice to include shared

+code, but partials are a special template type that enables the themes end user

+to be able to overwrite just a small piece of a file or inject code into the

+theme from their local /layouts. These partial templates are perfect for easy

+injection into the theme with minimal maintenance to ensure future

+compatibility.

+## Static

+Everything in the static directory will be copied directly into the final site

+when rendered. No structure is provided here to enable complete freedom. It is

+common to organize the static content into:

+```

+/css

+/js

+/img

+```

+The actual structure is entirely up to you, the theme creator, on how you would like to organize your files.

+## Archetypes

+If your theme makes use of specific keys in the front matter, it is a good idea

+to provide an archetype for each content type you have. [Read more about archetypes][archetypes].

+[archetypes]: /content-management/archetypes/

--- a/content/themes/creation.md

+++ /dev/null

@@ -1,78 +1,0 @@

----

-lastmod: 2015-08-04

-date: 2014-05-12T10:09:17Z

-menu:

-  main:

-    parent: themes

-next: /templates/overview

-prev: /themes/customizing

-title: Creating a Theme

-weight: 50

----

-Hugo has the ability to create a new theme in your themes directory for you

-using the `hugo new` command.

-`hugo new theme [name]`

-This command will initialize all of the files and directories a basic theme

-would need. Hugo themes are written in the Go template language. If you are new

-to Go, the [Go template primer](/layout/go-templates/) will help you get started.

-## Theme Components

-A theme consists of templates and static assets such as javascript and css

-files. Themes can also optionally provide [archetypes](/content/archetypes/)

-which are archetypal content types used by the `hugo new` command.

-### Layouts

-Hugo is built around the concept that things should be as simple as possible.

-Fundamentally website content is displayed in two different ways, a single

-piece of content and a list of content items. With Hugo a theme layout starts

-with the defaults. As additional layouts are defined they are used for the

-content type or section they apply to. This keeps layouts simple, but permits

-a large amount of flexibility.

-### Single Content

-The default single file layout is located at `layouts/_default/single.html`.

-### List of Contents

-The default list file layout is located at `layouts/_default/list.html`.

-### Partial Templates

-Theme creators should liberally use [partial templates](/templates/partials/)

-throughout their theme files. Not only is a good DRY practice to include shared

-code, but partials are a special template type that enables the themes end user

-to be able to overwrite just a small piece of a file or inject code into the

-theme from their local /layouts. These partial templates are perfect for easy

-injection into the theme with minimal maintenance to ensure future

-compatibility.

-### Static

-Everything in the static directory will be copied directly into the final site

-when rendered. No structure is provided here to enable complete freedom. It is

-common to organize the static content into:

-    /css

-    /js

-    /img

-The actual structure is entirely up to you, the theme creator, on how you would like to organize your files.

-### Archetypes

-If your theme makes use of specific keys in the front matter, it is a good idea

-to provide an archetype for each content type you have. Archetypes follow the

-[guidelines provided](/content/archetypes/).

-### Generator meta tag

-With a growing community around Hugo we recommend theme creators to include the [Generator meta tag]({{< relref "templates/variables.md#hugo-variables" >}}) with `.Hugo.Generator` in the `<head>` of your HTML code. The output  might looks like `<meta name="generator" content="Hugo 0.13" />` and helps us to analyse the usage and popularity of Hugo.

--- a/content/themes/customizing.md

+++ b/content/themes/customizing.md

@@ -1,56 +1,80 @@

---

-lastmod: 2015-08-04

-date: 2014-05-12T10:09:34Z

-menu:

-  main:

-    parent: themes

-next: /themes/creation

-prev: /themes/usage

 title: Customizing a Theme

-weight: 40

+linktitle: Customizing a Theme

+description: Customize a theme by overriding theme layouts and static assets in your top-level project directories.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [themes]

+#tags: [themes, source, organization, directories]

+menu:

+  docs:

+    parent: "themes"

+    weight: 20

+weight: 20

+sections_weight: 20

+draft: false

+aliases: [/themes/customize/]

 toc: true

+wip: true

---

-_The following are key concepts for Hugo site customization. Hugo permits you to **supplement or override** any theme template or static file, with files in your working directory._

+The following are key concepts for Hugo site customization with themes. Hugo permits you to supplement *or* override any theme template or static file with files in your working directory.

-_When you use a theme cloned from its git repository, you do not edit the theme's files directly. Rather, you override them as per the following:_

+{{% note %}}

+When you use a theme cloned from its git repository, do not edit the theme's files directly. Instead, theme customization in Hugo is a matter of *overriding* the templates made available to you in a theme. This provides the added flexibility of tweaking a theme to meet your needs while staying current with a theme's upstream.

+{{% /note %}}

-## Replace Static Files

+## Override Static Files

-For including a different file than what the theme ships with. For example, if you would like to use a more recent version of jQuery than what the theme happens to include, simply place an identically-named file in the same relative location but in your working directory.

+There are times where you want to include static assets that differ from versions of the same asset that ships with a theme.

-For example, if the theme has jQuery 1.6 in:

+For example, a theme may use jQuery 1.8 in the following location:

-    /themes/themename/static/js/jquery.min.js

+```bash

+/themes/<THEME>/static/js/jquery.min.js

+```

-... you would simply place your file in the same relative path, but in the root of your working folder:

+You want to replace the version of jQuery that ships with the theme with the newer `jquery-3.1.1.js`. The easiest way to do this is to replace the file *with a file of the same name* in the same relative path in your project's root. Therefore, change `jquery-3.1.1.js` to `jquery.min.js` so that it is *identical* to the theme's version and place the file here:

-    /static/js/jquery.min.js

+```bash

+/static/js/jquery.min.js

+```

-## Replace a single template file

+## Override Template Files

 Anytime Hugo looks for a matching template, it will first check the working directory before looking in the theme directory. If you would like to modify a template, simply create that template in your local `layouts` directory.

-In the [template documentation](/templates/overview/) _each different template type explains the rules it uses to determine which template to use_. Read and understand these rules carefully.

+The [template lookup order][lookup] explains the rules Hugo uses to determine which template to use for a given piece of content. Read and understand these rules carefully.

-This is especially helpful when the theme creator used [partial templates](/templates/partials/). These partial templates are perfect for easy injection into the theme with minimal maintenance to ensure future compatibility.

+This is especially helpful when the theme creator used [partial templates][partials]. These partial templates are perfect for easy injection into the theme with minimal maintenance to ensure future compatibility.

 For example:

-    /themes/themename/layouts/_default/single.html

+```bash

+/themes/<THEME>/layouts/_default/single.html

+```

-... would be overridden by:

+Would be overwritten by

-    /layouts/_default/single.html

+```bash

+/layouts/_default/single.html

+```

-**Warning**: This only works for templates that Hugo "knows about" (that follow its convention for folder structure and naming). If the theme imports template files in a creatively-named directory, Hugo won’t know to look for the local `/layouts` first.

+{{% warning %}}

+This only works for templates that Hugo "knows about" (i.e., that follow its convention for folder structure and naming). If a theme imports template files in a creatively named directory, Hugo won’t know to look for the local `/layouts` first.

+{{% /warning %}}

-## Replace an archetype

+## Override Archetypes

 If the archetype that ships with the theme for a given content type (or all content types) doesn’t fit with how you are using the theme, feel free to copy it to your `/archetypes` directory and make modifications as you see fit.

-## Beware of the default

+{{% warning "Beware of `layouts/_default`" %}}

+The `_default` directory is a very powerful force in Hugo, especially as it pertains to overwriting theme files. If a default file is located in the local [archetypes](/content-management/archetypes/) or layout directory (i.e., `archetypes/default.md` or `/layouts/_default/*.html`, respectively), it will override the file of the same name in the corresponding theme directory (i.e., `themes/<THEME>/archetypes/default.md` or `themes/<THEME>/layout/_defaults/*.html`, respectively).

-**Default** is a very powerful force in Hugo, especially as it pertains to overwriting theme files. If a default is located in the local archetype directory or `/layouts/_default/` directory, it will be used instead of any of the similar files in the theme.

+It is usually better to override specific files; i.e. rather than using `layouts/_default/*.html` in your working directory.

+{{% /warning %}}

-It is usually better to override specific files rather than using the default in your working directory.

+[archetypes]: /content-management/archetypes/

+[lookup]: /templates/lookup-order/

+[partials]: /templates/partials/

\ No newline at end of file

--- /dev/null

+++ b/content/themes/installing-and-using-themes.md

@@ -1,0 +1,114 @@

+---

+title: Installing and Using Themes

+linktitle: Installing and Using Themes

+description: Install and use a theme from the Hugo theme showcase easily through the CLI.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [themes]

+#tags: [install, themes, source, organization, directories,usage]

+menu:

+  docs:

+    parent: "themes"

+    weight: 10

+weight: 10

+sections_weight: 10

+draft: false

+aliases: [/themes/usage/,/themes/installing/]

+toc: true

+wip: true

+---

+{{% note "No Default Theme" %}}

+Hugo currently doesn’t ship with a “default” theme. This decision is intentional. We leave it up to you to decide which theme best suits your Hugo project.

+{{% /note %}}

+## Assumptions

+1. You have already [installed Hugo on your development machine][install].

+2. You have git installed on your machine and you are familiar with basic git usage.

+## Install Themes

+The community-contributed themes featured on [themes.gohugo.io](//themes.gohugo.io/) are hosted in a [centralized GitHub repository][themesrepo]. The Hugo Themes Repo at <https://github.com/gohugoio/hugoThemes> is really a meta repository that contains pointers to a set of contributed themes.

+{{% warning "Get `git` First" %}}

+Without [Git](https://git-scm.com/) installed on your computer, none of the following theme instructions will work. Git tutorials are beyond the scope of the Hugo docs, but [GitHub](https://try.github.io/) and [codecademy](https://www.codecademy.com/learn/learn-git) offer free, interactive courses for beginners.

+{{% /warning %}}

+### Install All Themes

+You can install *all* available Hugo themes by cloning the entire [Hugo Theme repository on GitHub][themesrepo] from within your working directory. Depending on your internet connection the download of all themes might take a while.

+```bash

+git clone --depth 1 --recursive https://github.com/gohugoio/hugoThemes.git themes

+```

+Before you use a theme, remove the .git folder in that theme's root folder. Otherwise, this will cause problem if you deploy using Git.

+### Install a Single Theme

+Change into the `themes` directory and download a theme by replacing `URL_TO_THEME` with the URL of the theme repository:

+```bash

+cd themes

+git clone URL_TO_THEME

+```

+The following example shows how to use the "Hyde" theme, which has its source hosted at <https://github.com/spf13/hyde>:

+{{% code file="clone-theme.sh" %}}

+```bash

+cd themes

+git clone https://github.com/spf13/hyde

+```

+{{% /code %}}

+Alternatively, you can download the theme as a `.zip` file, unzip the theme contents, and then move the unzipped source into your `themes` directory.

+{{% note "Read the `README`" %}}

+Always review the `README.md` file that is shipped with a theme. Often, these files contain further instructions required for theme setup; e.g., copying values from an example configuration file.

+{{% /note %}}

+## Theme Placement

+Please make certain you have installed the themes you want to use in the

+`/themes` directory. This is the default directory used by Hugo. Hugo comes with the ability to change the themes directory via the [`themesDir` variable in your site configuration][config], but this is not recommended.

+## Use Themes

+Hugo applies the decided theme first and then applies anything that is in the local directory. This allows for easier customization while retaining compatibility with the upstream version of the theme. To learn more, go to [customizing themes][customizethemes].

+### Command Line

+There are two different approaches to using a theme with your Hugo website: via the Hugo CLI or as part of your

+To change a theme via the Hugo CLI, you can pass the `-t` [flag][] when building your site:

+```bash

+hugo -t themename

+```

+Likely, you will want to add the theme when running the Hugo local server, especially if you are going to [customize the theme][customizethemes]:

+```bash

+hugo server -t themename

+```

+### `config` File

+If you've already decided on the theme for your site and do not want to fiddle with the command line, you can add the theme directly to your [site configuration file][config]:

+```yaml

+theme: themename

+```

+{{% note "A Note on `themename`" %}}

+The `themename` in the above examples must match the name of the specific theme directory inside `/themes`; i.e., the directory name (likely lowercase and urlized) rather than the name of the theme displayed in the [Themes Showcase site](http://themes.gohugo.io).

+{{% /note %}}

+[customizethemes]: /themes/customizing/

+[flag]: /getting-started/usage/ "See the full list of flags in Hugo's basic usage."

+[install]: /getting-started/installing/

+[config]: /getting-started/configuration/  "Learn how to customize your Hugo website configuration file in yaml, toml, or json."

+[themesrepo]: https://github.com/gohugoio/hugoThemes

\ No newline at end of file

--- a/content/themes/installing.md

+++ /dev/null

@@ -1,46 +1,0 @@

----

-lastmod: 2015-10-10

-date: 2014-05-12T10:09:49Z

-menu:

-  main:

-    parent: themes

-next: /themes/usage

-prev: /themes/overview

-title: Installing Themes

-weight: 20

----

-Community-contributed [Hugo themes](http://themes.gohugo.io/), showcased

-at [themes.gohugo.io](//themes.gohugo.io/), are hosted in a centralized

-GitHub repository.  The [Hugo Themes Repo](https://github.com/gohugoio/hugoThemes)

-itself at [github.com/gohugoio/hugoThemes](https://github.com/gohugoio/hugoThemes) is

-really a meta repository which contains pointers to set of contributed themes.

-## Installing all themes

-If you would like to install all of the available Hugo themes, simply

-clone the entire repository from within your working directory. Depending

-on your internet connection the download of all themes might take a while.

-> **NOTE:** Make sure you've installed [Git](https://git-scm.com/) on your computer.

-Otherwise you will not be able to clone the theme repositories.

-```bash

-$ git clone --depth 1 --recursive https://github.com/gohugoio/hugoThemes.git themes

-```

-Before you use a theme, remove the .git folder in that theme's root folder. Otherwise, this will cause problem if you deploy using Git.

-## Installing a specific theme

-Switch into the `themes` directory and download a theme by replacing `URL_TO_THEME`

-with the URL of the theme repository, e.g. `https://github.com/spf13/hyde`:

-    $ cd themes

-    $ git clone URL_TO_THEME

-Alternatively, you can download the theme as `.zip` file and extract it in the

-`themes` directory.

-**NOTE:** Please have a look at the `README.md` file that is shipped with all themes.

-It might contain further instructions that are required to setup the theme, e.g. copying

-an example configuration file.

--- a/content/themes/overview.md

+++ /dev/null

@@ -1,32 +1,0 @@

----

-lastmod: 2015-10-10

-date: 2014-05-12T10:03:52Z

-menu:

-  main:

-    parent: themes

-next: /themes/installing

-prev: /content/example

-title: Themes Overview

-weight: 10

----

-Hugo provides a robust theming system which is simple, yet capable of producing

-even the most complicated websites.

-The Hugo community has created [a wide variety of beautiful themes](//themes.gohugo.io/), as demoed at [themes.gohugo.io](//themes.gohugo.io/),

-ready for using in your own site.

-Hugo themes have been designed to be the perfect balance between

-simplicity and functionality. Hugo themes are powered by the excellent

-Go template library. If you are new to Go templates, see our [primer on

-Go templates](/templates/go-templates/).

-Hugo themes support all modern features you come to expect. They are

-structured in such a way to eliminate code duplication. Themes are also

-designed to be very easy to customize while retaining the ability to

-maintain upgradeability as the upstream theme changes.

-Hugo currently doesn’t ship with a “default” theme, allowing the user to

-pick whichever theme best suits their project.

-We hope you will find Hugo themes perfect for your site.

--- a/content/themes/usage.md

+++ /dev/null

@@ -1,27 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2014-05-12T10:09:27Z

-menu:

-  main:

-    parent: themes

-next: /themes/customizing

-prev: /themes/installing

-title: Using a Theme

-weight: 30

----

-Please make certain you have installed the themes you want to use in the

-`/themes` directory.

-To use a theme for a site, execute Hugo with the following parameter:

-    hugo -t ThemeName

-or add this line to your site configuration:

-    theme:                      "ThemeName"

-The *ThemeName* must match the name of the directory inside `/themes`.

-Hugo will then apply the theme first, then apply anything that is in the local

-directory. To learn more, go to [customizing themes](/themes/customizing/).

--- a/content/tools/_index.md

+++ b/content/tools/_index.md

@@ -1,144 +1,25 @@

---

-date: 2015-09-12T10:40:31+02:00

-title: Tools

-weight: 120

+title: Developer Tools

+linktitle: Developer Tools Overview

+description: In addition to Hugo's powerful CLI, there is a large number of community-developed tool chains for Hugo developers.

+date: 2016-12-05

+publishdate: 2016-12-05

+lastmod: 2017-02-26

+categories: [developer tools]

+#tags: []

+menu:

+  docs:

+    parent: "tools"

+    weight: 01

+weight: 01

+sections_weight: 01

+draft: false

+aliases: [/tools/]

---

-This section highlights some projects around Hugo that are independently developed. These tools try to extend the functionality of our static site generator or help you to get started.

+One of Hugo's greatest strengths is it's passionate---and always evolving---developer community. With the exception of the `highlight` shortcode mentioned in [Syntax Highlighting][syntax], the tools and other projects featured in this section are offerings from both commercial services and open-source projects, many of which are developed by Hugo developers just like you.

-> **Note:** Do you know or maintain a similar project around Hugo? Feel free to open a [pull request](https://github.com/gohugoio/hugo/pulls) on GitHub if you think it should be added.

+[See the popularity of Hugo compared with other static site generators.][staticgen]

-## Migration

-Take a look at this list of migration tools if you currently use other blogging tools like Jekyll or WordPress but intend to switch to Hugo instead. They'll take care to export

-your content into Hugo-friendly formats.

-### Jekyll

-Alternatively, you can follow the manual [migration guide]({{< relref "tutorials/migrate-from-jekyll.md" >}}) or use the new [Jekyll import command]({{< relref "commands/hugo_import_jekyll.md" >}}).

-- [JekyllToHugo](https://github.com/SenjinDarashiva/JekyllToHugo) - A Small script for converting Jekyll blog posts to a Hugo site.

-- [ConvertToHugo](https://github.com/coderzh/ConvertToHugo) - Convert your blog from Jekyll to Hugo.

-### Ghost

-- [ghostToHugo](https://github.com/jbarone/ghostToHugo) - Convert Ghost blog posts and export them to Hugo.

-### Octopress

-- [octohug](https://github.com/codebrane/octohug) - Octopress to Hugo migrator.

-### DokuWiki

-- [dokuwiki-to-hugo](https://github.com/wgroeneveld/dokuwiki-to-hugo) - Migrates your dokuwiki source pages from [DokuWiki syntax](https://www.dokuwiki.org/wiki:syntax) to Hugo Markdown syntax. Includes extra's like the TODO plugin. Written with extensibility in mind using python 3. Also generates a TOML header for each page. Designed to copypaste the wiki directory into your /content directory.

-### WordPress

-- [wordpress-to-hugo-exporter](https://github.com/SchumacherFM/wordpress-to-hugo-exporter) - A one-click WordPress plugin that converts all posts, pages, taxonomies, metadata, and settings to Markdown and YAML which can be dropped into Hugo. (Note: If you have trouble using this plugin, you can [export your site for Jekyll](https://wordpress.org/plugins/jekyll-exporter/) and use Hugo's built in Jekyll converter listed above.)

-### Tumblr

-- [tumblr-importr](https://github.com/carlmjohnson/tumblr-importr) - An importer that uses the Tumblr API to create a Hugo static site.

-- [tumblr2hugomarkdown](https://github.com/Wysie/tumblr2hugomarkdown) - Export all your Tumblr content to Hugo Markdown files with preserved original formatting.

-- [Tumblr to Hugo](https://github.com/jipiboily/tumblr-to-hugo) - A migration tool that converts each of your Tumblr posts to a content file with a proper title and path. Furthermore, "Tumblr to Hugo" creates a CSV file with the original URL and the new path on Hugo, to help you setup the redirections.

-### Drupal

-- [drupal2hugo](https://github.com/danapsimer/drupal2hugo) - Convert a Drupal site to Hugo.

-### Joomla

-- [hugojoomla](https://github.com/davetcc/hugojoomla) - This utility written in Java takes a Joomla database and converts all the content into Markdown files. It changes any URLs that are in Joomla's internal format and converts them to a suitable form.

-### Blogger

-- [blogimport](https://github.com/natefinch/blogimport) - A tool to import from Blogger posts to Hugo.

-### Contentful

-- [contentful2hugo](https://github.com/ArnoNuyts/contentful2hugo) - A tool to create content-files for Hugo from content on [Contentful](https://www.contentful.com/).

-----

-## Deployment

-If you don't want to use [Wercker for automated deployments]({{< relref "tutorials/automated-deployments.md" >}}), give these tools a try to get your content to the public:

-- [hugomac](https://github.com/nickoneill/hugomac) - Hugomac is an OS&nbsp;X menubar app to publish your blog directly to Amazon S3. No command line is needed.

-- [hugo-lambda](https://github.com/ryansb/hugo-lambda) - A wrapper around the Hugo static site generator to have it run in AWS Lambda whenever new (Markdown or other) content is uploaded.

-- [hugodeploy](https://github.com/mindok/hugodeploy) - Simple SFTP deployment tool for static websites (e.g. created by Hugo) with optional minification.

-- [webhook](https://github.com/adnanh/webhook) - Run build and deployment scripts (e.g. hugo) on incoming webhooks

-- [Hugo SFTP Upload](https://github.com/thomasmey/HugoSftpUpload) - Sync the local build of your Hugo website with your remote webserver via SFTP.

-----

-## Frontends

-Do you prefer an graphical user interface over a text editor? Then give these frontends a try:

-- [enwrite](https://github.com/zzamboni/enwrite) - Evernote-powered statically-generated blogs and websites. Now posting to your blog or updating your website is as easy as writing a new note in Evernote!

-- [caddy-hugo](https://github.com/hacdias/caddy-hugo) - This is an add-on for [Caddy](https://caddyserver.com/) which wants to deliver a good UI to edit the content of the website.

-- [Lipi](https://github.com/SohanChy/Lipi) - A native GUI frontend written in Java to manage your Hugo websites.

-----

-## Editor plugins

-If you still want to use an editor, look at these plugins to automate your workflow:

-### Sublime Text

-- [Hugofy](https://github.com/akmittal/Hugofy) - Hugofy is a plugin for Sublime Text 3 to make life easier to use Hugo static site generator.

-### Visual Studio Code

-- [Hugofy](https://marketplace.visualstudio.com/items?itemName=akmittal.hugofy) - Hugofy is a plugin for Visual Studio Code to make life easier to use Hugo static site generator. The source code can be found [here](https://github.com/akmittal/hugofy-vscode).

-### Emacs

-- [easy-hugo](https://github.com/masasam/emacs-easy-hugo) - Major mode & tools for Hugo.

-- [hugo.el](https://github.com/yewton/hugo.el) - Some helper functions for creating a Website with Hugo.

-### Vim

-- [Vim Hugo Helper](https://github.com/robertbasic/vim-hugo-helper) - A small Vim plugin to help me with writing posts with Hugo.

-### Atom

-- [Hugofy](https://atom.io/packages/hugofy) - A Hugo Static Website Generator package for Atom

-----

-## Search

-A static site with a dynamic search function? Yes. Alternatively to embeddable scripts from Google or other search engines you can provide your visitors a custom search by indexing your content files directly.

-- [Hugoidx](https://github.com/blevesearch/hugoidx) is an experimental application to create a search index. It's build on top of [Bleve](http://www.blevesearch.com/).

-- This [GitHub Gist](https://gist.github.com/sebz/efddfc8fdcb6b480f567) contains simple workflow to create a search index for your static site. It uses a simple Grunt script to index all your content files and [lunr.js](http://lunrjs.com/) to serve the search results.

-- [hugo-lunr](https://www.npmjs.com/package/hugo-lunr) - A simple way to add site search to your static Hugo site using [lunr.js](http://lunrjs.com/). Hugo-lunr will create an index file of any html and markdown documents in your Hugo project.

-----

-## Commercial Services

-- [Algolia](https://www.algolia.com/)'s Search API makes it easy to deliver a great search experience in your apps &amp; websites. Algolia Search provides hosted full-text, numerical, faceted and geolocalized search.

-- [Appernetic.io](https://appernetic.io) is a Hugo Static Site Generator as a Service that is easy to use for non-technical users.

-Features: inline PageDown editor, visual tree view, image upload and digital asset management with Cloudinary, site preview, continuous integration with GitHub, atomic deploy and hosting, Git and Hugo integration, autosave, custom domain, project syncing, theme cloning and management. Developers have complete control over the source code and can manage it with GitHub's deceptively simple workflow.

-- [Netlify.com](https://www.netlify.com), builds, deploy & hosts your static site or app (Hugo, Jekyll etc). Build, deploy and host your static site or app with a drag and drop interface and automatic deploys from GitHub or Bitbucket.

-Features: global CDN, atomic deploys, ultra fast DNS, instant cache invalidation, high availability, automated hosting, Git integration, form submission hooks, authentication providers, custom domain. Developers have complete control over the source code and can manage it with GitHub's or Bitbuckets deceptively simple workflow.

-- [Forestry.io](https://forestry.io/) - A simple CMS for Jekyll and Hugo sites with support for GitHub, GitLab and Bitbucket. Every time an update is made via the CMS, Forestry will commit changes back to your repo and will compile/deploy your site (S3, GitHub Pages, FTP, etc).

-----

-## Other

-And for all the other small things around Hugo:

-- [hugo-gallery](https://github.com/icecreammatt/hugo-gallery) lets you create an image gallery for Hugo sites.

-- [flickr-hugo-embed](https://github.com/nikhilm/flickr-hugo-embed) prints shortcodes to embed a set of images from an album on Flickr into Hugo.

-- [hugo-openapispec-shortcode](https://github.com/tenfourty/hugo-openapispec-shortcode) A shortcode which allows you to include [Open API Spec](https://openapis.org) (formerly known as Swagger Spec) in a page.

-- [HugoPhotoSwipe](https://github.com/GjjvdBurg/HugoPhotoSwipe) makes it easy to create image galleries using PhotoSwipe.

+[staticgen]: https://staticgen.com

+[syntax]: /tools/syntax-highlighting/

--- /dev/null

+++ b/content/tools/editors.md

@@ -1,0 +1,44 @@

+---

+title: Editor Plug-ins for Hugo

+linktitle: Editor Plug-ins

+description: The Hugo community uses a wide range of preferred tools and has developed plug-ins for some of the most popular text editors to help automate parts of your workflow.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [developer tools]

+#tags: [editor, plug-ins]

+menu:

+  docs:

+    parent: "tools"

+    weight: 50

+weight: 50

+sections_weight: 50

+draft: false

+aliases: []

+toc: false

+---

+The Hugo community uses a wide range of preferred tools and has developed plug-ins for some of the most popular text editors to help automate parts of your workflow.

+## Sublime Text

+* [Hugofy](https://github.com/akmittal/Hugofy). Hugofy is a plugin for Sublime Text 3 to make life easier to use Hugo static site generator.

+## Visual Studio Code

+* [Hugofy](https://marketplace.visualstudio.com/items?itemName=akmittal.hugofy). Hugofy is a plugin for Visual Studio Code to "make life easier" when developing with Hugo. The source code can be found [here](https://github.com/akmittal/hugofy-vscode).

+## Emacs

+* [hugo.el](https://github.com/yewton/hugo.el). Some helper functions for creating a Website with Hugo. Note that Hugo also supports [Org-mode][formats].

+## Vim

+* [Vim Hugo Helper](https://github.com/robertbasic/vim-hugo-helper). A small Vim plugin to help me with writing posts with Hugo.

+## Atom

+* [Hugofy](https://atom.io/packages/hugofy). A Hugo Static Website Generator package for Atom.

+* [language-hugo](https://atom.io/packages/language-hugo). Adds syntax highlighting to Hugo files.

+[formats]: /content-management/formats/

\ No newline at end of file

--- /dev/null

+++ b/content/tools/frontends.md

@@ -1,0 +1,33 @@

+---

+title: Frontend Interfaces with Hugo

+linktitle: Frontends

+description: Do you prefer a graphical user interface over a text editor? Give these frontends a try.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [developer tools]

+#tags: [frontend,gui]

+menu:

+  docs:

+    parent: "tools"

+    weight: 40

+weight: 40

+sections_weight: 40

+draft: false

+aliases: []

+toc: false

+---

+* [enwrite](https://github.com/zzamboni/enwrite). Enwrite enables evernote-powered, statically generated blogs and websites. Now posting to your blog or updating your website is as easy as writing a new note in Evernote!

+* [caddy-hugo](https://github.com/hacdias/caddy-hugo). `caddy-hugo` is an add-on for [Caddy](https://caddyserver.com/) that delivers a good UI to edit the content of your Hugo website.

+* [Lipi](https://github.com/SohanChy/Lipi). Lipi is a native GUI frontend written in Java to manage your Hugo websites.

+## Commercial Services

+* [Appernetic.io](https://appernetic.io) is a Hugo Static Site Generator as a Service that is easy to use for non-technical users.

+    * **Features:** inline PageDown editor, visual tree view, image upload and digital asset management with Cloudinary, site preview, continuous integration with GitHub, atomic deploy and hosting, Git and Hugo integration, autosave, custom domain, project syncing, theme cloning and management. Developers have complete control over the source code and can manage it with GitHub’s deceptively simple workflow.

+* [DATOCMS](https://www.datocms.com) DatoCMS is a fully customizable administrative area for your static websites. Use your favorite website generator, let your clients publish new content independently, and the host the site anywhere you like.

+* [Forestry.io](https://forestry.io/). Forestry is a simple CMS for Jekyll and Hugo websites with support for GitHub, GitLab, and Bitbucket. Every time an update is made via the CMS, Forestry will commit changes back to your repo and will compile/deploy your website to S3, GitHub Pages, FTP, etc.

+* [Netlify.com](https://www.netlify.com). Netlify builds, deploys, and hosts your static website or app (Hugo, Jekyll, etc). Netlify offers a drag-and-drop interface and automatic deployments from GitHub or Bitbucket.

+    * **Features:** global CDN, atomic deploys, ultra-fast DNS, instant cache invalidation, high availability, automated hosting, Git integration, form submission hooks, authentication providers, and custom domains. Developers have complete control over the source code and can manage it with GitHub or Bitbucket's deceptively simple workflow.

--- /dev/null

+++ b/content/tools/migrations.md

@@ -1,0 +1,71 @@

+---

+title: Migrate to Hugo

+linktitle: Migrations

+description: A list of community-developed tools for migrating from your existing static site generator or content management system to Hugo.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [migrations,jekyll,wordpress,drupal,ghost,contentful]

+menu:

+  docs:

+    parent: "tools"

+    weight: 10

+weight: 10

+sections_weight: 10

+draft: false

+aliases: [/developer-tools/migrations/,/developer-tools/migrated/]

+toc: true

+---

+This section highlights some projects around Hugo that are independently developed. These tools try to extend the functionality of our static site generator or help you to get started.

+{{% note %}}

+Do you know or maintain a similar project around Hugo? Feel free to open a [pull request](https://github.com/gohugoio/hugo/pulls) on GitHub if you think it should be added.

+{{% /note %}}

+Take a look at this list of migration tools if you currently use other logging tools like Jekyll or WordPress but intend to switch to Hugo instead. They'll take care to export your content into Hugo-friendly formats.

+## Jekyll

+Alternatively, you can use the new [Jekyll import command](/commands/hugo_import_jekyll/).

+- [JekyllToHugo](https://github.com/SenjinDarashiva/JekyllToHugo) - A Small script for converting Jekyll blog posts to a Hugo site.

+- [ConvertToHugo](https://github.com/coderzh/ConvertToHugo) - Convert your blog from Jekyll to Hugo.

+## Ghost

+- [ghostToHugo](https://github.com/jbarone/ghostToHugo) - Convert Ghost blog posts and export them to Hugo.

+## Octopress

+- [octohug](https://github.com/codebrane/octohug) - Octopress to Hugo migrator.

+## DokuWiki

+- [dokuwiki-to-hugo](https://github.com/wgroeneveld/dokuwiki-to-hugo) - Migrates your dokuwiki source pages from [DokuWiki syntax](https://www.dokuwiki.org/wiki:syntax) to Hugo Markdown syntax. Includes extra's like the TODO plugin. Written with extensibility in mind using python 3. Also generates a TOML header for each page. Designed to copypaste the wiki directory into your /content directory.

+## WordPress

+- [wordpress-to-hugo-exporter](https://github.com/SchumacherFM/wordpress-to-hugo-exporter) - A one-click WordPress plugin that converts all posts, pages, taxonomies, metadata, and settings to Markdown and YAML which can be dropped into Hugo. (Note: If you have trouble using this plugin, you can [export your site for Jekyll](https://wordpress.org/plugins/jekyll-exporter/) and use Hugo's built in Jekyll converter listed above.)

+## Tumblr

+- [tumblr-importr](https://github.com/carlmjohnson/tumblr-importr) - An importer that uses the Tumblr API to create a Hugo static site.

+- [tumblr2hugomarkdown](https://github.com/Wysie/tumblr2hugomarkdown) - Export all your Tumblr content to Hugo Markdown files with preserved original formatting.

+- [Tumblr to Hugo](https://github.com/jipiboily/tumblr-to-hugo) - A migration tool that converts each of your Tumblr posts to a content file with a proper title and path. Furthermore, "Tumblr to Hugo" creates a CSV file with the original URL and the new path on Hugo, to help you setup the redirections.

+## Drupal

+- [drupal2hugo](https://github.com/danapsimer/drupal2hugo) - Convert a Drupal site to Hugo.

+## Joomla

+- [hugojoomla](https://github.com/davetcc/hugojoomla) - This utility written in Java takes a Joomla database and converts all the content into Markdown files. It changes any URLs that are in Joomla's internal format and converts them to a suitable form.

+## Blogger

+- [blogimport](https://github.com/natefinch/blogimport) - A tool to import from Blogger posts to Hugo.

+## Contentful

+- [contentful2hugo](https://github.com/ArnoNuyts/contentful2hugo) - A tool to create content-files for Hugo from content on [Contentful](https://www.contentful.com/).

--- /dev/null

+++ b/content/tools/other.md

@@ -1,0 +1,28 @@

+---

+title: Other Hugo Community Projects

+linktitle: Other Projects

+description: Some interesting projects developed by the Hugo community that don't quite fit into our other developer tool categories.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [developer tools]

+#tags: [frontend,gui]

+menu:

+  docs:

+    parent: "tools"

+    weight: 70

+weight: 70

+sections_weight: 70

+draft: false

+aliases: []

+toc: false

+---

+And for all the other small things around Hugo:

+* [hugo-gallery](https://github.com/icecreammatt/hugo-gallery) lets you create an image gallery for Hugo sites.

+* [flickr-hugo-embed](https://github.com/nikhilm/flickr-hugo-embed) prints shortcodes to embed a set of images from an album on Flickr into Hugo.

+* [hugo-openapispec-shortcode](https://github.com/tenfourty/hugo-openapispec-shortcode) A shortcode that allows you to include [Open API Spec](https://openapis.org) (formerly known as Swagger Spec) in a page.

+* [HugoPhotoSwipe](https://github.com/GjjvdBurg/HugoPhotoSwipe) makes it easy to create image galleries using PhotoSwipe.

+* [Hugo SFTP Upload](https://github.com/thomasmey/HugoSftpUpload) Syncs the local build of your Hugo website with your remote webserver via SFTP.

+* [Emacs Easy Hugo](https://github.com/masasam/emacs-easy-hugo) Emacs package for writing blog posts in markdown or org-mode and building your site with Hugo.

--- /dev/null

+++ b/content/tools/search.md

@@ -1,0 +1,29 @@

+---

+title: Search for your Hugo Website

+linktitle: Search

+description: See some of the open-source and commercial search options for your newly created Hugo website.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-26

+categories: [developer tools]

+#tags: [search,tools]

+menu:

+  docs:

+    parent: "tools"

+    weight: 60

+weight: 60

+sections_weight: 60

+draft: false

+aliases: []

+toc: true

+---

+A static website with a dynamic search function? Yes. As alternatives to embeddable scripts from Google or other search engines, you can provide your visitors a custom search by indexing your content files directly.

+* [Hugoidx](https://github.com/blevesearch/hugoidx) is an experimental application to create a search index. It's built on top of [Bleve](http://www.blevesearch.com/).

+* [GitHub Gist for Hugo Workflow](https://gist.github.com/sebz/efddfc8fdcb6b480f567). This gist contains a simple workflow to create a search index for your static website. It uses a simple Grunt script to index all your content files and [lunr.js](http://lunrjs.com/) to serve the search results.

+* [hugo-lunr](https://www.npmjs.com/package/hugo-lunr). A simple way to add site search to your static Hugo site using [lunr.js](http://lunrjs.com/). Hugo-lunr will create an index file of any html and markdown documents in your Hugo project.

+## Commercial Search Services

+* [Algolia](https://www.algolia.com/)'s Search API makes it easy to deliver a great search experience in your apps and websites. Algolia Search provides hosted full-text, numerical, faceted, and geolocalized search.

\ No newline at end of file

--- /dev/null

+++ b/content/tools/starter-kits.md

@@ -1,0 +1,38 @@

+---

+title: Starter Kits

+linktitle: Starter Kits

+description: A list of community-developed projects designed to help you get up and running with Hugo.

+date: 2017-02-22

+publishdate: 2017-02-01

+lastmod: 2017-02-22

+#tags: [starters,assets,pipeline]

+menu:

+  docs:

+    parent: "tools"

+    weight: 30

+weight: 30

+sections_weight: 30

+draft: false

+aliases: [/developer-tools/migrations/,/developer-tools/migrated/]

+toc: false

+---

+Know of a Hugo-related starter kit that isn't mentioned here? [Please add it to the list.][addkit]

+{{% note "Starter Kits are Not Maintained by the Hugo Team"%}}

+The following starter kits are developed by active members of the Hugo community. If you find yourself having issues with any of the projects, it's best to file an issue directly with the project's maintainer(s).

+{{% /note %}}

+* [Victor Hugo][]. Victor Hugo is a Hugo boilerplate for creating truly epic websites using Gulp + Webpack as an asset pipeline. Victor Hugo uses post-css and Babel for CSS and JavaScript, respectively, and is actively maintained.

+* [GOHUGO AMP][]. GoHugo AMP is a starter theme that aims to make it easy to adopt [Google's AMP Project][amp]. The starter kit comes with 40+ shortcodes and partials plus automatic structured data. The project also includes a [separate site with extensive documentation][gohugodocs].

+* [Blaupause][]. Blaupause is a developer-friendly Hugo starter kit based on Gulp tasks. It comes ES6-ready with several helpers for SVG and fonts and basic structure for HTML, SCSS, and JavaScript.

+* [hugulp][]. hugulp is a tool to optimize the assets of a Hugo website. The main idea is to recreate the famous Ruby on Rails Asset Pipeline, which minifies, concatenates and fingerprints the assets used in your website.

+[addkit]: https://github.com/gohugoio/hugo/edit/master/docs/content/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

\ No newline at end of file

--- /dev/null

+++ b/content/tools/syntax-highlighting.md

@@ -1,0 +1,241 @@

+---

+title: Syntax Highlighting

+linktitle:

+description: Hugo provides server-side syntax highlighting via Pygments and, like most static site generators, works very well with client-side (JavaScript) syntax highlighting libraries as well.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [highlighting,pygments,code blocks,syntax]

+categories: [developer tools]

+menu:

+  docs:

+    parent: "tools"

+    weight: 20

+weight: 20

+sections_weight: 20

+draft: false

+aliases: [/extras/highlighting/,/extras/highlight/]

+toc: true

+---

+Hugo can highlight source code in _two different ways_&mdash;either pre-processed server side from your content or to defer the processing to the client side, using a JavaScript library.

+## Server-side

+For the pre-processed approach, highlighting is performed by an external Python-based program called [Pygments](http://pygments.org/) and is triggered via an embedded Hugo shortcode (see [example](#example-highlight-shortcode-input) below). If Pygments is absent from the path, it will silently simply pass the content along without highlighting.

+### Server-side Advantages

+The advantages of server-side syntax highlighting are that it doesn’t depend on a JavaScript library and, consequently, works very well when read from an RSS feed.

+### Pygments

+If you have never worked with Pygments before, here is a brief primer:

++ Install Python from [python.org](https://www.python.org/downloads/). Version 2.7.x is already sufficient.

++ Run `pip install Pygments` in order to install Pygments. Once installed, Pygments gives you a command `pygmentize`. Make sure it sits in your PATH; otherwise, Hugo will not be able to find and use it.

+On Debian and Ubuntu systems, you may also install Pygments by running `sudo apt-get install python3-pygments`.

+Hugo gives you two options that you can set with the variable `pygmentsuseclasses` (default `false`) in your [site configuration](/getting-started/configuration/).

+1. Color codes for highlighting keywords are directly inserted if `pygmentsuseclasses = false` (default). The color codes depend on your choice of the `pygmentsstyle` (default = `"monokai"`). You can explore the different color styles on [pygments.org](http://pygments.org/) after inserting some example code.

+2. If you choose `pygmentsuseclasses = true`, Hugo includes class names in your code instead of color codes. For class-names to be meaningful, you need to include a `.css` file in your website representing your color scheme. You can either generate this `.css` files according to the [description from the Pygments documentation](http://pygments.org/docs/cmdline/) or download the one of the many pre-built color schemes from [Pygment's GitHub css repository](https://github.com/richleland/pygments-css).

+### Server-side Usage

+Highlighting is carried out via the [built-in shortcode](/content-management/shortcodes/) `highlight`. `highlight` takes exactly one required parameter for the programming language to be highlighted and requires a closing shortcode. Note that `highlight` is *not* used for client-side javascript highlighting.

+### Example `highlight` Shortcode Input

+{{% code file="example-highlight-shortcode-input.md" %}}

+```html

+{{</* highlight html */>}}

+<section id="main">

+  <div>

+    <h1 id="title">{{ .Title }}</h1>

+    {{ range .Data.Pages }}

+      {{ .Render "summary"}}

+    {{ end }}

+  </div>

+</section>

+{{</* /highlight */>}}

+```

+{{% /code %}}

+### Example `highlight` Shortcode Output

+{{% output file="example-highlight-shortcode-output.html" %}}

+```

+<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 }}

+      {{ .Render &quot;summary&quot;}}

+    {{ end }}

+  <span style="color: #f92672">&lt;/div&gt;</span>

+<span style="color: #f92672">&lt;/section&gt;</span>

+```

+{{% /output %}}

+### Options

+Options for controlling highlighting can be added in the second argument as a quoted, comma-separated key-value list. The example below will syntax highlight in `go` with inline line numbers and line numbers 2 and 3 highlighted.

+```

+{{</* highlight go "linenos=inline,hl_lines=2 3" */>}}

+var a string

+var b string

+var c string

+var d string

+{{</* / highlight */>}}

+```

+The `highlight` shortcode includes the following supported keywords:

+* `style`

+* `encoding`

+* `noclasses`

+* `hl_lines`

+* `linenos`

+Note that `style` and `noclasses` will override the similar setting in the [global config](/getting-started/configuration/).

+The keywords in the `highlight` shortcode mirror those of Pygments from the command line. See the [Pygments documentation](http://pygments.org/docs/) for more information.

+### Code Fences

+It is also possible to add syntax highlighting with GitHub flavored code fences. To enable this, set the `PygmentsCodeFences` to `true` in Hugo's [configuration file](/getting-started/configuration/);

+````

+```html

+<section id="main">

+  <div>

+    <h1 id="title">{{ .Title }}</h1>

+    {{ range .Data.Pages }}

+      {{ .Render "summary"}}

+    {{ end }}

+  </div>

+</section>

+```

+````

+{{% note "Disclaimers on Pygments" %}}

+* Pygments is relatively slow and _causes a performance hit when building your site_, but Hugo has been designed to cache the results to disk.

+* The caching can be turned off by setting the `--ignoreCache` flag to `true`.

+* The languages available for highlighting depend on your Pygments installation.

+{{% /note %}}

+## Client-side

+Alternatively, code highlighting can be applied to your code blocks in client-side JavaScript.

+Client-side syntax highlighting is very simple to add. You'll need to pick

+a library and a corresponding theme. Some popular libraries are:

+- [Highlight.js]

+- [Prism]

+- [Rainbow]

+- [Syntax Highlighter]

+- [Google Prettify]

+### Client-side Advantages

+The advantages of client-side syntax highlighting are that it doesn’t cost anything when building your site, and some of the highlighting scripts available cover more languages than Pygments does.

+### Highlight.js Example

+This example uses the popular [Highlight.js] library, hosted by [Yandex], a popular Russian search engine.

+In your `./layouts/partials/` (or `./layouts/chrome/`) folder, depending on your specific theme, there will be a snippet that will be included in every generated HTML page, such as `header.html` or `header.includes.html`. Simply add the css and js to initialize [Highlight.js]:

+```

+<link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.6.0/styles/default.min.css">

+<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.6.0/highlight.min.js"></script>

+<script>hljs.initHighlightingOnLoad();</script>

+```

+### Prism example

+Prism is another popular highlighter library and is used on some major sites.

+The [download section of the prism.js website][prismdownload] is simple to use and affords you a high degree of customization to pick only the languages you'll be using on your site.

+Similar to Highlight.js, you simply load `prism.css` in your `<head>` via whatever Hugo partial template is creating that part of your pages:

+```html

+...

+<link href="/css/prism.css" rel="stylesheet" />

+...

+```

+Add `prism.js` near the bottom of your `<body>` tag in whatever Hugo partial template is appropriate for your site or theme.

+```html

+...

+<script src="/js/prism.js"></script>

+</body>

+```

+In this example, the local paths indicate that your downloaded copy of these files are being added to the site, typically under `./static/css/` and `./static/js/`, respectively.

+### Client-side Usage

+To use client-side highlighting, most of these javascript libraries expect your code to be wrapped in semantically correct `<code>` elements with language-specific class attributes. For example, a code block for HTML would have `class="language-html"`.

+The client-side highlighting script therefore looks for programming language classes according to this convention: `language-go`, `language-html`, `language-css`, `language-bash`, etc. If you look at the page's source, you might see something like the following:

+```html

+<pre>

+  <code class="language-css">

+  body {

+    font-family: "Noto Sans", sans-serif;

+  }

+  </code>

+</pre>

+```

+If you are using markdown, your content pages needs to use the following syntax, with the name of the language to be highlighted entered directly after the first "fence." A fenced code block can be noted by opening and closing triple tilde <kbd>~</kbd> or triple back ticks <kbd>`</kbd>:

+{{< nohighlight >}}

+~~~css

+body {

+  font-family: "Noto Sans", sans-serif;

+}

+~~~

+{{< /nohighlight >}}

+Here is the same example but with triple back ticks to denote the fenced code block:

+{{< nohighlight >}}

+```css

+body {

+  font-family: "Noto Sans", sans-serif;

+}

+```

+{{< /nohighlight >}}

+Passing the above examples through the highlighter script would yield the following markup:

+{{< nohighlight >}}

+&lt;pre&gt;&lt;code class="language-css hljs"&gt;;&lt;span class="hljs-selector-tag"&gt;body&lt;/span&gt; {

+  &lt;span class="hljs-attribute"&gt;font-family&lt;/span&gt;: &ltspan class="hljs-string"&gt;"Noto Sans"&lt;/span&gt;, sans-serif;

+}

+{{< /nohighlight >}}

+In the case of the coding color scheme used by the Hugo docs, the resulting output would then look like the following to the website's end users:

+```css

+body {

+  font-family: "Noto Sans", sans-serif;

+}

+```

+Please see individual libraries' documentation for how to implement each of the JavaScript-based libraries.

+[Prism]: http://prismjs.com

+[prismdownload]: http://prismjs.com/download.html

+[Highlight.js]: http://highlightjs.org/

+[Rainbow]: http://craig.is/making/rainbows

+[Syntax Highlighter]: http://alexgorbatchev.com/SyntaxHighlighter/

+[Google Prettify]: https://github.com/google/code-prettify

+[Yandex]: http://yandex.ru/

\ No newline at end of file

--- /dev/null

+++ b/content/troubleshooting/_index.md

@@ -1,0 +1,26 @@

+---

+title: Troubleshooting

+linktitle: Troubleshooting

+description: Frequently asked questions and known issues pulled from the Hugo Discuss forum.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+menu:

+  docs:

+    parent: "troubleshooting"

+    weight: 01

+weight: 01	#rem

+draft: false

+hidesectioncontents: false

+slug:

+aliases: [/troubleshooting/faqs/,/faqs/]

+toc: false

+notesforauthors:

+---

+The Troubleshooting section includes known issues, recent workarounds, and FAQs pulled from the [Hugo Discussion Forum][forum].

+[forum]: https://discourse.gohugo.io

--- /dev/null

+++ b/content/troubleshooting/accented-characters-in-urls.md

@@ -1,0 +1,60 @@

+---

+title: Accented Characters in URLs

+linktitle: Accented Characters in URLs

+description: If you're having trouble with special characters in your taxonomies or titles adding odd characters to your URLs.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+#tags: [urls,multilingual,special characters]

+categories: [troubleshooting]

+menu:

+  docs:

+    parent: "troubleshooting"

+weight:

+draft: false

+slug:

+aliases: [/troubleshooting/categories-with-accented-characters/]

+toc: true

+---

+## Trouble: Categories with accented characters

+> One of my categories is named "Le-carré," but the link ends up being generated like this:

+>

+> ```bash

+> categories/le-carr%C3%A9

+> ```

+>

+> And not working. Is there an easy fix for this that I'm overlooking?

+## Solution

+Are you a macOS user? If so, you are likely a victim of HFS Plus file system's insistence to store the "é" (U+00E9) character in Normal Form Decomposed (NFD) mode, i.e. as "e" + "  ́" (U+0065 U+0301).

+`le-carr%C3%A9` is actually correct, `%C3%A9` being the UTF-8 version of U+00E9 as expected by the web server. The problem is that OS X turns [U+00E9] into [U+0065 U+0301], and thus `le-carr%C3%A9` no longer works.  Instead, only `le-carre%CC%81` ending with `e%CC%81` would match that [U+0065 U+0301] at the end.

+This is unique to OS X. The rest of the world does not do this, and most certainly not your web server which is most likely running Linux. This is not a Hugo-specific problem either. Other people have been bitten by this when they have accented characters in their HTML files.

+Note that this problem is not specific to Latin scripts. Japanese Mac users often run into the same issue; e.g., with `だ` decomposing into `た` and `&#x3099;`. (Read the [Japanese Perl users article][]).

+Rsync 3.x to the rescue! From [an answer posted on Server Fault][]:

+> You can use rsync's `--iconv` option to convert between UTF-8 NFC & NFD, at least if you're on a Mac. There is a special `utf-8-mac` character set that stands for UTF-8 NFD. So to copy files from your Mac to your web server, you'd need to run something like:

+>

+> `rsync -a --iconv=utf-8-mac,utf-8 localdir/ mywebserver:remotedir/`

+>

+> This will convert all the local filenames from UTF-8 NFD to UTF-8 NFC on the remote server. The files' contents won't be affected. - [Server Fault][]

+Please make sure you have the latest version of rsync 3.x installed. The rsync that ships with OS X is outdated. Even the version that comes packaged with 10.10 (Yosemite) is version 2.6.9 protocol version 29. The `--iconv` flag is new in rsync 3.x.

+### Discussion Forum References

+* http://discourse.gohugo.io/t/categories-with-accented-characters/505

+* http://wiki.apache.org/subversion/NonNormalizingUnicodeCompositionAwareness

+* https://en.wikipedia.org/wiki/Unicode_equivalence#Example

+* http://zaiste.net/2012/07/brand_new_rsync_for_osx/

+* https://gogo244.wordpress.com/2014/09/17/drived-me-crazy-convert-utf-8-mac-to-utf-8/

+[an Answer posted on Server Fault]: http://serverfault.com/questions/397420/converting-utf-8-nfd-filenames-to-utf-8-nfc-in-either-rsync-or-afpd "Converting UTF-8 NFD filenames to UTF-8 NFC in either rsync or afpd, Server Fault Discussion"

+[Japanese Perl users article]: http://perl-users.jp/articles/advent-calendar/2010/english/24 "Encode::UTF8Mac makes you happy while handling file names on MacOSX"

+[Server Fault]: http://serverfault.com/questions/397420/converting-utf-8-nfd-filenames-to-utf-8-nfc-in-either-rsync-or-afpd "Converting UTF-8 NFD filenames to UTF-8 NFC in either rsync or afpd, Server Fault Discussion"

--- /dev/null

+++ b/content/troubleshooting/build-performance.md

@@ -1,0 +1,23 @@

+---

+title: Build Performance

+linktitle: Build Performance

+description:

+date: 2017-03-12

+publishdate: 2017-03-12

+lastmod: 2017-03-12

+#tags: [performance, build]

+categories: [troubleshooting]

+menu:

+  docs:

+    parent: "troubleshooting"

+weight:

+draft: true

+slug:

+aliases: []

+toc: true

+wip: true

+---

+<!-- See https://discourse.gohugo.io/t/new-docs-site-need-feedback/5765/6-->

+<!-- Lots of forums threads that give the same answers. Should call attention to --verbose, --stepAnalysis, and --renderToMemory (for troubleshooting disk I/O). Highlight partialCached template function. -->

--- a/content/troubleshooting/categories-with-accented-characters.md

+++ /dev/null

@@ -1,50 +1,0 @@

----

-lastmod: 2015-01-08

-date: 2015-01-08T16:32:00-07:00

-menu:

-  main:

-    parent: troubleshooting

-title: Accented Categories

-weight: 10

----

-## Trouble: Categories with accented characters

-One of my categories is named "Le-carré," but the link ends up being generated like this:

-    categories/le-carr%C3%A9

-And not working. Is there an easy fix for this that I'm overlooking?

-## Solution

-Mac OS X user?  If so, you are likely a victim of HFS Plus file system's insistence to store the "é" (U+00E9) character in Normal Form Decomposed (NFD) mode, i.e. as "e" + "  ́" (U+0065 U+0301).

-`le-carr%C3%A9` is actually correct, `%C3%A9` being the UTF-8 version of U+00E9 as expected by the web server.  Problem is, OS X turns [U+00E9] into [U+0065 U+0301], and thus `le-carr%C3%A9` no longer works.  Instead, only `le-carre%CC%81` ending with `e%CC%81` would match that [U+0065 U+0301] at the end.

-This is unique to OS X.  The rest of the world does not do this, and most certainly not your web server which is most likely running Linux.  This is not a Hugo-specific problem either.  Other people have been bitten by this when they have accented characters in their HTML files.

-Nor is this problem specific to Latin scripts.  Japanese Mac users often run into the same issue, e.g. with `だ` decomposing into `た` and <code>&#x3099;</code>.[^1]

-Rsync 3.x to the rescue!  From [an answer posted on Server Fault](http://serverfault.com/questions/397420/converting-utf-8-nfd-filenames-to-utf-8-nfc-in-either-rsync-or-afpd):

-> You can use rsync's `--iconv` option to convert between UTF-8 NFC & NFD, at least if you're on a Mac. There is a special `utf-8-mac` character set that stands for UTF-8 NFD. So to copy files from your Mac to your web server, you'd need to run something like:

->

-> `rsync -a --iconv=utf-8-mac,utf-8 localdir/ mywebserver:remotedir/`

->

-> This will convert all the local filenames from UTF-8 NFD to UTF-8 NFC on the remote server. The files' contents won't be affected.

-Please make sure you have the latest version rsync 3.x installed.  The rsync that ships with OS X (even the latest 10.10 Yosemite) is the horribly old at version 2.6.9 protocol version 29.  The `--iconv` flag is new in rsync 3.x.

-### References

-* https://discourse.gohugo.io/t/categories-with-accented-characters/505

-* [Converting UTF-8 NFD filenames to UTF-8 NFC, in either rsync or afpd](http://serverfault.com/questions/397420/converting-utf-8-nfd-filenames-to-utf-8-nfc-in-either-rsync-or-afpd) (Server Fault)

-* http://wiki.apache.org/subversion/NonNormalizingUnicodeCompositionAwareness

-* https://en.wikipedia.org/wiki/Unicode_equivalence#Example

-* http://zaiste.net/2012/07/brand_new_rsync_for_osx/

-* https://gogo244.wordpress.com/2014/09/17/drived-me-crazy-convert-utf-8-mac-to-utf-8/

-[^1]: As explained in the Japanese Perl Users article [Encode::UTF8Mac makes you happy while handling file names on MacOSX](http://perl-users.jp/articles/advent-calendar/2010/english/24).

--- /dev/null

+++ b/content/troubleshooting/eof-error.md

@@ -1,0 +1,49 @@

+---

+title: EOF Error

+linktitle: EOF Error

+description: If you find yourself seeing an EOF error in the console whenever you create a new content file from Hugo's archetype feature.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [troubleshooting]

+menu:

+  docs:

+    parent: "troubleshooting"

+#tags: [eof, end of file, error, faqs]

+draft: false

+weight:

+aliases: [/troubleshooting/strange-eof-error/]

+toc: true

+---

+## Trouble: `hugo new` Aborts with EOF error

+> I'm running into an issue where I cannot get archetypes working, when running `hugo new showcase/test.md`, for example, I see an `EOF` error thrown by Hugo.

+>

+> When I run Hugo with v0.12 via `hugo new -v showcase/test.md`, I see the following output:

+>

+> ```bash

+> INFO: 2015/01/04 Using config file: /private/tmp/test/config.toml

+> INFO: 2015/01/04 attempting to create  showcase/test.md of showcase

+> INFO: 2015/01/04 curpath: /private/tmp/test/archetypes/showcase.md

+> ERROR: 2015/01/04 EOF

+> ```

+>

+> Is there something that I am blatantly missing?

+## Solution: Carriage Returns

+The solution is to add a final newline (i.e., `EOL`) to the end of your default.md archetype file of your theme. You can do this by adding a carriage return after the closing `+++` or `---` of your TOML or YAML front matter, respectively.

+{{% note "Final EOL Unnecessary in v0.13+" %}}

+As of v0.13, Hugo's parser has been enhanced to accommodate archetype files without final EOL thanks to the great work by [@tatsushid](https://github.com/tatsushid).

+{{% /note %}}

+## Discussion Forum References

+* http://discourse.gohugo.io/t/archetypes-not-properly-working-in-0-12/544

+* http://discourse.gohugo.io/t/eol-f-in-archetype-files/554

+## Related Hugo Issues

+* https://github.com/gohugoio/hugo/issues/776

--- a/content/troubleshooting/overview.md

+++ /dev/null

@@ -1,36 +1,0 @@

----

-lastmod: 2015-01-27

-date: 2015-01-18T02:41:52-07:00

-menu:

-  main:

-    parent: troubleshooting

-title: Troubleshooting Overview

-weight: 0

----

-Got stuck?  Worry not!  Chances are other users have encountered

-the exact same problem as you have, brought it up for

-[discussion](https://discourse.gohugo.io/), and have likely found a solution

-through the collective wisdom of our vibrant Hugo community!

-Here are some examples:

-* [`hugo new` aborts with cryptic EOF error](/troubleshooting/strange-eof-error/) (affects v0.12 and lower)

-* [Categories with accented characters inaccessible](/troubleshooting/categories-with-accented-characters/) (affects Mac OS&nbsp;X users)

-* [My CSS files aren't loaded!](https://discourse.gohugo.io/t/deployment-workflow/90/15)

-* [How do I include an image gallery on my website?](https://discourse.gohugo.io/t/image-gallery/594)

-* ... And a lot more!

-{{% youtube c8fJIRNChmU %}}

-Indeed, you may find many questions and solutions

-to problems in our [discussion forum](https://discourse.gohugo.io/),

-and you may find the [support](https://discourse.gohugo.io/category/support)

-and [tips & tricks](https://discourse.gohugo.io/category/tips-tricks)

-categories particularly helpful.

-Can't find anything?  Please write on the forum and post your questions

-and comments!  Sometimes, your feedback may lead to the discovery of

-existing bugs in the code or in the documentation, and may even spur

-the interest of adding new features to the next Hugo version, improving

-Hugo for everybody!  (Thank you!)  See you on the forum!

--- a/content/troubleshooting/strange-eof-error.md

+++ /dev/null

@@ -1,43 +1,0 @@

----

-lastmod: 2015-01-17

-date: 2015-01-08T16:11:23-07:00

-menu:

-  main:

-    parent: troubleshooting

-title: Strange EOF error

-weight: 5

----

-## Trouble: `hugo new` aborts with cryptic EOF error

-> I'm running into an issue where I cannot get archetypes working, when running `hugo new showcase/test.md`, for example, I see an `EOF` error thrown by Hugo.

->

-> I have set up this test repository to show exactly what I've done, but it is essentially a vanilla installation of Hugo. https://github.com/polds/hugo-archetypes-test

->

-> When in that repository, using Hugo v0.12 to run `hugo new -v showcase/test.md`, I see the following output:

->

->     INFO: 2015/01/04 Using config file: /private/tmp/test/config.toml

->     INFO: 2015/01/04 attempting to create  showcase/test.md of showcase

->     INFO: 2015/01/04 curpath: /private/tmp/test/archetypes/showcase.md

->     ERROR: 2015/01/04 EOF

->

-> Is there something that I am blatantly missing?

-## Solution

-Thank you for reporting this issue.  The solution is to add a final newline (i.e. EOL) to the end of your default.md archetype file of your theme.  More discussions happened on the forum here:

-* https://discourse.gohugo.io/t/archetypes-not-properly-working-in-0-12/544

-* https://discourse.gohugo.io/t/eol-f-in-archetype-files/554

-Due to popular demand, Hugo's parser has been enhanced to

-accommodate archetype files without final EOL,

-thanks to the great work by [@tatsushid](https://github.com/tatsushid),

-in the upcoming v0.13 release,

-Until then, for us running the stable v0.12 release, please remember to add the final EOL diligently.  <i class="fa fa-smile-o"></i>

-## References

-* https://github.com/gohugoio/hugo/issues/776

--- a/content/tutorials/automated-deployments.md

+++ /dev/null

@@ -1,275 +1,0 @@

----

-authors:

-- Arjen Schwarz

-- Samuel Debruyn

-lastmod: 2017-02-26

-date: 2015-01-12

-linktitle: Automated deployments

-toc: true

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/creating-a-new-theme

-prev: /community/contributing

-title: Automated deployments with Wercker

-weight: 10

----

-# Automated deployments with Wercker

-In this tutorial we will set up a basic Hugo project and then configure a free tool called Wercker to automatically deploy the generated site any time we add an article. We will deploy it to GitHub pages as that is easiest to set up, but you will see that we can use anything. This tutorial takes you through every step of the process, complete with screenshots and is fairly long.

-The  assumptions made for this tutorial are that you know how to use git for version control, and have a GitHub account. In case you are unfamiliar with these, in their [help section](https://help.github.com/articles/set-up-git/) GitHub has an explanation of how to install and use git and you can easily sign up for a free GitHub account as well.

-## Creating a basic Hugo site

-There are already [pages](http://gohugo.io/overview/quickstart/) dedicated to describing how to set up a Hugo site so we will only go through the most basic steps required to get a site up and running before we dive into the Wercker configuration. All the work for setting up the project is done using the command line, and kept as simple as possible.

-Create the new site using the `hugo new site` command, and we move into it.

-```bash

-hugo new site hugo-wercker-example

-cd hugo-wercker-example

-```

-Add the herring-cove theme by cloning it into the theme directory using the following commands.

-```bash

-mkdir themes

-cd themes

-git clone https://github.com/spf13/herring-cove.git

-```

-Cloning the project like this will conflict with our own version control, so we remove the external git configuration.

-```bash

-rm -rf herring-cove/.git

-```

-Let's add a quick **about** page.

-```bash

-hugo new about.md

-```

-Now we'll edit contents/about.md to ensure it's no longer a draft and add some text to it.

-```bash

-hugo undraft content/about.md

-```

-Once completed it's a good idea to do a quick check if everything is working by running

-```bash

-hugo server --theme=herring-cove

-```

-If everything is fine, you should be able to see something similar to the image below when you go to localhost:1313 in your browser.

-![][1]

-[1]: /img/tutorials/automated-deployments/creating-a-basic-hugo-site.png

-## Setting up version control

-Adding git to our project is done by running the `git init` command from the root directory of the project.

-```bash

-git init

-```

-Running `git status` at this point will show you p entries: the **config.toml** file, the **themes** directory, the **contents** directory, and the **public** directory. We don't want the **public** directory version controlled however, as we will use wercker to generate that later on. Therefore, we'll add a gitignore file that will exclude this using the following command.

-```bash

-echo "/public" >> .gitignore

-```

-As we currently have no static files outside of the theme directory, Wercker might complain when we try to build the site later on. To prevent this, we simply have to add any file to the static folder. To keep it simple for now we'll add a robots.txt file that will give all search engines full access to the site when it's up.

-```bash

-echo "User-agent: *\nDisallow:" > static/robots.txt

-```

-After this we can add everything to the repository.

-```bash

-git commit -a -m "Initial commit"

-```

-## Adding the project to GitHub

-First we'll create a new repository. You can do this by clicking on the **+** sign at the top right, or by going to https://github.com/new

-We then choose a name for the project (**hugo-wercker-example**). When clicking on create repository GitHub displays the commands for adding an existing project to the site. The commands shown below are the ones used for this site, if you're following along you will need to use the ones shown by GitHub. Once we've run those commands the project is in GitHub and we can move on to setting up the Wercker configuration.

-```bash

-git remote add origin [email protected]:YourUsername/hugo-wercker-example.git

-git push -u origin master

-```

-![][2]

-[2]: /img/tutorials/automated-deployments/adding-the-project-to-github.png

-## Welcome to wercker

-Let's start by setting up an account for Wercker. To do so we'll go to http://wercker.com and click on the **Sign up** button.

-![][3]

-[3]: /img/tutorials/automated-deployments/wercker-sign-up.png

-## Register

-To make life easier for ourselves, we will then register using GitHub. If you don't have a GitHub account, or don't want to use it for your account, you can of course register with a username and password as well.

-![][4]

-[4]: /img/tutorials/automated-deployments/wercker-sign-up-page.png

-## Connect GitHub/Bitbucket

-After you are registered, you will need to link your GitHub and/or Bitbucket account to Wercker. You do this by going to your profile settings, and then "Git connections" If you registered using GitHub it will most likely look like the image below. To connect a missing service, simply click on the connect button which will then send you to either GitHub or Bitbucket where you might need to log in and approve their access to your account.

-![][5]

-[5]: /img/tutorials/automated-deployments/wercker-git-connections.png

-## Add your project

-Now that we've got all the preliminaries out of the way, it's time to set up our application. For this we click on the **+ Create** button next to Applications. Create a new application, and choose to use GitHub.

-![][6]

-[6]: /img/tutorials/automated-deployments/wercker-add-app.png

-## Select a repository

-Clicking this will make Wercker show you all the repositories you have on GitHub, but you can easily filter them as well. So we search for our repository, select it, and then click on "Use selected repo".

-![][7]

-[7]: /img/tutorials/automated-deployments/wercker-select-repository.png

-## Configure access

-As Wercker doesn't access to check out your private projects by default, it will ask you what you want to do. When your project is public, as needs to be the case if you wish to use GitHub Pages, the top choice is recommended. When you use this it will simply check out the code in the same way anybody visiting the project on GitHub can do.

-![][8]

-[8]: /img/tutorials/automated-deployments/wercker-access.png

-## Public or not

-This is a personal choice; you can make an app public so that everyone can see more details about it. This doesn't give you any real benefits either way in general, although as part of the tutorial I have of course made this app public so you can see it in action [yourself](https://app.wercker.com/#applications/5586dcbdaf7de9c51b02b0d5).

-![][9]

-[9]: /img/tutorials/automated-deployments/public-or-not.png

-## Wercker.yml

-Choose Default for your programming language. Wercker will now attempt to create an initial *wercker.yml* file for you. Or rather, it will create the code you can copy into it yourself. Because there is nothing special about our project according to Wercker, we will simply get the `debian` box. So what we do now is create a *wercker.yml* file in the local root of our project that contains the provided configuration, and after we finish setting up the app we will expand this file to make it actually do something.

-![][10]

-[10]: /img/tutorials/automated-deployments/werckeryml.png

-## And we've got an app

-The application is added now, and Wercker will be offering you the chance to trigger a build. As we haven't pushed up the **wercker.yml** file however, we will politely decline this option. Wercker has automatically added a build pipeline to your application.

-## Adding build step

-And now we're going to add the build step to the build pipeline. First, we go to the "Registry" action in the top menu and then search for "hugo build". Find the **Hugo-Build** task by Arjen and select it.

-![][11]

-[11]: /img/tutorials/automated-deployments/wercker-search.png

-## Using Hugo-Build

-Inside the details of this step you will see how to use it. At the top is a summary for very basic usage, but when scrolling down you go through the README of the step which will usually contain more details about the advanced options available and a full example of using the step.

-We're not going to use any of the advanced features in this tutorial, so we'll return to our project and add the details we need to our wercker.yml file so that it looks like below:

-```yaml

-box: debian

-build:

-  steps:

-    - install-packages:

-        packages: git

-    - script:

-        name: download theme

-        code: |

-            $(git clone https://github.com/spf13/herring-cove ./themes/herring-cove)

-    - arjen/hugo-build:

-        version: "0.14"

-        theme: herring-cove

-        flags: --buildDrafts=true

-```

-As you can see, we have two steps in the build pipeline. The first step downloads the theme, and the second step runs arjen's hugo-build step. To use a different theme, you can replace the link to the herring-cove source with another theme's repository - just make sure the name of the folder you download the theme to (./themes/your-theme-name) matches the theme name you tell arjen/hugo-build to use (theme: your-theme-name). Now we'll test that it all works as it should by pushing up our wercker.yml file to GitHub and seeing the magic at work.

-```bash

-git commit -a -m "Add wercker.yml"

-git push origin master

-```

-Once completed a nice tick should have appeared in front of your first build, and if you want you can look at the details by clicking on it. However, we're not done yet as we still need to deploy it to GitHub Pages.

-![][12]

-[12]: /img/tutorials/automated-deployments/using-hugo-build.png

-## Adding a deploy pipeline

-In order to deploy to GitHub Pages we need to add a deploy pipeline.

-1. First, go to your Wercker application's page. Go to the "Workflows" tab and click on "Add new pipeline." Name it whatever you want; "deploy-production" or "deploy" works fine. For your YML Pipeline name, type in "deploy" without quotes. Leave the hook type as "Default" and hit the Create button.

-2. Now you need to link the deploy pipeline to your build pipeline. In the workflow editor, click on the + next to your build pipeline and add the deploy pipeline you've just made. Now the deploy pipeline will be run automatically whenever the build pipeline is completed successfully.

-![][13]

-[13]: /img/tutorials/automated-deployments/adding-a-deploy-pipeline.png

-## Adding a deploy step

-Next, we need to add a step to our deploy pipeline that will deploy the Hugo-built website to your GitHub pages repository. Once again searching through the Steps registry, we find that the most popular step is the **lukevevier/gh-pages** step so we add the configuration for that to our wercker.yml file. Additionally, we need to ensure that the box we run on has git and ssh installed. We can do this using the **install-packages** command, which then turns the wercker.yml file into this:

-```yaml

-box: debian

-build:

-  steps:

-    - arjen/hugo-build:

-        version: "0.14"

-        theme: herring-cove

-        flags: --buildDrafts=true

-deploy:

-  steps:

-    - install-packages:

-        packages: git ssh-client

-    - lukevivier/[email protected]:

-        token: $GIT_TOKEN

-        domain: hugo-wercker.ig.nore.me

-        basedir: public

-```

-How does the GitHub Pages configuration work? We've selected a couple of things, first the domain we want to use for the site. Configuring this here will ensure that GitHub Pages is aware of the domain you want to use.

-Secondly we've configured the basedir to **public**, this is the directory that will be used as the website on GitHub Pages.

-And lastly, you can see here that this has a **$GIT_TOKEN** variable. This is used for pushing our changes up to GitHub and we will need to configure this before we can do that. To do this, go to your application page and click on the "Environment" tab. Under Application Environment Variables, put **$GIT_TOKEN** for the Key. Now you'll need to create an access token in GitHub. How to do that is described on a [GitHub help page](https://help.github.com/articles/creating-an-access-token-for-command-line-use/). Copy and paste the access token you generated from GitHub into the Value box. **Make sure you check Protected** and then hit Add.

-![][14]

-[14]: /img/tutorials/automated-deployments/adding-a-deploy-step.png

-With the deploy step configured in Wercker, we can push the updated wercker.yml file to GitHub and it will create the GitHub pages site for us. The example site we used here is accessible under hugo-wercker.ig.nore.me

-## Conclusion

-From now on, any time you want to put a new post on your blog all you need to do is push your new page to GitHub and the rest will happen automatically. The source code for the example site used here is available on [GitHub](https://github.com/ArjenSchwarz/hugo-wercker-example), as is the [Hugo Build step](https://github.com/ArjenSchwarz/wercker-step-hugo-build) itself.

-If you want to see an example of how you can deploy to S3 instead of GitHub pages, take a look at [Wercker's documentation](http://devcenter.wercker.com/docs/deploy/s3.html) about how to set that up.

--- a/content/tutorials/create-a-multilingual-site.md

+++ /dev/null

@@ -1,168 +1,0 @@

----

-author: "Rick Cogley"

-lastmod: 2015-12-24

-date: 2015-07-08

-linktitle: Multilingual Site

-menu:

-  main:

-    parent: tutorials

-prev: /tutorials/migrate-from-jekyll

-title: Create a Multilingual Site

-weight: 10

----

-> **Note:** Since v0.17 Hugo has built-in support for the creation of multilingual website. [Read more about it]({{< relref "content/multilingual.md" >}}).

-## Introduction

-Hugo allows you to create a multilingual site from its built-in tools. This tutorial will show one way to do it, and assumes:

-* You already know the basics about creating a Hugo site

-* You have a separate domain name for each language

-* You'll use `/data` files for some translation strings

-* You'll use single, combined `layout` and `static` folders

-* You'll use a subfolder for each language under `content` and `public`

-## Site Configs

-Create your site configs in the root of your repository, for example for an English and Japanese site.

-**English Config `config_en.toml`**:

-~~~toml

-baseURL = "http://acme.com/"

-title = "Acme Inc."

-contentDir = "content/en"

-publishDir = "public/en"

-[params]

-    locale = "en-US"

-~~~

-**Japanese Config `config_ja.toml`**:

-~~~toml

-baseURL = "http://acme.jp/"

-title = "有限会社アクミー"

-contentDir = "content/ja"

-publishDir = "public/ja"

-[params]

-    locale = "ja-JP"

-~~~

-If you had more domains and languages, you would just create more config files. The standard `config.toml` is what Hugo will run as a default, but since we're creating language-specific ones, you'll need to specify each config file when running `hugo server` or just `hugo` before deploying.

-## Prep Translation Strings in `/data`

-Create `.yaml` (or `.json` or `.toml`) files for each language, under `/data/translations`.

-**English Strings `en-US.yaml`**:

-~~~yaml

-topSlogan: Acme Inc.

-topSubslogan: You'll love us

-...

-~~~

-**Japanese Strings `ja-JP.yaml`**:

-~~~yaml

-topSlogan: 有限会社アクミー

-topSubslogan: キット勝つぞ

-...

-~~~

-In some cases, where there is more complex formatting within the strings you want to show, it might be better to employ some conditional logic in your template, to display a block of html per language.

-## Reference Strings in templates

-Now you can reference the strings in your templates. One way is to do it like in this `layouts/index.html`, leveraging the fact that you have the locale set:

-~~~html

-<!DOCTYPE html>

-<html lang="{{ .Site.Params.locale }}">

-...

-  <head>

-    <meta charset="utf-8">

-    <title>{{ if eq .Site.Params.locale "en-US" }}{{ if .IsHome }}Welcome to {{ end }}{{ end }}{{ .Title }}{{ if eq .Site.Params.locale "ja-JP" }}{{ if .IsHome }}へようこそ{{ end }}{{ end }}{{ if ne .Title .Site.Title }} : {{ .Site.Title }}{{ end }}</title>

-    ...

-  </head>

-  <body>

-    <div class="container">

-      <h1 class="header">{{ ( index $.Site.Data.translations $.Site.Params.locale ).topSlogan }}</h1>

-      <h3 class="subheader">{{ ( index $.Site.Data.translations $.Site.Params.locale ).topSubslogan }}</h3>

-    </div>

-  </body>

-</html>

-~~~

-The above shows both techniques, using an `if eq` and `else if eq` to check the locale, and using `index` to pull strings from the data file that matches the locale set in the site's config file.

-## Customize Dates

-At the time of this writing, Golang does not yet have support for internationalized locales, but if you do some work, you can simulate it. For example, if you want to use French month names, you can add a data file like ``data/mois.yaml`` with this content:

-~~~toml

-1: "janvier"

-2: "février"

-3: "mars"

-4: "avril"

-5: "mai"

-6: "juin"

-7: "juillet"

-8: "août"

-9: "septembre"

-10: "octobre"

-11: "novembre"

-12: "décembre"

-~~~

-... then index the non-English date names in your templates like so:

-~~~html

-<time class="post-date" datetime="{{ .Date.Format "2006-01-02T15:04:05Z07:00" | safeHTML }}">

-  Article publié le {{ .Date.Day }} {{ index $.Site.Data.mois (printf "%d" .Date.Month) }} {{ .Date.Year }} (dernière modification le {{ .Lastmod.Day }} {{ index $.Site.Data.mois (printf "%d" .Lastmod.Month) }} {{ .Lastmod.Year }})

-</time>

-~~~

-This technique extracts the day, month and year by specifying ``.Date.Day``, ``.Date.Month``, and ``.Date.Year``, and uses the month number as a key, when indexing the month name data file.

-## Create Multilingual Content

-Now you can create markdown content in your languages, in the `content/en` and `content/ja` folders. The frontmatter stays the same on the key side, but the values would be set in each of the languages.

-## Run Hugo Server or Deploy Commands

-Once you have things set up, you can run `hugo server` or `hugo` before deploying. You can create scripts to do it, or as shell functions. Here are sample basic `zsh` functions:

-**Live Reload with `hugo server`**:

-~~~shell

-function hugoserver-com {

-  cd /Users/me/dev/mainsite

-  hugo server --buildDrafts --verbose --source="/Users/me/dev/mainsite" --config="/Users/me/dev/mainsite/config_en.toml" --port=1377

-}

-function hugoserver-jp {

-  cd /Users/me/dev/mainsite

-  hugo server --buildDrafts --verbose --source="/Users/me/dev/mainsite" --config="/Users/me/dev/mainsite/config_ja.toml" --port=1399

-}

-~~~

-**Deploy with `hugo` and `rsync`**:

-~~~shell

-function hugodeploy-acmecom {

-    rm -rf /tmp/acme.com

-    hugo --config="/Users/me/dev/mainsite/config_en.toml" -s /Users/me/dev/mainsite/ -d /tmp/acme.com

-    rsync -avze "ssh -p 22" --delete /tmp/acme.com/ [email protected]:/home/me/webapps/acme_com_site

-}

-function hugodeploy-acmejp {

-    rm -rf /tmp/acme.jp

-    hugo --config="/Users/me/dev/mainsite/config_ja.toml" -s /Users/me/dev/mainsite/ -d /tmp/acme.jp

-    rsync -avze "ssh -p 22" --delete /tmp/acme.jp/ [email protected]:/home/me/webapps/acme_jp_site

-}

-~~~

-Adjust to fit your situation, setting dns, your webserver config, and other settings as appropriate.

--- a/content/tutorials/creating-a-new-theme.md

+++ /dev/null

@@ -1,1717 +1,0 @@

----

-author: "Michael Henderson"

-lastmod: 2016-09-01

-date: 2015-11-26

-linktitle: Creating a New Theme

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/github-pages-blog

-prev: /tutorials/automated-deployments

-title: Creating a New Theme

-weight: 10

----

-## Introduction

-This tutorial will show you how to create a simple theme in Hugo.

-I'll introduce Hugo's use of templates,

-and explain how to organize them into a theme.

-The theme will grow, minimizing effort while meeting evolving needs.

-To promote this focus, and to keep everything simple, I'll omit CSS styling.

-We'll start by creating a tiny, blog-like web site.

-We'll implement this blog with just one &mdash; quite basic &mdash; template.

-Then we'll add an About page, and a few articles.

-Overall, this web site (along with what you learn here)

-will provide a good basis for you to continue working with Hugo in the future.

-By making small variations,

-you'll be able to create many different kinds of web sites.

-I will assume you're comfortable with HTML, Markdown formatting,

-and the Bash command line (possibly using [Git for

-Windows](https://git-for-windows.github.io/)).

-A few symbols might call for explanation: in this tutorial,

-the commands you'll enter will be preceded by a `$` prompt &mdash;

-and their output will follow.

-`vi` means to open your editor; then `:wq` means to save the file.

-Sometimes I'll add comments to explain a point &mdash; these start with `#`.

-So, for example:

-```bash

-# this is a comment

-$ echo this is a command

-this is a command

-# edit the file

-$ vi foo.md

-+++

-date = "2040-01-18"

-title = "creating a new theme"

-+++

-Bah! Humbug!

-:wq

-# show it

-$ cat foo.md

-+++

-date = "2040-01-18"

-title = "creating a new theme"

-+++

-Bah! Humbug!

-```

-## Definitions

-Three concepts:

-1. _Non-content_ files;

-1. _Templates_ (as Hugo defines them); and

-1. _Front-matter_

-are essential for creating your first Hugo theme,

-as well as your first Hugo website.

-### Non-Content

-The source files of a web site (destined to be rendered by Hugo)

-are divided into two kinds:

-1. The files containing its textual content (and nothing else &mdash;

-except Hugo front-matter: see below, and Markdown styling); and

-1. All other files. (These contain ***no*** textual content &mdash; ideally.)

-Temporarily, let's affix the adjective _non-content_

-to the latter kind of source files.

-Non-content files are responsible for your web site's look and feel.

-(Follow these article links from [Bop

-Design](https://www.bopdesign.com/bop-blog/2013/11/what-is-the-look-and-feel-of-a-website-and-why-its-important/)

-and

-[Wikipedia](https://en.wikipedia.org/w/index.php?title=Look_and_feel&oldid=731052704)

-if you wish for more information.)

-They comprise its images, its CSS (for the sizes, colors and fonts),

-its JavaScript (for the actions and reactions), and its Hugo templates

-(which contain the rules Hugo uses to transform your content into HTML).

-Given these files, Hugo will render a static web site &mdash;

-informed by your content &mdash;

-which contains the above images, HTML, CSS and JavaScript,

-ready to be served to visitors.

-Actually, a few of your invariant textual snippets

-could reside in non-content files as well.

-However, because someone might reuse your theme (eventually),

-preferably you should keep those textual snippets in their own content files.

-#### Where

-Regarding where to create your non-content files, you have two options.

-The simplest is the `./layouts/` and `./static/` filesystem trees.

-If you choose this way,

-then you needn't worry about configuring Hugo to find them.

-Invariably, these are the first two places Hugo seeks for templates

-(as well as images, CSS and JavaScript);

-so in that case, it's guaranteed to find all your non-content files.

-The second option is to create them in a filesystem tree

-located somewhere under the `./themes/` directory.

-If you choose that way,

-then you must always tell Hugo where to search for them &mdash;

-that's extra work, though. So, why bother?

-#### Theme

-Well &mdash; the difference between creating your non-content files under

-`./layouts/` and `./static/` and creating them under `./themes/`

-is admittedly very subtle.

-Non-content files created under `./layouts/` and `./static/`

-cannot be customized without editing them directly.

-On the other hand, non-content files created under `./themes/`

-can be customized, in another way. That way is both conventional

-(for Hugo web sites) and non-destructive. Therefore,

-creating your non-content files under `./themes/`

-makes it easier for other people to use them.

-The rest of this tutorial will call a set of non-content files a ***theme***

-if they comprise a filesystem tree rooted anywhere under the

-`./themes/` directory.

-Note that you can use this tutorial to create your set of non-content files

-under `./layouts/` and `./static/` if you wish. The only difference is that

-you wouldn't need to edit your web site's configuration file

-in order to select a theme.

-### Home

-The home page, or landing page,

-is the first page that many visitors to a web site will see.

-Often this is `/index.html`, located at the root URL of the web site.

-Since Hugo writes files into the `./public/` tree,

-your home page will reside in file `./public/index.html`.

-### Configure

-When Hugo runs, it first looks for an overall configuration file,

-in order to read its settings, and applies them to the entire web site.

-These settings override Hugo's default values.

-The file can be in TOML, YAML, or JSON format.

-I prefer TOML for my configuration files.

-If you prefer JSON or YAML, you'll need to translate my examples.

-You'll also need to change the basename, since Hugo uses its extension

-to determine how to process it.

-Hugo translates Markdown files into HTML.

-By default, Hugo searches for Markdown files in the `./content/` tree

-and template files under the `./themes/` directory.

-It will render HTML files to the `./public/` tree.

-You can override any of these defaults by specifying alternative locations

-in the configuration file.

-### Template

-_Templates_ direct Hugo in rendering content into HTML;

-they bridge content and presentation.

-Rules in template files determine which content is published and where,

-and precisely how it will be rendered into HTML files.

-Templates also guide your web site's presentation

-by specifying the CSS styling to use.

-Hugo uses its knowledge of each piece of content

-to seek a template file to use in rendering it.

-If it can't find a template that matches the content, it will zoom out,

-one conceptual level; it will then resume the search from there.

-It will continue to do so, till it finds a matching template,

-or runs out of templates to try.

-Its last resort is your web site's default template,

-which could conceivably be missing. If it finds no suitable template,

-it simply forgoes rendering that piece of content.

-It's important to note that _front-matter_ (see next)

-can influence Hugo's template file selection process.

-### Content

-Content is stored in text files which contain two sections.

-The first is called _front-matter_: this is information about the content.

-The second contains Markdown-formatted text,

-destined for conversion to HTML format.

-#### Front-Matter

-The _front-matter_ is meta-information describing the content.

-Like the web site's configuration file, it can be written in the

-TOML, YAML, or JSON formats.

-Unlike the configuration file, Hugo doesn't use the file's extension

-to determine the format.

-Instead, it looks for markers in the file which signal this.

-TOML is surrounded by "`+++`" and YAML by "`---`", but

-JSON is enclosed in curly braces. I prefer to use TOML.

-You'll need to translate my examples if you prefer YAML or JSON.

-Hugo informs its chosen template files with the front-matter information

-before rendering the content in HTML.

-#### Markdown

-Content is written in Markdown format, which makes it easy to create.

-Hugo runs the content through a Markdown engine to transform it into HTML,

-which it then renders to the output file.

-### Template Kinds

-Here I'll discuss three kinds of Hugo templates:

-_Single_, _List_, and _Partial_.

-All these kinds take one or more pieces of content as input,

-and transform the pieces, based on commands in the template.

-#### Single

-A _Single_ template is used to render one piece of content.

-For example, an article or a post is a single piece of content;

-thus, it uses a Single template.

-#### List

-A _List_ template renders a group of related content items.

-This could be a summary of recent postings,

-or all of the articles in a category.

-List templates can contain multiple groups (or categories).

-The home page template is a special kind of List template.

-This is because Hugo assumes that your home page will act as a portal

-to all of the remaining content on your web site.

-#### Partial

-A _Partial_ template is a template that's incapable of producing a web page,

-by itself. To include a Partial template in your web site,

-another template must call it, using the `partial` command.

-Partial templates are very handy for rolling up common behavior.

-For example, you might want the same banner to appear on all

-of your web site's pages &mdash; so, rather than copy your banner's text

-into multiple content files,

-as well as the other information relevant to your banner

-into multiple template files (both Single and List),

-you can instead create just one content file and one Partial template.

-That way, whenever you decide to change the banner, you can do so

-by editing one file only (or maybe two).

-## Site

-Let's let Hugo help you create your new web site.

-The `hugo new site` command will generate a skeleton &mdash;

-it will give you a basic directory structure, along with

-a usable configuration file:

-```bash

-$ cd /tmp/

-$ hugo new site mySite

-$ cd mySite/

-$ ls -l

-total 8

-drwxr-xr-x  2 {user} {group}   68 {date} archetypes

--rw-r--r--  1 {user} {group}  107 {date} config.toml

-drwxr-xr-x  2 {user} {group}   68 {date} content

-drwxr-xr-x  2 {user} {group}   68 {date} data

-drwxr-xr-x  2 {user} {group}   68 {date} layouts

-drwxr-xr-x  2 {user} {group}   68 {date} static

-drwxr-xr-x  2 {user} {group}   68 {date} themes

-```

-Take a look in the `./content/` and `./themes/` directories to confirm

-they are empty.

-The other directories

-(`./archetypes/`, `./data/`, `./layouts/` and `./static/`)

-are used for customizing a named theme.

-That's a topic for a different tutorial, so please ignore them for now.

-### Render

-Running the `hugo` command with no options will read

-all of the available content and render the HTML files. Also, it will copy

-all the static files (that's everything besides content).

-Since we have an empty web site, Hugo won't be doing much.

-However, generally speaking, Hugo does this very quickly:

-```bash

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-WARN: {date} {source} No theme set

-INFO: {date} {source} /tmp/mySite/static/ is the only static directory available to sync from

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-WARN: {date} {source} Unable to locate layout for homepage: [index.html _default/list.html]

-WARN: {date} {source} "/" is rendered empty

-=============================================================

-Your rendered home page is blank: /index.html is zero-length

- * Did you specify a theme on the command-line or in your

-   "config.toml" file?  (Current theme: "")

-=============================================================

-WARN: {date} {source} Unable to locate layout for 404 page: [404.html]

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-0 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 4 ms

-```

-The "`--verbose`" flag gives extra information that will be helpful

-whenever we are developing a template.

-Every line of the output starting with "INFO:" or "WARN:" is present

-because we used that flag. The lines that start with "WARN:"

-are warning messages. We'll go over them later.

-We can verify that the command worked by looking at the directory again:

-```bash

-$ ls -l

-total 8

-drwxr-xr-x  2 {user} {group}   68 {date} archetypes

--rw-r--r--  1 {user} {group}  107 {date} config.toml

-drwxr-xr-x  2 {user} {group}   68 {date} content

-drwxr-xr-x  2 {user} {group}   68 {date} data

-drwxr-xr-x  2 {user} {group}   68 {date} layouts

-drwxr-xr-x  6 {user} {group}  204 {date} public

-drwxr-xr-x  2 {user} {group}   68 {date} static

-drwxr-xr-x  2 {user} {group}   68 {date} themes

-```

-See that new `./public/` directory?

-Hugo placed all its rendered content there.

-When you're ready to publish your web site, that's the place to start.

-For now, though, let's just confirm we have the files we expect

-for a web site with no content:

-```bash

-$ ls -l public/

-total 16

--rw-r--r--  1 {user} {group}    0 {date} 404.html

--rw-r--r--  1 {user} {group}    0 {date} index.html

--rw-r--r--  1 {user} {group}  511 {date} index.xml

--rw-r--r--  1 {user} {group}  210 {date} sitemap.xml

-```

-Hugo rendered two XML files and some empty HTML files.

-The XML files are used for RSS feeds. Hugo has an opinion about what

-those feeds should contain, so it populated those files.

-Hugo has no opinion on the look or content of your web site,

-so it left those files empty.

-If you look back at the output from the `hugo server` command,

-you'll notice that Hugo said:

-```bash

-0 pages created

-```

-That's because Hugo doesn't count the home page, the 404 error page,

-or the RSS feed files as pages.

-### Serve

-Let's verify you can run the built-in web server &mdash;

-that'll shorten your development cycle, dramatically.

-Start it, by running the `hugo server` command.

-If successful, you'll see output similar to the following:

-```bash

-$ hugo server --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-WARN: {date} {source} No theme set

-INFO: {date} {source} /tmp/mySite/static/ is the only static directory available to sync from

-INFO: {date} {source} syncing static files to /

-WARN: {date} {source} Unable to locate layout for homepage: [index.html _default/list.html]

-WARN: {date} {source} "/" is rendered empty

-=============================================================

-Your rendered home page is blank: /index.html is zero-length

- * Did you specify a theme on the command-line or in your

-   "config.toml" file?  (Current theme: "")

-=============================================================

-WARN: {date} {source} Unable to locate layout for 404 page: [404.html]

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-0 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 3 ms

-Watching for changes in /tmp/mySite/{data,content,layouts,static}

-Serving pages from memory

-Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

-Press Ctrl+C to stop

-```

-Connect to the listed URL (it's on the line that begins with

-`Web Server is available`). If everything's working correctly,

-you should get a page that shows nothing.

-### Warnings

-Let's go back and look at some of those warnings again:

-```bash

-WARN: {date} {source} Unable to locate layout for 404 page: [404.html]

-WARN: {date} {source} Unable to locate layout for homepage: [index.html _default/list.html]

-```

-The 404 warning is easy to explain &mdash; it's because we haven't created

-the template file `layouts/404.html`. Hugo uses this to render an HTML file

-which serves "page not found" errors. However,

-the 404 page is a topic for a separate tutorial.

-Regarding the home page warning: the first layout Hugo looked for was

-`layouts/index.html`. Note that Hugo uses this file for the home page only.

-It's good that Hugo lists the files it seeks, when

-we give it the verbose flag. For the home page, these files are

-`layouts/index.html` and `layouts/_default/list.html`.

-Later, we'll cover some rules which explain these paths

-(including their basenames). For now, just remember that

-Hugo couldn't find a template to use for the home page, and it said so.

-All right! So, now &mdash; after these few steps &mdash; you have a working

-installation, and a web site foundation you can build upon.

-All that's left is to add some content, as well as a theme to display it.

-## Theme

-Hugo doesn't ship with a default theme. However, a large number of themes

-are easily available: for example, at

-[hugoThemes](https://github.com/gohugoio/hugoThemes).

-Also, Hugo comes with a command to generate them.

-We're going to generate a new theme called Zafta.

-The goal of this tutorial is simply to show you how to create

-(in a theme) the minimal files Hugo needs in order to display your content.

-Therefore, the theme will exclude CSS &mdash;

-it'll be functional, not beautiful.

-Every theme has its own opinions on content and layout. For example, this

-Zafta theme prefers the Type "article" over the Types "blog" or "post."

-Strong opinions make for simpler templates, but unconventional opinions

-make themes tougher for other users. So when you develop a theme, you should

-consider the value of adopting the terms used by themes similar to yours.

-### Skeleton

-Let's press Ctrl+C and use the `hugo new theme` command

-to generate the skeleton of a theme. The result is a directory structure

-containing empty files for you to fill out:

-```bash

-$ hugo new theme zafta

-$ find themes -type f | xargs ls -l

--rw-r--r--  1 {user} {group}     8 {date} themes/zafta/archetypes/default.md

--rw-r--r--  1 {user} {group}     0 {date} themes/zafta/layouts/404.html

--rw-r--r--  1 {user} {group}     0 {date} themes/zafta/layouts/_default/list.html

--rw-r--r--  1 {user} {group}     0 {date} themes/zafta/layouts/_default/single.html

--rw-r--r--  1 {user} {group}     0 {date} themes/zafta/layouts/index.html

--rw-r--r--  1 {user} {group}     0 {date} themes/zafta/layouts/partials/footer.html

--rw-r--r--  1 {user} {group}     0 {date} themes/zafta/layouts/partials/header.html

--rw-r--r--  1 {user} {group}  1081 {date} themes/zafta/LICENSE.md

--rw-r--r--  1 {user} {group}   450 {date} themes/zafta/theme.toml

-```

-The skeleton includes templates (files ending in `.html`), a license file,

-a description of your theme (`theme.toml`), and a default archetype file.

-When you're developing a real theme, please remember to fill out files

-`theme.toml` and `LICENSE.md`. They're optional, but if you're going to

-distribute your theme, it tells the world who to praise (or blame).

-It's also important to declare your choice of license, so people will know

-whether (or where) they can use your theme.

-Note that the skeleton theme's template files are empty. Don't worry;

-we'll change that shortly:

-```bash

-$ find themes/zafta -name '*.html' | xargs ls -l

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/404.html

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/_default/list.html

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/_default/single.html

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/index.html

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/partials/footer.html

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/partials/header.html

-```

-### Select

-Now that we've created a theme we can work with, it's a good idea

-to add its name to the configuration file. This is optional, because

-it's possible to add "-t zafta" to all your commands.

-I like to put it in the configuration file because I like

-shorter command lines. If you don't put it in the configuration file,

-or specify it on the command line, sometimes you won't get the template

-you're expecting.

-So, let's edit your configuration file to add the theme name:

-```toml

-$ vi config.toml

-theme = "zafta"

-baseURL = "http://example.org/"

-title = "My New Hugo Site"

-languageCode = "en-us"

-:wq

-```

-### Themed Render

-Now that we have a theme (albeit empty), let's render the web site again:

-```bash

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-WARN: {date} {source} "/" is rendered empty

-=============================================================

-Your rendered home page is blank: /index.html is zero-length

- * Did you specify a theme on the command-line or in your

-   "config.toml" file?  (Current theme: "zafta")

-=============================================================

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-0 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 4 ms

-```

-Did you notice the output is different?

-Two previous warning messages have disappeared, which contained the words

-"Unable to locate layout" for your home page and the 404 page.

-And, a new informational message tells us Hugo is accessing your theme's tree

-(`./themes/zafta/`).

-Let's check the `./public/` directory to see what Hugo rendered:

-```bash

-$ ls -l public/

-total 16

--rw-r--r--  1 {user} {group}    0 {date} 404.html

-drwxr-xr-x  2 {user} {group}   68 {date} css

--rw-r--r--  1 {user} {group}    0 {date} index.html

--rw-r--r--  1 {user} {group}  511 {date} index.xml

-drwxr-xr-x  2 {user} {group}   68 {date} js

--rw-r--r--  1 {user} {group}  210 {date} sitemap.xml

-```

-It's similar to what we had before, without a theme.

-We'd expect so, since all your theme's templates are empty. But notice:

-in `./public/`, Hugo created the `css/` and `js/` directories.

-That's because Hugo found them in your theme's `static/` directory:

-```bash

-$ ls -l themes/zafta/static/

-total 0

-drwxr-xr-x  2 {user} {group}  68 {date} css

-drwxr-xr-x  2 {user} {group}  68 {date} js

-```

-#### Home

-In a Hugo web site, each kind of page is informed (primarily) by just one

-of the many different kinds of templates available;

-yet the home page is special, because it gets its own kind of template,

-and its own template file.

-Hugo uses template file `layouts/index.html` to render the home page's HTML.

-Although Hugo's documentation may state that this file is the home page's

-only required template, Hugo's earlier warning message showed it actually

-looks for two different templates:

-```bash

-WARN: {date} {source} Unable to locate layout for homepage: [index.html _default/list.html]

-```

-#### Empty

-When Hugo generated your theme, it included an empty home page template.

-Whenever Hugo renders your web site, it seeks that same template and uses it

-to render the HTML for the home page. Currently, the template file is empty,

-so the output HTML file is empty, too. Whenever we add rules to that template,

-Hugo will use them in rendering the home page:

-```bash

-$ find * -name index.html | xargs ls -l

--rw-r--r--  1 {user} {group}  0 {date} public/index.html

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/index.html

-```

-As we'll see later, Hugo follows this same pattern for all its templates.

-## Static Files

-Hugo does two things when it renders your web site.

-Besides using templates to transform your content into HTML,

-it also incorporates your static files. Hugo's rule is simple:

-unlike with templates and content, static files aren't transformed.

-Hugo copies them over, exactly as they are.

-Hugo assumes that your web site will use both CSS and JavaScript,

-so it generates some directories in your theme to hold them.

-Remember opinions? Well, Hugo's opinion is that you'll store your CSS

-in directory `static/css/`, and your JavaScript in directory `static/js/`.

-If you don't like that, you can relocate these directories

-or change their names (as long as they remain in your theme's `static/` tree),

-or delete them completely.

-Hugo is nice enough to offer its opinion; yet it still behaves nicely,

-if you disagree:

-```bash

-$ find themes/zafta/* -type d | xargs ls -dl

-drwxr-xr-x  3 {user} {group}  102 {date} themes/zafta/archetypes

-drwxr-xr-x  6 {user} {group}  204 {date} themes/zafta/layouts

-drwxr-xr-x  4 {user} {group}  136 {date} themes/zafta/layouts/_default

-drwxr-xr-x  4 {user} {group}  136 {date} themes/zafta/layouts/partials

-drwxr-xr-x  4 {user} {group}  136 {date} themes/zafta/static

-drwxr-xr-x  2 {user} {group}   68 {date} themes/zafta/static/css

-drwxr-xr-x  2 {user} {group}   68 {date} themes/zafta/static/js

-```

-## Theme Development

-Generally (using any kind of software), working on a theme means

-changing your files, serving your web site again, and then verifying

-the resulting improvements in your browser.

-With Hugo, this way of working is quite easy:

-- First purge the `./public/` tree. (This is optional but useful,

-if you want to start with a clean slate.)

-- Run the built-in Hugo web server.

-- Open your web site in a browser &mdash; and then:

-1. Edit your theme;

-1. Glance at your browser window to see your changes; and

-1. Repeat.

-I'll throw in one more opinion: ***never*** directly edit a theme on a live

-web site. Instead, always develop ***using a copy***. First, make some changes

-to your theme and test them. Afterwards, **when you've got them working,**

-copy them to your web site. For added safety, use a tool like Git to keep

-some revision history of your content, and of your theme. Believe me:

-it's too easy to lose your changes, and your mind!

-Check out the main Hugo web site for information about using Git with Hugo.

-### Purge

-When rendering your web site, Hugo will create new files in the `./public/`

-tree and update existing ones. But it won't delete files that are

-no longer used. For example, files previously rendered with

-(what is now) the wrong basename, or in the wrong directory, will remain.

-Later, if you leave them, they'll likely confuse you.

-Cleaning out your `./public/` files prior to rendering can help.

-When Hugo is running in web server mode (as of version 0.15),

-it doesn't actually write the files. Instead,

-it keeps all the rendered files in memory. So, you can "clean" up

-your files simply by stopping and restarting the web server.

-### Serve

-#### Watch

-Hugo's watch functionality monitors the relevant content, theme and

-(overriding) site trees for filesystem changes,

-and renders your web site again automatically, when changes are detected.

-By default, watch is

-enabled when in web server mode (`hugo server`),

-but disabled for the web site renderer (`hugo`).

-In some use cases,

-Hugo's web site renderer should continue running and watch &mdash; simply

-type `hugo --watch` on the command line.

-Sometimes with Docker containers (and Heroku slugs),

-the site sources may live on a read-only filesystem.

-In that scenario, it makes no sense

-for Hugo's web server to watch for file changes &mdash; so

-use `hugo server --watch=false`.

-#### Reload

-Hugo's built in web server includes

-[LiveReload](/extras/livereload/) functionality. When any page is updated

-in the filesystem, the web browser is told to refresh its currently-open tabs

-from your web site. Usually, this happens faster than you can say,

-"Wow, that's totally amazing!"

-### Workflow

-Again,

-I recommend you use the following commands as the basis for your workflow:

-```bash

-# purge old files. Hugo will recreate the public directory

-$ rm -rf public/

-# run Hugo in watch mode with LiveReload;

-# when you're done, stop the web server

-$ hugo server --verbose

-Press Ctrl+C to stop

-```

-Below is some sample output showing Hugo detecting a change in the home page

-template. (Actually, the change is the edit we're about to do.) Once it's

-rendered again, the web browser automatically reloads the page.

-(As I said above &mdash; it's amazing:)

-```bash

-$ rm -rf public/

-$ hugo server --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /

-Started building site

-WARN: {date} {source} "/" is rendered empty

-=============================================================

-Your rendered home page is blank: /index.html is zero-length

- * Did you specify a theme on the command-line or in your

-   "config.toml" file?  (Current theme: "")

-=============================================================

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-0 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 4 ms

-Watching for changes in /tmp/mySite/{data,content,layouts,static,themes}

-Serving pages from memory

-Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

-Press Ctrl+C to stop

-INFO: {date} {source} Received System Events: ["/tmp/mySite/themes/zafta/layouts/index.html": WRITE]

-Change detected, rebuilding site

-{date}

-Template changed /tmp/mySite/themes/zafta/layouts/index.html

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-0 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 3 ms

-```

-## Home Template

-The home page is one of the few special pages Hugo renders automatically.

-As mentioned earlier, it looks in your theme's `layouts/` tree for one

-of two files:

-1. `index.html`

-1. `_default/list.html`

-We could edit the default template, but a good design principle is to edit

-the most specific template available. That's not a hard-and-fast rule

-(in fact, in this tutorial, we'll break it a few times),

-but it's a good generalization.

-### Static

-Right now, your home page is empty because you've added no content,

-and because its template includes no logic. Let's change that by adding

-some text to your home page template (`layouts/index.html`):

-```html

-$ vi themes/zafta/layouts/index.html

-<!DOCTYPE html>

-<html>

-<body>

-  <p>Hugo says hello!</p>

-</body>

-</html>

-:wq

-```

-Let's press Ctrl+C and render the web site, and then verify the results:

-```html

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-0 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 4 ms

-$ ls -l public/index.html

--rw-r--r--  1 {user} {group}  72 {date} public/index.html

-$ cat public/index.html

-<!DOCTYPE html>

-<html>

-<body>

-  <p>Hugo says hello!</p>

-</body>

-</html>

-```

-### Dynamic

-A ***dynamic*** home page? Because Hugo is a _static web site_ generator,

-the word _dynamic_ seems odd, doesn't it? But this means arranging for your

-home page to reflect the content in your web site automatically,

-each time Hugo renders it.

-To accomplish that, later we'll add an iterator to your home page template.

-## Article

-Now that Hugo is successfully rendering your home page with static content,

-let's add more pages to your web site. We'll display some new articles

-as a list on your home page; and we'll display each article

-on its own page, too.

-Hugo has a command to generate an entry skeleton for new content,

-just as it does for web sites and themes:

-```bash

-$ hugo --verbose new article/First.md

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} attempting to create  article/First.md of article

-INFO: {date} {source} curpath: /tmp/mySite/themes/zafta/archetypes/default.md

-INFO: {date} {source} creating /tmp/mySite/content/article/First.md

-/tmp/mySite/content/article/First.md created

-$ ls -l content/article/

-total 8

--rw-r--r--  1 {user} {group}  61 {date} First.md

-```

-Let's generate a second article, while we're here:

-```bash

-$ hugo --verbose new article/Second.md

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} attempting to create  article/Second.md of article

-INFO: {date} {source} curpath: /tmp/mySite/themes/zafta/archetypes/default.md

-INFO: {date} {source} creating /tmp/mySite/content/article/Second.md

-/tmp/mySite/content/article/Second.md created

-$ ls -l content/article/

-total 16

--rw-r--r--  1 {user} {group}  61 {date} First.md

--rw-r--r--  1 {user} {group}  62 {date} Second.md

-```

-Let's edit both those articles. Be careful to preserve their front-matter,

-but append some text to their bodies, as follows:

-```bash

-$ vi content/article/First.md

-In vel ligula tortor. Aliquam erat volutpat.

-Pellentesque at felis eu quam tincidunt dignissim.

-Nulla facilisi.

-Pellentesque tempus nisi et interdum convallis.

-In quam ante, vulputate at massa et, rutrum

-gravida dui. Phasellus tristique libero at ex.

-:wq

-$ vi content/article/Second.md

-Fusce lacus magna, maximus nec sapien eu,

-porta efficitur neque. Aliquam erat volutpat.

-Vestibulum enim nibh, posuere eu diam nec,

-varius sagittis turpis.

-Praesent quis sapien egestas mauris accumsan

-pulvinar. Ut mattis gravida venenatis. Vivamus

-lobortis risus id nisi rutrum, at iaculis.

-:wq

-```

-So, for example, `./content/article/Second.md` becomes:

-```toml

-$ cat content/article/Second.md

-+++

-date = "2040-01-18T21:08:08-06:00"

-title = "Second"

-+++

-Fusce lacus magna, maximus nec sapien eu,

-porta efficitur neque. Aliquam erat volutpat.

-Vestibulum enim nibh, posuere eu diam nec,

-varius sagittis turpis.

-Praesent quis sapien egestas mauris accumsan

-pulvinar. Ut mattis gravida venenatis. Vivamus

-lobortis risus id nisi rutrum, at iaculis.

-```

-Let's render the web site, and then verify the results:

-```bash

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-INFO: {date} {source} found taxonomies: map[string]string{"tag":"tags", "category":"categories"}

-WARN: {date} {source} "article" is rendered empty

-WARN: {date} {source} "article/Second.html" is rendered empty

-WARN: {date} {source} "article/First.html" is rendered empty

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-2 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 7 ms

-```

-The output says Hugo rendered ("created") two pages.

-Those pages are your new articles:

-```bash

-$ find public -type f -name '*.html' | xargs ls -l

--rw-r--r--  1 {user} {group}   0 {date} public/404.html

--rw-r--r--  1 {user} {group}   0 {date} public/article/First/index.html

--rw-r--r--  1 {user} {group}   0 {date} public/article/index.html

--rw-r--r--  1 {user} {group}   0 {date} public/article/Second/index.html

--rw-r--r--  1 {user} {group}  72 {date} public/index.html

-```

-The new pages are empty, because Hugo rendered their HTML from empty

-template files. The home page doesn't show us the new content, either:

-```html

-$ cat public/index.html

-<!DOCTYPE html>

-<html>

-<body>

-  <p>Hugo says hello!</p>

-</body>

-</html>

-```

-So, we have to edit the templates, in order to pick up the articles.

-### Single & List

-Here again I'll discuss three kinds of Hugo templates. One kind is

-the home page template we edited previously; it's applicable only to

-the home page. Another kind is Single templates, which render output for

-just one content file. The third kind are List templates, which group

-multiple pieces of content before rendering output.

-It's important to note that, generally, List templates

-(except the home page template) are named `list.html`;

-and Single templates are named `single.html`.

-Hugo also has three other kinds of templates:

-Partials, _Content Views_, and _Terms_.

-We'll give examples of some Partial templates; but otherwise,

-we won't go into much detail about these.

-### Home

-You'll want your home page to list the articles you just created.

-So, let's alter its template file (`layouts/index.html`) to show them.

-Hugo runs each template's logic whenever it renders that template's web page

-(of course):

-```html

-$ vi themes/zafta/layouts/index.html

-<!DOCTYPE html>

-<html>

-<body>

-  {{- range first 10 .Data.Pages }}

-    <h4><a href="{{ .Permalink }}">{{ .Title }}</a></h4>

-  {{- end }}

-</body>

-</html>

-:wq

-```

-#### Engine

-Hugo uses the [Go language's template

-engine](https://gohugo.io/templates/go-templates/).

-That engine scans your template files for commands enclosed between

-"{{" and "}}" (these are doubled, curly braces &mdash; affectionately

-known as "mustaches").

-BTW, a hyphen, if placed immediately after an opening mustache, or

-immediately before a closing one, will prevent extraneous newlines.

-(This can make Hugo's output look better, when viewed as text.)

-So, the mustache commands in your newly-altered template are:

-1. &nbsp;`range ...`

-1. &nbsp;`.Permalink`

-1. &nbsp;`.Title`

-1. &nbsp;`end`

-The `range` command is an iterator. We're using it to go through the latest

-ten pages. (Hugo characterizes some of its HTML output files as "pages,"

-but not all &mdash; see above.)

-Looping through the list of data pages will consider each such HTML file

-that Hugo renders (or rather &mdash; to speak more precisely &mdash; each

-such HTML file that Hugo currently calculates it _will_ render).

-It's helpful to remember that Hugo sets some variables, such as `.Data`, quite

-early in its overall processing. Hugo loads information from every content

-file into that variable, and gives all the templates a chance to process that

-variable's contents, before actually rendering any HTML output files.

-`.Permalink` supplies the URL which links to that article's page, and

-`.Title` supplies the value of its "title" variable. Hugo obtains this

-from the front-matter in the article's Markdown file.

-Automatically, the pages are considered in descending order of the generation

-times of their Markdown files (actually, based on the value of the "date"

-variable in their front-matter) so that the latest is first (naturally).

-The `end` command signals the end of the range iterator. The engine

-loops back to the top of the iterator, whenever it finds `end.`

-Everything between `range` and `end` is reevaluated,

-each time the engine goes through the iterator.

-For the present template, this means that the titles of your latest

-ten pages (or however many exist, if that's less) become the

-[textContent](https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent)

-of an equivalent number of copies Hugo makes, of your level-four

-subheading tags (and anchor tags). `.Permalink` enables these to link

-to the actual articles.

-Let's render your web site, and then verify the results:

-```html

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-INFO: {date} {source} found taxonomies: map[string]string{"tag":"tags", "category":"categories"}

-WARN: {date} {source} "article" is rendered empty

-WARN: {date} {source} "article/Second.html" is rendered empty

-WARN: {date} {source} "article/First.html" is rendered empty

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-2 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 7 ms

-$ find public -type f -name '*.html' | xargs ls -l

--rw-r--r--  1 {user} {group}   0 {date} public/404.html

--rw-r--r--  1 {user} {group}   0 {date} public/article/First/index.html

--rw-r--r--  1 {user} {group}   0 {date} public/article/index.html

--rw-r--r--  1 {user} {group}   0 {date} public/article/Second/index.html

--rw-r--r--  1 {user} {group} 232 {date} public/index.html

-$ cat public/index.html

-<!DOCTYPE html>

-<html>

-<body>

-    <h4><a href="http://example.org/article/Second/">Second</a></h4>

-    <h4><a href="http://example.org/article/First/">First</a></h4>

-</body>

-</html>

-```

-### All Done

-Congratulations! Your home page shows the titles of your two articles, along

-with the links to them. The articles themselves are still empty. But,

-let's take a moment to appreciate what we've done, so far!

-Your home page template (`layouts/index.html`) now renders output dynamically.

-Believe it or not, by inserting the range command inside those doubled

-curly braces, you've learned everything you need to know &mdash;

-essentially &mdash; about developing a theme.

-All that's left is understanding which of your templates renders each content

-file, and becoming more familiar with the commands for the template engine.

-## More

-Well &mdash; if things were so simple, this tutorial would be much shorter!

-Some things are still useful to learn, because they'll make creating new

-templates _much_ easier &mdash; so, I'll cover them, now.

-### Base URL

-While developing and testing your theme, did you notice that the links in the

-rendered `./public/index.html` file use the full "baseURL" from your

-`./config.toml` file? That's because those files are intended to be deployed

-to your web server.

-Whenever you test your theme, you start Hugo in web server mode

-(with `hugo server`) and connect to it with your web browser.

-That command is smart enough to replace the "baseURL" with

-`http://localhost:1313` on the fly, so that the links automatically

-work for you.

-That's another reason why we recommend testing with the built-in web server.

-### Content

-The articles you've been working with are in your `./content/article/`

-directory. That means their _Section_ (as far as templates are concerned)

-is "article". Unless we do something unusual in their front-matter, their

-_Type_ is also "article".

-#### Search

-Hugo uses the Section and Type to find a template file for every piece of

-content it renders. Hugo first will seek a template file in subdirectories of

-`layouts/` that match its Section or Type name (i.e., in `layouts/SECTION/`

-or `layouts/TYPE/`). If it can't find a file there, then it will look in the

-`layouts/_default/` directory. Other documentation covers some twists about

-categories and tags, but we won't use those in this tutorial. Therefore,

-we can assume that Hugo will try first `layouts/article/single.html`, then

-`layouts/_default/single.html`.

-Now that we know the search rule, let's see what's available:

-```bash

-$ find themes/zafta -name single.html | xargs ls -l

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/_default/single.html

-```

-If you look back at the articles Hugo has rendered, you can see that

-they were empty. Now we can see that this is because Hugo sought

-`layouts/article/single.html` but couldn't find it, and template

-`layouts/_default/single.html` was empty. Therefore, the rendered article

-file was empty, too.

-So, we could either create a new template, `layouts/article/single.html`,

-or edit the default one.

-#### Default Single

-Since we know of no other content Types, let's start by editing the default

-template file, `layouts/_default/single.html`.

-As we mentioned earlier, you always should edit (or create) the most

-specific template first, in order to avoid accidentally changing how other

-content is displayed. However, we're breaking that rule intentionally,

-just so we can explore how the default is used.

-Remember, any content &mdash; for which we don't create a specific template

-&mdash; will end up using this default template. That can be good or bad.

-Bad, because I know we'll be adding different Types of content, and we'll

-eventually undo some of the changes we've made. Good, because then we'll be

-able to see some results immediately. It's also good to create the default

-template first, because with it, we can start to develop the basic layout

-for the web site.

-As we add more content Types, we'll refactor this file and move its logic

-around. Hugo makes this fairly painless, so we'll accept the cost and proceed.

-Please see Hugo's documentation on template rendering, for all the details on

-determining which template to use. And, as the documentation mentions, if

-your web site is a single-page application (SPA), you can delete all the

-other templates and work with just the default Single one. By itself,

-that fact provides a refreshing amount of joy.

-Let's edit the default template file (`layouts/_default/single.html`):

-```html

-$ vi themes/zafta/layouts/_default/single.html

-<!DOCTYPE html>

-<html>

-<head>

-  <title>{{ .Title }}</title>

-</head>

-<body>

-  <h1>{{ .Title }}</h1>

-  <h6>{{ .Date.Format "Mon, Jan 2, 2006" }}</h6>

-  {{ .Content }}

-  <h4><a href="{{ .Site.BaseURL }}">Home</a></h4>

-</body>

-</html>

-:wq

-```

-#### Verify

-Let's render the web site, and verify the results:

-```bash

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-INFO: {date} {source} found taxonomies: map[string]string{"tag":"tags", "category":"categories"}

-WARN: {date} {source} "article" is rendered empty

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-2 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 7 ms

-$ find public -type f -name '*.html' | xargs ls -l

--rw-r--r--  1 {user} {group}    0 {date} public/404.html

--rw-r--r--  1 {user} {group}  473 {date} public/article/First/index.html

--rw-r--r--  1 {user} {group}    0 {date} public/article/index.html

--rw-r--r--  1 {user} {group}  514 {date} public/article/Second/index.html

--rw-r--r--  1 {user} {group}  232 {date} public/index.html

-```

-Note that although Hugo rendered a file, to list your articles:

-`./public/article/index.html`, the file is empty, because we don't have

-a template for it. (However: see next.) The other HTML files contain your

-content, as we can see below:

-```html

-$ cat public/article/First/index.html

-<!DOCTYPE html>

-<html>

-<head>

-  <title>First</title>

-</head>

-<body>

-  <h1>First</h1>

-  <h6>Wed, Jan 18, 2040</h6>

-  <p>In vel ligula tortor. Aliquam erat volutpat.

-Pellentesque at felis eu quam tincidunt dignissim.

-Nulla facilisi.</p>

-<p>Pellentesque tempus nisi et interdum convallis.

-In quam ante, vulputate at massa et, rutrum

-gravida dui. Phasellus tristique libero at ex.</p>

-  <h4><a href="http://example.org/">Home</a></h4>

-</body>

-</html>

-$ cat public/article/Second/index.html

-<!DOCTYPE html>

-<html>

-<head>

-  <title>Second</title>

-</head>

-<body>

-  <h1>Second</h1>

-  <h6>Wed, Jan 18, 2040</h6>

-  <p>Fusce lacus magna, maximus nec sapien eu,

-porta efficitur neque. Aliquam erat volutpat.

-Vestibulum enim nibh, posuere eu diam nec,

-varius sagittis turpis.</p>

-<p>Praesent quis sapien egestas mauris accumsan

-pulvinar. Ut mattis gravida venenatis. Vivamus

-lobortis risus id nisi rutrum, at iaculis.</p>

-  <h4><a href="http://example.org/">Home</a></h4>

-</body>

-</html>

-```

-Again, notice that your rendered article files have content.

-You can run `hugo server` and use your browser to confirm this.

-You should see your home page, and it should contain the titles of both

-articles. Each title should be a link to its respective article.

-Each article should be displayed fully on its own page. And at the bottom of

-each article, you should see a link which takes you back to your home page.

-### Article List

-Your home page still lists your most recent articles. However &mdash;

-remember, from above, that I mentioned an empty file,

-`./public/article/index.html`?

-Let's make that show a list of ***all*** of your articles

-(not just the latest ten).

-We need to decide which template to edit. Key to this, is that

-individual pages always come from Single templates. On the other hand,

-only List templates are capable of rendering pages which display collections

-(or lists) of other pages.

-Because the new page will show a listing, we should select a List template.

-Let's take a quick look to see which List templates are available already:

-```bash

-$ find themes/zafta -name list.html | xargs ls -l

--rw-r--r--  1 {user} {group}  0 {date} themes/zafta/layouts/_default/list.html

-```

-So, just as before with the single articles, so again now with the list of

-articles, we must decide: whether to edit `layouts/_default/list.html`,

-or to create `layouts/article/list.html`.

-#### Default List

-We still don't have multiple content Types &mdash; so, remaining consistent,

-let's edit the default List template:

-```html

-$ vi themes/zafta/layouts/_default/list.html

-<!DOCTYPE html>

-<html>

-<body>

-  <h1>Articles</h1>

-  {{- range first 10 .Data.Pages }}

-    <h4><a href="{{ .Permalink }}">{{ .Title }}</a></h4>

-  {{- end }}

-  <h4><a href="{{ .Site.BaseURL }}">Home</a></h4>

-</body>

-</html>

-:wq

-```

-Let's render everything again:

-```bash

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-INFO: {date} {source} found taxonomies: map[string]string{"tag":"tags", "category":"categories"}

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-2 pages created

-0 non-page files copied

-0 paginator pages created

-0 categories created

-0 tags created

-in 7 ms

-$ find public -type f -name '*.html' | xargs ls -l

--rw-r--r--  1 {user} {group}    0 {date} public/404.html

--rw-r--r--  1 {user} {group}  473 {date} public/article/First/index.html

--rw-r--r--  1 {user} {group}  327 {date} public/article/index.html

--rw-r--r--  1 {user} {group}  514 {date} public/article/Second/index.html

--rw-r--r--  1 {user} {group}  232 {date} public/index.html

-```

-Now (as you can see), we have a list of articles. To confirm it,

-type `hugo server`; then, in your browser, navigate to `/article/`.

-(Later, we'll link to it.)

-## About

-Let's add an About page, and try to display it at the top level

-(as opposed to the next level down, where we placed your articles).

-### Guide

-Hugo's default goal is to let the directory structure of the `./content/`

-tree guide the location of the HTML it renders to the `./public/` tree.

-Let's check this, by generating an About page at the content's top level:

-```toml

-$ hugo new About.md

-/tmp/mySite/content/About.md created

-$ ls -l content/

-total 8

--rw-r--r--   1 {user} {group}   61 {date} About.md

-drwxr-xr-x   4 {user} {group}  136 {date} article

-$ vi content/About.md

-+++

-date = "2040-01-18T22:01:00-06:00"

-title = "About"

-+++

-Neque porro quisquam est qui dolorem

-ipsum quia dolor sit amet consectetur

-adipisci velit.

-:wq

-```

-### Check

-Let's render your web site, and check the results:

-```html

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-INFO: {date} {source} found taxonomies: map[string]string{"tag":"tags", "category":"categories"}

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-3 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 9 ms

-$ ls -l public/

-total 24

--rw-r--r--  1 {user} {group}     0 {date} 404.html

-drwxr-xr-x  3 {user} {group}   102 {date} About

-drwxr-xr-x  6 {user} {group}   204 {date} article

-drwxr-xr-x  2 {user} {group}    68 {date} css

--rw-r--r--  1 {user} {group}   316 {date} index.html

--rw-r--r--  1 {user} {group}  2221 {date} index.xml

-drwxr-xr-x  2 {user} {group}    68 {date} js

--rw-r--r--  1 {user} {group}   681 {date} sitemap.xml

-$ ls -l public/About/

-total 8

--rw-r--r--  1 {user} {group}  305 {date} index.html

-$ cat public/About/index.html

-<!DOCTYPE html>

-<html>

-<head>

-  <title>About</title>

-</head>

-<body>

-  <h1>About</h1>

-  <h6>Wed, Jan 18, 2040</h6>

-  <p>Neque porro quisquam est qui dolorem

-ipsum quia dolor sit amet consectetur

-adipisci velit.</p>

-  <h4><a href="http://example.org/">Home</a></h4>

-</body>

-</html>

-```

-Oh, well. &mdash; Did you notice that your page wasn't rendered at the

-top level? It was rendered to a subdirectory named `./public/About/`.

-That name came from the basename of your Markdown file `./content/About.md`.

-Interesting &mdash; but, we'll let that go, for now.

-### Home

-One other thing &mdash; let's take a look at your home page:

-```html

-$ cat public/index.html

-<!DOCTYPE html>

-<html>

-<body>

-    <h4><a href="http://example.org/About/">About</a></h4>

-    <h4><a href="http://example.org/article/Second/">Second</a></h4>

-    <h4><a href="http://example.org/article/First/">First</a></h4>

-</body>

-</html>

-```

-Did you notice that the About link is listed with your articles?

-That's not exactly where we want it; so, let's edit your home page template

-(`layouts/index.html`):

-```html

-$ vi themes/zafta/layouts/index.html

-<!DOCTYPE html>

-<html>

-<body>

-  <h2>Articles</h2>

-  {{- range first 10 .Data.Pages -}}

-    {{- if eq .Type "article"}}

-      <h4><a href="{{ .Permalink }}">{{ .Title }}</a></h4>

-    {{- end -}}

-  {{- end }}

-  <h2>Pages</h2>

-  {{- range first 10 .Data.Pages -}}

-    {{- if eq .Type "page" }}

-      <h4><a href="{{ .Permalink }}">{{ .Title }}</a></h4>

-    {{- end -}}

-  {{- end }}

-</body>

-</html>

-:wq

-```

-Let's render your web site, and verify the results:

-```html

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-INFO: {date} {source} found taxonomies: map[string]string{"tag":"tags", "category":"categories"}

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-3 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 9 ms

-$ cat public/index.html

-<!DOCTYPE html>

-<html>

-<body>

-  <h2>Articles</h2>

-      <h4><a href="http://example.org/article/Second/">Second</a></h4>

-      <h4><a href="http://example.org/article/First/">First</a></h4>

-  <h2>Pages</h2>

-      <h4><a href="http://example.org/About/">About</a></h4>

-</body>

-</html>

-```

-Good! This time, your home page has two Sections: "article" and "page", and

-each Section contains the correct set of headings and links.

-## Template Sharing

-If you've been following along on your computer, you might've noticed that

-your home page doesn't show its title in your browser, although both of your

-article pages do. That's because we didn't add your home page's title to its

-template (`layouts/index.html`). That would be easy to do &mdash; but instead,

-let's look at a better option.

-We can put the common information into a shared template.

-These reside in the `layouts/partials/` directory.

-### Header & Footer

-In Hugo (as elsewhere), a Partial is a template that's intended to be used

-within other templates. We're going to create a Partial template that will

-contain a header, for all of your page templates to use. That Partial will

-enable us to maintain the header information in a single place, thus easing

-our maintenance. Let's create both the header (`layouts/partials/header.html`)

-and the footer (`layouts/partials/footer.html`):

-```html

-$ vi themes/zafta/layouts/partials/header.html

-<!DOCTYPE html>

-<html>

-<head>

-  <title>{{ .Title }}</title>

-</head>

-<body>

-:wq

-$ vi themes/zafta/layouts/partials/footer.html

-  <h4><a href="{{ .Site.BaseURL }}">Home</a></h4>

-</body>

-</html>

-:wq

-```

-### Calling

-Any `partial` is called relative to its conventional location

-`layouts/partials/`. So, you pass just the basename, followed by the context

-(the period before the closing mustache). For example:

-```bash

-{{ partial "header.html" . }}

-```

-#### From Home

-Let's change your home page template (`layouts/index.html`)

-in order to use the new header Partial we just created:

-```html

-$ vi themes/zafta/layouts/index.html

-{{ partial "header.html" . }}

-  <h2>Articles</h2>

-  {{- range first 10 .Data.Pages -}}

-    {{- if eq .Type "article"}}

-      <h4><a href="{{ .Permalink }}">{{ .Title }}</a></h4>

-    {{- end -}}

-  {{- end }}

-  <h2>Pages</h2>

-  {{- range first 10 .Data.Pages -}}

-    {{- if eq .Type "page" }}

-      <h4><a href="{{ .Permalink }}">{{ .Title }}</a></h4>

-    {{- end -}}

-  {{- end }}

-</body>

-</html>

-:wq

-```

-Render your web site and verify the results. Now, the title on your home page

-should be "My New Hugo Site". This comes from the "title" variable

-in the `./config.toml` file.

-#### From Default

-Let's also edit the default templates (`layouts/_default/single.html` and

-`layouts/_default/list.html`) to use your new Partials:

-```html

-$ vi themes/zafta/layouts/_default/single.html

-{{ partial "header.html" . }}

-  <h1>{{ .Title }}</h1>

-  <h6>{{ .Date.Format "Mon, Jan 2, 2006" }}</h6>

-  {{ .Content }}

-{{ partial "footer.html" . -}}

-:wq

-$ vi themes/zafta/layouts/_default/list.html

-{{ partial "header.html" . -}}

-  <h1>Articles</h1>

-  {{- range first 10 .Data.Pages }}

-    <h4><a href="{{ .Permalink }}">{{ .Title }}</a></h4>

-  {{- end }}

-{{ partial "footer.html" . -}}

-:wq

-```

-Render your web site and verify the results.

-Now, the title of your About page should reflect the value of the "title"

-variable in its corresponding Markdown file (`./content/About.md`).

-The same should be true for each of your article pages as well (i.e.,

-`./content/article/First.md` and `./content/article/Second.md`).

-### DRY

-Don't Repeat Yourself (also known as DRY) is a desirable goal,

-in any kind of source code development &mdash;

-and Hugo's partials do a fine job to help with that.

-Part of the art of good templates is knowing when to add new ones, and when

-to edit existing ones. While you're still figuring out the art of templates,

-you should accept that you'll do some refactoring &mdash; Hugo makes this

-easy and fast. And it's okay to delay splitting your templates into Partials.

-## Section

-### Date

-Articles commonly display the date they were published

-(or finalized) &mdash; so, here, let's do the same.

-The front-matter of your articles contains a "date" variable

-(as discussed above). Hugo sets this, when it creates each content file.

-Now, sometimes an article requires many days to prepare, so its actual

-publishing date might be later than the front-matter's "date". However, for

-simplicity's sake, let's pretend this is the date we want to display, each time.

-In Hugo, in order to format a variable date (or time),

-we must do it by formatting the Go language [reference

-time](https://golang.org/pkg/time/); for example:

-```bash

-{{ .Date.Format "Mon, Jan 2, 2006" }}

-```

-Now, your articles use the `layouts/_default/single.html` template (see above).

-Because that template includes a date-formatting snippet, they show a

-nice looking date. However, your About page uses the same default template.

-Unfortunately, now it too shows its creation date (which makes no sense)!

-There are a couple of ways to make the date display only for articles.

-We could use an "if" statement, to display the date only when the Type equals

-"article." That is workable, and acceptable for web sites with only a couple

-of content Types. It aligns with the principle of "code for today," too.

-### Template

-Let's assume, though (for didactic purposes), that you've made your web site so

-complex that you feel you must create a new template Type. In Hugo-speak, this

-will be a new Section. It will contain your new, "article" Single template.

-Let's restore your default Single template (`layouts/_default/single.html`)

-to its earlier state (before we forget):

-```html

-$ vi themes/zafta/layouts/_default/single.html

-{{ partial "header.html" . }}

-  <h1>{{ .Title }}</h1>

-  {{ .Content }}

-{{ partial "footer.html" . -}}

-:wq

-```

-Now, let's create your new template. If you remember Hugo's rules,

-the template engine will prefer this version over the default. The first step

-is to create (within your theme) its Section's directory: `layouts/article/`.

-Then, create a Single template (`layouts/article/single.html`) within it:

-```html

-$ mkdir themes/zafta/layouts/article

-$ vi themes/zafta/layouts/article/single.html

-{{ partial "header.html" . }}

-  <h1>{{ .Title }}</h1>

-  <h6>{{ .Date.Format "Mon, Jan 2, 2006" }}</h6>

-  {{ .Content }}

-{{ partial "footer.html" . -}}

-:wq

-```

-Basically, we moved the date logic &mdash; from the default template, to the

-new "article" Section, Single template: `layouts/article/single.html`.

-Let's render your web site and verify the results:

-```html

-$ rm -rf public/

-$ hugo --verbose

-INFO: {date} {source} Using config file: /tmp/mySite/config.toml

-INFO: {date} {source} using a UnionFS for static directory comprised of:

-INFO: {date} {source} Base: /tmp/mySite/themes/zafta/static

-INFO: {date} {source} Overlay: /tmp/mySite/static/

-INFO: {date} {source} syncing static files to /tmp/mySite/public/

-Started building site

-INFO: {date} {source} found taxonomies: map[string]string{"tag":"tags", "category":"categories"}

-WARN: {date} {source} "404.html" is rendered empty

-0 draft content

-0 future content

-0 expired content

-3 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-in 10 ms

-$ cat public/article/First/index.html

-<!DOCTYPE html>

-<html>

-<head>

-  <title>First</title>

-</head>

-<body>

-  <h1>First</h1>

-  <h6>Wed, Jan 18, 2040</h6>

-  <p>In vel ligula tortor. Aliquam erat volutpat.

-Pellentesque at felis eu quam tincidunt dignissim.

-Nulla facilisi.</p>

-<p>Pellentesque tempus nisi et interdum convallis.

-In quam ante, vulputate at massa et, rutrum

-gravida dui. Phasellus tristique libero at ex.</p>

-  <h4><a href="http://example.org/">Home</a></h4>

-</body>

-</html>

-$ cat public/About/index.html

-<!DOCTYPE html>

-<html>

-<head>

-  <title>About</title>

-</head>

-<body>

-  <h1>About</h1>

-  <p>Neque porro quisquam est qui dolorem

-ipsum quia dolor sit amet consectetur

-adipisci velit.</p>

-  <h4><a href="http://example.org/">Home</a></h4>

-</body>

-</html>

-```

-Now, as you can see, your articles show their dates,

-and your About page (sensibly) doesn't.

--- a/content/tutorials/deployment-with-rsync.md

+++ /dev/null

@@ -1,125 +1,0 @@

----

-authors:

-- Adrien Poupin

-date: 2016-11-01

-linktitle: Deployment with rsync

-toc: true

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/creating-a-new-theme

-prev: /tutorials/automated-deployments

-title: Easy deployments with rsync

-weight: 11

----

-# How to build and deploy with hugo and rsync

-We assume here that you have an access to your web host with SSH. In that case, as you will see, deployment is very simple. We also assume that you have a functional static site with hugo installed.

-The spoil is, you can deploy your entire site with a command that looks like this:

-```bash

-hugo && rsync -avz --delete public/ [email protected]:~/www/

-```

-As you will see, we put it in a shell script file, which makes building and deployment as easy as executing `./deploy`.

-## Installing SSH Key

-If it is not done yet, we will make an automated way to SSH to your server. If you have already installed an SSH key, switch to the next section.

-First, install the ssh client. On Debian/Ubuntu/derivates, enter `sudo apt-get install openssh-client`.

-Then generate your ssh key by entering the following commands:

-```

-~$ cd && mkdir .ssh & cd .ssh

-~/.ssh/$ ssh-keygen -t rsa -q -C "For SSH" -f rsa_id

-~/.ssh/$ cat >> config <<EOF

-Host HOST

-     Hostname HOST

-     Port 22

-     User USER

-     IdentityFile ~/.ssh/rsa_id

-EOF

-```

-Don't forget to replace the `HOST` and `USER` values with your own ones. Then copy your ssh public key to the remote server:

-```

-~/.ssh/$ ssh-copy-id -i rsa_id.pub [email protected]

-```

-Now you can easily connect to the remote server:

-```

-~$ ssh user@host

-Enter passphrase for key '/home/mylogin/.ssh/rsa_id':

-```

-And you've done it!

-## Shell script

-We will put the first command in a script at the root of your hugo tree:

-```

-~/websites/topologix.fr$ editor deploy

-```

-Here you put the following content. Replace the `USER`, `HOST` and `DIR` values with your own.

-```

-#!/bin/sh

-USER=my-user

-HOST=my-server.com

-DIR=my/directory/to/topologix.fr/   # might sometimes be empty!

-hugo && rsync -avz --delete public/ ${USER}@${HOST}:~/${DIR}

-exit 0

-```

-Note that `DIR` is the relative path from the remote user's home. If you have to specify a full path (for instance `/var/www/mysite/`) you must change `~/${DIR}` to `${DIR}` inside the command line. For most cases you should not have to.

-Save and close, and make the `deploy` file executable:

-```

-~/websites/topologix.fr$ chmod +x deploy

-```

-Now you only have to enter the following command to deploy and update your website:

-```

-~/websites/topologix.fr$ ./deploy

-Started building sites ...

-Built site for language en:

-0 draft content

-0 future content

-0 expired content

-5 pages created

-0 non-page files copied

-0 paginator pages created

-0 tags created

-0 categories created

-total in 56 ms

-sending incremental file list

-404.html

-index.html

-index.xml

-sitemap.xml

-cours-versailles/index.html

-exercices/index.html

-exercices/index.xml

-exercices/barycentre-et-carres-des-distances/index.html

-post/

-post/index.html

-sujets/index.html

-sujets/index.xml

-sujets/2016-09_supelec-jp/index.html

-tarifs-contact/index.html

-sent 9,550 bytes  received 1,708 bytes  7,505.33 bytes/sec

-total size is 966,557  speedup is 85.86

-```

-And it's done!

--- a/content/tutorials/github-pages-blog.md

+++ /dev/null

@@ -1,197 +1,0 @@

----

-aliases:

-    - /tutorials/github_pages_blog/

-author: Spencer Lyon, Gunnar Morling

-lastmod: 2017-01-11

-date: 2014-03-21

-linktitle: Hosting on GitHub

-toc: true

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/how-to-contribute-to-hugo/

-prev: /tutorials/creating-a-new-theme

-title: Hosting on GitHub Pages

-weight: 10

----

-*This tutorial was contributed by [Spencer Lyon](http://spencerlyon.com/) (Personal/Organization Pages) and [Gunnar Morling](https://github.com/gunnarmorling/).*

-## Introduction

-This tutorial describes how to deploy your Hugo based website to [GitHub pages](https://pages.github.com/).

-The following sections are based on the assumption that you are working with a "Project Pages Site".

-This means that you'll have your Hugo sources and the generated HTML output within a single repository

-(in contrast, with a "User/Organization Pages Site", you'd have one repo for the sources and another repo for the published HTML files;

-refer to the [GitHub Pages docs](https://help.github.com/articles/user-organization-and-project-pages/) to learn more).

-## Deployment via _/docs_ folder on master branch

-[As described](https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/#publishing-your-github-pages-site-from-a-docs-folder-on-your-master-branch) in the GitHub Pages docs, you can deploy from a folder called _docs_ on your master branch.

-This requires to change the Hugo publish directory in the site config (e.g. _config.toml_):

-    publishDir = "docs"

-After running `hugo`, push your master branch to the remote repo and choose the _docs_ folder as the website source of your repo

-(in your GitHub project, go to "Settings " -> "GitHub Pages" -> "Source" -> Select "master branch /docs folder").

-If that option isn't enabled, you likely haven't pushed your _docs_ folder yet.

-This is the simplest approach but requires the usage of a non-standard publish directory

-(GitHub Pages cannot be configured to use another directory than _docs_ currently).

-Also the presence of generated files on the master branch may not be to everyone's taste.

-## Deployment via gh-pages branch

-Alternatively, you can deploy site through a separate branch called "gh_pages".

-That approach is a bit more complex but has some advantages:

-* It keeps sources and generated HTML in two different branches

-* It uses the default _public_ folder

-* It keeps the histories of source branch and gh-pages branch fully separated from each other

-### Preparations

-These steps only need to be done once (replace "upstream" with the name of your remote, e.g. "origin"):

-First, add the _public_ folder to _.gitignore_ so it's ignored on the master branch:

-    echo "public" >> .gitignore

-Then initialize the gh-pages branch as an empty [orphan branch](https://git-scm.com/docs/git-checkout/#git-checkout---orphanltnewbranchgt):

-    git checkout --orphan gh-pages

-    git reset --hard

-    git commit --allow-empty -m "Initializing gh-pages branch"

-    git push upstream gh-pages

-    git checkout master

-### Building and Deployment

-Now check out the gh-pages branch into your _public_ folder, using git's [worktree feature](https://git-scm.com/docs/git-worktree)

-(essentially, it allows you to have multiple branches of the same local repo to be checked out in different directories):

-    rm -rf public

-    git worktree add -B gh-pages public upstream/gh-pages

-Regenerate the site using Hugo and commit the generated files on the gh-pages branch:

-    hugo

-    cd public && git add --all && git commit -m "Publishing to gh-pages" && cd ..

-If the changes in your local gh-pages branch look alright, push them to the remote repo:

-    git push upstream gh-pages

-After a short while you'll see the updated contents on your GitHub Pages site.

-### Putting it into a script

-To automate these steps, you can create a script _scripts/publish_to_ghpages.sh_ with the following contents:

-```

-#!/bin/sh

-DIR=$(dirname "$0")

-cd $DIR/..

-if [[ $(git status -s) ]]

-then

-    echo "The working directory is dirty. Please commit any pending changes."

-    exit 1;

-fi

-echo "Deleting old publication"

-rm -rf public

-mkdir public

-git worktree prune

-rm -rf .git/worktrees/public/

-echo "Checking out gh-pages branch into public"

-git worktree add -B gh-pages public upstream/gh-pages

-echo "Removing existing files"

-rm -rf public/*

-echo "Generating site"

-hugo

-echo "Updating gh-pages branch"

-cd public && git add --all && git commit -m "Publishing to gh-pages (publish.sh)"

-```

-This will abort if there are pending changes in the working directory and also makes sure that all previously existing output files are removed.

-Adjust the script to taste, e.g. to include the final push to the remote repository if you don't need to take a look at the gh-pages branch before pushing. Or adding `echo yourdomainname.com >> CNAME` if you set up for your gh-pages to use customize domain.

-## Deployment with Git 2.4 and earlier

-The `worktree` command was only introduced in Git 2.5.

-If you are still on an earlier version and cannot update, you can simply clone your local repo into the _public_ directory, only keeping the gh-pages branch:

-    git clone .git --branch gh-pages public

-Having re-generated the site, you'd push back the gh-pages branch to your primary local repo:

-    cd public && git add --all && git commit -m "Publishing to gh-pages" && git push origin gh-pages

-The other steps are the same as with the worktree approach.

-## Hosting Personal/Organization Pages

-As mentioned [in this GitHub's article](https://help.github.com/articles/user-organization-and-project-pages/), besides project pages, you may also want to host a user/organization page. Here are the key differences:

-> - You must use the `username.github.io` naming scheme.

-> - Content from the `master` branch will be used to build and publish your GitHub Pages site.

-It becomes much simpler in that case: we'll create two separate repos, one for Hugo's content, and a git submodule with the `public` folder's content in it.

-Step by step:

-1. Create on GitHub `<your-project>-hugo` repository (it will host Hugo's content)

-2. Create on GitHub `<username>.github.io` repository (it will host the `public` folder: the static website)

-3. `git clone <<your-project>-hugo-url> && cd <your-project>-hugo`

-4. Make your website work locally (`hugo server -t <yourtheme>`)

-5. Once you are happy with the results, <kbd>Ctrl</kbd>+<kbd>C</kbd> (kill server) and `rm -rf public` (don't worry, it can always be regenerated with `hugo -t <yourtheme>`)

-6. `git submodule add -b master [email protected]:<username>/<username>.github.io.git public`

-7. Almost done: add a `deploy.sh` script to help you (and make it executable: `chmod +x deploy.sh`):

-```

-#!/bin/bash

-echo -e "\033[0;32mDeploying updates to GitHub...\033[0m"

-# Build the project.

-hugo # if using a theme, replace by `hugo -t <yourtheme>`

-# Go To Public folder

-cd public

-# Add changes to git.

-git add -A

-# Commit changes.

-msg="rebuilding site `date`"

-if [ $# -eq 1 ]

-  then msg="$1"

-fi

-git commit -m "$msg"

-# Push source and build repos.

-git push origin master

-# Come Back

-cd ..

-```

-7. `./deploy.sh "Your optional commit message"` to send changes to `<username>.github.io` (careful, you may also want to commit changes on the `<your-project>-hugo` repo).

-That's it! Your personal page is running at [http://username.github.io/](http://username.github.io/) (after up to 10 minutes delay).

-## Using a custom domain

-If you'd like to use a custom domain for your GitHub Pages site, create a file _static/CNAME_ with the domain name as its sole contents.

-This will put the CNAME file to the root of the published site as required by GitHub Pages.

-Refer to the [official documentation](https://help.github.com/articles/using-a-custom-domain-with-github-pages/) for further information.

-## Conclusion

-Hopefully this tutorial helped you to get your website off its feet and out into the open! If you have any further questions, feel free to contact the community through the [discussion forum](/community/mailing-list/).

--- a/content/tutorials/hosting-on-bitbucket.md

+++ /dev/null

@@ -1,138 +1,0 @@

----

-authors:

-- Jason Gowans

-lastmod: 2017-02-04

-date: 2017-02-04

-linktitle: Hosting on Bitbucket

-toc: true

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/github-pages-blog

-prev: /tutorials/creating-a-new-theme

-title: Continuous deployment with Bitbucket & Aerobatic

-weight: 10

----

-# Continuous deployment with Bitbucket & Aerobatic

-## Introduction

-In this tutorial, we will use [Bitbucket](https://bitbucket.org/) and [Aerobatic](https://www.aerobatic.com) to build, deploy, and host a Hugo site. Aerobatic is a static hosting service that integrates with Bitbucket and provides a free hosting tier.

-It is assumed that you know how to use git for version control and have a Bitbucket account.

-## Install Aerobatic CLI

-If you haven't previously used Aerobatic, you'll first need to install the Command Line Interface (CLI) and create an account. For a list of all commands available, see the [Aerobatic CLI](https://www.aerobatic.com/docs/cli/) docs.

-```bash

-npm install aerobatic-cli -g

-aero register

-```

-## Create and Deploy Site

-```bash

-hugo new site my-new-hugo-site

-cd my-new-hugo-site

-cd themes; git clone https://github.com/eliasson/liquorice

-hugo -t liquorice

-aero create                                           # create the Aerobatic site

-hugo --baseURL https://my-new-hugo-site.aerobatic.io  # build the site overriding baseURL

-aero deploy -d public                                 # deploy output to Aerobatic

-Version v1 deployment complete.

-View now at https://hugo-docs-test.aerobatic.io

-```

-In the rendered page response, the `https://__baseurl__` will be replaced with your actual site url (in this example, `https://my-new-hugo-site.aerobatic.io`). You can always rename your Aerobatic website with the `aero rename` command.

-## Push Hugo site to Bitbucket

-We will now create a git repository and then push our code to Bitbucket. In Bitbucket, create a repository.

-![][1]

-[1]: /img/tutorials/hosting-on-bitbucket/bitbucket-create-repo.png

-```bash

-# initialize new git repository

-git init

-# set up our .gitignore file

-echo -e "/public \n/themes \naero-deploy.tar.gz" >> .gitignore

-# commit and push code to master branch

-git add --all

-git commit -m "Initial commit"

-git remote add origin [email protected]:YourUsername/my-new-hugo-site.git

-git push -u origin master

-```

-## Continuous Deployment With Bitbucket Pipelines

-In the example above, we pushed the compiled assets in the `/public` folder to Aerobatic. In the following example, we use Bitbucket Pipelines to continuously create and deploy the compiled assets to Aerobatic.

-### Step 1: Configure Bitbucket Pipelines

-In your Hugo website's Bitbucket repo;

-1. Click the Pipelines link in the left nav menu of your Bitbucket repository.

-2. Click the Enable Pipelines button.

-3. On the next screen, leave the default template and click Next.

-4. In the editor, paste in the yaml contents below and click Commit.

-```bash

-image: beevelop/nodejs-python

-pipelines:

-  branches:

-    master:

-      - step:

-          script:

-            - apt-get update -y && apt-get install wget

-            - apt-get -y install git

-            - wget https://github.com/gohugoio/hugo/releases/download/v0.18/hugo_0.18-64bit.deb

-            - dpkg -i hugo*.deb

-            - git clone https://github.com/eliasson/liquorice themes/liquorice

-            - hugo --theme=liquorice --baseURL https://__baseurl__ --buildDrafts

-            - npm install -g aerobatic-cli

-            - aero deploy

-```

-### Step 2: Create `AEROBATIC_API_KEY` environment variable.

-This step only needs to be done once per account. From the command line;

-```bash

-aero apikey

-```

-1. Navigate to the Bitbucket account settings for the account that the website repo belongs to.

-2. Scroll down to the bottom of the left nav and click the Environment variables link in the PIPELINES section.

-3. Create a new environment variable called AEROBATIC_API_KEY with the value you got by running the `aero apikey` command. Be sure to click the Secured checkbox.

-## Step 3: Edit and Commit Code

-```bash

-hugo new post/good-to-great.md

-hugo server --buildDrafts -t liquorice #Check that all looks good

-# commit and push code to master branch

-git add --all

-git commit -m "New blog post"

-git push -u origin master

-```

-Your code will be committed to Bitbucket, Bitbucket Pipelines will run your build, and a new version of your site will be deployed to Aerobatic.

-At this point, you can now create and edit blog posts directly in the Bitbucket UI.

-![][2]

-[2]: /img/tutorials/hosting-on-bitbucket/bitbucket-blog-post.png

-## Suggested next steps

-The code for this example can be found in this Bitbucket [repository](https://bitbucket.org/dundonian/hugo-docs-test). Aerobatic also provides a number of additional [plugins](https://www.aerobatic.com/docs) such as auth and redirects that you can use for your Hugo site.

--- a/content/tutorials/hosting-on-gitlab.md

+++ /dev/null

@@ -1,68 +1,0 @@

----

-author: Riku-Pekka Silvola

-lastmod: 2016-06-23

-date: 2016-06-23

-linktitle: Hosting on GitLab

-toc: true

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/how-to-contribute-to-hugo/

-prev: /tutorials/github-pages-blog

-title: Hosting on GitLab Pages

-weight: 10

----

-# Continuous deployment with GitLab

-## Introduction

-In this tutorial, we will use [GitLab](https://gitlab.com/) to build, deploy, and host a [Hugo](https://gohugo.io/) site. With Hugo and GitLab, this is incredibly easy.

-It is assumed that you know how to use git for version control and have a GitLab account, and that you have gone through the [quickstart guide]({{< relref "overview/quickstart.md" >}}) and already have a Hugo site on your local machine.

-## Create .gitlab-ci.yml

-```bash

-cd your-hugo-site

-```

-In the root directory of your Hugo site, create a `.gitlab-ci.yml` file. The `.gitlab-ci.yml` configures the GitLab CI on how to build your page. Simply add the content below.

-```yml

-image: publysher/hugo

-pages:

-  script:

-  - hugo

-  artifacts:

-    paths:

-    - public

-  only:

-  - master

-```

-## Push Hugo site to GitLab

-Next up, create a new repository on GitLab. It is *not* necessary to set the repository public. In addition, you might want to add `/public` to your .gitignore file, as there is no need to push compiled assets to GitLab.

-```bash

-# initialize new git repository

-git init

-# add /public directory to our .gitignore file

-echo "/public" >> .gitignore

-# commit and push code to master branch

-git add .

-git commit -m "Initial commit"

-git remote add origin https://gitlab.com/YourUsername/your-hugo-site.git

-git push -u origin master

-```

-## Wait for your page to be built

-That's it! You can now follow the CI agent building your page at https://gitlab.com/YourUsername/your-hugo-site/pipelines.

-After the build has passed, your new website is available at https://YourUsername.gitlab.io/your-hugo-site/

-## Suggested next steps

-GitLab supports using custom CNAME's and TLS certificates, but this is out of the scope of this tutorial. For more details on GitLab Pages, see [https://about.gitlab.com/2016/04/07/gitlab-pages-setup/](https://about.gitlab.com/2016/04/07/gitlab-pages-setup/)

--- a/content/tutorials/how-to-contribute-to-hugo.md

+++ /dev/null

@@ -1,352 +1,0 @@

----

-date: 2016-04-03T13:21:56+02:00

-linktitle: How to contribute

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/installing-on-mac/

-prev: /tutorials/github-pages-blog/

-title: How to contribute to Hugo

-weight: 10

----

-## Introduction

-Hugo is an open source project and lives by the work of its [contributors](https://github.com/gohugoio/hugo/graphs/contributors). Help to make Hugo even more awesome. There are plenty of [open issues](https://github.com/gohugoio/hugo/issues) on GitHub and we need your help.

-This tutorial is intended for people who are new to Git, GitHub or open source projects in general. It should help to overcome most of the barriers that newcomers encounter. It describes step by step what you need to do.

-For any kind of questions please take a look at our [forum](https://discourse.gohugo.io/).

-## Install Go

-The installation of Go should take only a few minutes. [Download](https://golang.org/dl/) the latest stable version of Go and follow the official [installation guide](https://golang.org/doc/install).

-Let's confirm the correct installation of Go. Open a terminal (or command line under Windows). Execute `go version` and you should see the version number of your Go installation. Next, make sure that you setup the `GOPATH` as described in the installation guide.

-You can print the `GOPATH` with `echo $GOPATH`. You should see a non-empty string containing a valid path to your Go workspace.

-### GVM as alternative

-More experienced users can use the [Go Version Manager](https://github.com/moovweb/gvm), or GVM for short. It allows you to switch between different Go versions *on the same machine*. Probably you don't need this feature. But you can easily upgrade to a new released Go version with a few commands.

-This is handy if you follow the developement of Hugo over a longer period of time. Future versions of Hugo will usually be compiled with the latest version of Go. Sooner or later you have to upgrade if you want to keep up.

-## Create an account on GitHub

-If you're going to contribute code, you'll need to have an account on GitHub. Go to [www.github.com/join](https://github.com/join) and set up a personal account.

-## Install Git on your system

-You will need to install Git. This tutorial assumes basic knowledge about Git. Refer to this excellent [Git book](https://git-scm.com/) if you are not sure where to begin. The used terminology will be explained with annotations.

-Git is a [version control system](https://en.wikipedia.org/wiki/Version_control) to track the changes of source code. Hugo depends on smaller third-party packages that are used to extend the functionality. We use them because we don't want to reinvent the wheel.

-Go ships with a sub-command called `get` that will download these packages for us when we setup our working environment. The source code of the packages is tracked with Git. `get` will interact with the Git servers of the package hosters in order to fetch all dependencies.

-Move back to the terminal and check if Git is already installed. Type in `git version` and press enter. You can skip the rest of this section if the command returned a version number. Otherwise [download](https://git-scm.com/downloads) the lastest version of Git and follow this [installation guide](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).

-Finally, check again with `git version` if Git was installed successfully.

-### Git Graphical Front Ends

-There are several [GUI clients](https://git-scm.com/downloads/guis) that help you to operate Git. Not all are available for all operating systems and maybe differ in their usage. Thus, so we will use the command line since the commands are everywhere the same.

-### Install Hub on your system (optional)

-Hub is a great tool for working with GitHub. The main site for it is [www.hub.github.com](https://hub.github.com/). Feel free to install this little Git wrapper.

-On a Mac, install Hub using brew:

-```sh

-brew install hub

-```

-Create an alias (in Bash) so that typing git actually runs Hub:

-```sh

-echo "alias git='hub'" >> ~/.bash_profile

-```

-Confirm the installation:

-```sh

-git version 2.6.3

-hub version 2.2.2

-```

-## Set up your working copy

-The working copy is set up locally on your computer. It's what you'll edit, compile, and end up pushing back to GitHub. The main steps are cloning the repository and creating your fork as a remote.

-### Vendored Dependencies

-Hugo uses [govendor](https://github.com/kardianos/govendor) to vendor dependencies, but we don't commit the vendored packages themselves to the Hugo git repository.

-Therefore, a simple `go get` is not supported since `go get` is not vendor-aware.

-You **must use govendor** to fetch and manage Hugo's dependencies.

-```sh

-go get -v -u github.com/kardianos/govendor

-```

-### Fetch the Sources from GitHub

-We assume that you've set up your `GOPATH` (see the section above if you're unsure about this). You should now copy the Hugo repository down to your computer. You'll hear this called "clone the repo". GitHub's [help pages](https://help.github.com/articles/cloning-a-repository/) give us a short explanation:

-> When you create a repository on GitHub, it exists as a remote repository. You can create a local clone of your repository on your computer and sync between the two locations.

-We're going to clone the [master Hugo repository](https://github.com/gohugoio/hugo). That seems counter-intuitive, since you won't have commit rights on it. But it's required for the Go workflow. You'll work on a copy of the master and push your changes to your own repository on GitHub.

-So, let's clone that master repository with govendor:

-```sh

-govendor get -v github.com/gohugoio/hugo

-```

-### Fork the repository

-If you're not familiar with this term, GitHub's [help pages](https://help.github.com/articles/fork-a-repo/) provide again a simple explanation:

-> A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.

-#### Fork by hand

-Open the [Hugo repository](https://github.com/gohugoio/hugo) on GitHub and click on the "Fork" button in the top right.

-![Fork button](/img/tutorials/how-to-contribute-to-hugo/forking-a-repository.png)

-Now open your fork repository on GitHub and copy the remote url of your fork. You can choose between HTTPS and SSH as protocol that Git should use for the following operations. HTTPS works always [if you're not sure](https://help.github.com/articles/which-remote-url-should-i-use/).

-![Copy remote url](/img/tutorials/how-to-contribute-to-hugo/copy-remote-url.png)

-Switch back to the terminal and move into the directory of the cloned master repository from the last step.

-```sh

-cd $GOPATH/src/github.com/gohugoio/hugo

-```

-Now Git needs to know that our fork exists by adding the copied remote url:

-```sh

-git remote add <YOUR-GITHUB-USERNAME> <COPIED REMOTE-URL>

-```

-#### Fork with Hub

-Alternatively, you can use the Git wrapper Hub. Hub makes forking a repository easy:

-```sh

-git fork

-```

-That command will log in to GitHub using your account, create a fork of the repository that you're currently working in, and add it as a remote to your working copy.

-#### Trust, but verify

-Let's check if everything went right by listing all known remotes:

-```sh

-git remote -v

-```

-The output should look similar:

-```sh

-digitalcraftsman	[email protected]:digitalcraftsman/hugo.git (fetch)

-digitalcraftsman	[email protected]:digitalcraftsman/hugo.git (push)

-origin	https://github.com/gohugoio/hugo (fetch)

-origin	https://github.com/gohugoio/hugo (push)

-```

-## The contribution workflow

-### Create a new branch

-You should never develop against the "master" branch. The development team will not accept a pull request against that branch. Instead, create a descriptive named branch and work on it.

-First, you should always pull the latest changes from the master repository:

-```sh

-git checkout master

-git pull

-```

-Now we can create a new branch for your additions:

-```sh

-git checkout -b <BRANCH-NAME>

-```

-You can check on which branch your are with `git branch`. You should see a list of all local branches. The current branch is indicated with a little asterisk.

-### Contributing to the documentation

-Perhaps you want to start contributing to the docs. Then you can ignore most of the following steps. You can find the documentation within the cloned repository in the subfolder `docs`. Change the directory with `cd docs`. Install the [latest release]({{< relref "overview/installing.md" >}}). Or read on and build Hugo from source.

-You can start Hugo's built-in server via `hugo server`. Browse the documentation by entering [http://localhost:1313](http://localhost:1313) in the address bar of your browser. The server automatically updates the page if you change its content.

-### Building Hugo

-While making changes in the codebase it's a good idea to build the binary to test them:

-```sh

-make hugo

-```

-### Testing

-Sometimes changes on the codebase can cause unintended side effects. Or they don't work as expected. Most functions have their own test cases. You can find them in files ending with `_test.go`.

-```sh

-make check

-```

-### Formatting

-The Go code styleguide maybe is opinionated but it ensures that the codebase looks the same, regardless who wrote the code. Go comes with its own formatting tool. Let's apply the styleguide to our additions:

-```sh

-govendor fmt +local

-```

-Once you made your additions commit your changes. Make sure that you follow our [code contribution guidelines](https://github.com/gohugoio/hugo/blob/master/CONTRIBUTING.md):

-```sh

-# Add all changed files

-git add --all

-git commit --message "YOUR COMMIT MESSAGE"

-```

-The commit message should describe what the commit does (e.g. add feature XYZ), not how it is done.

-### Modify commits

-You noticed some commit messages don't fulfill the code contribution guidelines or you just forget something to add some files? No problem. Git provides the necessary tools to fix such problems. The next two methods cover all common cases.

-If you are unsure what a command does leave the commit as it is. We can fix your commits later in the pull request.

-#### Modifying the last commit

-Let's say you want to modify the last commit message. Run the following command and replace the current message:

-```sh

-git commit --amend -m"YOUR NEW COMMIT MESSAGE"

-```

-Take a look at the commit log to see the change:

-```sh

-git log

-# Exit with q

-```

-After making the last commit you may forgot something. There is no need to create a new commit. Just add the latest changes and merge them into the intended commit:

-```sh

-git add --all

-git commit --amend

-```

-#### Modifying multiple commits

-This is a bit more advanced. Git allows you to [rebase](https://git-scm.com/docs/git-rebase) commits interactively. In other words: it allows you to rewrite the commit history. **Take care of your actions. They can cause unintended changes. Skip this section if you're not sure!**

-```sh

-git rebase --interactive @~6

-```

-The `6` at the end of the command represents the number of commits that should be modified. An editor should open and present a list of last six commit messages:

-```sh

-pick 80d02a1 tpl: Add hasPrefix to the template funcs' "smoke test"

-pick aaee038 tpl: Sort the smoke tests

-pick f0dbf2c tpl: Add the other test case for hasPrefix

-pick 911c35b Add "How to contribute to Hugo" tutorial

-pick 33c8973 Begin workflow

-pick 3502f2e Refactoring and typo fixes

-```

-In the case above we should merge the last to commits in the commit of this tutorial (`Add "How to contribute to Hugo" tutorial`). You can "squash" commits, i.e. merge two or more commits into a single one.

-All operations are written before the commit message. Replace "pick" with an operation. In this case `squash` or `s` for short:

-```sh

-pick 80d02a1 tpl: Add hasPrefix to the template funcs' "smoke test"

-pick aaee038 tpl: Sort the smoke tests

-pick f0dbf2c tpl: Add the other test case for hasPrefix

-pick 911c35b Add "How to contribute to Hugo" tutorial

-squash 33c8973 Begin workflow

-squash 3502f2e Refactoring and typo fixes

-```

-We also want to rewrite the commits message of the third last commit. We forgot "docs:" as prefix according to the code contribution guidelines. The operation to rewrite a commit is called `reword` (or `r` as shortcut).

-You should end up with a similar setup:

-```sh

-pick 80d02a1 tpl: Add hasPrefix to the template funcs' "smoke test"

-pick aaee038 tpl: Sort the smoke tests

-pick f0dbf2c tpl: Add the other test case for hasPrefix

-reword 911c35b Add "How to contribute to Hugo" tutorial

-squash 33c8973 Begin workflow

-squash 3502f2e Refactoring and typo fixes

-```

-Close the editor. It should open again with a new tab. A text is instructing you to define a new commit message for the last two commits that should be merged (a.k.a. squashed). Save the file (<kbd>CTRL</kbd>+<kbd>S</kbd>) and close the editor again.

-A last time a new tab opens. Enter a new commit message and save again. Your terminal should contain a status message. Hopefully this one:

-```sh

-Successfully rebased and updated refs/heads/<BRANCHNAME>.

-```

-Check the commit log if everything looks as expected. Should an error occur you can abort this rebase with `git rebase --abort`.

-### Push commits

-To push our commits to the fork on GitHub we need to specify a destination. A destination is defined by the remote and a branch name. Earlier, the defined that the remote url of our fork is the same as our GitHub handle, in my case `digitalcraftsman`. The branch should have the same as our local one. This makes it easy to identify corresponding branches.

-```sh

-git push --set-upstream <YOUR-GITHUB-USERNAME> <BRANCHNAME>

-```

-Now Git knows the destination. Next time when you to push commits you just need to enter `git push`.

-If you modified your commit history in the last step GitHub will reject your try to push. This is a safety-feature because the commit history isn't the same and new commits can't be appended as usual. You can enforce this push explicitly with `git push --force`.

-## Open a pull request

-We made a lot of progress. Good work. In this step we finally open a pull request to submit our additions. Open the [Hugo master repository](https://github.com/gohugoio/hugo/) on GitHub in your browser.

-You should find a green button labeled with "New pull request". But GitHub is clever and probably suggests you a pull request like in the beige box below:

-<img src="/img/tutorials/how-to-contribute-to-hugo/open-pull-request.png" alt="Open a pull request">

-The new page summaries the most important information of your pull request. Scroll down and you find the additions of all your commits. Make sure everything looks as expected and click on "Create pull request".

-### Accept the contributor license agreement

-Last but not least you should accept the contributor license agreement (CLA). A new comment should be added automatically to your pull request. Click on the yellow badge, accept the agreement and authenticate yourself with your GitHub account. It just takes a few clicks and only needs to be done once.

-<img src="/img/tutorials/how-to-contribute-to-hugo/accept-cla.png" alt="Accept the CLA">

-### Automatic builds

-We use the [Travis CI loop](https://travis-ci.org/gohugoio/hugo) (Linux and OS&nbsp;X) and [AppVeyor](https://ci.appveyor.com/project/gohugoio/hugo/branch/master) (Windows) to compile Hugo with your additions. This should ensure that everything works as expected before merging your pull request. This in most cases only relevant if you made changes to the codebase of Hugo.

-<img src="/img/tutorials/how-to-contribute-to-hugo/ci-errors.png" alt="Automic builds and their status">

-Above you can see that Travis wasn't able to compile the changes in this pull request. Click on "Details" and try to investigate why the build failed. But it doesn't have to be your fault. Mostly, the `master` branch that we used as foundation for your pull request should build without problems.

-If you have questions leave a comment in the pull request. We are willing to assist you.

-## Where to start?

-Thank you for reading this tutorial. Hopefully, we see you again on GitHub. There are plenty of [open issues](https://github.com/gohugoio/hugo/issues) on GitHub. Feel free to open an issue if you think you found a bug or you have a new idea to improve Hugo. We are happy to hear from you.

--- a/content/tutorials/installing-on-mac.md

+++ /dev/null

@@ -1,240 +1,0 @@

----

-author: "Michael Henderson"

-lastmod: 2016-08-10

-date: 2015-02-22

-linktitle: Installing on Mac

-toc: true

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/installing-on-windows

-prev: /tutorials/how-to-contribute-to-hugo/

-title: Installing on a Mac

-weight: 10

----

-# Installing Hugo on a Mac

-This tutorial aims to be a complete guide to installing Hugo on your Mac computer.

-## Assumptions

-1. You know how to open a terminal window.

-2. You're running a modern 64-bit Mac.

-3. You will use `~/Sites` as the starting point for your site.

-## Pick Your Method

-There are three ways to install Hugo on your Mac computer: the `brew` utility, from the distribution, or from source.

-There's no "best" way to do this. You should use the method that works best for your use case.

-There are pros and cons for each.

-1. `Brew` is the simplest and least work to maintain. The drawbacks

-   aren't severe. The default package will be for the most recent

-   release, so it will not have bug-fixes until the next release

-   (unless you install it with the `--HEAD` option). The release to

-   `brew` may lag a few days behind because it has to be coordinated

-   with another team. Still, I'd recommend `brew` if you want to work

-   from a stable, widely used source. It works well and is really easy

-   to update.

-2. Downloading the tarball and installing from it is also easy. You have to have a few more command line skills. Updates are easy, too. You just repeat the process with the new binary. This gives you the flexibility to have multiple versions on your computer. If you don't want to use `brew`, then the binary is a good choice.

-3. Compiling from source is the most work. The advantage is that you don't have to wait for a release to add features or bug fixes. The disadvantage is that you need to spend more time managing the setup. It's not a lot, but it's more than with the other two options.

-Since this is a "beginner" how-to, I'm going to cover the first two

-options in detail and go over the third more quickly.

-## Brew

-### Step 1: Install `brew` if you haven't already

-Go to the `brew` website, http://brew.sh/, and follow the directions there. The most important step is:

-```

-ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

-```

-When I did this, I had some problems with directory permissions. Searches on Google pointed me to pages that walked me through updating permissions on the `/usr/local` directory. Seemed scary, but it's worked well since.

-### Step 2: Run the `brew` command to install `hugo`

-```bash

-$ brew install hugo

-==> Downloading https://homebrew.bintray.com/bottles/hugo-0.21.sierra.bottle.tar.gz

-######################################################################## 100,0%

-==> Pouring hugo-0.21.sierra.bottle.tar.gz

-==> Using the sandbox

-==> Caveats

-Bash completion has been installed to:

-  /usr/local/etc/bash_completion.d

-==> Summary

-🍺  /usr/local/Cellar/hugo/0.21: 32 files, 17.4MB

-```

-(Note: Replace `brew install hugo` with `brew install hugo --HEAD`

-if you want the absolute latest version in development,

-but beware — there might be bugs!)

-`Brew` should have updated your path to include Hugo. Confirm by opening a new terminal window and running a few commands:

-```bash

-$ # show the location of the hugo executable

-$ which hugo

-/usr/local/bin/hugo

-$ # show the installed version

-$ ls -l $( which hugo )

-lrwxr-xr-x  1 mdhender admin  30 Mar 28 22:19 /usr/local/bin/hugo -> ../Cellar/hugo/0.13_1/bin/hugo

-$ # verify that hugo runs correctly

-$ hugo version

-Hugo Static Site Generator v0.13 BuildDate: 2015-03-09T21:34:47-05:00

-```

-### Step 3: You're Done

-You've installed Hugo. Now you need to set up your site. Read the

-[Quickstart guide](/overview/quickstart/), explore the rest of the

-documentation, and if you still have questions

-[just ask!](https://discourse.gohugo.io/ "Discussion forum")

-## From Tarball

-### Step 1: Decide on the location

-When installing from the tarball, you have to decide if you're going to install the binary in `/usr/local/bin` or in your home directory. There are three camps on this:

-1. Install it in `/usr/local/bin` so that all the users on your system have access to it. This is a good idea because it's a fairly standard place for executables. The downside is that you may need elevated privileges to put software into that location. Also, if there are multiple users on your system, they will all run the same version. Sometimes this can be an issue if you want to try out a new release.

-2. Install it in `~/bin` so that only you can execute it. This is a good idea because it's easy to do, easy to maintain, and doesn't require elevated privileges. The downside is that only you can run Hugo. If there are other users on your site, they have to maintain their own copies. That can lead to people running different versions. Of course, this does make it easier for you to experiment with different releases.

-3. Install it in your `sites` directory. This is not a bad idea if you have only one site that you're building. It keeps every thing in a single place. If you want to try out new releases, you can just make a copy of the entire site, update the Hugo executable, and have it.

-All three locations will work for you. I'm going to document the second option, mostly because I'm comfortable with it.

-### Step 2: Download the Tarball

-1. Open <https://github.com/gohugoio/hugo/releases> in your browser.

-2. Find the current release by scrolling down and looking for the green tag that reads "Latest Release."

-3. Download the current tarball for the Mac. The name will be something like `hugo_X.Y_osx-64bit.tgz`, where `X.YY` is the release number.

-4. By default, the tarball will be saved to your `~/Downloads` directory. If you chose to use a different location, you'll need to change that in the following steps.

-### Step 3: Confirm your download

-Verify that the tarball wasn't corrupted during the download:

-```

-$ tar tvf ~/Downloads/hugo_X.Y_osx-64bit.tgz

--rwxrwxrwx  0 0      0           0 Feb 22 04:02 hugo_X.Y_osx-64bit/hugo_X.Y_osx-64bit.tgz

--rwxrwxrwx  0 0      0           0 Feb 22 03:24 hugo_X.Y_osx-64bit/README.md

--rwxrwxrwx  0 0      0           0 Jan 30 18:48 hugo_X.Y_osx-64bit/LICENSE.md

-```

-The `.md` files are documentation. The other file is the executable.

-### Step 4: Install into your bin directory

-```

-$ # create the directory if needed

-$ mkdir -p ~/bin

-$ # make it the working directory

-$ cd ~/bin

-$ # extract the tarball

-$ tar -xvzf ~/Downloads/hugo_X.Y_osx-64bit.tgz

-Archive:  hugo_X.Y_osx-64bit.tgz

-  x ./

-  x ./hugo

-  x ./LICENSE.md

-  x ./README.md

-$ # verify that it runs

-$ ./hugo version

-Hugo Static Site Generator v0.13 BuildDate: 2015-02-22T04:02:30-06:00

-```

-You may need to add your bin directory to your `PATH` variable. The `which` command will check for us. If it can find `hugo`, it will print the full path to it. Otherwise, it will not print anything.

-```

-$ # check if hugo is in the path

-$ which hugo

-/Users/USERNAME/bin/hugo

-```

-If `hugo` is not in your `PATH`, add it by updating your `~/.bash_profile` file. First, start up an editor:

-```

-$ nano ~/.bash_profile

-```

-Add a line to update your `PATH` variable:

-```

-export PATH=$PATH:$HOME/bin

-```

-Then save the file by pressing Control-X, then Y to save the file and return to the prompt.

-Close the terminal and then open a new terminal to pick up the changes to your profile. Verify by running the `which hugo` command again.

-### Step 5: You're Done

-You've installed Hugo. Now you need to set up your site. Read the

-[Quickstart guide](/overview/quickstart/), explore the rest of the

-documentation, and if you still have questions

-[just ask!](https://discourse.gohugo.io/ "Discussion forum")

-## Building from Source

-If you want to compile Hugo yourself, you'll need

-[Go](http://golang.org), which is also available from Homebrew: `brew

-install go`.

-### Step 1: Get the Source

-If you want to compile a specific version, go to

-<https://github.com/gohugoio/hugo/releases> and download the source code

-for the version of your choice.  If you want to compile Hugo with all

-the latest changes (which might include bugs), clone the Hugo

-repository:

-```

-git clone https://github.com/gohugoio/hugo

-```

-### Step 2: Compiling

-Make the directory containing the source your working directory, then

-fetch Hugo's dependencies:

-```

-mkdir -p src/github.com/spf13

-ln -sf $(pwd) src/github.com/gohugoio/hugo

-# set the build path for Go

-export GOPATH=$(pwd)

-go get

-```

-This will fetch the absolute latest version of the dependencies, so if

-Hugo fails to build it may be because the author of a dependency

-introduced a breaking change.

-Then compile:

-```

-go build -o hugo main.go

-```

-Then place the `hugo` executable somewhere in your `$PATH`.

-### Step 3: You're Done

-You probably know where to go from here.

--- a/content/tutorials/installing-on-windows.md

+++ /dev/null

@@ -1,123 +1,0 @@

----

-author: "Michael Henderson"

-lastmod: 2016-07-18

-date: 2015-03-30

-linktitle: Installing on Windows

-toc: true

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/mathjax

-prev: /tutorials/installing-on-mac

-title: Installing on Windows

-weight: 10

----

-# Installing Hugo on Windows

-This tutorial aims to be a complete guide to installing Hugo on your Windows computer.

-## Assumptions

-1. We'll call your website `example.com` for the purpose of this tutorial.

-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

-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).

-1. Open Windows Explorer.

-2. Create a new folder: `C:\Hugo` (assuming you want Hugo on your C drive – it can go anywhere.)

-3. Create a subfolder in the Hugo folder: `C:\Hugo\bin`.

-4. Create another subfolder in Hugo: `C:\Hugo\Sites`.

-## Technical users

-1. Download the latest zipped Hugo executable from the [Hugo Releases](https://github.com/gohugoio/hugo/releases) page.

-2. Extract all contents to your `..\Hugo\bin` folder.

-3. The hugo executable will be named as `hugo_hugo-version_platform_arch.exe`. Rename that executable to `hugo.exe` for ease of use.

-4. In PowerShell or your preferred CLI, add the `hugo.exe` executable to your PATH by navigating to `C:\Hugo\bin` (or the location of your hugo.exe file) and use the command `set PATH=%PATH%;C:\Hugo\bin`. If the `hugo` command does not work after a reboot, you may have to run the command prompt as administrator.

-## Less technical users

-1. Go the [Hugo Releases](https://github.com/gohugoio/hugo/releases) page.

-2. The latest release is announced on top. Scroll to the bottom of the release announcement to see the downloads. They're all ZIP files.

-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.

-7. Now add Hugo to your Windows PATH settings:

-    ### For Windows 10 users:

-    - Right click on the **Start** button.

-    - Click on **System**.

-    - Click on **Advanced System Settings** on the left.

-    - Click on the **Environment Variables...** button on the bottom.

-    - In the User variables section, find the row that starts with PATH (PATH will be all caps).

-    - Double-click on **PATH**.

-    - Click the **New...** button.

-    - Type in the folder where `hugo.exe` was extracted, which is `C:\Hugo\bin` if you went by the instructions above. *The PATH entry should be the folder where Hugo lives, not the binary.* Press <kbd>Enter</kbd> when you're done typing.

-    - Click OK at every window to exit.

-    > <small>Note that the path editor in Windows 10 was added in the large [November 2015 Update](https://blogs.windows.com/windowsexperience/2015/11/12/first-major-update-for-windows-10-available-today/). You'll need to have that or a later update installed for the above steps to work. You can see what Windows 10 build you have by clicking on the <i class="fa fa-windows"></i>&nbsp;Start button → Settings → System → About. See [here](http://www.howtogeek.com/236195/how-to-find-out-which-build-and-version-of-windows-10-you-have/) for more.)</small>

-    ### For Windows 7 and 8.x users:

-    Windows 7 and 8.1 do not include the easy path editor included in Windows 10, so non-technical users on those platforms are advised to install a free third-party path editor like [Windows Environment Variables Editor](http://eveditor.com/) or [Path Editor](https://patheditor2.codeplex.com/).

-## Verify the executable

-Run a few commands to verify that the executable is ready to run, and then build a sample site to get started.

-1. Open a command prompt window.

-2. At the prompt, type `hugo help` and press the <kbd>Enter</kbd> key. You should see output that starts with:

-    {{< nohighlight >}}hugo is the main command, used to build your Hugo site.

-Hugo is a Fast and Flexible Static Site Generator

-built with love by spf13 and friends in Go.

-Complete documentation is available at http://gohugo.io/.

-{{< /nohighlight >}}

-    If you do, then the installation is complete. If you don't, double-check the path that you placed the `hugo.exe` file in and that you typed that path correctly when you added it to your PATH variable. If you're still not getting the output, post a note on the Hugo discussion list (in the `Support` topic) with your command and the output.

-3. At the prompt, change your directory to the `Sites` directory.

-    {{< nohighlight >}}C:\Program Files> cd C:\Hugo\Sites

-C:\Hugo\Sites>

-{{< /nohighlight >}}

-4. Run the command to generate a new site. I'm using `example.com` as the name of the site.

-    {{< nohighlight >}}C:\Hugo\Sites> hugo new site example.com

-{{< /nohighlight >}}

-5. You should now have a directory at `C:\Hugo\Sites\example.com`.  Change into that directory and list the contents. You should get output similar to the following:

-    {{< nohighlight >}}C:\Hugo\Sites&gt;cd example.com

-C:\Hugo\Sites\example.com&gt;dir

-&nbsp;Directory of C:\hugo\sites\example.com

-&nbsp;

-04/13/2015  10:44 PM    &lt;DIR&gt;          .

-04/13/2015  10:44 PM    &lt;DIR&gt;          ..

-04/13/2015  10:44 PM    &lt;DIR&gt;          archetypes

-04/13/2015  10:44 PM                83 config.toml

-04/13/2015  10:44 PM    &lt;DIR&gt;          content

-04/13/2015  10:44 PM    &lt;DIR&gt;          data

-04/13/2015  10:44 PM    &lt;DIR&gt;          layouts

-04/13/2015  10:44 PM    &lt;DIR&gt;          static

-               1 File(s)             83 bytes

-               7 Dir(s)   6,273,331,200 bytes free

-{{< /nohighlight >}}

-You now have Hugo installed and a site to work with. You need to add a layout (or theme), then create some content. Go to http://gohugo.io/overview/quickstart/ for steps on doing that.

-## Troubleshooting

-@dhersam has created a nice video on common issues:

-{{< youtube c8fJIRNChmU >}}

--- a/content/tutorials/mathjax.md

+++ /dev/null

@@ -1,84 +1,0 @@

----

-author: Spencer Lyon

-lastmod: 2015-05-22

-date: 2014-03-20

-menu:

-  main:

-    parent: tutorials

-next: /tutorials/migrate-from-jekyll

-prev: /tutorials/installing-on-windows

-title: MathJax Support

-toc: true

-weight: 10

----

-## What is MathJax?

-[MathJax](http://www.mathjax.org/) is a JavaScript library that allows the display of mathematical expressions described via a LaTeX-style syntax in the HTML (or Markdown) source of a web page. As it is a pure a JavaScript library, getting it to work within Hugo is fairly straightforward, but does have some oddities that will be discussed here.

-This is not an introduction into actually using MathJax to render typeset mathematics on your website. Instead, this page is a collection of tips and hints for one way to get MathJax working on a website built with Hugo.

-## Enabling MathJax

-The first step is to enable MathJax on pages that you would like to have typeset math. There are multiple ways to do this (adventurous readers can consult the [Loading and Configuring](http://docs.mathjax.org/en/latest/configuration.html) section of the MathJax documentation for additional methods of including MathJax), but the easiest way is to use [the officially recommended secure CDN](https://cdnjs.com/) by including the following HTML snippet in the source of a page:

-    <script type="text/javascript"

-      src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-AMS-MML_HTMLorMML">

-    </script>

-One way to ensure that this code is included in all pages is to put it in one of the templates that live in the `layouts/partials/` directory. For example, I have included this in the bottom of my template `footer.html` because I know that the footer will be included in every page of my website.

-### Options and Features

-MathJax is a stable open-source library with many features. I encourage the interested reader to view the [MathJax Documentation](http://docs.mathjax.org/en/latest/index.html), specifically the sections on [Basic Usage](http://docs.mathjax.org/en/latest/index.html#basic-usage) and [MathJax Configuration Options](http://docs.mathjax.org/en/latest/index.html#mathjax-configuration-options).

-## Issues with Markdown

-After enabling MathJax, any math entered in-between proper markers (see documentation) will be processed and typeset in the web page. One issue that comes up, however, with Markdown is that the underscore character (`_`) is interpreted by Markdown as a way to wrap text in `emph` blocks while LaTeX (MathJax) interprets the underscore as a way to create a subscript. This "double speak" of the underscore can result in some unexpected and unwanted behavior.

-### Solution

-There are multiple ways to remedy this problem. One solution is to simply escape each underscore in your math code by entering `\_` instead of `_`. This can become quite tedious if the equations you are entering are full of subscripts.

-Another option is to tell Markdown to treat the MathJax code as verbatim code and not process it. One way to do this is to wrap the math expression inside a `<div>` `</div>` block. Markdown would ignore these sections and they would get passed directly on to MathJax and processed correctly. This works great for display style mathematics, but for inline math expressions the line break induced by the `<div>` is not acceptable. The syntax for instructing Markdown to treat inline text as verbatim is by wrapping it in backticks (`` ` ``). You might have noticed, however, that the text included in between backticks is rendered differently than standard text (on this site these are items highlighted in red). To get around this problem, we could create a new CSS entry that would apply standard styling to all inline verbatim text that includes MathJax code. Below I will show the HTML and CSS source that would accomplish this (note this solution was adapted from [this blog post](http://doswa.com/2011/07/20/mathjax-in-markdown.html)---all credit goes to the original author).

-    <script type="text/x-mathjax-config">

-    MathJax.Hub.Config({

-      tex2jax: {

-        inlineMath: [['$','$'], ['\\(','\\)']],

-        displayMath: [['$$','$$'], ['\[','\]']],

-        processEscapes: true,

-        processEnvironments: true,

-        skipTags: ['script', 'noscript', 'style', 'textarea', 'pre'],

-        TeX: { equationNumbers: { autoNumber: "AMS" },

-             extensions: ["AMSmath.js", "AMSsymbols.js"] }

-      }

-    });

-    </script>

-    <script type="text/x-mathjax-config">

-      MathJax.Hub.Queue(function() {

-        // Fix <code> tags after MathJax finishes running. This is a

-        // hack to overcome a shortcoming of Markdown. Discussion at

-        // https://github.com/mojombo/jekyll/issues/199

-        var all = MathJax.Hub.getAllJax(), i;

-        for(i = 0; i < all.length; i += 1) {

-            all[i].SourceElement().parentNode.className += ' has-jax';

-        }

-    });

-    </script>

-As before, this content should be included in the HTML source of each page that will be using MathJax. The next code snippet contains the CSS that is used to have verbatim MathJax blocks render with the same font style as the body of the page.

-    code.has-jax {font: inherit;

-                  font-size: 100%;

-                  background: inherit;

-                  border: inherit;

-                  color: #515151;}

-In the CSS snippet, notice the line `color: #515151;`. `#515151` is the value assigned to the `color` attribute of the `body` class in my CSS. In order for the equations to fit in with the body of a web page, this value should be the same as the color of the body.

-### Usage

-With this setup, everything is in place for a natural usage of MathJax on pages generated using Hugo. In order to include inline mathematics, just put LaTeX code in between `` `$ TeX Code $` `` or `` `\( TeX Code \)` ``. To include display style mathematics, just put LaTeX code in between `<div>$$TeX Code$$</div>`. All the math will be properly typeset and displayed within your Hugo generated web page!

--- a/content/tutorials/migrate-from-jekyll.md

+++ /dev/null

@@ -1,162 +1,0 @@

----

-lastmod: 2015-12-24

-date: 2014-03-10

-linktitle: Migrating from Jekyll

-toc: true

-menu:

-  main:

-    parent: tutorials

-prev: /tutorials/mathjax

-next: /tutorials/create-a-multilingual-site

-title: Migrate to Hugo from Jekyll

-weight: 10

----

-**Note:** Hugo 0.15 comes with a `hugo import jekyll` command, see [import from Jekyll](/commands/hugo_import_jekyll/).

-## Move static content to `static`

-Jekyll has a rule that any directory not starting with `_` will be copied as-is to the `_site` output. Hugo keeps all static content under `static`. You should therefore move it all there.

-With Jekyll, something that looked like

-    ▾ <root>/

-        ▾ images/

-            logo.png

-should become

-    ▾ <root>/

-        ▾ static/

-            ▾ images/

-                logo.png

-Additionally, you'll want any files that should reside at the root (such as `CNAME`) to be moved to `static`.

-## Create your Hugo configuration file

-Hugo can read your configuration as JSON, YAML or TOML. Hugo supports parameters custom configuration too. Refer to the [Hugo configuration documentation](/overview/configuration/) for details.

-## Set your configuration publish folder to `_site`

-The default is for Jekyll to publish to `_site` and for Hugo to publish to `public`. If, like me, you have [`_site` mapped to a git submodule on the `gh-pages` branch](http://blog.blindgaenger.net/generate_github_pages_in_a_submodule.html), you'll want to do one of two alternatives:

-1. Change your submodule to point to map `gh-pages` to public instead of `_site` (recommended).

-        git submodule deinit _site

-        git rm _site

-        git submodule add -b gh-pages [email protected]:your-username/your-repo.git public

-2. Or, change the Hugo configuration to use `_site` instead of `public`.

-        {

-            ..

-            "publishDir": "_site",

-            ..

-        }

-## Convert Jekyll templates to Hugo templates

-That's the bulk of the work right here. The documentation is your friend. You should refer to [Jekyll's template documentation](http://jekyllrb.com/docs/templates/) if you need to refresh your memory on how you built your blog and [Hugo's template](/layout/templates/) to learn Hugo's way.

-As a single reference data point, converting my templates for [heyitsalex.net](http://heyitsalex.net/) took me no more than a few hours.

-## Convert Jekyll plugins to Hugo shortcodes

-Jekyll has [plugins](http://jekyllrb.com/docs/plugins/); Hugo has [shortcodes](/doc/shortcodes/). It's fairly trivial to do a port.

-### Implementation

-As an example, I was using a custom [`image_tag`](https://github.com/alexandre-normand/alexandre-normand/blob/74bb12036a71334fdb7dba84e073382fc06908ec/_plugins/image_tag.rb) plugin to generate figures with caption when running Jekyll. As I read about shortcodes, I found Hugo had a nice built-in shortcode that does exactly the same thing.

-Jekyll's plugin:

-```ruby

-module Jekyll

-  class ImageTag < Liquid::Tag

-    @url = nil

-    @caption = nil

-    @class = nil

-    @link = nil

-    // Patterns

-    IMAGE_URL_WITH_CLASS_AND_CAPTION =

-    IMAGE_URL_WITH_CLASS_AND_CAPTION_AND_LINK = /(\w+)(\s+)((https?:\/\/|\/)(\S+))(\s+)"(.*?)"(\s+)->((https?:\/\/|\/)(\S+))(\s*)/i

-    IMAGE_URL_WITH_CAPTION = /((https?:\/\/|\/)(\S+))(\s+)"(.*?)"/i

-    IMAGE_URL_WITH_CLASS = /(\w+)(\s+)((https?:\/\/|\/)(\S+))/i

-    IMAGE_URL = /((https?:\/\/|\/)(\S+))/i

-    def initialize(tag_name, markup, tokens)

-      super

-      if markup =~ IMAGE_URL_WITH_CLASS_AND_CAPTION_AND_LINK

-        @class   = $1

-        @url     = $3

-        @caption = $7

-        @link = $9

-      elsif markup =~ IMAGE_URL_WITH_CLASS_AND_CAPTION

-        @class   = $1

-        @url     = $3

-        @caption = $7

-      elsif markup =~ IMAGE_URL_WITH_CAPTION

-        @url     = $1

-        @caption = $5

-      elsif markup =~ IMAGE_URL_WITH_CLASS

-        @class = $1

-        @url   = $3

-      elsif markup =~ IMAGE_URL

-        @url = $1

-      end

-    end

-    def render(context)

-      if @class

-        source = "<figure class='#{@class}'>"

-      else

-        source = "<figure>"

-      end

-      if @link

-        source += "<a href=\"#{@link}\">"

-      end

-      source += "<img src=\"#{@url}\">"

-      if @link

-        source += "</a>"

-      end

-      source += "<figcaption>#{@caption}</figcaption>" if @caption

-      source += "</figure>"

-      source

-    end

-  end

-end

-Liquid::Template.register_tag('image', Jekyll::ImageTag)

-```

-is written as this Hugo shortcode:

-    <!-- image -->

-    <figure {{ with .Get "class" }}class="{{.}}"{{ end }}>

-        {{ with .Get "link"}}<a href="{{.}}">{{ end }}

-            <img src="{{ .Get "src" }}" {{ if or (.Get "alt") (.Get "caption") }}alt="{{ with .Get "alt"}}{{.}}{{else}}{{ .Get "caption" }}{{ end }}"{{ end }} />

-        {{ if .Get "link"}}</a>{{ end }}

-        {{ if or (or (.Get "title") (.Get "caption")) (.Get "attr")}}

-        <figcaption>{{ if isset .Params "title" }}

-            {{ .Get "title" }}{{ end }}

-            {{ if or (.Get "caption") (.Get "attr")}}<p>

-            {{ .Get "caption" }}

-            {{ with .Get "attrlink"}}<a href="{{.}}"> {{ end }}

-                {{ .Get "attr" }}

-            {{ if .Get "attrlink"}}</a> {{ end }}

-            </p> {{ end }}

-        </figcaption>

-        {{ end }}

-    </figure>

-    <!-- image -->

-### Usage

-I simply changed:

-    {% image full http://farm5.staticflickr.com/4136/4829260124_57712e570a_o_d.jpg "One of my favorite touristy-type photos. I secretly waited for the good light while we were "having fun" and took this. Only regret: a stupid pole in the top-left corner of the frame I had to clumsily get rid of at post-processing." ->http://www.flickr.com/photos/alexnormand/4829260124/in/set-72157624547713078/ %}

-to this (this example uses a slightly extended version named `fig`, different than the built-in `figure`):

-    {{%/* fig class="full" src="http://farm5.staticflickr.com/4136/4829260124_57712e570a_o_d.jpg" title="One of my favorite touristy-type photos. I secretly waited for the good light while we were having fun and took this. Only regret: a stupid pole in the top-left corner of the frame I had to clumsily get rid of at post-processing." link="http://www.flickr.com/photos/alexnormand/4829260124/in/set-72157624547713078/" */%}}

-As a bonus, the shortcode named parameters are, arguably, more readable.

-## Finishing touches

-### Fix content

-Depending on the amount of customization that was done with each post with Jekyll, this step will require more or less effort. There are no hard and fast rules here except that `hugo server` is your friend. Test your changes and fix errors as needed.

-### Clean up

-You'll want to remove the Jekyll configuration at this point. If you have anything else that isn't used, delete it.

-## A practical example in a diff

-[Hey, it's Alex](http://heyitsalex.net/) was migrated in less than a _father-with-kids day_ from Jekyll to Hugo. You can see all the changes (and screw-ups) by looking at this [diff](https://github.com/alexandre-normand/alexandre-normand/compare/869d69435bd2665c3fbf5b5c78d4c22759d7613a...b7f6605b1265e83b4b81495423294208cc74d610).

--- /dev/null

+++ b/content/variables/_index.md

@@ -1,0 +1,23 @@

+---

+title: Variables and Params

+linktitle: Variables Overview

+description: Page-, file-, taxonomy-, and site-level variables and parameters available in templates.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [variables and params]

+#tags: [variables,params,values,globals]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 1

+weight: 01	#rem

+sections_weight: 01

+aliases: [/templates/variables/]

+toc: false

+---

+Hugo's templates are context aware and make a large number of values available to you as you're creating views for your website.

+[Go templates]: /templates/introduction/ "Understand context in Go templates by learning the language's fundamental templating functions."

--- /dev/null

+++ b/content/variables/files.md

@@ -1,0 +1,48 @@

+---

+title: File Variables

+linktitle:

+description: "You can access filesystem-related data for a content file in the `.File` variable."

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [variables and params]

+#tags: [files]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 40

+weight: 40

+sections_weight: 40

+aliases: [/variables/file-variables/]

+toc: false

+---

+{{% note "Rendering Local Files" %}}

+For information on creating shortcodes and templates that tap into Hugo's file-related feature set, see [Local File Templates](/templates/files/).

+{{% /note %}}

+The `.File` object contains the following fields:

+`.File.Path`

+: the original relative path of the page (e.g., `content/posts/foo.en.md`)

+`.File.LogicalName`

+: the name of the content file that represents a page (e.g., `foo.en.md`)

+`.File.TranslationBaseName`

+: the filename without extension or optional language identifier (e.g., `foo`)

+`.File.BaseFileName`

+: the filename without extension (e.g., `foo.en`)

+`.File.Ext`

+: the file extension of the content file (e.g., `md`); this can also be called using `.File.Extension` as well. Note that it is *only* the extension without `.`.

+`.File.Lang`

+: the language associated with the given file if Hugo's [Multilingual features][multilingual] are enabled (e.g., `en`)

+`.File.Dir`

+: given the path `content/posts/dir1/dir2/`, the relative directory path of the content file will be returned (e.g., `posts/dir1/dir2/`)

+[Multilingual]: /content-management/multilingual/

\ No newline at end of file

--- /dev/null

+++ b/content/variables/git.md

@@ -1,0 +1,54 @@

+---

+title: Git Info Variables

+linktitle: Git Variables

+description: Get the last Git revision information for every content file.

+date: 2017-03-12

+publishdate: 2017-03-12

+lastmod: 2017-03-12

+categories: [variables and params]

+#tags: [git]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 70

+weight: 70

+sections_weight: 70

+aliases: [/extras/gitinfo/]

+toc: false

+wip: false

+---

+{{% note "`.GitInfo` Performance Considerations"  %}}

+Hugo's Git integrations should be fairly performant but *can* increase your build time. This will depend on the size of your Git history.

+{{% /note %}}

+## `.GitInfo` Prerequisites

+1. The Hugo site must be in a Git-enabled directory.

+2. The Git executable must be installed and in your system `PATH`.

+3. The `.GitInfo` feature must be enabled in your Hugo project by passing `--enableGitInfo` flag on the command line or by setting `enableGitInfo` to `true` in your [site's configuration file][configuration].

+## The `.GitInfo` Object

+The `GitInfo` object contains the following fields:

+`.AbbreviatedHash`

+: the abbreviated commit hash (e.g., `866cbcc`)

+`.AuthorName`

+: the author's name, respecting `.mailmap`

+`.AuthorEmail`

+: the author's email address, respecting `.mailmap`

+`.AuthorDate`

+: the author date

+`.Hash`

+: the commit hash (e.g., `866cbccdab588b9908887ffd3b4f2667e94090c3`)

+`.Subject`

+: commit message subject (e.g., `tpl: Add custom index function`)

+[configuration]: /getting-started/configuration/

--- /dev/null

+++ b/content/variables/hugo.md

@@ -1,0 +1,39 @@

+---

+title: Hugo-specific Variables

+linktitle: Hugo Variables

+description: The `.Hugo` variable provides easy access to Hugo-related data.

+date: 2017-03-12

+publishdate: 2017-03-12

+lastmod: 2017-03-12

+categories: [variables and params]

+#tags: [hugo,generator]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 60

+weight: 60

+sections_weight: 60

+aliases: []

+toc: false

+wip: false

+---

+It contains the following fields:

+`.Hugo.Generator`

+: `<meta>` tag for the version of Hugo that generated the site. `.Hugo.Generator` outputs a *complete* HTML tag; e.g. `<meta name="generator" content="Hugo 0.18" />`

+`.Hugo.Version`

+: the current version of the Hugo binary you are using e.g. `0.13-DEV`<br>

+`.Hugo.CommitHash`

+: the git commit hash of the current Hugo binary e.g. `0e8bed9ccffba0df554728b46c5bbf6d78ae5247`

+`.Hugo.BuildDate`

+: the compile date of the current Hugo binary formatted with RFC 3339 e.g. `2002-10-02T10:00:00-05:00`<br>

+{{% note "Use the Hugo Generator Tag" %}}

+We highly recommend using `.Hugo.Generator` in your website's `<head>`. `.Hugo.Generator` is included by default in all themes hosted on [themes.gohugo.io](http://themes.gohugo.io). The generator tag allows the Hugo team to track the usage and popularity of Hugo.

+{{% /note %}}

--- /dev/null

+++ b/content/variables/menus.md

@@ -1,0 +1,50 @@

+---

+title: Menu Variables

+linktitle: Menu Variables

+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

+categories: [variables and params]

+#tags: [menus]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 50

+weight: 50

+sections_weight: 50

+aliases: [/variables/menu/]

+toc: false

+---

+The [menu template][] has the following properties:

+`.URL`

+: string

+`.Name`

+: string

+`.Menu`

+: string

+`.Identifier`

+: string

+`.Pre`

+: template.HTML

+`.Post`

+: template.HTML

+`.Weight`

+: int

+`.Parent`

+: string

+`.Children`

+: Menu

+[menu template]: /templates/menu-templates/

\ No newline at end of file

--- /dev/null

+++ b/content/variables/page.md

@@ -1,0 +1,272 @@

+---

+title: Page Variables

+linktitle:

+description: Page-level variables are defined in a content file's front matter, derived from the content's file location, or extracted from the content body itself.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [variables and params]

+#tags: [pages]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 20

+weight: 20

+sections_weight: 20

+aliases: [/variables/page/]

+toc: true

+---

+The following is a list of page-level variables. Many of these will be defined in the front matter, derived from file location, or extracted from the content itself.

+{{% note "`.Scratch`" %}}

+See [`.Scratch`](/functions/scratch/) for page-scoped, writable variables.

+{{% /note %}}

+## Page Variables

+`.AlternativeOutputFormats`

+: contains all alternative formats for a given page; this variable is especially useful `link rel` list in your site's `<head>`. (See [Output Formats](/templates/output-formats/).)

+`.Content`

+: the content itself, defined below the front matter.

+`.Data`

+: the data specific to this type of page.

+`.Date`

+: the date associated with the page; `.Date` pulls from the `date` field in a content's front matter. See also `.ExpiryDate`, `.PublishDate`, and `.Lastmod`.

+`.Description`

+: the description for the page.

+`.Draft`

+: a boolean, `true` if the content is marked as a draft in the front matter.

+`.ExpiryDate`

+: the date on which the content is scheduled to expire; `.ExpiryDate` pulls from the `expirydate` field in a content's front matter. See also `.PublishDate`, `.Date`, and `.Lastmod`.

+`.FuzzyWordCount`

+: the approximate number of words in the content.

+`.Hugo`

+: see [Hugo Variables](/variables/hugo/).

+`.IsHome`

+: `true` in the context of the [homepage](/templates/homepage/).

+`.IsNode`

+: always `false` for regular content pages.

+`.IsPage`

+: always `true` for regular content pages.

+`.IsTranslated`

+: `true` if there are translations to display.

+`.Keywords`

+: the meta keywords for the content.

+`.Kind`

+: the page's *kind*. Possible return values are `page`, `home`, `section`, `taxonomy`, or `taxonomyTerm`. Note that there are also `RSS`, `sitemap`, `robotsTXT`, and `404` kinds, but these are only available during the rendering of each of these respective page's kind and therefore *not* available in any of the `Pages` collections.

+`.Lang`

+: language taken from the language extension notation.

+`.Language`

+: a language object that points to the language's definition in the site

+`config`.

+`.Lastmod`

+: the date the content was last modified; `.Lastmod` pulls from the `lastmod` field in a content's front matter. If `lastmod` is not set, Hugo will default to the `date` field. See also `.ExpiryDate`, `.Date`, and `.PublishDate`.

+`.LinkTitle`

+: access when creating links to the content. If set, Hugo will use the `linktitle` from the front matter before `title`.

+`.Next`

+: pointer to the following content (based on the `publishdate` field in front matter).

+`.NextInSection`

+: pointer to the following content within the same section (based on `publishdate` field in front matter).

+`.OutputFormats`

+: 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`.

+`.Permalink`

+: the Permanent link for this page; see [Permalinks](/content-management/urls/)

+`.Plain`

+: the Page content stripped of HTML tags and presented as a string.

+`.PlainWords`

+: the Page content stripped of HTML as a `[]string` using Go's [`strings.Fields`](https://golang.org/pkg/strings/#Fields) to split `.Plain` into a slice.

+`.Prev`

+: Pointer to the previous content (based on `publishdate` in front matter).

+`.PrevInSection`

+: Pointer to the previous content within the same section (based on `publishdate` in front matter). For example, `{{if .PrevInSection}}{{.PrevInSection.Permalink}}{{end}}`.

+`.PublishDate`

+: the date on which the content was or will be published; `.Publishdate` pulls from the `publishdate` field in a content's front matter. See also `.ExpiryDate`, `.Date`, and `.Lastmod`.

+`.RSSLink`

+: link to the taxonomies' RSS link.

+`.RawContent`

+: raw markdown content without the front matter. Useful with [remarkjs.com](

+http://remarkjs.com)

+`.ReadingTime`

+: the estimated time, in minutes, it takes to read the content.

+`.Ref`

+: returns the permalink for a given reference (e.g., `.Ref "sample.md"`).  `.Ref` does *not* handle in-page fragments correctly. See [Cross References](/content-management/cross-references/).

+`.RelPermalink`

+: the relative permanent link for this page.

+`.RelRef`

+: returns the relative permalink for a given reference (e.g., `RelRef

+"sample.md"`). `.RelRef` does *not* handle in-page fragments correctly. See [Cross References](/content-management/cross-references/).

+`.Section`

+: the [section](/content-management/sections/) this content belongs to.

+`.Site`

+: see [Site Variables](/variables/site/).

+`.Summary`

+: a generated summary of the content for easily showing a snippet in a summary view. The breakpoint can be set manually by inserting <code>&lt;!&#x2d;&#x2d;more&#x2d;&#x2d;&gt;</code> at the appropriate place in the content page. See [Content Summaries](/content-management/summaries/) for more details.

+`.TableOfContents`

+: the rendered [table of contents](/content-management/toc/) for the page.

+`.Title`

+: the title for this page.

+`.Translations`

+: a list of translated versions of the current page. See [Multilingual Mode](/content-management/multilingual/) for more information.

+`.Truncated`

+: a boolean, `true` if the `.Summary` is truncated. Useful for showing a "Read more..." link only when necessary.  See [Summaries](/content-management/summaries/) for more information.

+`.Type`

+: the [content type](/content-management/types/) of the content (e.g., `post`).

+`.URL`

+: the URL for the page relative to the web root. Note that a `url` set directly in front matter overrides the default relative URL for the rendered page.

+`.UniqueID`

+: the MD5-checksum of the content file's path.

+`.Weight`

+: assigned weight (in the front matter) to this content, used in sorting.

+`.WordCount`

+: the number of words in the content.

+## Page-level Params

+Any other value defined in the front matter in a content file, including taxonomies, will be made available as part of the `.Params` variable.

+```yaml

+---

+title: My First Post

+date: date: 2017-02-20T15:26:23-06:00

+categories: [one]

+#tags: [two,three,four]

+```

+With the above front matter, the `tags` and `categories` taxonomies are accessible via the following:

+* `.Params.tags`

+* `.Params.categories`

+{{% note "Casing of Params" %}}

+Page-level `.Params` are *only* accessible in lowercase.

+{{% /note %}}

+The `.Params` variable is particularly useful for the introduction of user-defined front matter fields in content files. For example, a Hugo website on book reviews could have the following front matter in `/content/review/book01.md`:

+```yaml

+---

+...

+affiliatelink: "http://www.my-book-link.here"

+recommendedby: "My Mother"

+...

+---

+```

+These fields would then be accessible to the `/themes/yourtheme/layouts/review/single.html` template through `.Params.affiliatelink` and `.Params.recommendedby`, respectively.

+Two common situations where this type of front matter field could be introduced is as a value of a certain attribute like `href=""` or by itself to be displayed as text to the website's visitors.

+{{% code file="/themes/yourtheme/layouts/review/single.html" %}}

+```html

+<h3><a href={{ printf "%s" $.Params.affiliatelink }}>Buy this book</a></h3>

+<p>It was recommended by {{ .Params.recommendedby }}.</p>

+```

+{{% /code %}}

+This template would render as follows, assuming you've set [`uglyURLs`](/content-management/urls/) to `false` in your [site `config`](/getting-started/configuration/):

+{{% output file="yourbaseurl/review/book01/index.html" %}}

+```html

+<h3><a href="http://www.my-book-link.here">Buy this book</a></h3>

+<p>It was recommended by my Mother.</p>

+```

+{{% /output %}}

+{{% note %}}

+See [Archetypes](/content-management/archetypes/) for consistency of `Params` across pieces of content.

+{{% /note %}}

+### The `.Param` Method

+In Hugo, you can declare params in individual pages and globally for your entire website. A common use case is to have a general value for the site param and a more specific value for some of the pages (i.e., a header image):

+```golang

+{{ $.Param "header_image" }}

+```

+The `.Param` method provides a way to resolve a single value according to it's definition in a page parameter (i.e. in the content's front matter) or a site parameter (i.e., in your `config`).

+### Access Nested Fields in Front Matter

+When front matter contains nested fields like the following:

+```yaml

+---

+author:

+  given_name: John

+  family_name: Feminella

+  display_name: John Feminella

+---

+```

+`.Param` can access these fields by concatenating the field names together with a dot:

+```

+{{ $.Param "author.display_name" }}

+```

+If your front matter contains a top-level key that is ambiguous with a nested key, as in the following case:

+```

+---

+favorites.flavor: vanilla

+favorites:

+  flavor: chocolate

+---

+```

+The top-level key will be preferred. Therefore, the following method, when applied to the previous example, will print `vanilla` and not `chocolate`:

+```golang

+{{ $.Param "favorites.flavor" }}

+=> vanilla

+```

--- /dev/null

+++ b/content/variables/shortcodes.md

@@ -1,0 +1,36 @@

+---

+title: Shortcode Variables

+linktitle: Shortcode Variables

+description: Shortcodes can access page variables and also have their own specific built-in variables.

+date: 2017-03-12

+publishdate: 2017-03-12

+lastmod: 2017-03-12

+categories: [variables and params]

+#tags: [shortcodes]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 20

+weight: 20

+sections_weight: 20

+aliases: []

+toc: false

+---

+[Shortcodes][shortcodes] have access to parameters delimited in the shortcode declaration via [`.Get`][getfunction], page- and site-level variables, and also the following shortcode-specific fields:

+`.Parent`

+: provides access to the parent shortcode context in nested shortcodes. This can be very useful for inheritance of common shortcode parameters from the root.

+`.IsNamedParams`

+: boolean that returns `true` when the shortcode in question uses [named rather than positional parameters][shortcodes]

+`.Inner`

+: represents the content between the opening and closing shortcode tags when a [closing shortcode][markdownshortcode] is used

+[getfunction]: /functions/get/

+[markdownshortcode]: /content-management/shortcodes/#shortcodes-with-markdown

+[shortcodes]: /templates/shortcode-templates/

--- /dev/null

+++ b/content/variables/site.md

@@ -1,0 +1,127 @@

+---

+title: Site Variables

+linktitle: Site Variables

+description: Many, but not all, site-wide variables are defined in your site's configuration. However, Hugo provides a number of built-in variables for convenient access to global values in your templates.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [variables and params]

+#tags: [global,site]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 10

+weight: 10

+sections_weight: 10

+aliases: [/variables/site-variables/]

+toc: true

+---

+The following is a list of site-level (aka "global") variables. Many of these variables are defined in your site's [configuration file][config], whereas others are built into Hugo's core for convenient usage in your templates.

+## Site Variables List

+`.Site.AllPages`

+: array of all pages, regardless of their translation.

+`.Site.Author`

+: a map of the authors as defined in the site configuration.

+`.Site.BaseURL`

+: the base URL for the site as defined in the site configuration.

+`.Site.BuildDrafts`

+: a boolean (default: `false`) to indicate whether to build drafts as defined in the site configuration.

+`.Site.Copyright`

+: a string representing the copyright of your website as defined in the site configuration.

+`.Site.Data`

+: custom data, see [Data Templates](/templates/data-templates/).

+`.Site.DisqusShortname`

+: a string representing the shortname of the Disqus shortcode as defined in the site configuration.

+`.Site.Files`

+: all source files for the Hugo website.

+`.Site.GoogleAnalytics`

+: a string representing your tracking code for Google Analytics as defined in the site configuration.

+`.Site.IsMultiLingual`

+: whether there are more than one language in this site. See [Multilingual](/content-management/multilingual/) for more information.

+`.Site.Language.Lang`

+: the language code of the current locale (e.g., `en`).

+`.Site.Language.LanguageName`

+: the full language name (e.g. `English`).

+`.Site.Language.Weight`

+: the weight that defines the order in the `.Site.Languages` list.

+`.Site.Language`

+: indicates the language currently being used to render the website. This object's attributes are set in site configurations' language definition.

+`.Site.LanguageCode`

+: a string representing the language as defined in the site configuration. This is mostly used to populate the RSS feeds with the right language code.

+`.Site.LanguagePrefix`

+: this can be used to prefix URLs to point to the correct language. It will even work when only one defined language. See also the functions [absLangURL](/functions/abslangurl/) and [relLangURL](/functions/rellangurl).

+`.Site.Languages`

+: an ordered list (ordered by defined weight) of languages.

+`.Site.LastChange`

+: a string representing the date/time of the most recent change to your site. This string is based on the [`date` variable in the front matter](/content-management/front-matter) of your content pages.

+`.Site.Menus`

+: all of the menus in the site.

+`.Site.Pages`

+: array of all content ordered by Date with the newest first. This array contains only the pages in the current language.

+`.Site.Permalinks`

+: a string to override the default [permalink](/content-management/urls/) format as defined in the site configuration.

+`.Site.RegularPages`

+: a shortcut to the *regular* page collection. `.Site.RegularPages` is equivalent to `where .Site.Pages "Kind" "page"`.

+`.Site.RSSLink`

+: the URL for the site RSS.

+`.Site.Sections`

+: top-level directories of the site.

+`.Site.Taxonomies`

+: the [taxonomies](/taxonomies/usage/) for the entire site.  Replaces the now-obsolete `.Site.Indexes` since v0.11. Also see section [Taxonomies elsewhere](#taxonomies-elsewhere).

+`.Site.Title`

+: a string representing the title of the site.

+## The `.Site.Params` Variable

+`.Site.Params` is a container holding the values from the `params` section of your site configuration.

+### Example: `.Site.Params`

+The following `config.toml` defines a site-wide param for `description`:

+```toml

+baseURL = "http://yoursite.example.com/"

+[params]

+  description = "Tesla's Awesome Hugo Site"

+  author = "Nikola Tesla"

+```

+You can use `.Site.Params` in a [partial template](/templates/partials/) to call the default site description:

+{{% code file="layouts/partials/head.html" %}}

+```html

+<meta name="description" content="{{if .IsHome}}{{ $.Site.Params.description }}{{else}}{{.Description}}{{end}}" />

+```

+{{% /code %}}

+[config]: /getting-started/configuration/

\ No newline at end of file

--- /dev/null

+++ b/content/variables/sitemap.md

@@ -1,0 +1,32 @@

+---

+title: Sitemap Variables

+linktitle: Sitemap Variables

+description:

+date: 2017-03-12

+publishdate: 2017-03-12

+lastmod: 2017-03-12

+categories: [variables and params]

+#tags: [sitemap]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 80

+weight: 80

+sections_weight: 80

+aliases: []

+toc: false

+---

+A sitemap is a `Page` and therefore has all the [page variables][pagevars] available to use sitemap templates. They also have the following sitemap-specific variables available to them:

+`.Sitemap.ChangeFreq`

+: the page change frequency

+`.Sitemap.Priority`

+: the priority of the page

+`.Sitemap.Filename`

+: the sitemap filename

+[pagevars]: /variables/page/

\ No newline at end of file

--- /dev/null

+++ b/content/variables/taxonomy.md

@@ -1,0 +1,86 @@

+---

+title: Taxonomy Variables

+linktitle:

+description: Taxonomy pages are of type `Page` and have all page-, site-, and list-level variables available to them. However, taxonomy terms templates have additional variables available to their templates.

+date: 2017-02-01

+publishdate: 2017-02-01

+lastmod: 2017-02-01

+categories: [variables and params]

+#tags: [taxonomies,terms]

+draft: false

+menu:

+  docs:

+    parent: "variables"

+    weight: 30

+weight: 30

+sections_weight: 30

+aliases: []

+toc: true

+---

+## Taxonomy Terms Page Variables

+[Taxonomy terms pages][taxonomytemplates] are of the type `Page` and have the following additional variables.

+For example, the following fields would be available in `layouts/_defaults/terms.html`, depending on how you organize your [taxonomy templates][taxonomytemplates]:

+`.Data.Singular`

+: The singular name of the taxonomy (e.g., `tags => `tag`)

+`.Data.Plural`

+: The plural name of the taxonomy (e.g., `tags => tags`)

+`.Data.Pages`

+: The list of pages in the taxonomy

+`.Data.Terms`

+: The taxonomy itself

+`.Data.Terms.Alphabetical`

+: The taxonomy terms alphabetized

+`.Data.Terms.ByCount`

+: The Terms ordered by popularity

+Note that `.Data.Terms.Alphabetical` and `.Data.Terms.ByCount` can also be reversed:

+* `.Data.Terms.Alphabetical.Reverse`

+* `.Data.Terms.ByCount.Reverse`

+## Use `.Site.Taxonomies` Outside of Taxonomy Templates

+The `.Site.Taxonomies` variable holds all the taxonomies defined site-wide. `.Site.Taxonomies` is a map of the taxonomy name to a list of its values (e.g., `"tags" -> ["tag1", "tag2", "tag3"]``). Each value, though, is not a string but rather a *Taxonomy variable*.

+## The `.Taxonomy` Variable

+The `.Taxonomy` variable, available, for example, as `.Site.Taxonomies.tags`, contains the list of tags (values) and, for each tag, their corresponding content pages.

+### Example Usage of `.Site.Taxonomies`

+The following [partial template][partials] will list all your site's taxonomies, each of their keys, and all the content assigned to each of the keys. For more examples of how to order and render your taxonomies, see  [Taxonomy Templates][taxonomytemplates].

+{{% code file="all-taxonomies-keys-and-pages.html" download="all-taxonomies-keys-and-pages.html" %}}

+```html

+<section>

+  <ul>

+    {{ range $taxonomyname, $taxonomy := .Site.Taxonomies }}

+      <li><a href="{{ "/" | relLangURL}}{{ $taxonomyname | urlize }}">{{ $taxonomyname }}</a>

+        <ul>

+          {{ range $key, $value := $taxonomy }}

+          <li> {{ $key }} </li>

+                <ul>

+                {{ range $value.Pages }}

+                    <li><a href="{{ .Permalink}}"> {{ .LinkTitle }} </a> </li>

+                {{ end }}

+                </ul>

+          {{ end }}

+        </ul>

+      </li>

+    {{ end }}

+  </ul>

+</section>

+```

+{{% /code %}}

+[partials]: /templates/partials/

+[taxonomytemplates]: /templates/taxonomy-templates/

\ No newline at end of file

--- /dev/null

+++ b/data/articles.toml

@@ -1,0 +1,731 @@

+[[article]]

+	title = "A visit to the Workshop: Hugo/Unix/Vim integration"

+	url = "https://blog.afoolishmanifesto.com/posts/hugo-unix-vim-integration/"

+	author = "fREW Schmidt"

+	date = "2017-07-22"

+[[article]]

+	title = "Hugo Easy Gallery - Automagical PhotoSwipe image gallery with a one-line shortcode"

+	url = "https://www.liwen.id.au/heg/"

+	author = "Li-Wen Yip"

+	date = "2017-03-25"

+[[article]]

+	title = "Automagical Image Gallery in Hugo with PhotoSwipe and jQuery"

+	url = "https://www.liwen.id.au/photoswipe/"

+	author = "Li-Wen Yip"

+	date = "2017-03-04"

+[[article]]

+	title = "Adding Isso Comments to Hugo"

+	url = "https://stiobhart.net/2017-02-24-isso-comments/"

+	author = "Stíobhart Matulevicz"

+	date = "2017-02-24"

+[[article]]

+	title = "Hugo Tutorial: How to Build & Host a (Very Fast) Static E-Commerce Site"

+	url = "https://snipcart.com/blog/hugo-tutorial-static-site-ecommerce"

+	author = "Snipcart"

+	date = "2017-02-23"

+[[article]]

+	title = "How to Password Protect a Hugo Site"

+	url = "https://www.aerobatic.com/blog/password-protect-a-hugo-site/"

+	author = "Aerobatic"

+	date = "2017-02-19"

+[[article]]

+	title = "Switching from Wordpress to Hugo"

+	url = "http://schnuddelhuddel.de/switching-from-wordpress-to-hugo/"

+	author = "Mario Martelli"

+	date = "2017-02-19"

+[[article]]

+	title = "Zero to HTTP/2 with AWS and Hugo"

+	url = "https://habd.as/zero-to-http-2-aws-hugo/"

+	author = "Josh Habdas"

+	date = "2017-02-16"

+[[article]]

+	title = "Deploy a Hugo site to Aerobatic with CircleCI"

+	url = "https://www.aerobatic.com/blog/hugo-github-circleci/"

+	author = "Aerobatic"

+	date = "2017-02-14"

+[[article]]

+	title = "NPM scripts for building and deploying Hugo site"

+	url = "https://www.aerobatic.com/blog/hugo-npm-buildtool-setup/"

+	author = "Aerobatic"

+	date = "2017-02-12"

+[[article]]

+	title = "Getting started with Hugo and the plain-blog theme, on NearlyFreeSpeech.Net"

+	url = "https://www.penwatch.net/cms/get_started_plain_blog/"

+	author = "Li-aung “Lewis” Yip"

+	date = "2017-02-12"

+[[article]]

+	title = "Choose Hugo over Jekyll"

+	url = "https://habd.as/choose-hugo-over-jekyll/"

+	author = "Josh Habdas"

+	date = "2017-02-10"

+[[article]]

+	title = "Build a Hugo site using Cloud9 IDE and host on App Engine"

+	url = "https://loyall.ch/lab/2017/01/build-a-static-website-with-cloud9-hugo-and-app-engine/"

+	author = "Pascal Aubort"

+	date = "2017-02-05"

+[[article]]

+	title = "Hugo Continuous Deployment with Bitbucket Pipelines and Aerobatic"

+	url = "https://www.aerobatic.com/blog/hugo-bitbucket-pipelines/"

+	author = "Aerobatic"

+	date = "2017-02-04"

+[[article]]

+	title = "How to use Firebase to host a Hugo site"

+	url = "https://www.m0d3rnc0ad.com/post/static-site-firebase/"

+	author = "Andrew Cuga"

+	date= "2017-02-04"

+[[article]]

+	title = "A publishing workflow for teams using static site generators"

+	url = "https://www.keybits.net/post/publishing-workflow-for-teams-using-static-site-generators/"

+	author = "Tom Atkins"

+	date = "2017-01-02"

+[[article]]

+	title = "How To Dynamically Use Google Fonts In A Hugo Website"

+	url = "https://stoned.io/web-development/hugo/How-To-Dynamically-Use-Google-Fonts-In-A-Hugo-Website/"

+	author = "Hash Borgir"

+	date = "2016-10-27"

+[[article]]

+	title = "Embedding Facebook In A Hugo Template"

+	url = "https://stoned.io/web-development/hugo/Embedding-Facebook-In-A-Hugo-Template/"

+	author = "Hash Borgir"

+	date = "2016-10-22"

+[[article]]

+	title = "通过 Gitlab-cl 将 Hugo blog 自动部署至 GitHub <small>(Chinese, Continious integration)</small>"

+	url = "https://zetaoyang.github.io/post/2016/10/17/gitlab-cl.html"

+	author = "Zetao Yang"

+	date = "2016-10-17"

+[[article]]

+	title = "A Step-by-Step Guide: Hugo on Netlify"

+	url = "https://www.netlify.com/blog/2016/09/21/a-step-by-step-guide-hugo-on-netlify/"

+	author = "Eli Williamson"

+	date = "2016-09-21"

+[[article]]

+	title = "Building our site: From Django & Wordpress to a static generator (Part I)"

+	url = "https://tryolabs.com/blog/2016/09/20/building-our-site-django-wordpress-to-static-part-i/"

+	author = "Alan Descoins"

+	date = "2016-09-20"

+[[article]]

+	title = "Webseitenmaschine - Statische Websites mit Hugo erzeugen <small>(German, $)</small>"

+	url = "http://www.heise.de/ct/ausgabe/2016-12-Statische-Websites-mit-Hugo-erzeugen-3211704.html"

+	author = "Christian Helmbold"

+	date = "2016-05-27"

+[[article]]

+	title = "Cómo hacer sitios web estáticos con Hugo y Go - Platzi <small>(Video tutorial)</small>"

+	url = "https://www.youtube.com/watch?v=qaXXpdiCHXE"

+	author = "Verónica López"

+	date = "2016-04-06"

+[[article]]

+	title = "CDNOverview: A CDN comparison site made with Hugo"

+	url = "https://www.cloakfusion.com/cdnoverview-cdn-comparison-site-made-hugo/"

+	author = "Thijs de Zoete"

+	date = "2016-02-23"

+[[article]]

+	title = "Hugo: A Modern WebSite Engine That Just Works"

+	url = "https://github.com/shekhargulati/52-technologies-in-2016/blob/master/07-hugo/README.md"

+	author = "Shekhar Gulati"

+	date = "2016-02-14"

+[[article]]

+	title = "Minify Hugo Generated HTML"

+	url = "http://ratson.name/blog/minify-hugo-generated-html/"

+	author = "Ratson"

+	date = "2016-02-02"

+[[article]]

+	title = "<span lang='ja'>HugoのデプロイをWerckerからCircle CIに変更した</span> - log"

+	url = "http://log.deprode.net/logs/2016-01-17/"

+	author = "Deprode"

+	date = "2016-01-17"

+[[article]]

+	title = "Static site generators: el futuro de las webs estáticas<br>(Hugo, Jekyll, Flask y otros)"

+	url = "http://sitelabs.es/static-site-generators-futuro-las-webs-estaticas/"

+	author = "Eneko Sarasola"

+	date = "2016-01-09"

+[[article]]

+	title = "Writing a Lambda Function for Hugo"

+	url = "https://blog.jolexa.net/post/writing-a-lambda-function-for-hugo/"

+	author = "Jeremy Olexa"

+	date = "2016-01-01"

+[[article]]

+	title = "Ein Blog mit Hugo erstellen - Tutorial <small>(Deutsch/German)</small>"

+	url = "http://privat.albicker.org/tags/hugo.html"

+	author = "Bernhard Albicker"

+	date = "2015-12-30"

+[[article]]

+	title = "How to host Hugo static website generator on AWS Lambda"

+	url = "http://bezdelev.com/post/hugo-aws-lambda-static-website/"

+	author = "Ilya Bezdelev"

+	date = "2015-12-15"

+[[article]]

+	title = "Migrating from Pelican to Hugo"

+	url = "http://www.softinio.com/post/migrating-from-pelican-to-hugo/"

+	author = "Salar Rahmanian"

+	date = "2015-11-29"

+[[article]]

+	title = "Static Website Generators Reviewed: Jekyll, Middleman, Roots, Hugo"

+	url = "http://www.smashingmagazine.com/2015/11/static-website-generators-jekyll-middleman-roots-hugo-review/"

+	author = "Mathias Biilmann Christensen"

+	date = "2015-11-16"

+[[article]]

+	title = "How To Deploy a Hugo Site to Production with Git Hooks on Ubuntu 14.04"

+	url = "https://www.digitalocean.com/community/tutorials/how-to-deploy-a-hugo-site-to-production-with-git-hooks-on-ubuntu-14-04"

+	author = "Justin Ellingwood"

+	date = "2015-11-12"

+[[article]]

+	title = "How To Install and Use Hugo, a Static Site Generator, on Ubuntu 14.04"

+	url = "https://www.digitalocean.com/community/tutorials/how-to-install-and-use-hugo-a-static-site-generator-on-ubuntu-14-04"

+	author = "Justin Ellingwood"

+	date = "2015-11-09"

+[[article]]

+	title = "Switching from Wordpress to Hugo"

+	url = "http://justinfx.com/2015/11/08/switching-from-wordpress-to-hugo/"

+	author = "Justin Israel"

+	date = "2015-11-08"

+[[article]]

+	title = "Hands-on Experience with Hugo as a Static Site Generator"

+	url = "http://usersnap.com/blog/hands-on-experience-with-hugo-static-site-generator/"

+	author = "Thomas Peham"

+	date = "2015-10-15"

+[[article]]

+	title = "Statische Webseites mit Hugo erstellen/Vortrag mit Foliensatz (deutsch)"

+	url = "http://sfd.koelnerlinuxtreffen.de/2015/HaraldWeidner/"

+	author = "Harald Weidner"

+	date = "2015-09-19"

+[[article]]

+	title = "Moving from WordPress to Hugo"

+	url = "http://abhipandey.com/2015/09/moving-to-hugo/"

+	author = "Abhishek Pandey"

+	date = "2015-09-15"

+[[article]]

+	title = "<span lang='zh-CN'>通过webhook将Hugo自动部署至GitHub Pages和GitCafe Pages</span> <small>(Automated&nbsp;deployment)</small>"

+	url = "http://blog.coderzh.com/2015/09/13/use-webhook-automated-deploy-hugo/"

+	author = "CoderZh"

+	date = "2015-09-13"

+[[article]]

+	title = "<span lang='zh-CN'>使用hugo搭建个人博客站点</span> <small>(Using Hugo to build a personal blog site)</small>"

+	url = "http://blog.coderzh.com/2015/08/29/hugo/"

+	author = "CoderZh"

+	date = "2015-08-29"

+[[article]]

+	title = "Good-Bye Wordpress, Hello Hugo! <small>(German)</small>"

+	url = "http://blog.arminhanisch.de/2015/08/blog-migration-zu-hugo/"

+	author = "Armin Hanisch"

+	date = "2015-08-18"

+[[article]]

+	title = "Générer votre site web statique avec Hugo <small>(Generate your static site with Hugo)<small>"

+	url = "http://www.linux-pratique.com/?p=191"

+	author = "Benoît Benedetti"

+	date = "2015-06-26"

+[[article]]

+	title = "<span lang='ja'>Hugo向けの新しいテーマを作った</span> <small>(I created a new theme for Hugo)<small>"

+	url = "https://yet.unresolved.xyz/blog/2016/10/03/how-to-make-of-hugo-theme/"

+	author = "Daisuke Tsuji"

+	date = "2015-06-20"

+[[article]]

+	title = "Hugo - Gerando um site com conteúdo estático. (Portuguese Brazil)"

+	url = "http://blog.ffrizzo.com/posts/hugo/"

+	author = "Fabiano Frizzo"

+	date = "2015-06-02"

+[[article]]

+	title = "An Introduction to Static Site Generators"

+	url = "http://davidwalsh.name/introduction-static-site-generators"

+	author = "Eduardo Bouças"

+	date = "2015-05-20"

+[[article]]

+	title = "Hugo Still Rules"

+	url = "http://cheekycoder.com/2015/05/hugo-still-rules/"

+	author = "Cheeky Coder"

+	date = "2015-05-18"

+[[article]]

+	title = "hugo - Static Site Generator"

+	url = "http://gscacco.github.io/post/hugo/"

+	author = "G Scaccoio"

+	date = "2015-05-04"

+[[article]]

+	title = "<span lang='ja'>WindowsでHugoを使う</span>"

+	url = "http://ureta.net/2015/05/hugo-on-windows/"

+	author = "<span lang='ja'>うれ太郎</span>"

+	date = "2015-05-01"

+[[article]]

+	title = "<span lang='ja'>Hugoのshortcodesを用いてサイトにスライドなどを埋め込む</span>"

+	url = "http://blog.yucchiy.com/2015/04/29/hugo-shortcode/"

+	author = "Yucchiy"

+	date = "2015-04-29"

+[[article]]

+	title = "<span lang='ja'>HugoとCircleCIでGitHub PagesにBlogを公開してみたら超簡単だった</span>"

+	url = "http://hori-ryota.github.io/blog/create-blog-with-hugo-and-circleci/"

+	author = "Hori Ryota"

+	date = "2015-04-17"

+[[article]]

+	title = "10 Best Static Site Generators"

+	url = "http://beebom.com/2015/04/best-static-site-generators"

+	author = "Aniruddha Mysore"

+	date = "2015-04-06"

+[[article]]

+	title = "Goodbye WordPress; Hello Hugo"

+	url = "http://willwarren.com/2015/04/05/goodbye-wordpress-hello-hugo/"

+	author = "Will Warren"

+	date = "2015-04-05"

+[[article]]

+	title = "Static Websites with Hugo on Google Cloud Storage"

+	url = "http://www.moxie.io/post/static-websites-with-hugo-on-google-cloud-storage/"

+	author = "Moxie Input/Output"

+	date = "2015-04-02"

+[[article]]

+	title = "De nuevo iniciando un blog"

+	url = "https://alvarolizama.net/"

+	author = "Alvaro Lizama"

+	date = "2015-03-29"

+[[article]]

+	title = "We moved our blog from Posthaven to Hugo after only three posts. Why?"

+	url = "http://blog.hypriot.com/post/moved-from-posthaven-to-hugo/"

+	author = "Hypriot"

+	date = "2015-03-27"

+[[article]]

+	title = "Top Static Site Generators in 2015"

+	url = "http://superdevresources.com/static-site-generators-2015/"

+	author = "Kanishk Kunal"

+	date = "2015-03-12"

+[[article]]

+	title = "Moving to Hugo"

+	url = "http://abiosoft.com/moving-to-hugo/"

+	author = "Abiola Ibrahim"

+	date = "2015-03-08"

+[[article]]

+	title = "Migrating a blog (yes, this one!) from Wordpress to Hugo"

+	url = "http://justindunham.net/migrating-from-wordpress-to-hugo/"

+	author = "Justin Dunham"

+	date = "2015-02-13"

+[[article]]

+	title = "<span lang='ja'>blogをoctopressからHugoに乗り換えたメモ</span>"

+	url = "http://blog.jigyakkuma.org/2015/02/11/hugo/"

+	author = "jigyakkuma"

+	date = "2015-02-11"

+[[article]]

+	title = "<span lang='ja'>Hugoでブログをつくった</span>"

+	url = "http://porgy13.github.io/post/new-hugo-blog/"

+	author = "porgy13"

+	date = "2015-02-07"

+[[article]]

+	title = "<span lang='ja'>Hugoにブログを移行した</span>"

+	url = "http://keichi.net/post/first/"

+	author = "Keichi Takahashi"

+	date = "2015-02-04"

+[[article]]

+	title = "<span lang='zh-CN'>Hugo静态网站生成器中文教程</span>"

+	url = "http://nanshu.wang/post/2015-01-31/"

+	author = "Nanshu Wang"

+	date = "2015-01-31"

+[[article]]

+	title = "<span lang='ja'>Hugo + Github Pages + Wercker CI = ¥0（無料）<br>でコマンド 1 発（自動化）でサイト<br>・ブログを公開・運営・分析・収益化</span>"

+	url = "http://qiita.com/yoheimuta/items/8a619cac356bed89a4c9"

+	author = "Yohei Yoshimuta"

+	date = "2015-01-31"

+[[article]]

+	title = "Running Hugo websites on anynines"

+	url = "http://blog.anynines.com/running-hugo-websites-on-anynines/"

+	author = "Julian Weber"

+	date = "2015-01-30"

+[[article]]

+	title = "MiddlemanからHugoへ移行した"

+	url = "http://re-dzine.net/2015/01/hugo/"

+	author = "Haruki Konishi"

+	date = "2015-01-21"

+[[article]]

+	title = "WordPress から Hugo に乗り換えました"

+	url = "http://rakuishi.com/archives/wordpress-to-hugo/"

+	author = "rakuishi"

+	date = "2015-01-20"

+[[article]]

+	title = "HUGOを使ってサイトを立ち上げる方法"

+	url = "http://qiita.com/syui/items/869538099551f24acbbf"

+	author = "Syui"

+	date = "2015-01-17"

+[[article]]

+	title = "<span lang='ja'>Jekyllが許されるのは小学生までだよね</span>"

+	url = "http://t32k.me/mol/log/hugo/"

+	author = "Ishimoto Koji"

+	date = "2015-01-16"

+[[article]]

+	title = "Getting started with Hugo"

+	url = "http://anthonyfok.org/post/getting-started-with-hugo/"

+	author = "Anthony Fok"

+	date = "2015-01-12"

+[[article]]

+	title = "<span lang='zh-CN'>把这个博客静态化了</span> <small>(Migrate to Hugo)</small>"

+	url = "http://lich-eng.com/2015/01/03/migrate-to-hugo/"

+	author = "Li Cheng"

+	date = "2015-01-03"

+[[article]]

+	title = "Porting my blog with Hugo"

+	url = "http://blog.srackham.com/posts/porting-my-blog-with-hugo/"

+	author = "Stuart Rackham"

+	date = "2014-12-30"

+[[article]]

+	title = "Hugoを使ってみたときのメモ"

+	url = "http://machortz.github.io/posts/usinghugo/"

+	author = "Machortz"

+	date = "2014-12-29"

+[[article]]

+	title = "OctopressからHugoへ移行した"

+	url = "http://deeeet.com/writing/2014/12/25/hugo/"

+	author = "Taichi Nakashima"

+	date = "2014-12-25"

+[[article]]

+	title = "Migrating to Hugo From Octopress"

+	url = "http://nathanleclaire.com/blog/2014/12/22/migrating-to-hugo-from-octopress/"

+	author = "Nathan LeClaire"

+	date = "2014-12-22"

+[[article]]

+	title = "Dynamic Pages with GoHugo.io"

+	url = "http://cyrillschumacher.com/2014/12/21/dynamic-pages-with-gohugo.io/"

+	author = "Cyrill Schumacher"

+	date = "2014-12-21"

+[[article]]

+	title = "6 Static Blog Generators That Aren’t Jekyll"

+	url = "http://www.sitepoint.com/6-static-blog-generators-arent-jekyll/"

+	author = "David Turnbull"

+	date = "2014-12-08"

+[[article]]

+	title = "Travel Blogging Setup"

+	url = "http://www.stou.dk/2014/11/travel-blogging-setup/"

+	author = "Rasmus Stougaard"

+	date = "2014-11-23"

+[[article]]

+	title = "Hosting A Hugo Website Behind Nginx"

+	url = "http://www.bigbeeconsultants.co.uk/blog/hosting-hugo-website-behind-nginx"

+	author = "Rick Beton"

+	date = "2014-11-20"

+[[article]]

+	title = "<span lang='zh-CN'>使用Hugo搭建免费个人Blog</span> <small>(How to use Hugo)</small>"

+	url = "http://ulricqin.com/post/how-to-use-hugo/"

+	author = "Ulric Qin <span lang='zh-CN'>秦晓辉</span>"

+	date = "2014-11-11"

+[[article]]

+	title = "Built in Speed and Built for Speed by Hugo"

+	url = "http://cheekycoder.com/2014/10/built-for-speed-by-hugo/"

+	author = "Cheeky Coder"

+	date = "2014-10-30"

+[[article]]

+	title = "Hugo para crear sitios web estáticos"

+	url = "http://www.webbizarro.com/noticias/1076/hugo-para-crear-sitios-web-estaticos/"

+	author = "Web Bizarro"

+	date = "2014-08-19"

+[[article]]

+	title = "Going with hugo"

+	url = "http://www.markuseliasson.se/article/going-with-hugo/"

+	author = "Markus Eliasson"

+	date = "2014-08-18"

+[[article]]

+	title = "Benchmarking Jekyll, Hugo and Wintersmith"

+	url = "http://fredrikloch.me/post/2014-08-12-Jekyll-and-its-alternatives-from-a-site-generation-point-of-view/"

+	author = "Fredrik Loch"

+	date = "2014-08-12"

+[[article]]

+	title = "Goodbye Octopress, Hello Hugo!"

+	url = "http://andreimihu.com/blog/2014/08/11/goodbye-octopress-hello-hugo/"

+	author = "Andrei Mihu"

+	date = "2014-08-11"

+[[article]]

+	title = "Beautiful sites for Open Source projects"

+	url = "http://beautifulopen.com/2014/08/09/hugo/"

+	author = "Beautiful Open"

+	date = "2014-08-09"

+[[article]]

+	title = "Hugo: Beyond the Defaults"

+	url = "http://npf.io/2014/08/hugo-beyond-the-defaults/"

+	author = "Nate Finch"

+	date = "2014-08-08"

+[[article]]

+	title = "First Impressions of Hugo"

+	url = "https://peteraba.com/blog/first-impressions-of-hugo/"

+	author = "Peter Aba"

+	date = "2014-06-06"

+[[article]]

+	title = "New Site Workflow"

+	url = "http://vurt.co.uk/post/new_website/"

+	author = "Giles Paterson"

+	date = "2014-08-05"

+[[article]]

+	title = "How I Learned to Stop Worrying and Love the (Static) Web"

+	url = "http://cognition.ca/post/about-hugo/"

+	author = "Joshua McKenty"

+	date = "2014-08-04"

+[[article]]

+	title = "Hugo - Static Site Generator"

+	url = "http://kenwoo.io/blog/hugo---static-site-generator/"

+	author = "Kenny Woo"

+	date = "2014-08-03"

+[[article]]

+	title = "Hugo Is Friggin' Awesome"

+	url = "http://npf.io/2014/08/hugo-is-awesome/"

+	author = "Nate Finch"

+	date = "2014-08-01"

+[[article]]

+	title = "<span lang='zh-CN'>再次搬家</span> <small>(Move from WordPress to Hugo)</small>"

+	url = "http://www.chingli.com/misc/move-from-wordpress-to-hugo/"

+	author = "<span lang='zh-CN'>青砾</span> (chingli)"

+	date = "2014-07-12"

+[[article]]

+	title = "Embedding Gists in Hugo"

+	url = "http://danmux.com/posts/embedded_gists/"

+	author = "Dan Mull"

+	date = "2014-07-05"

+[[article]]

+	title = "An Introduction To Hugo"

+	url = "http://www.cirrushosting.com/web-hosting-blog/an-introduction-to-hugo/"

+	author = "Dan Silber"

+	date = "2014-07-01"

+[[article]]

+	title = "Moving to Hugo"

+	url = "http://danmux.com/posts/hugo_based_blog/"

+	author = "Dan Mull"

+	date = "2014-05-29"

+[[article]]

+	title = "<span lang='zh-CN'>开源之静态站点生成器排行榜</span><br><small>(Leaderboard of open-source static website generators)</small>"

+	url = "http://code.csdn.net/news/2819909"

+	author = "CSDN.net"

+	date = "2014-05-23"

+[[article]]

+	title = "Finally, a satisfying and effective blog setup"

+	url = "http://michaelwhatcott.com/now-powered-by-hugo/"

+	author = "Michael Whatcott"

+	date = "2014-05-20"

+[[article]]

+	title = "Hugo from scratch"

+	url = "http://zackofalltrades.com/notes/2014/05/hugo-from-scratch/"

+	author = "Zack Williams"

+	date = "2014-05-18"

+[[article]]

+	title = "Why I switched away from Jekyll"

+	url = "http://www.jakejanuzelli.com/why-I-switched-away-from-jekyll/"

+	author = "Jake Januzelli"

+	date = "2014-05-10"

+[[article]]

+	title = "Welcome our new blog"

+	url = "http://blog.ninya.io/posts/welcome-our-new-blog/"

+	author = "Ninya.io"

+	date = "2014-04-11"

+[[article]]

+	title = "Mission Not Accomplished"

+	url = "http://johnsto.co.uk/blog/mission-not-accomplished/"

+	author = "Dave Johnston"

+	date = "2014-04-03"

+[[article]]

+	title = "Hugo - A Static Site Builder in Go"

+	url = "http://deepfriedcode.com/post/hugo/"

+	author = "Deep Fried Code"

+	date = "2014-03-30"

+[[article]]

+	title = "Adventures in Angular Podcast"

+	url = "http://devchat.tv/adventures-in-angular/003-aia-gdes"

+	author = "Matias Niemela"

+	date = "2014-03-28"

+[[article]]

+	title = "Hugo"

+	url = "http://bra.am/post/hugo/"

+	author = "bra.am"

+	date = "2014-03-23"

+[[article]]

+	title = "Converting Blogger To Markdown"

+	url = "http://trishagee.github.io/project/atom-to-hugo/"

+	author = "Trisha Gee"

+	date = "2014-03-20"

+[[article]]

+	title = "Moving to Hugo Static Web Pages"

+	url = "http://tepid.org/tech/hugo-web/"

+	author = "Tobias Weingartner"

+	date = "2014-03-16"

+[[article]]

+	title = "New Blog Engine: Hugo"

+	url = "https://blog.afoolishmanifesto.com/posts/hugo/"

+	author = "fREW Schmidt"

+	date = "2014-03-15"

+[[article]]

+	title = "Hugo + gulp.js = Huggle"

+	url = "http://ktmud.github.io/huggle/en/intro/)"

+	author = "Jesse Yang <span lang='zh-CN'>杨建超</span>"

+	date = "2014-03-08"

+[[article]]

+	title = "Powered by Hugo"

+	url = "http://kieranhealy.org/blog/archives/2014/02/24/powered-by-hugo/"

+	author = "Kieran Healy"

+	date = "2014-02-24"

+[[article]]

+	title = "<span lang='ja'>静的サイトを素早く構築するために<br>GoLangで作られたジェネレータHugo</span>"

+	url = "http://hamasyou.com/blog/2014/02/21/hugo/"

+	author = "<div lang='ja' style='line-height: 1.1;'>Shogo Hamada<br>濱田章吾</div>"

+	date = "2014-02-21"

+[[article]]

+	title = "Latest Roundup of Useful Tools For Developers"

+	url = "http://codegeekz.com/latest-roundup-of-useful-tools-for-developers/"

+	author = "CodeGeekz"

+	date = "2014-02-13"

+[[article]]

+	title = "Hugo: Static Site Generator written in Go"

+	url = "http://www.braveterry.com/2014/02/06/hugo-static-site-generator-written-in-go/"

+	author = "Brave Terry"

+	date = "2014-02-06"

+[[article]]

+	title = "10 Useful HTML5 Tools for Web Designers and Developers"

+	url = "http://designdizzy.com/10-useful-html5-tools-for-web-designers-and-developers/"

+	author = "Design Dizzy"

+	date = "2014-02-04"

+[[article]]

+	title = "Hugo – Fast, Flexible Static Site Generator"

+	url = "http://cube3x.com/hugo-fast-flexible-static-site-generator/"

+	author = "Joby Joseph"

+	date = "2014-01-18"

+[[article]]

+	title = "Hugo: A new way to build static website"

+	url = "http://www.w3update.com/opensource/hugo-a-new-way-to-build-static-website.html"

+	author = "w3update"

+	date = "2014-01-17"

+[[article]]

+	title = "Xaprb now uses Hugo"

+	url = "http://xaprb.com/blog/2014/01/15/using-hugo/"

+	author = "Baron Schwartz"

+	date = "2014-01-15"

+[[article]]

+	title = "New jQuery Plugins And Resources That Web Designers Need"

+	url = "http://www.designyourway.net/blog/resources/new-jquery-plugins-and-resources-that-web-designers-need/"

+	author = "Design Your Way"

+	date = "2014-01-01"

+[[article]]

+	title = "On Blog Construction"

+	url = "http://alexla.sh/post/on-blog-construction/"

+	author = "Alexander Lash"

+	date = "2013-12-27"

+[[article]]

+	title = "Hugo"

+	url = "http://onethingwell.org/post/69070926608/hugo"

+	author = "One Thing Well"

+	date = "2013-12-05"

+[[article]]

+	title = "In Praise Of Hugo"

+	url = "http://sound-guru.com/blog/post/hello-world/"

+	author = "sound-guru.com"

+	date = "2013-10-19"

+[[article]]

+	title = "Hosting a blog on S3 and Cloudfront"

+	url = "http://www.danesparza.net/2013/07/hosting-a-blog-on-s3-and-cloudfront/"

+	author = "Dan Esparza"

+	date = "2013-07-24"

--- a/data/docs.json

+++ b/data/docs.json

@@ -6,7 +6,8 @@

         "String": "application/javascript+js",

         "MainType": "application",

         "SubType": "javascript",

-        "Suffix": "js"

+        "Suffix": "js",

+        "Delimiter": "."

},

         "Type": "application/json",

@@ -13,7 +14,8 @@

         "String": "application/json+json",

         "MainType": "application",

         "SubType": "json",

-        "Suffix": "json"

+        "Suffix": "json",

+        "Delimiter": "."

},

         "Type": "application/rss",

@@ -20,7 +22,8 @@

         "String": "application/rss+xml",

         "MainType": "application",

         "SubType": "rss",

-        "Suffix": "xml"

+        "Suffix": "xml",

+        "Delimiter": "."

},

         "Type": "application/xml",

@@ -27,7 +30,8 @@

         "String": "application/xml+xml",

         "MainType": "application",

         "SubType": "xml",

-        "Suffix": "xml"

+        "Suffix": "xml",

+        "Delimiter": "."

},

         "Type": "text/calendar",

@@ -34,7 +38,8 @@

         "String": "text/calendar+ics",

         "MainType": "text",

         "SubType": "calendar",

-        "Suffix": "ics"

+        "Suffix": "ics",

+        "Delimiter": "."

},

         "Type": "text/css",

@@ -41,7 +46,8 @@

         "String": "text/css+css",

         "MainType": "text",

         "SubType": "css",

-        "Suffix": "css"

+        "Suffix": "css",

+        "Delimiter": "."

},

         "Type": "text/csv",

@@ -48,7 +54,8 @@

         "String": "text/csv+csv",

         "MainType": "text",

         "SubType": "csv",

-        "Suffix": "csv"

+        "Suffix": "csv",

+        "Delimiter": "."

},

         "Type": "text/html",

@@ -55,7 +62,8 @@

         "String": "text/html+html",

         "MainType": "text",

         "SubType": "html",

-        "Suffix": "html"

+        "Suffix": "html",

+        "Delimiter": "."

},

         "Type": "text/plain",

@@ -62,7 +70,8 @@

         "String": "text/plain+txt",

         "MainType": "text",

         "SubType": "plain",

-        "Suffix": "txt"

+        "Suffix": "txt",

+        "Delimiter": "."

},

@@ -170,6 +179,21 @@

},

+        "Example": "AMP home, French language\".",

+        "OutputFormat": "AMP",

+        "Suffix": "html",

+        "Template Lookup Order": [

+          "layouts/index.fr.amp.html",

+          "layouts/index.amp.html",

+          "layouts/index.fr.html",

+          "layouts/index.html",

+          "layouts/_default/list.fr.amp.html",

+          "layouts/_default/list.amp.html",

+          "layouts/_default/list.fr.html",

+          "layouts/_default/list.html"

+        ]

+      },

+      {

         "Example": "JSON home, no theme.",

         "OutputFormat": "JSON",

         "Suffix": "json",

@@ -958,6 +982,19 @@

               "{{div 6 3}}",

"2"

+            ]

+          ]

+        },

+        "Log": {

+          "Description": "",

+          "Args": [

+            "a"

+          ],

+          "Aliases": null,

+          "Examples": [

+            [

+              "{{math.Log 1}}",

+              "0"

},

--- /dev/null

+++ b/data/homepagetweets.toml

@@ -1,0 +1,258 @@

+[[tweet]]

+name = "STOQE"

+twitter_handle = "@STOQE"

+quote = "I fear <a href='https://twitter.com/gohugoio' target='_blank'>@GoHugoIO</a> v0.22 might be so fast it creates a code vortex that time-warps me back to a time I used Wordpress. <a href='https://twitter.com/hashtag/gasp?src=hash'>#gasp</a>"

+link = "https://twitter.com/STOQE/status/874184881701494784"

+date = 2017-06-12T00:00:00Z

+[[tweet]]

+name = "Christophe Diericx"

+twitter_handle = "@spcrngr_"

+quote = "The more I use <a href='https://gohugo.io' target='_blank'>gohugo.io</a>, the more I really like it. Super intuitive/powerful static site generator...great job <a href='https://twitter.com/gohugoio' target='_blank'>@GoHugoIO</a>"

+link = "https://twitter.com/spcrngr_/status/870863020905435136"

+date = 2017-06-03T00:00:00Z

+[[tweet]]

+name = "marcoscan"

+twitter_handle = "@marcoscan"

+quote = "Blog migrated from <a href='https://twitter.com/WordPress' target='_blank'>@WordPress</a> to <a href='https://twitter.com/GoHugoIO' target='_blank'>@GoHugoIO</a>, with a little refresh of my theme, Vim shortcuts and a full featured deploy script <a href='https://twitter.com/hashtag/gohugo?src=hash' target='_blank'>#gohugo</a>"

+link = "https://twitter.com/marcoscan/status/869661175960752129"

+date = 2017-05-30T00:00:00Z

+[[tweet]]

+name = "Sandra Kuipers"

+twitter_handle = "@SKuipersDesign"

+quote = "Who knew static site building could be fun 🤔 Learning <a href='https://twitter.com/hashtag/gohugo?src=hash'>#gohugo</a> today"

+link = "https://twitter.com/SKuipersDesign/status/868796256902029312"

+date = 2017-05-28T00:00:00Z

+[[tweet]]

+name = "Netlify"

+twitter_handle = "@Netlify"

+quote = "Top Ten Static Site Generators of 2017. Congrats to the top 3: 1. <a href='https://twitter.com/jekyllrb'>@Jekyllrb</a> 2. <a href='https://twitter.com/GoHugoIO'>@GoHugoIO</a> 3. <a href='https://twitter.com/hexojs'>@hexojs</a>"

+link = "https://twitter.com/Netlify/status/868122279221362688"

+date = 2017-05-26T00:00:00Z

+[[tweet]]

+name = "Phil Hawksworth"

+twitter_handle = "@philhawksworth"

+quote = "I've been keen on <a href='https://twitter.com/hashtag/JAMStack?src=hash' target='_blank'>#JAMStack</a> for some time, but <a href='https://twitter.com/gohugoio' target='_blank'>@GoHugoIO</a> is wooing me all over again. Great fun to build with. And speeeeedy."

+link = "https://twitter.com/philhawksworth/status/866684170512326657"

+date = 2017-05-22T00:00:00Z

+[[tweet]]

+name = "Aras Pranckevicius"

+twitter_handle = "@aras_p"

+quote = "I've probably said it before...but having Hugo rebuild the whole website in 300ms is amazing. <a href='https://gohugo.io' target='_blank'>gohugo.io</a>, <a href='https://twitter.com/hashtag/gohugo' target='_blank'>#gohugo</a>"

+link = "https://twitter.com/aras_p/status/861157286823288832"

+date = 2017-05-07T00:00:00Z

+[[tweet]]

+name = "Hans Beck"

+twitter_handle = "@EnrichedGamesHB"

+quote = "Diving deeper into <a href='https://twitter.com/GoHugoIO' target='_blank' rel='noopener noreferrer'>@GoHugoIO</a>. A lot of docs there, top work! But I've the impressed that <a href='https://twitter.com/hashtag/gohugo' target='_blank' rel='noopener noreferrer'>#gohugo</a> is far easier than its feels from the docs!"

+link = "https://twitter.com/EnrichedGamesHB/status/836854762440130560"

+date = 2017-03-01T00:00:00Z

+[[tweet]]

+name = "Alan Richardson"

+twitter_handle = "@eviltester"

+quote = "I migrated the <a href='https://twitter.com/BlackOpsTesting' target='_blank' rel='noopener noreferrer'> @BlackOpsTesting </a>.com website from docpad to Hugo last weekend. http://gohugo.io/ Super Fast HTML Generation <a href='https://twitter.com/spf13' target='_blank' rel='noopener noreferrer'> @spf13 </a>"

+link = "https://twitter.com/eviltester/status/553520335115808768"

+date = 2015-01-09T00:00:00Z

+[[tweet]]

+name = "Janez Čadež‏"

+twitter_handle = "@jamziSLO"

+quote = "Building <a href='https://twitter.com/garazaFRI' target='_blank' rel='noopener noreferrer'>@garazaFRI</a> website in <a href='https://twitter.com/hashtag/hugo' target='_blank' rel='noopener noreferrer'>#hugo</a>. This static site generator is soooo damn fast! <a href='https://twitter.com/hashtag/gohugo' target='_blank' rel='noopener noreferrer'>#gohugo</a> <a href='https://twitter.com/hashtag/golang' target='_blank' rel='noopener noreferrer'>#golang</a>"

+link = "https://twitter.com/jamziSLO/status/817720283977183234"

+date = 2017-01-07T00:00:00Z

+[[tweet]]

+name = "Execute‏‏"

+twitter_handle = "@executerun"

+quote = "Hah, <a href='https://twitter.com/hashtag/gohugo' target='_blank' rel='noopener noreferrer'>#gohugo</a>. I was working with <a href='https://twitter.com/hashtag/gohugo' target='_blank' rel='noopener noreferrer'>#gohugo</a> on <a href='https://twitter.com/hashtag/linux' target='_blank' rel='noopener noreferrer'>#linux</a> but now I realised how easy is to set-up it on <a href='https://twitter.com/hashtag/windows' target='_blank' rel='noopener noreferrer'>#windows</a>. Just need to add binary to <a href='https://twitter.com/hashtag/path' target='_blank' rel='noopener noreferrer'>#path</a>!"

+link = "https://twitter.com/executerun/status/809753145270272005"

+date = 2016-12-16T00:00:00Z

+[[tweet]]

+name = "Baron Schwartz"

+twitter_handle = "@xaprb"

+quote = "Hugo is impressively capable. It's a static site generator by <a href='https://twitter.com/spf13'> @spf13 </a> written in <a href='https://twitter.com/hashtag/golang?src=hash'> #golang </a> . Just upgraded to latest release; very powerful.  "

+link = "https://twitter.com/xaprb/status/556894866488455169"

+date = 2015-01-18T00:00:00Z

+[[tweet]]

+name = "Dave Cottlehuber"

+twitter_handle = "@dch__"

+quote = "I just fell in love with #hugo, a static site/blog engine written by @spf13 in #golang  + stellar docs"

+link = "https://twitter.com/dch__/status/460158115498176512"

+date = 2014-04-26T00:00:00Z

+[[tweet]]

+name = "David Caunt"

+twitter_handle = "@dcaunt"

+quote = "I had a play with Hugo and it was good, uses Markdown files for content"

+link = "https://twitter.com/dcaunt/statuses/406466996277374976"

+date = 2013-11-29T00:00:00Z

+[[tweet]]

+name = "David Gay"

+twitter_handle = "@oddshocks"

+quote = "Hugo is super-rad."

+link = "https://twitter.com/oddshocks/statuses/405083217893421056"

+date = 2013-11-25T00:00:00Z

+[[tweet]]

+name = "Diti"

+twitter_handle = "@DitiPengi"

+quote = "The dev version of Hugo is AWESOME! &lt;3 I promise, I will try to learn go ASAP and help contribute to the project! Just too great!"

+link = "https://twitter.com/DitiPengi/status/472470974051676160"

+date = 2014-05-30T00:00:00Z

+[[tweet]]

+name = "Douglas Stephen "

+twitter_handle = "@DougStephenJr"

+quote = "Even as a long-time Octopress fan, I’ve gotta admit that this project Hugo looks very very cool"

+link = "https://twitter.com/DougStephenJr/statuses/364512471660249088"

+date = 2013-08-05T00:00:00Z

+[[tweet]]

+name = "Hugo Rodger-Brown"

+twitter_handle = "@hugorodgerbrown"

+quote = "Finally someone builds me my own static site generator"

+link = "https://twitter.com/hugorodgerbrown/statuses/364417910153818112"

+date = 2013-05-08T00:00:00Z

+[[tweet]]

+name = "Hugo Roy"

+twitter_handle = "@hugoroyd"

+quote = "Finally the answer to the question my parents have been asking: What does Hugo do?"

+link = "https://twitter.com/hugoroyd/status/501704796727173120"

+date = 2014-08-19T00:00:00Z

+[[tweet]]

+name = "Daniel Miessler"

+twitter_handle = "@DanielMiessler"

+quote = "Websites for named vulnerabilities should run on static site generator platforms like Hugo. Read-only + burst traffic = static."

+link = "https://twitter.com/DanielMiessler/status/704703841673957376"

+date = 2016-03-01T00:00:00Z

+[[tweet]]

+name = "Javier Segura"

+twitter_handle = "@jsegura"

+quote = "Another site generated with Hugo here! I'm getting in love with it."

+link = "https://twitter.com/jsegura/status/465978434154659841"

+date = 2014-05-12T00:00:00Z

+[[tweet]]

+name = "Jim Biancolo"

+twitter_handle = "@jimbiancolo"

+quote = "I’m loving the static site generator renaissance we are currently enjoying. Hugo is new, looks great, written in Go"

+link = "https://twitter.com/jimbiancolo/statuses/408678420348813314"

+date = 2013-05-12T00:00:00Z

+[[tweet]]

+name = "Jip J. Dekker"

+twitter_handle = "@jipjdekker"

+quote = "Building a personal website in Hugo. Works like a charm. And written in @golang!"

+link = "https://twitter.com/jipjdekker/status/413783548735152131"

+date = 2013-12-19T00:00:00Z

+[[tweet]]

+name = "Jose Gonzalvo"

+twitter_handle = "@jgonzalvo"

+quote = "Checking out Hugo; Loving it so far. Like Jekyll but not so blog-oriented and written in go"

+link = "https://twitter.com/jgonzalvo/statuses/408177855819173888"

+date = 2013-12-04T00:00:00Z

+[[tweet]]

+name = "Josh Matz"

+twitter_handle = "@joshmatz"

+quote = "A static site generator without the long build times? Yes, please!"

+link = "https://twitter.com/joshmatz/statuses/364437436870696960"

+date = 2013-08-05T00:00:00Z

+[[tweet]]

+name = "Kieran Healy"

+twitter_handle = "@kjhealy"

+quote = "OK, so in today's speed battle of static site generators, @spf13's hugo is kicking everyone's ass, by miles."

+link = "https://twitter.com/kjhealy/status/437349384809115648"

+date = 2014-02-22T00:00:00Z

+[[tweet]]

+name = "Ludovic Chabant"

+twitter_handle = "@ludovicchabant"

+quote = "Good work on Hugo, I’m impressed with the speed!"

+link = "https://twitter.com/ludovicchabant/statuses/408806199602053120"

+date = 2013-12-06T00:00:00Z

+[[tweet]]

+name = "Luke Holder"

+twitter_handle = "@lukeholder"

+quote = "this is AWESOME. a single little executable and so fast."

+link = "https://twitter.com/lukeholder/status/430352287936946176"

+date = 2014-02-03T00:00:00Z

+[[tweet]]

+name = "Markus Eliasson"

+twitter_handle = "@markuseliasson"

+quote = "Hugo is fast, dead simple to setup and well documented"

+link = "https://twitter.com/markuseliasson/status/501594865877008384"

+date = 2014-08-19T00:00:00Z

+[[tweet]]

+name = "mercime"

+twitter_handle = "@mercime_one"

+quote = "Hugo: Makes the Web Fun Again"

+link = "https://twitter.com/mercime_one/status/500547145087205377"

+date = 2014-08-16T00:00:00Z

+[[tweet]]

+name = "Michael Whatcott"

+twitter_handle = "@mdwhatcott"

+quote = "One more satisfied #Hugo blogger. Thanks @spf13 and friends!"

+link = "https://twitter.com/mdwhatcott/status/469980686531571712"

+date = 2014-05-23T00:00:00Z

+[[tweet]]

+name = "Nathan Toups"

+twitter_handle = "@rojoroboto"

+quote = "I love Hugo! My site is generated with it now http://rjrbt.io"

+link = "https://twitter.com/rojoroboto/status/423439915620106242"

+date = 2014-01-15T00:00:00Z

+[[tweet]]

+name = "Ruben Solvang"

+twitter_handle = "@messo85"

+quote = "#Hugo is the new @jekyllrb / @middlemanapp! Faster, easier and runs everywhere."

+link = "https://twitter.com/messo85/status/472825062027182081"

+date = 2014-05-31T00:00:00Z

+[[tweet]]

+name = "Ryan Martinsen"

+twitter_handle = "@popthestack"

+quote = "Also, I re-launched my blog (it looks the same as before) using Hugo, a *fast* static engine. Very happy with it.  <a href='http://gohugo.io/'>gohugo.io</a>"

+link = "https://twitter.com/popthestack/status/549972754125307904"

+date = 2014-12-30T00:00:00Z

+[[tweet]]

+name = "The Lone Cuber"

+twitter_handle = "@TheLoneCuber"

+quote = "Jekyll is dead to me these days though... long live Hugo! Hugo is *by far* the best in its field. Thanks for making it happen."

+link = "https://twitter.com/TheLoneCuber/status/495716684456398848"

+date = 2014-08-02T00:00:00Z

+[[tweet]]

+name = "The Lone Cuber"

+twitter_handle = "@TheLoneCuber"

+quote = "Finally, a publishing platform that's a joy to use. #NoMoreBarriers"

+link = "https://twitter.com/TheLoneCuber/status/495731334711488512"

+date = 2014-08-02T00:00:00Z

+[[tweet]]

+name = "WorkHTML"

+twitter_handle = "@workhtml"

+quote = "<a href='https://twitter.com/hashtag/Hugo?src=hash'> #Hugo </a> A very good alternative for <a href='https://twitter.com/hashtag/wordpress?src=hash'> #wordpress </a> !!! A fast and modern static website engine <a href='http://gohugo.io/'> gohugo.io </a>"

+link = "https://twitter.com/workhtml/status/563064361301053440"

+date = 2015-02-04T00:00:00Z

--- a/layouts/404.html

+++ /dev/null

@@ -1,5 +1,0 @@

-{{ partial "header.html" . }}

-<div class="col-lg-8 col-md-12">

-Page Not Found.

-</div>

-{{ partial "footer.html" . }}

--- a/layouts/_default/baseof.html

+++ /dev/null

@@ -1,12 +1,0 @@

-{{ partial "header.html" . }}

-{{ if .Params.toc }}

-<div class="col-lg-8 col-md-12">

-{{block "main" .}}{{end}}

-</div>

-<div id="toc" class="col-lg-offset-6 toc {{ if gt (len .TableOfContents) 2500 }}compact{{ end }}">

-    {{ .TableOfContents }}

-</div>

-{{ else }}

-{{block "main" .}}{{end}}

-{{ end }}

-{{ partial "footer.html" . }}

--- a/layouts/_default/list.html

+++ /dev/null

@@ -1,12 +1,0 @@

-{{ define "main" }}

-{{ with .Content }}

-{{ . }}

-{{ end }}

-<ul style="margin-top: 20px">

-    {{ range .Data.Pages }}

-    <li>

-         <a href="{{ .Permalink }}">{{ .Title }}</a> <em>Updated {{ .Lastmod.Format "Mon, Jan 2, 2006" }}</em>

-    </li>

-    {{ end }}

-</ul>

-{{ end }}

--- a/layouts/_default/single.html

+++ /dev/null

@@ -1,1 +1,0 @@

-{{ define "main" }}{{ .Content }}{{ end }}

--- a/layouts/index.html

+++ /dev/null

@@ -1,319 +1,0 @@

-<!DOCTYPE html>

-<html lang="en">

-  <head>

-    <meta charset="utf-8">

-    <meta name="viewport" content="width=device-width, initial-scale=1.0">

-    <meta name="description" content="Hugo, a fast and flexible static site generator built with love by spf13, bep, and friends in Go">

-    <meta name="author" content="Steve Francia (spf13), Bjørn Erik Pedersen (bep), and friends">

-    <title>Hugo :: A fast and modern static website engine</title>

-    {{ "<!--icon for browser shortcuts-->" | safeHTML }}

-    <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico">

-    {{ "<!--icon to represent this web page on Apple iOS-->" | safeHTML }}

-    <link rel="apple-touch-icon" href="/apple-touch-icon.png">

-    {{ "<!--Bootstrap core CSS-->" | safeHTML }}

-    <link rel="stylesheet" type="text/css" href="/css/bootstrap-stripped-gohugo.css">

-    <link rel="stylesheet" type="text/css" href="/css/bootstrap-changes-gohugo.css">

-    <link rel="stylesheet" type="text/css" href="/css/bootstrap-additions-gohugo.css">

-    {{ "<!--non-Bootstrap CSS (keep below Bootstrap CSS)-->" | safeHTML }}

-    <link rel="stylesheet" type="text/css" href="/vendor/OwlCarousel2/css/owl.carousel.css">

-    <link rel="stylesheet" type="text/css" href="/vendor/OwlCarousel2/css/owl.theme.default.css">

-    <link rel="stylesheet" type="text/css" href="//fonts.googleapis.com/css?family=Arbutus+Slab%7CCabin:600%7CSource+Code+Pro">

-    <link rel="stylesheet" type="text/css" href="/css/hugofont.css">

-    <link rel="stylesheet" type="text/css" href="/css/home-page-style.css">

-    <link rel="stylesheet" type="text/css" href="/css/home-page-style-responsive.css">

-  </head>

-  <body>

-    {{ "<!--full page image header area start-->" | safeHTML }}

-    <div id="top" class="header">

-      <div class="vert-text">

-        <a href="#intro">

-            <img class="logo" src="/img/hugo.png" alt="Hugo logo">

-        </a>

-        <div class="buttonbox">

-            <a class="btn-primary btn btn-lg" href="/overview/introduction/">

-                Docs <i class="icon-idea"></i>

-            </a>

-            <a class="btn-success btn btn-lg" href="#action">

-                Install <i class="icon-arrow-down"></i>

-            </a>

-            <a class="btn-info btn btn-lg" href="https://discourse.gohugo.io/">

-                Community <i class="icon-talking"></i>

-            </a>

-            <a class="btn-repo btn btn-lg" href="https://github.com/gohugoio/hugo">

-                GitHub <i class="icon-circlestar"></i>

-            </a>

-        </div>

-      </div>

-    </div>

-    {{ "<!--full page image header area end-->" | safeHTML }}

-    {{ "<!--main start-->" | safeHTML }}

-    <div id="main">

-        {{ "<!--intro start-->" | safeHTML }}

-        <div id="intro" class="counterpoint">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-6 col-md-offset-3">

-                  <i class="lead-icon icon-pacman"></i>

-                <h2>Make the Web Fun Again</h2>

-                <p class="lead">

-                    Introducing Hugo, a new idea for making website creation simple again.

-                    Hugo works flexibly with many formats, and is ideal for

-                    blogs, docs, portfolios and much more.

-                    Hugo’s speed fosters

-                    creativity&mdash;it makes building a website fun again.

-                </p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--intro end-->" | safeHTML }}

-        {{ "<!--point start-->" | safeHTML }}

-        <div class="point">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-6 col-md-offset-3">

-                  <i class="point-icon icon-tux"></i>

-                  <i class="point-icon icon-apple"></i>

-                  <i class="point-icon icon-windows8"></i>

-                <h2>Run Anywhere</h2>

-                <p class="lead">

-                Hugo is quite possibly the easiest software to install you’ve ever used:

-                simply download and run!

-                <b>

-                Hugo doesn’t depend on administrative privileges, databases, runtimes,

-                interpreters or external libraries.

-                </b>

-                Sites built with Hugo can be deployed on S3, GitHub Pages, Dropbox or any web host.

-                </p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--point end-->" | safeHTML }}

-        {{ "<!--counterpoint start-->" | safeHTML }}

-        <div class="counterpoint">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-6 col-md-offset-3">

-                  <i class="lead-icon icon-rocket"></i>

-                <h2>Fast &amp; Powerful</h2>

-                <p class="lead">

-                Hugo is designed for speed and performance. Great care has been

-                taken to ensure build time with Hugo is as short as possible.

-                We’re talking milliseconds to build your entire site&mdash;for most setups!

-                </p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--counterpoint end-->" | safeHTML }}

-        {{ "<!--point start-->" | safeHTML }}

-        <div class="point">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-6 col-md-offset-3">

-                  <i class="point-icon icon-fork"></i>

-                <h2>Flexible</h2>

-                <p class="lead">

-                Hugo is designed to work the way you do.

-                Organize your content however you want with any URL structure.

-                Group your content using your own indexes and categories.

-                Define your own metadata in any format: YAML, TOML or JSON.

-                Best of all, Hugo handles all these variations

-                with virtually no configuration. Hugo

-                just works.

-                </p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--point end-->" | safeHTML }}

-        {{ "<!--quote carousel start-->" | safeHTML }}

-        <div class="callout">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-12">

-                  <i class="callout-icon icon-circlestar"></i>

-                  <p></p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-12">

-                  {{ "<!--wrapper for slides start-->" | safeHTML }}

-                  <div class="carousel-inner owl-carousel">

-{{ partial "quotes.html" ((where $.Site.Data.references.quotes "date" "ge" (now.AddDate -2 0 0) | shuffle )) }}

-                  </div>

-                  {{ "<!--wrapper for slides end-->" | safeHTML }}

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--quote carousel end-->" | safeHTML }}

-    </div>

-    {{ "<!--main end-->" | safeHTML }}

-        {{ "<!--counterpoint start-->" | safeHTML }}

-        <div class="counterpoint">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-6 col-md-offset-3">

-                  <i class="lead-icon icon-octocat"></i>

-                <h2>Open and Free</h2>

-                <p class="lead">

-                    Hugo is <a href="https://github.com/gohugoio/hugo">open source</a> and completely free.

-                </p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--counterpoint end-->" | safeHTML }}

-        {{ "<!--point start-->" | safeHTML }}

-        <div class="point">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-6 col-md-offset-3">

-                  <i class="point-icon icon-beaker-alt"></i>

-                  <i class="point-icon icon-heart"></i>

-                  <i class="point-icon icon-spf13"></i>

-                  <h2>Built with <i class="icon-heart"></i></h2>

-                <p class="lead">

-                Hugo is developed with love by <a href="http://spf13.com">spf13</a> and friends.

-                We welcome all contributions.

-                    New to Go? We’ll help you.

-                    Not a developer? No problem! Help

-                with <a href="/overview/introduction/">docs,</a> testing

-                and <a href="https://github.com/gohugoio/hugoThemes/">themes.</a>

-                </p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--counterpoint end-->" | safeHTML }}

-        {{ "<!--call to action start-->" | safeHTML }}

-        <div id="action" class="call-to-action">

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-10 col-md-offset-1">

-                <h1>Getting Started</h1>

-                <a class="btn-primary btn btn-lg" href="https://github.com/gohugoio/hugo/releases">

-                    Download

-                    <i class="icon-arrow-down"></i>

-                </a>

-                <a class="quickstart" href="/overview/quickstart/">

-                    Quickstart Guide

-                </a>

-                <p>&nbsp;</p>

-                <h4>Using Homebrew?</h4>

-                <pre><code>brew install hugo</code></pre>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </div>

-        {{ "<!--call to action end-->" | safeHTML }}

-        {{ "<!--footer start-->" | safeHTML }}

-        <footer>

-          <div class="container">

-            {{ "<!--row start-->" | safeHTML }}

-            <div class="row">

-              <div class="text-center col-md-6 col-md-offset-3">

-                <ul class="list-inline">

-                    <li><a class="icon-twitter icon-2x" href="https://twitter.com/gohugoio"></a></li>

-                    <li><a class="icon-octocat icon-2x" href="https://github.com/gohugoio/hugo"></a></li>

-                </ul>

-                <hr>

-                <p>Copyright &copy; Steve Francia 2013&ndash;{{ now.Format "2006" }}</p>

-              </div>

-            </div>

-            {{ "<!--row end-->" | safeHTML }}

-          </div>

-        </footer>

-        {{ "<!--footer end-->" | safeHTML }}

-  {{ "<!--JavaScript: Keep at the end of the document so the page loads faster-->" | safeHTML }}

-  <script src="/vendor/jquery/js/jquery-2.1.4.min.js"></script>

-  {{ "<!--Bootstrap core JavaScript here-->" | safeHTML }}

-  {{ `<!--<script src="/vendor/twitter/js/bootstrap.min.js"></script>-->` | safeHTML }}

-  <script src="/vendor/OwlCarousel2/js/owl.carousel.min.js"></script>

-  <script src="/js/owl.carousel-custom.js"></script>

-  {{ "<!--custom JavaScript-->" | safeHTML }}

-  <script>

-    $(function() {

-        $('a[href*=#]:not([href=#])').click(function() {

-          if (location.pathname.replace(/^\//,'') == this.pathname.replace(/^\//,'')

-              || location.hostname == this.hostname) {

-            var target = $(this.hash);

-            target = target.length ? target : $('[name=' + this.hash.slice(1) +']');

-            if (target.length) {

-              $('html,body').animate({

-                scrollTop: target.offset().top

-              }, 1000);

-              return false;

-            }

-          }

-        });

-      });

-  </script>

-{{ "<!--Google analytics-->" | safeHTML }}

-{{ template "partials/analytics.html" . }}

-  </body>

-</html>

--- a/layouts/index.redir

+++ /dev/null

@@ -1,6 +1,0 @@

-# Netlify redirects. See https://www.netlify.com/docs/redirects/

-{{  range $p := .Site.Pages -}}

-{{ range .Aliases }}

-{{  . | printf "%-35s" }}	{{ $p.RelPermalink -}}

-{{ end -}}

-{{- end -}}

--- a/layouts/partials/analytics.html

+++ /dev/null

@@ -1,10 +1,0 @@

-<script>

-  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){

-  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),

-  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)

-  })(window,document,'script','//www.google-analytics.com/analytics.js','ga');

-  ga('create', 'UA-7131036-4', 'spf13.com');

-  ga('send', 'pageview');

-</script>

--- a/layouts/partials/footer.html

+++ /dev/null

@@ -1,59 +1,0 @@

-                    <div class="row">

-                        <div class="footer-panel">

-			  <p>Last revision: {{ .Lastmod.Format "January 2, 2006" }}{{ if .IsPage }}{{ with .GitInfo }} | <a href="https://github.com/gohugoio/hugoDocs/commit/{{ .Hash }}">{{ .Subject }} ({{ .AbbreviatedHash }})</a>{{end }}{{ end }}

-                          <span style="float: right;">Hugo v{{ .Site.Params.release }} documentation</span>

-                        </p>

-                        {{ with  getenv "REPOSITORY_URL" -}}

-                        <a href="https://www.netlify.com" style="float: right; padding-right: 20px;">

-                        <img src="https://www.netlify.com/img/global/badges/netlify-color-bg.svg"/>

-                        </a>

-                        {{- end }}

-                        </div>

-                    </div>

-                    </div>

-                    </section>

-                    </div>

-                <div class="col-md-1">

-                    {{ if .IsPage }}

-                    {{ with .GetParam "next" }}

-                    <a class="navigation next" href="{{.}}">

-                        <i class="fa fa-angle-right"> </i>

-                    </a>

-                    {{ end }}

-                    {{ end }}

-                </div>

-              </div>

-              <!-- page start-->

-          </section>

-      </section>

-     <!--main content end-->

-  </section>

-  <!-- container section end -->

-    <!-- javascripts -->

-    <script type="text/javascript" src="/vendor/jquery/js/jquery-2.1.4.min.js"></script>

-    <script type="text/javascript" src="/vendor/flesler/js/jquery.scrollTo.min.js"></script>

-    <script type="text/javascript" src="/vendor/twitter/js/bootstrap.min.js"></script>

-    <!--custom script for all page-->

-    <script type="text/javascript" src="/vendor/highlightjs/js/highlight.pack.js"></script>

-    <script>hljs.initHighlightingOnLoad();</script>

-    <script src="/js/scripts.js"></script>

-    <!-- Algolia search -->

-    <script type="text/javascript" src="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.js"></script>

-    <script type="text/javascript">

-    docsearch({

-      apiKey: '167e7998590aebda7f9fedcf86bc4a55',

-      indexName: 'hugodocs',

-      inputSelector: '#search-input',

-      algoliaOptions: {

-        hitsPerPage: 5

-      }

-    });

-    </script>

-    <!-- Google Analytics -->

-    {{ template "partials/analytics.html" . }}

-  </body>

-</html>

--- a/layouts/partials/header.html

+++ /dev/null

@@ -1,93 +1,0 @@

-<!DOCTYPE html>

-<html lang="en">

-  <head>

-    <meta charset="utf-8">

-    <meta name="viewport" content="width=device-width, initial-scale=1.0">

-    <meta name="description" content="{{ with .Description }}{{ . }}{{ else }}{{ with .Site.Params.description }}{{ . }}{{ end }}{{ end }}">

-    {{ with .Site.Params.author }}<meta name="author" content="{{ . }}">{{ end }}

-    {{ .Hugo.Generator }}

-    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />

-{{ .Scratch.Add "title" "" }}{{ if isset .Site.Data.titles .Title }}{{ .Scratch.Set "title" (index .Site.Data.titles .Title).title }}{{ else }}{{ .Scratch.Set "title" .Title}}{{end}}

-    <title>Hugo - {{ .Scratch.Get "title" }}</title>

-    <link rel="stylesheet" type="text/css" href="/css/bootstrap-stripped-gohugo.css">

-    <link rel="stylesheet" type="text/css" href="/css/bootstrap-changes-gohugo.css">

-    <link rel="stylesheet" type="text/css" href="/css/bootstrap-additions-gohugo.css">

-    <link rel="stylesheet" type="text/css" href="/vendor/font-awesome/css/font-awesome.min.css">

-    <link rel="stylesheet" href="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css" />

-    <link href="/css/style.css" rel="stylesheet">

-    <link rel="stylesheet" type="text/css" href="/css/content-style.css" />

-    <link href="/css/style-responsive.css" rel="stylesheet" />

-    <link rel="stylesheet" type="text/css" href="/vendor/highlightjs/css/monokai-sublime.css">

-  </head>

-  <body>

-  <!-- container section start -->

-  <section id="container" class="">

-      <!--header start-->

-      <header class="header black-bg">

-            <div class="toggle-nav">

-                <i class="fa fa-bars"></i>

-                <div class="icon-reorder tooltips" data-original-title="Toggle Navigation" data-placement="bottom"></div>

-            </div>

-            <!--logo start-->

-            <a href="/" class="logo"><img src="/img/hugo-logo.png" style="height: 40px; vertical-align: bottom;"> <span style="font-size: small; text-transform: none;">v{{ .Site.Params.release }}</span></a>

-            <!--logo end-->

-            <div class="top-nav notification-row">

-                <!-- notification dropdown end-->

-                <div class="hidden-xs nav-github pull-right">

-                    <span rel="show-github" data-user="bep" data-type="follow"></span>

-                    <span rel="show-github" data-user="spf13" data-type="follow"></span>

-                    <span rel="show-github" data-user="spf13" data-repo="hugo"></span>

-                </div>

-            </div>

-            <div class="nav title-row" id="top_menu">

-                <h1 class="nav top-menu">{{ .Scratch.Get "title" }}</h1>

-            </div>

-      </header>

-      <!--header end-->

-{{ partial "menu.html" . }}

-      <!--main content start-->

-      <section id="main-content">

-          <section class="wrapper">

-              <!--<div class="row">-->

-                  <!--<div class="col-lg-12">-->

-                      <!--breadcrumbs start -->

-                      <!--<ul class="breadcrumb">-->

-                          <!--<li><a href="#"><i class="icon_house_alt"></i> Home</a></li>-->

-                          <!--<li><a href="#"> UI Kit</a></li>-->

-                          <!--<li class="active"> General</li>-->

-                      <!--</ul>-->

-                      <!--breadcrumbs end -->

-                  <!--</div>-->

-              <!--</div>-->

-              <div class="row">

-                  <div class="col-md-1">

-                      {{ if .IsPage }}

-                      {{ with .GetParam "prev" }}

-                      <a class="navigation prev" href="{{.}}">

-                      <i class="fa fa-angle-left"></i>

-                      </a>

-                      {{ end }}

-                      {{ end }}

-                  </div>

-                <div class="col-md-10">

-                    <section class="panel">

-                          <!--<header class="panel-heading">-->

-                              <!--<h3>{{ .Scratch.Get "title" }}</h3>-->

-                          <!--</header>-->

-                    <div class="panel-body">

-                        <div class="row">

-                            <div class="col-lg-8 col-lg-offset-2 cse">

-                                {{ partial "search.html" . }}

-                            </div>

-                        </div>

--- a/layouts/partials/menu.html

+++ /dev/null

@@ -1,40 +1,0 @@

-<!--sidebar start-->

-<aside>

-    <div id="sidebar" class="nav-collapse">

-        <!-- sidebar menu start-->

-        <ul class="sidebar-menu">

-          {{ $currentNode := . }}

-          {{ range .Site.Menus.main }}

-              {{ if .HasChildren }}

-            <li class="sub-menu{{if $currentNode.HasMenuCurrent "main" . }} active{{end}}">

-            <a href="javascript:;" class="">

-                {{ .Pre }}

-                <!--<i class="icon_desktop"></i>-->

-                <span>{{ .Name }}</span>

-                <span class="menu-arrow fa {{if $currentNode.HasMenuCurrent "main" . }}fa-angle-down{{else}}fa-angle-right{{end}}"></span>

-            </a>

-                <ul class="sub{{if $currentNode.HasMenuCurrent "main" . }} open{{end}}">

-                    {{ range .Children }}

-                    <li{{if $currentNode.IsMenuCurrent "main" . }} class="active"{{end}}><a href="{{.URL}}">{{ .Name }}</a> </li>

-                    {{ end }}

-                </ul>

-              {{else}}

-                <li>

-                <a class="" href="{{.URL}}">

-                    {{ .Pre }}

-                    <!--<i class="icon_house_alt"></i>-->

-                    <span>{{ .Name }}</span>

-                </a>

-              {{end}}

-              </li>

-          {{end}}

-            <li> <a href="https://github.com/gohugoio/hugo/issues" target="blank"><i class='fa fa-life-ring'></i> <span>Issues & Help</span></a> </li>

-            {{ if .IsPage }}

-            {{ $File := .File }}  {{with $File.Path }}<li><a href="https://github.com/gohugoio/hugoDocs/edit/master/content/{{ $File.Dir }}{{ $File.LogicalName }}" target="blank"><i class='fa fa-edit'></i> Refine this Page</a> </li>{{end}}

-            {{ end }}

-        </ul>

-        <!-- sidebar menu end-->

-    </div>

-</aside>

-<!--sidebar end-->

--- a/layouts/partials/quotes.html

+++ /dev/null

@@ -1,12 +1,0 @@

-{{ range . }}

-<div class="item">

-    <blockquote>

-        <p>

-        {{ .quote | safeHTML }}

-        </p>

-        &mdash; {{ .name }} ({{ .twitter_handle }}) <a href="{{ .link }}">

-            {{ dateFormat "January 2, 2006" .date }}

-        </a>

-    </blockquote>

-</div>

-{{ end }}

--- a/layouts/partials/search.html

+++ /dev/null

@@ -1,1 +1,0 @@

-<input type="search" id="search-input" placeholder="Search...">

\ No newline at end of file

--- a/layouts/section/commands.html

+++ /dev/null

@@ -1,12 +1,0 @@

-{{ partial "header.html" . }}

-<h1>Hugo Commands</h1>

-<p>Hugo’s CLI (command line interface) commands are listed here.

-This autogenerated list is always up to date (thanks to

-    <a href="https://github.com/spf13/cobra">Cobra</a>).

-</p>

-<ul>

-{{- range .Data.Pages }}

-    <li><a href="{{ .URL }}">{{ .Title }}</a></li>

-{{- end }}

-</ul>

-{{ partial "footer.html" . }}

--- a/layouts/section/release-notes.html

+++ /dev/null

@@ -1,6 +1,0 @@

-{{ define "main" }}

-{{ range .Pages }}

-<h1>{{ .Title }} {{ .Date.Format "Jan 2, 2006" }}</h1>

-{{ .Content }}

-{{ end }}

-{{ end }}

\ No newline at end of file

--- a/layouts/section/showcase.html

+++ /dev/null

@@ -1,17 +1,0 @@

-{{ partial "header.html" . }}

-<h1 id="title">Hugo-built Sites (with source)</h1>

-<div class="row">

-	{{ range .Data.Pages.ByDate }}

-    	{{ .Render "thumbnail"}}

-    {{ end }}

-</div>

-<hr>

-<blockquote>

-If you want to be added to this page, please send a <a href="https://github.com/gohugoio/hugoDocs/pulls">pull request</a>. Check out the <a href="{{ relref . "community/contributing.md#showcase-additions" }}">how-to guide</a>.

-</blockquote>

-{{ partial "footer.html" . }}

--- /dev/null

+++ b/layouts/shortcodes/articlelist.html

@@ -1,0 +1,18 @@

+<table class="utils-table">

+<thead>

+	<tr>

+		<th class="col-title">Title</td>

+		<th class="col-author">Author</td>

+		<th class="col-date">Date</td>

+	</tr>

+</thead>

+<tbody>

+	{{ range $ind, $art := $.Site.Data.articles.article }}

+	<tr>

+		<td><a href="{{$art.url}}" target="_blank">{{$art.title | markdownify }}</a></td>

+		<td>{{ $art.author | markdownify }}</td>

+		<td>{{ $art.date }}</td>

+	</tr>

+	{{ end }}

+</tbody>

+</table>

--- /dev/null

+++ b/layouts/shortcodes/code.html

@@ -1,0 +1,15 @@

+<div class="code relative bg-primary-color moon-gray" id="{{.Get "file" | urlize}}">

+	{{- with .Get "file" -}}

+		<div class="filename san-serif f6 dib lh-solid pl2 pv2">{{.}}</div>

+	{{- end -}}

+	{{ if ne (.Get "copy") "false" }}

+		<button class="needs-js copy bg-accent-color-dark f6 absolute top-0 right-0 lh-solid hover-bg-primary-color-dark bn white ph3 pv2" title="Copy this code to your clipboard." data-clipboard-action="copy" aria-label="copy button">

+		</button>

+		{{/* Functionality located within filesaver.js The copy here is located in the css with .copy class so it can be replaced with JS on success */}}

+	{{end}}

+	<div class="code-copy-content nt3" {{with .Get "download"}}id="{{.}}"{{end}}>

+		{{- .Inner -}}

+	</div>

+</div>

--- a/layouts/shortcodes/datatable-vertical.html

+++ /dev/null

@@ -1,26 +1,0 @@

-{{ $package := (index .Params 0) }}

-{{ $listname := (index .Params 1) }}

-{{ $list := (index (index .Site.Data.docs $package) $listname) }}

-{{ $fields := after 2 .Params }}

-<table class="table table-bordered">

-	{{ range $list }}

-	{{ range $k, $v := . }}

-	{{ $.Scratch.Set $k $v }}

-	{{ end }}

-	{{ end }}

-	{{ range $i, $_ := $fields }}

-	<tr>

-		{{ $.Scratch.Set "i" $i }}

-		{{ $field := (index $fields  ($.Scratch.Get "i") ) }}

-		<th>{{ $field }}</th>

-		{{ range $list }}

-		<td>

-			{{ index . $field }}

-		</td>

-		{{ end }}

-	</tr>

-	{{ end }}

-</table>

\ No newline at end of file

--- a/layouts/shortcodes/datatable.html

+++ b/layouts/shortcodes/datatable.html

@@ -16,8 +16,7 @@

 		{{ end }}

 		{{ range $fields }}

 			<td>{{ $.Scratch.Get . }}</td>

-		{{ end }}

+		{{ end }}

 	</tr>

 	{{ end }}

 </table>

--- a/layouts/shortcodes/directoryindex.html

+++ b/layouts/shortcodes/directoryindex.html

@@ -7,7 +7,7 @@

 {{- range $files }}

     <tr>

         <td>{{ .Size }}</td>

-        <td><a href="{{ $pathURL }}{{ .Name | relURL }}"> {{ .Name }}</a></td>

+        <td><a href="{{ $pathURL }}{{ .Name | relURL }}" target="_blank"> {{ .Name }}</a></td>

     </tr>

 {{- end }}

 </table>

--- /dev/null

+++ b/layouts/shortcodes/docfile.html

@@ -1,0 +1,11 @@

+{{ $file := .Get 0}}

+{{ $filepath := $file }}

+{{ $syntax := index (split $file ".") 1 }}

+{{ $syntaxoverride := eq (len .Params) 2 }}

+<div class="code-copy" id="{{$file | urlize}}">

+	<div class="code-copy-header"><div class="action-buttons"></div><span title="" class="filename">{{$filepath}}</span><i class="icon-{{$syntax}} input"></i></div>

+	<button class="copy-button" title="Copy to clipboard" data-clipboard-snippet>

+			<div class="copy-text"><i class="icon-clipboard"></i> COPY</div>

+	</button>

+	<pre><code class="language-{{if $syntaxoverride}}{{.Get 1}}{{else}}{{$syntax}}{{end}}">{{- readFile $file -}}</code></pre>

+</div>

--- /dev/null

+++ b/layouts/shortcodes/exfile.html

@@ -1,0 +1,12 @@

+{{ $file := .Get 0}}

+{{ $filepath := replace $file "static/" ""}}

+{{ $syntax := index (split $file ".") 1 }}

+{{ $syntaxoverride := eq (len .Params) 2 }}

+<div class="code-copy" id="{{$file | urlize}}">

+	<div class="code-copy-header examplesite"><div class="action-buttons"></div><span class="filename"><i class="icon-website"></i>{{$filepath}}</span><i class="icon-{{$syntax}} input"></i></div>

+	<button class="copy-button" title="Copy to clipboard" data-clipboard-snippet>

+			<div class="copy-text"><i class="icon-clipboard"></i> COPY</div>

+	</button>

+	<pre><code class="language-{{if $syntaxoverride}}{{.Get 1}}{{else}}{{$syntax}}{{end}}">{{- readFile $file -}}</code></pre>

+	<a role="button" target="_blank" href="{{$.Site.Params.ghdocsrepo}}{{$file}}" title="See {{$filepath}} source on GitHub" class="tooltip see-on-github" data-tooltip="See {{$filepath}} source on GitHub">Source<i class="icon-github"></i></a>

+</div>

--- /dev/null

+++ b/layouts/shortcodes/exfm.html

@@ -1,0 +1,13 @@

+<!-- Similar to exfile.html but *only* pulls the front matter from the example/content/*md -->

+{{ $file := .Get 0}}

+{{ $filepath := replace $file "static/" ""}}

+{{ $syntax := index (split $file ".") 1 }}

+{{ $syntaxoverride := eq (len .Params) 2 }}

+<div class="code-copy" id="{{$file | urlize}}">

+	<div class="code-copy-header examplesite"><div class="action-buttons"></div><span title="" class="filename">{{$filepath}}</span><i class="icon-{{$syntax}} input"></i></div>

+	<button class="copy-button" title="Copy to clipboard" data-clipboard-snippet>

+			<div class="copy-text"><i class="icon-clipboard"></i> COPY</div>

+	</button>

+	<pre><code class="language-{{if $syntaxoverride}}{{.Get 1}}{{else}}{{$syntax}}{{end}}">{{- readFile $file -}}</code></pre>

+	<a role="button" target="_blank" href="{{$.Site.Params.ghdocsrepo}}{{$file}}" title="See {{$filepath}} on GitHub" class="see-on-github">Source<i class="icon-github"></i></a>

+</div>

\ No newline at end of file

--- a/layouts/shortcodes/gh.html

+++ b/layouts/shortcodes/gh.html

@@ -1,9 +1,9 @@

 {{ range .Params }}

-{{   if eq (substr . 0 1) "@" }}

-<a href="//github.com/{{ substr . 1 }}">{{ . }}</a>

-{{   else if eq (substr . 0 2) "0x" }}

-<a href="//github.com/gohugoio/hugo/commit/{{ substr . 2 }}">{{ substr . 2 6 }}</a>

-{{   else }}

-<a href="//github.com/gohugoio/hugo/issues/{{ . }}">#{{ . }}</a>

-{{   end }}

-{{ end }}

+	{{   if eq (substr . 0 1) "@" }}

+	<a href="//github.com/{{ substr . 1 }}">{{ . }}</a>

+	{{   else if eq (substr . 0 2) "0x" }}

+	<a href="//github.com/spf13/hugo/commit/{{ substr . 2 }}">{{ substr . 2 6 }}</a>

+	{{   else }}

+	<a href="//github.com/spf13/hugo/issues/{{ . }}">#{{ . }}</a>

+	{{ end }}

+{{ end }}

\ No newline at end of file

--- /dev/null

+++ b/layouts/shortcodes/ghrepo.html

@@ -1,0 +1,1 @@

+<a href="{{$.Site.Params.ghrepo}}" target="_blank">GitHub repository</a>

\ No newline at end of file

--- a/layouts/shortcodes/nohighlight.html

+++ b/layouts/shortcodes/nohighlight.html

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

-<pre><code class="hljs nohighlight">{{ .Inner }}</code></pre>

+<pre><code class="hljs nohighlight">{{ .Inner }}</code></pre>

\ No newline at end of file

--- /dev/null

+++ b/layouts/shortcodes/note.html

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

+<aside class="admonition note">

+	<div class="note-icon">

+		{{partial "svg/exclamation.svg" (dict "size" "20px" ) }}

+	</div>

+	<!-- <h2 id="{{if .Get 0}}{{.Get 0 | urlize}}{{else}}note{{end}}">{{if .Get 0}}{{.Get 0 | markdownify}}{{else}}Note{{end}}</h2> -->

+	<!-- <h3>Note</h3> -->

+	<div class="admonition-content">{{- .Inner -}}</div>

+</aside>

--- /dev/null

+++ b/layouts/shortcodes/output.html

@@ -1,0 +1,11 @@

+{{$file := .Get "file"}}

+{{$icon := index (split $file ".") 1 }}

+<div class="code" id="{{$file | urlize}}">

+	<div class="filename" title="{{$file}}">{{$file}}</div>

+<!-- 	<div class="code-icon">

+		<i class="icon-{{$icon}}"></i>

+	</div> -->

+	<div class="code-copy-content output-content">

+	{{- .Inner -}}

+	</div>

+</div>

\ No newline at end of file

--- a/layouts/shortcodes/readfile.html

+++ b/layouts/shortcodes/readfile.html

@@ -1,1 +1,6 @@

-{{- .Get 0 | readFile -}}

+{{$file := .Get "file"}}

+{{- if eq (.Get "markdown") "true" -}}

+{{- $file  | readFile | markdownify -}}

+{{- else -}}

+{{ $file  | readFile | safeHTML }}

+{{- end -}}

\ No newline at end of file

--- /dev/null

+++ b/layouts/shortcodes/tip.html

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

+<aside class="admonition tip">

+	<div class="tip-icon">

+		{{partial "svg/exclamation.svg" .}}

+	</div>

+	<!-- <h2 id="{{if .Get 0}}{{.Get 0 | urlize}}{{else}}tip{{end}}">{{if .Get 0}}{{.Get 0 | markdownify}}{{else}}Tip{{end}}</h2> -->

+	<!-- <h3>Tip</h3> -->

+	<div class="admonition-content">{{- .Inner -}}</div>

+</aside>

--- /dev/null

+++ b/layouts/shortcodes/todo.html

@@ -1,0 +1,1 @@

+{{ if .Inner }}{{ end }}

\ No newline at end of file

--- /dev/null

+++ b/layouts/shortcodes/warning.html

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

+<aside class="admonition warning">

+	<div class="admonition-icon">

+		{{partial "svg/exclamation.svg" .}}

+	</div>

+	<!-- <h2 id="{{if .Get 0}}{{.Get 0 | urlize}}{{else}}warning{{end}}">{{if .Get 0}}{{.Get 0 | markdownify}}{{else}}Warning{{end}}</h2> -->

+	<!-- <h3>Warning</h3> -->

+	<div class="admonition-content">{{- .Inner -}}</div>

+</aside>

--- a/layouts/shortcodes/youtube.html

+++ /dev/null

@@ -1,4 +1,0 @@

-<div class="video-container">

-<iframe class="youtube-player" type="text/html" width="100%" height="auto" src="https://www.youtube.com/embed/{{ index .Params 0 }}" allowfullscreen frameborder="0">

-</iframe>

-</div>

--- /dev/null

+++ b/layouts/shortcodes/yt.html

@@ -1,0 +1,11 @@

+<div class="video-wrapper" data-streaming="youtube" data-videoid="{{.Get "id"}}" >

+	<i class="icon-video-play-button shortcode"></i>

+	{{if (.Get "thumbnail")}}

+	<div style="background-image:url(/images/thumbnails/{{.Get "thumbnail"}})" alt="YouTube Thumbnail" class="video-thumbnail"></div>

+	{{else}}

+	<div style="background-image:url(//img.youtube.com/vi/{{.Get "id"}}/0.jpg)" alt="YouTube Thumbnail" class="video-thumbnail"></div>

+	{{end}}

+</div>

+{{ if (.Get "description") }}

+<div class="video-description">{{ .Get "description" | markdownify }}</div>

+{{ end }}

\ No newline at end of file

--- a/layouts/showcase/thumbnail.html

+++ /dev/null

@@ -1,17 +1,0 @@

-<div class="col-sm-6 col-md-4" style="padding-bottom:1em;">

-    <div class="showcase-container">

-      <div class="dummy"></div>

-      <div class="thumbnail">

-      <a href="{{ .Params.sitelink }}"><img class="img-responsive img-rounded" style="width:100%;" src="{{ .Params.thumbnail }}" alt="{{ .Description }}"></a>

-      <h4>

-        <a href="{{ .Params.sitelink }}">{{ .Title | safeHTML }}</a>

-        {{ if (isset .Params "sourcelink") }}

-        <a href="{{ .Params.sourcelink }}" class="small pull-right">source</a>

-        {{ end }}

-      </h4>

-              {{ range .Params.tags }}

-              <span class="label label-default" style="font-size:60%;">{{ . }}</span>

-              {{ end }}

-      </div>

-  </div>

-</div>

--- /dev/null

+++ b/netlify.toml

@@ -1,0 +1,18 @@

+[build]

+  publish = "public"

+  command = "hugo"

+[context.production.environment]

+  HUGO_VERSION = "0.25.1"

+  HUGO_ENV = "production"

+  HUGO_ENABLEGITINFO = "true"

+[context.deploy-preview.environment]

+  HUGO_VERSION = "0.25.1"

+[context.branch-deploy.environment]

+  HUGO_VERSION = "0.25.1"

+[context.next.environment]

+  HUGO_BASEURL = "https://next--gohugoio.netlify.com/"

+  HUGO_ENABLEGITINFO = "true"

\ No newline at end of file

--- a/static/_headers

+++ b/static/_headers

@@ -1,4 +1,5 @@

/*

   X-Frame-Options: DENY

   X-XSS-Protection: 1; mode=block

-  X-Content-Type-Options: nosniff

\ No newline at end of file

+  X-Content-Type-Options: nosniff

+  Referrer-Policy: origin-when-cross-origin

binary files /dev/null b/static/contribute/development/accept-cla.png differ

binary files /dev/null b/static/contribute/development/ci-errors.png differ

binary files /dev/null b/static/contribute/development/copy-remote-url.png differ

binary files /dev/null b/static/contribute/development/forking-a-repository.png differ

binary files /dev/null b/static/contribute/development/open-pull-request.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/adding-a-github-pages-step.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/adding-the-project-to-github.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/and-we-ve-got-an-app.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/configure-the-deploy-step.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/creating-a-basic-hugo-site.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/public-or-not.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/using-hugo-build.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-access.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-account-settings.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-add-app.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-git-connections.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-search.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-select-owner.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-select-repository.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-sign-up-page.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/wercker-sign-up.png differ

binary files /dev/null b/static/hosting-and-deployment/deployment-with-wercker/werckeryml.png differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-bitbucket/bitbucket-blog-post.png differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-bitbucket/bitbucket-create-repo.png differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-add-new-site.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-authorize-added-permissions.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-1.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-2.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-3.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-deploy-published.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-deploying-site.gif differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-first-authorize.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-live-site.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-push-to-deploy.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/netlify-signup.jpg differ

binary files /dev/null b/static/hosting-and-deployment/hosting-on-netlify/tibobeijennl.jpg differ

binary files /dev/null b/static/images/contribute/development/accept-cla.png differ

binary files /dev/null b/static/images/contribute/development/ci-errors.png differ

binary files /dev/null b/static/images/contribute/development/copy-remote-url.png differ

binary files /dev/null b/static/images/contribute/development/forking-a-repository.png differ

binary files /dev/null b/static/images/contribute/development/open-pull-request.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/adding-a-github-pages-step.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/adding-the-project-to-github.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/and-we-ve-got-an-app.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/configure-the-deploy-step.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/creating-a-basic-hugo-site.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/public-or-not.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/using-hugo-build.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-access.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-account-settings.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-add-app.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-git-connections.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-search.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-select-owner.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-select-repository.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-sign-up-page.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/wercker-sign-up.png differ

binary files /dev/null b/static/images/hosting-and-deployment/deployment-with-wercker/werckeryml.png differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-blog-post.png differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-create-repo.png differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-add-new-site.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-authorize-added-permissions.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-1.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-2.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-3.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-deploy-published.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-deploying-site.gif differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-first-authorize.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-live-site.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-push-to-deploy.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/netlify-signup.jpg differ

binary files /dev/null b/static/images/hosting-and-deployment/hosting-on-netlify/tibobeijennl.jpg differ

--- /dev/null

+++ b/static/images/icon-custom-outputs.svg

@@ -1,0 +1,36 @@

+<svg fill="#777" stroke="#fff" width="100pt" height="100pt" version="1.1" viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg">

+ <g>

+  <path d="m28.332 63.332h3.332v3.332h-3.332z"/>

+  <path d="m28.332 76.668h3.332v3.332h-3.332z"/>

+  <path d="m28.332 90h3.332v3.332h-3.332z"/>

+  <path d="m25 56.668c-1.8438 0-3.332 1.4922-3.332 3.332v36.668c0 1.8398 1.4883 3.332 3.332 3.332h30c1.8438 0 3.332-1.4922 3.332-3.332v-36.668c0-1.8398-1.4883-3.332-3.332-3.332zm30 40h-30v-10h30zm0-13.336h-30v-10h30zm0-23.332v10h-30v-10z"/>

+  <path d="m5 43.332h30c1.8438 0 3.332-1.4922 3.332-3.332v-36.668c0-1.8398-1.4883-3.332-3.332-3.332h-30c-1.8438 0-3.332 1.4922-3.332 3.332v36.668c0 1.8398 1.4883 3.332 3.332 3.332zm0-40h30v10h-30zm0 13.336h30v10h-30zm0 13.332h30v10h-30z"/>

+  <path d="m8.332 6.668h3.332v3.332h-3.332z"/>

+  <path d="m8.332 20h3.332v3.332h-3.332z"/>

+  <path d="m8.332 33.332h3.332v3.332h-3.332z"/>

+  <path d="m65 60h30c1.8438 0 3.332-1.4922 3.332-3.332v-36.668c0-1.8398-1.4883-3.332-3.332-3.332h-30c-1.8438 0-3.332 1.4922-3.332 3.332v36.668c0 1.8398 1.4883 3.332 3.332 3.332zm0-40h30v10h-30zm0 13.332h30v10h-30zm0 13.336h30v10h-30z"/>

+  <path d="m68.332 23.332h3.332v3.332h-3.332z"/>

+  <path d="m68.332 36.668h3.332v3.332h-3.332z"/>

+  <path d="m68.332 50h3.332v3.332h-3.332z"/>

+  <path d="m41.668 3.332h3.332v3.332h-3.332z"/>

+  <path d="m48.332 3.332h3.332v3.332h-3.332z"/>

+  <path d="m55 3.332h3.332v3.332h-3.332z"/>

+  <path d="m61.668 3.332h3.332v3.332h-3.332z"/>

+  <path d="m68.332 3.332h3.332v3.332h-3.332z"/>

+  <path d="m75 3.332h3.332v3.332h-3.332z"/>

+  <path d="m75 10h3.332v3.332h-3.332z"/>

+  <path d="m81.668 70h3.332v3.332h-3.332z"/>

+  <path d="m88.332 70h3.332v3.332h-3.332z"/>

+  <path d="m88.332 63.332h3.332v3.332h-3.332z"/>

+  <path d="m75 70h3.332v3.332h-3.332z"/>

+  <path d="m68.332 70h3.332v3.332h-3.332z"/>

+  <path d="m61.668 70h3.332v3.332h-3.332z"/>

+  <path d="m8.332 46.668h3.332v3.332h-3.332z"/>

+  <path d="m8.332 53.332h3.332v3.332h-3.332z"/>

+  <path d="m8.332 60h3.332v3.332h-3.332z"/>

+  <path d="m8.332 66.668h3.332v3.332h-3.332z"/>

+  <path d="m8.332 73.332h3.332v3.332h-3.332z"/>

+  <path d="m8.332 80h3.332v3.332h-3.332z"/>

+  <path d="m15 80h3.332v3.332h-3.332z"/>

+ </g>

+</svg>

binary files /dev/null b/static/images/quickstart/bookshelf-bleak-theme.png differ

binary files /dev/null b/static/images/quickstart/bookshelf-disqus.png differ

binary files /dev/null b/static/images/quickstart/bookshelf-new-default-image.png differ

binary files /dev/null b/static/images/quickstart/bookshelf-only-picture.png differ

binary files /dev/null b/static/images/quickstart/bookshelf-robust-theme.png differ

binary files /dev/null b/static/images/quickstart/bookshelf-updated-config.png differ

binary files /dev/null b/static/images/quickstart/bookshelf.png differ

binary files /dev/null b/static/images/quickstart/default.jpg differ

binary files /dev/null b/static/images/quickstart/gh-pages-ui.png differ

--- /dev/null

+++ b/static/images/site-hierarchy.svg

@@ -1,0 +1,634 @@

+<?xml version="1.0" encoding="UTF-8" standalone="no"?>

+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">

+<svg width="1800px" height="100%" viewBox="0 0 3900 1080" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:1.5;">

+    <g transform="matrix(1.00649,0,0,1.00649,25.8182,35.9777)">

+        <g transform="matrix(1.50472,0,0,1.50472,15.1711,-25.8885)">

+            <path d="M119.631,36.154L203.822,85.066L203.822,181.395L119.631,229.184L35.578,181.395L35.578,85.066L119.631,36.154Z" style="fill:rgb(255,64,136);"/>

+            <path d="M208.665,80.243L210.425,83.301L210.425,183.178L208.632,186.258L121.373,235.788L117.884,235.786L30.766,186.255L28.975,183.176L28.975,83.302L30.733,80.245L117.848,29.552L121.409,29.551L208.665,80.243ZM42.181,88.863L42.181,177.554L119.634,221.59L197.22,177.551L197.22,88.866L119.634,43.792L42.181,88.863Z" style="fill:rgb(201,23,126);"/>

+        </g>

+        <g transform="matrix(1.41079,0,0,1.59861,3.82297,88.2168)">

+            <path d="M179.238,106.552L154.758,106.552L154.758,62.2L112.134,62.2L112.134,106.552L87.654,106.552L87.654,1.648L112.134,1.648L112.134,45.496L154.758,45.496L154.758,1.648L179.238,1.648L179.238,106.552Z" style="fill:white;fill-rule:nonzero;"/>

+        </g>

+    </g>

+    <g transform="matrix(1.17016,0,0,1.00319,-96.1682,5.61636)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,131,192);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM764.103,105.938L764.103,344.801L1242.29,344.801L1242.29,105.938L764.103,105.938Z"/>

+    </g>

+    <g transform="matrix(0.565324,0,0,0.565324,625.187,85.961)">

+        <path d="M468.111,106.218L482.028,106.218L482.028,227.059L468.111,227.059L468.111,171.561L395.64,171.561L395.64,227.059L381.893,227.059L381.893,106.218L395.64,106.218L395.64,159.85L468.111,159.85L468.111,106.218Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M524.288,222.816C518.179,219.196 513.455,214.047 510.117,207.372C506.779,200.696 505.11,192.889 505.11,183.95C505.11,175.012 506.779,167.204 510.117,160.529C513.455,153.853 518.179,148.705 524.288,145.084C530.398,141.463 537.47,139.653 545.504,139.653C553.537,139.653 560.609,141.463 566.719,145.084C572.829,148.705 577.552,153.853 580.89,160.529C584.228,167.204 585.897,175.012 585.897,183.95C585.897,192.889 584.228,200.696 580.89,207.372C577.552,214.047 572.829,219.196 566.719,222.816C560.609,226.437 553.537,228.247 545.504,228.247C537.47,228.247 530.398,226.437 524.288,222.816ZM565.021,208.475C569.547,202.874 571.81,194.699 571.81,183.95C571.81,173.541 569.491,165.479 564.852,159.765C560.213,154.051 553.763,151.194 545.504,151.194C537.131,151.194 530.625,154.051 525.986,159.765C521.347,165.479 519.027,173.541 519.027,183.95C519.027,194.699 521.318,202.874 525.901,208.475C530.483,214.076 537.018,216.876 545.504,216.876C553.99,216.876 560.496,214.076 565.021,208.475Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M730.329,173.427L730.329,227.059L716.582,227.059L716.582,174.106C716.582,166.073 715.196,160.246 712.424,156.625C709.652,153.004 705.154,151.194 698.931,151.194C691.69,151.194 686.032,153.627 681.959,158.492C677.886,163.357 675.849,169.977 675.849,178.349L675.849,227.059L662.102,227.059L662.102,174.106C662.102,166.186 660.687,160.387 657.859,156.71C655.03,153.033 650.504,151.194 644.281,151.194C637.04,151.194 631.354,153.627 627.224,158.492C623.094,163.357 621.029,169.977 621.029,178.349L621.029,227.059L607.282,227.059L607.282,165.62C607.282,156.795 606.829,148.818 605.924,141.69L618.993,141.69L620.35,156.625C622.726,151.194 626.262,147.008 630.958,144.066C635.654,141.124 641.113,139.653 647.336,139.653C654.125,139.653 659.669,141.011 663.969,143.726C668.268,146.442 671.436,150.628 673.473,156.286C676.075,151.194 679.894,147.149 684.929,144.151C689.964,141.152 695.65,139.653 701.986,139.653C720.882,139.653 730.329,150.911 730.329,173.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M827.919,183.95L765.292,183.95C765.405,194.812 767.923,203.015 772.844,208.56C777.766,214.104 784.923,216.876 794.314,216.876C804.271,216.876 813.436,213.538 821.809,206.862L826.391,216.876C822.657,220.384 817.877,223.156 812.05,225.192C806.223,227.229 800.254,228.247 794.144,228.247C780.793,228.247 770.327,224.315 762.746,216.452C755.165,208.588 751.375,197.811 751.375,184.12C751.375,175.408 753.072,167.685 756.466,160.953C759.861,154.221 764.613,148.988 770.723,145.254C776.833,141.52 783.791,139.653 791.599,139.653C802.913,139.653 811.795,143.359 818.245,150.77C824.694,158.181 827.919,168.392 827.919,181.404L827.919,183.95ZM774.372,156.795C769.903,161.094 767.046,167.148 765.801,174.955L815.529,174.955C814.85,166.922 812.502,160.812 808.486,156.625C804.469,152.439 798.897,150.345 791.768,150.345C784.64,150.345 778.841,152.495 774.372,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M911.252,145.254C917.022,148.988 921.491,154.221 924.66,160.953C927.828,167.685 929.412,175.464 929.412,184.29C929.412,193.115 927.828,200.837 924.66,207.456C921.491,214.076 917.05,219.196 911.337,222.816C905.623,226.437 898.975,228.247 891.394,228.247C884.719,228.247 878.892,226.776 873.913,223.835C868.935,220.893 865.144,216.706 862.542,211.275L862.542,263.719L848.794,263.719L848.794,165.62C848.794,156.795 848.342,148.818 847.437,141.69L860.505,141.69L861.863,158.153C864.239,152.269 868.001,147.715 873.149,144.49C878.298,141.265 884.379,139.653 891.394,139.653C898.862,139.653 905.481,141.52 911.252,145.254ZM908.282,208.39C912.864,202.733 915.155,194.699 915.155,184.29C915.155,173.88 912.836,165.762 908.197,159.935C903.558,154.108 897.108,151.194 888.849,151.194C880.362,151.194 873.857,154.023 869.331,159.68C864.805,165.337 862.542,173.427 862.542,183.95C862.542,194.473 864.805,202.591 869.331,208.305C873.857,214.019 880.362,216.876 888.849,216.876C897.221,216.876 903.699,214.047 908.282,208.39Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1025.81,141.69L1025.81,227.059L1012.24,227.059L1012.24,211.615C1009.75,216.933 1005.98,221.034 1000.95,223.919C995.914,226.805 990.059,228.247 983.383,228.247C975.802,228.247 969.155,226.437 963.441,222.816C957.727,219.196 953.314,214.076 950.203,207.456C947.091,200.837 945.535,193.115 945.535,184.29C945.535,175.464 947.119,167.685 950.287,160.953C953.456,154.221 957.897,148.988 963.61,145.254C969.324,141.52 975.915,139.653 983.383,139.653C990.059,139.653 995.886,141.124 1000.86,144.066C1005.84,147.008 1009.63,151.138 1012.24,156.455L1012.24,141.69L1025.81,141.69ZM1005.45,208.305C1009.97,202.591 1012.24,194.473 1012.24,183.95C1012.24,173.427 1009.97,165.337 1005.45,159.68C1000.92,154.023 994.471,151.194 986.098,151.194C977.726,151.194 971.191,154.108 966.496,159.935C961.8,165.762 959.452,173.88 959.452,184.29C959.452,194.699 961.772,202.733 966.411,208.39C971.05,214.047 977.612,216.876 986.098,216.876C994.471,216.876 1000.92,214.019 1005.45,208.305Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1128.49,141.69L1128.49,226.38C1128.49,239.053 1125.24,248.642 1118.74,255.148C1112.23,261.654 1102.64,264.907 1089.97,264.907C1076.96,264.907 1065.75,261.965 1056.36,256.081L1058.74,244.88C1064.17,247.935 1069.29,250.141 1074.1,251.499C1078.91,252.857 1084.2,253.536 1089.97,253.536C1098.23,253.536 1104.45,251.358 1108.64,247.001C1112.82,242.645 1114.92,236.168 1114.92,227.568L1114.92,207.372C1112.31,212.803 1108.5,217.017 1103.46,220.016C1098.42,223.014 1092.46,224.513 1085.56,224.513C1078.09,224.513 1071.44,222.76 1065.61,219.252C1059.79,215.745 1055.29,210.766 1052.12,204.317C1048.95,197.867 1047.37,190.456 1047.37,182.083C1047.37,173.71 1048.95,166.299 1052.12,159.85C1055.29,153.4 1059.79,148.422 1065.61,144.914C1071.44,141.407 1078.09,139.653 1085.56,139.653C1092.34,139.653 1098.26,141.124 1103.29,144.066C1108.33,147.008 1112.14,151.138 1114.75,156.455L1114.75,141.69L1128.49,141.69ZM1107.7,204.741C1112.4,199.253 1114.75,191.701 1114.75,182.083C1114.75,172.466 1112.4,164.913 1107.7,159.426C1103.01,153.938 1096.53,151.194 1088.27,151.194C1079.9,151.194 1073.31,153.938 1068.5,159.426C1063.69,164.913 1061.29,172.466 1061.29,182.083C1061.29,191.701 1063.69,199.253 1068.5,204.741C1073.31,210.229 1079.9,212.972 1088.27,212.972C1096.53,212.972 1103.01,210.229 1107.7,204.741Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1226.42,183.95L1163.8,183.95C1163.91,194.812 1166.43,203.015 1171.35,208.56C1176.27,214.104 1183.43,216.876 1192.82,216.876C1202.78,216.876 1211.94,213.538 1220.31,206.862L1224.89,216.876C1221.16,220.384 1216.38,223.156 1210.55,225.192C1204.73,227.229 1198.76,228.247 1192.65,228.247C1179.3,228.247 1168.83,224.315 1161.25,216.452C1153.67,208.588 1149.88,197.811 1149.88,184.12C1149.88,175.408 1151.58,167.685 1154.97,160.953C1158.37,154.221 1163.12,148.988 1169.23,145.254C1175.34,141.52 1182.3,139.653 1190.1,139.653C1201.42,139.653 1210.3,143.359 1216.75,150.77C1223.2,158.181 1226.42,168.392 1226.42,181.404L1226.42,183.95ZM1172.88,156.795C1168.41,161.094 1165.55,167.148 1164.31,174.955L1214.03,174.955C1213.35,166.922 1211.01,160.812 1206.99,156.625C1202.97,152.439 1197.4,150.345 1190.27,150.345C1183.14,150.345 1177.35,152.495 1172.88,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.303961,0,0,0.303961,833.43,229.447)">

+        <path d="M-14.066,227.059L-4.731,106.218L17.333,106.218L9.016,209.069L65.533,209.069L64.176,227.059L-14.066,227.059Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M79.111,227.059L85.9,141.35L107.115,141.35L100.326,227.059L79.111,227.059ZM87.597,102.484L111.188,102.484L109.661,123.36L86.07,123.36L87.597,102.484Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M118.486,217.555L125.784,202.789C135.402,209.465 145.642,212.803 156.504,212.803C167.479,212.803 172.967,209.635 172.967,203.298C172.967,200.357 171.524,198.122 168.639,196.594C165.754,195.067 161.143,193.341 154.807,191.418C148.81,189.721 143.831,188.023 139.871,186.326C135.911,184.629 132.545,182.168 129.773,178.943C127.001,175.719 125.615,171.504 125.615,166.299C125.615,158.153 128.896,151.59 135.458,146.612C142.021,141.633 150.733,139.144 161.595,139.144C167.932,139.144 174.042,140.106 179.925,142.029C185.809,143.953 190.731,146.612 194.691,150.006L187.563,164.432C179.077,157.983 170.308,154.758 161.256,154.758C155.938,154.758 151.865,155.607 149.036,157.304C146.207,159.001 144.793,161.49 144.793,164.772C144.793,167.827 146.236,170.118 149.121,171.645C152.006,173.173 156.673,174.898 163.123,176.822C169.346,178.632 174.381,180.358 178.228,181.998C182.075,183.639 185.385,186.1 188.157,189.381C190.929,192.663 192.315,196.906 192.315,202.11C192.315,210.37 189.034,216.819 182.471,221.458C175.908,226.097 167.083,228.417 155.995,228.417C142.077,228.417 129.575,224.796 118.486,217.555Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M237.121,195.661C236.329,205.731 240.572,210.766 249.85,210.766C252.453,210.766 255.394,210.37 258.676,209.578L257.318,226.211C253.584,227.568 248.945,228.247 243.401,228.247C234.462,228.247 227.617,225.899 222.865,221.204C218.112,216.508 215.736,209.691 215.736,200.753C215.736,199.055 215.793,197.754 215.906,196.849L218.961,157.304L202.498,157.304L203.856,141.35L220.149,141.35L221.846,120.475L243.57,113.346L241.364,141.35L264.276,141.35L262.919,157.304L240.176,157.304L237.121,195.661Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M266.992,217.555L274.29,202.789C283.907,209.465 294.147,212.803 305.009,212.803C315.985,212.803 321.472,209.635 321.472,203.298C321.472,200.357 320.03,198.122 317.144,196.594C314.259,195.067 309.648,193.341 303.312,191.418C297.315,189.721 292.337,188.023 288.377,186.326C284.417,184.629 281.05,182.168 278.278,178.943C275.506,175.719 274.12,171.504 274.12,166.299C274.12,158.153 277.401,151.59 283.964,146.612C290.527,141.633 299.239,139.144 310.101,139.144C316.437,139.144 322.547,140.106 328.431,142.029C334.314,143.953 339.236,146.612 343.197,150.006L336.068,164.432C327.582,157.983 318.813,154.758 309.762,154.758C304.444,154.758 300.37,155.607 297.542,157.304C294.713,159.001 293.299,161.49 293.299,164.772C293.299,167.827 294.741,170.118 297.627,171.645C300.512,173.173 305.179,174.898 311.628,176.822C317.852,178.632 322.887,180.358 326.734,181.998C330.581,183.639 333.89,186.1 336.662,189.381C339.434,192.663 340.82,196.906 340.82,202.11C340.82,210.37 337.539,216.819 330.977,221.458C324.414,226.097 315.589,228.417 304.5,228.417C290.583,228.417 278.08,224.796 266.992,217.555Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M401.241,213.142L406.502,202.45C412.499,207.541 418.609,211.162 424.832,213.312C431.055,215.462 438.297,216.537 446.556,216.537C456.287,216.537 463.783,214.641 469.044,210.851C474.306,207.06 476.936,201.714 476.936,194.812C476.936,190.739 475.664,187.429 473.118,184.884C470.572,182.338 467.234,180.329 463.104,178.859C458.974,177.388 453.458,175.86 446.556,174.276C437.278,172.239 429.641,170.033 423.644,167.657C417.647,165.281 412.782,161.858 409.048,157.389C405.314,152.92 403.447,147.064 403.447,139.823C403.447,132.921 405.258,126.839 408.878,121.578C412.499,116.316 417.619,112.215 424.238,109.273C430.857,106.331 438.58,104.86 447.405,104.86C455.778,104.86 463.585,106.162 470.826,108.764C478.068,111.366 484.178,115.157 489.156,120.135L483.725,130.828C478.068,125.962 472.326,122.398 466.499,120.135C460.672,117.872 454.307,116.741 447.405,116.741C438.014,116.741 430.659,118.749 425.341,122.766C420.023,126.783 417.364,132.299 417.364,139.314C417.364,145.424 419.684,150.006 424.323,153.061C428.962,156.116 436.09,158.775 445.708,161.038C456.117,163.527 464.292,165.818 470.232,167.912C476.173,170.005 481.123,173.173 485.083,177.416C489.043,181.659 491.023,187.288 491.023,194.303C491.023,201.092 489.213,207.06 485.592,212.209C481.971,217.357 476.795,221.345 470.063,224.174C463.33,227.003 455.438,228.417 446.387,228.417C427.491,228.417 412.443,223.325 401.241,213.142Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M583.521,183.95L520.894,183.95C521.007,194.812 523.525,203.015 528.447,208.56C533.369,214.104 540.525,216.876 549.916,216.876C559.873,216.876 569.038,213.538 577.411,206.862L581.994,216.876C578.26,220.384 573.479,223.156 567.652,225.192C561.825,227.229 555.857,228.247 549.747,228.247C536.395,228.247 525.929,224.315 518.348,216.452C510.767,208.588 506.977,197.811 506.977,184.12C506.977,175.408 508.674,167.685 512.069,160.953C515.463,154.221 520.215,148.988 526.325,145.254C532.435,141.52 539.394,139.653 547.201,139.653C558.515,139.653 567.398,143.359 573.847,150.77C580.296,158.181 583.521,168.392 583.521,181.404L583.521,183.95ZM529.974,156.795C525.505,161.094 522.648,167.148 521.403,174.955L571.131,174.955C570.453,166.922 568.105,160.812 564.088,156.625C560.071,152.439 554.499,150.345 547.37,150.345C540.242,150.345 534.443,152.495 529.974,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M618.568,222.816C612.402,219.196 607.65,214.076 604.312,207.456C600.974,200.837 599.305,193.115 599.305,184.29C599.305,175.464 601.002,167.685 604.397,160.953C607.791,154.221 612.628,148.988 618.908,145.254C625.187,141.52 632.514,139.653 640.887,139.653C646.657,139.653 652.23,140.643 657.604,142.623C662.979,144.603 667.42,147.347 670.927,150.855L666.345,161.038C662.045,157.643 657.887,155.154 653.87,153.57C649.853,151.986 645.752,151.194 641.565,151.194C632.853,151.194 626.008,154.108 621.029,159.935C616.051,165.762 613.562,173.88 613.562,184.29C613.562,194.586 616.023,202.591 620.944,208.305C625.866,214.019 632.74,216.876 641.565,216.876C645.752,216.876 649.853,216.084 653.87,214.5C657.887,212.916 662.045,210.427 666.345,207.032L670.927,217.215C667.306,220.61 662.752,223.297 657.265,225.277C651.777,227.257 646.091,228.247 640.208,228.247C631.948,228.247 624.735,226.437 618.568,222.816Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M706.908,152.552L706.908,199.225C706.908,205.561 708.209,210.002 710.812,212.548C713.414,215.094 717.091,216.367 721.843,216.367C725.011,216.367 728.066,215.858 731.008,214.839L731.008,226.55C727.501,227.682 723.541,228.247 719.128,228.247C710.981,228.247 704.617,225.956 700.034,221.374C695.452,216.791 693.161,210.031 693.161,201.092L693.161,152.552L676.528,152.552L676.528,141.69L693.161,141.69L693.161,119.796L706.908,114.874L706.908,141.69L731.348,141.69L731.348,152.552L706.908,152.552Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M747.98,227.059L747.98,141.69L761.728,141.69L761.728,227.059L747.98,227.059ZM746.623,105.539L763.425,105.539L763.425,121.154L746.623,121.154L746.623,105.539Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M802.461,222.816C796.351,219.196 791.627,214.047 788.289,207.372C784.951,200.696 783.282,192.889 783.282,183.95C783.282,175.012 784.951,167.204 788.289,160.529C791.627,153.853 796.351,148.705 802.461,145.084C808.571,141.463 815.642,139.653 823.676,139.653C831.709,139.653 838.781,141.463 844.891,145.084C851.001,148.705 855.725,153.853 859.063,160.529C862.4,167.204 864.069,175.012 864.069,183.95C864.069,192.889 862.4,200.696 859.063,207.372C855.725,214.047 851.001,219.196 844.891,222.816C838.781,226.437 831.709,228.247 823.676,228.247C815.642,228.247 808.571,226.437 802.461,222.816ZM843.194,208.475C847.72,202.874 849.982,194.699 849.982,183.95C849.982,173.541 847.663,165.479 843.024,159.765C838.385,154.051 831.936,151.194 823.676,151.194C815.303,151.194 808.797,154.051 804.158,159.765C799.519,165.479 797.199,173.541 797.199,183.95C797.199,194.699 799.491,202.874 804.073,208.475C808.655,214.076 815.19,216.876 823.676,216.876C832.162,216.876 838.668,214.076 843.194,208.475Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M958.773,173.427L958.773,227.059L945.026,227.059L945.026,174.106C945.026,166.186 943.442,160.387 940.274,156.71C937.106,153.033 932.127,151.194 925.338,151.194C917.418,151.194 911.082,153.627 906.33,158.492C901.578,163.357 899.201,169.92 899.201,178.18L899.201,227.059L885.454,227.059L885.454,165.62C885.454,156.795 885.002,148.818 884.096,141.69L897.165,141.69L898.523,156.965C901.125,151.42 905.029,147.149 910.233,144.151C915.438,141.152 921.378,139.653 928.054,139.653C948.534,139.653 958.773,150.911 958.773,173.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M979.479,217.215L984.062,207.032C988.701,210.653 993.396,213.255 998.149,214.839C1002.9,216.423 1008.22,217.215 1014.1,217.215C1020.55,217.215 1025.44,216.112 1028.78,213.906C1032.12,211.7 1033.79,208.503 1033.79,204.317C1033.79,200.922 1032.66,198.207 1030.4,196.17C1028.13,194.133 1024.4,192.549 1019.19,191.418L1004.77,188.023C997.639,186.439 992.124,183.611 988.22,179.537C984.316,175.464 982.365,170.599 982.365,164.941C982.365,157.474 985.363,151.392 991.36,146.696C997.357,142.001 1005.28,139.653 1015.12,139.653C1021.12,139.653 1026.78,140.615 1032.09,142.538C1037.41,144.462 1041.88,147.234 1045.5,150.855L1040.92,160.868C1032.88,154.192 1024.29,150.855 1015.12,150.855C1009.01,150.855 1004.29,152.014 1000.95,154.334C997.611,156.653 995.942,159.906 995.942,164.093C995.942,167.6 996.989,170.373 999.082,172.409C1001.18,174.446 1004.54,176.03 1009.18,177.161L1023.61,180.725C1031.53,182.536 1037.41,185.336 1041.26,189.127C1045.11,192.917 1047.03,197.867 1047.03,203.977C1047.03,211.332 1044.03,217.215 1038.03,221.628C1032.04,226.041 1023.89,228.247 1013.59,228.247C999.224,228.247 987.852,224.57 979.479,217.215Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1207.25,227.059L1194.01,196L1130.87,196L1117.46,227.059L1103.04,227.059L1156.16,106.218L1168.38,106.218L1221.5,227.059L1207.25,227.059ZM1135.79,184.459L1189.08,184.459L1162.44,122.342L1135.79,184.459Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1256.29,209.578L1256.29,221.968C1256.29,226.72 1255.5,231.076 1253.92,235.036C1252.33,238.996 1249.67,242.843 1245.94,246.577L1239.49,241.655C1243.9,236.564 1246.39,231.698 1246.96,227.059L1238.81,227.059L1238.81,209.578L1256.29,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1411.08,175.379C1414.93,180.414 1416.85,186.666 1416.85,194.133C1416.85,204.656 1413.34,212.774 1406.33,218.488C1399.31,224.202 1389.41,227.059 1376.63,227.059L1326.39,227.059L1326.39,106.218L1374.93,106.218C1387.26,106.218 1396.85,108.962 1403.7,114.45C1410.54,119.937 1413.96,127.716 1413.96,137.786C1413.96,144.236 1412.3,149.808 1408.96,154.504C1405.62,159.199 1400.95,162.679 1394.96,164.941C1401.86,166.865 1407.23,170.344 1411.08,175.379ZM1340.14,159.85L1372.72,159.85C1381.77,159.85 1388.62,158.039 1393.26,154.419C1397.9,150.798 1400.22,145.48 1400.22,138.465C1400.22,124.661 1391.05,117.759 1372.72,117.759L1340.14,117.759L1340.14,159.85ZM1396.4,210.172C1400.87,206.608 1403.1,201.149 1403.1,193.794C1403.1,178.972 1393.88,171.561 1375.44,171.561L1340.14,171.561L1340.14,215.518L1375.44,215.518C1384.94,215.518 1391.93,213.736 1396.4,210.172Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1453.85,209.578L1453.85,221.968C1453.85,226.72 1453.06,231.076 1451.47,235.036C1449.89,238.996 1447.23,242.843 1443.5,246.577L1437.05,241.655C1441.46,236.564 1443.95,231.698 1444.51,227.059L1436.37,227.059L1436.37,209.578L1453.85,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1545.75,220.949C1537.32,215.971 1530.85,208.814 1526.32,199.48C1521.79,190.145 1519.53,179.141 1519.53,166.469C1519.53,153.796 1521.79,142.849 1526.32,133.628C1530.85,124.407 1537.32,117.307 1545.75,112.328C1554.18,107.35 1564.11,104.86 1575.54,104.86C1583.91,104.86 1591.58,106.133 1598.54,108.679C1605.49,111.225 1611.52,115.044 1616.61,120.135L1611.35,130.828C1605.58,125.849 1599.89,122.285 1594.29,120.135C1588.69,117.985 1582.5,116.911 1575.71,116.911C1562.47,116.911 1552.2,121.21 1544.9,129.809C1537.61,138.408 1533.96,150.628 1533.96,166.469C1533.96,182.423 1537.58,194.727 1544.82,203.383C1552.06,212.039 1562.36,216.367 1575.71,216.367C1582.5,216.367 1588.69,215.292 1594.29,213.142C1599.89,210.992 1605.58,207.428 1611.35,202.45L1616.61,213.142C1611.52,218.234 1605.49,222.052 1598.54,224.598C1591.58,227.144 1583.91,228.417 1575.54,228.417C1564.11,228.417 1554.18,225.928 1545.75,220.949Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.922959,-810.571,447.236)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(201,23,126);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM764.103,106.414L764.103,344.325L1242.29,344.325L1242.29,106.414L764.103,106.414Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,-159.104,767.346)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,49.662,767.346)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,258.428,767.346)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,552.302,769.023)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,761.069,769.023)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,974.126,769.023)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,1269.17,766.789)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,1477.94,766.789)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.313837,0,0,0.703144,1686.7,766.789)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM776.928,108.277L776.928,342.462L1229.46,342.462L1229.46,108.277L776.928,108.277Z"/>

+    </g>

+    <g transform="matrix(0.617288,0,0,0.617288,-133.676,514.244)">

+        <path d="M435.015,213.142L440.277,202.45C446.274,207.541 452.383,211.162 458.607,213.312C464.83,215.462 472.071,216.537 480.331,216.537C490.061,216.537 497.557,214.641 502.819,210.851C508.08,207.06 510.711,201.714 510.711,194.812C510.711,190.739 509.438,187.429 506.892,184.884C504.346,182.338 501.008,180.329 496.879,178.859C492.749,177.388 487.233,175.86 480.331,174.276C471.053,172.239 463.415,170.033 457.419,167.657C451.422,165.281 446.556,161.858 442.823,157.389C439.089,152.92 437.222,147.064 437.222,139.823C437.222,132.921 439.032,126.839 442.653,121.578C446.274,116.316 451.393,112.215 458.013,109.273C464.632,106.331 472.354,104.86 481.179,104.86C489.552,104.86 497.359,106.162 504.601,108.764C511.842,111.366 517.952,115.157 522.931,120.135L517.5,130.828C511.842,125.962 506.1,122.398 500.273,120.135C494.446,117.872 488.081,116.741 481.179,116.741C471.788,116.741 464.434,118.749 459.116,122.766C453.798,126.783 451.139,132.299 451.139,139.314C451.139,145.424 453.458,150.006 458.097,153.061C462.736,156.116 469.865,158.775 479.482,161.038C489.892,163.527 498.067,165.818 504.007,167.912C509.947,170.005 514.897,173.173 518.857,177.416C522.818,181.659 524.798,187.288 524.798,194.303C524.798,201.092 522.987,207.06 519.367,212.209C515.746,217.357 510.569,221.345 503.837,224.174C497.105,227.003 489.213,228.417 480.161,228.417C461.266,228.417 446.217,223.325 435.015,213.142Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M617.295,183.95L554.668,183.95C554.782,194.812 557.299,203.015 562.221,208.56C567.143,214.104 574.3,216.876 583.691,216.876C593.648,216.876 602.813,213.538 611.185,206.862L615.768,216.876C612.034,220.384 607.254,223.156 601.427,225.192C595.599,227.229 589.631,228.247 583.521,228.247C570.17,228.247 559.704,224.315 552.123,216.452C544.542,208.588 540.751,197.811 540.751,184.12C540.751,175.408 542.449,167.685 545.843,160.953C549.237,154.221 553.99,148.988 560.1,145.254C566.209,141.52 573.168,139.653 580.975,139.653C592.29,139.653 601.172,143.359 607.621,150.77C614.071,158.181 617.295,168.392 617.295,181.404L617.295,183.95ZM563.749,156.795C559.279,161.094 556.422,167.148 555.178,174.955L604.906,174.955C604.227,166.922 601.879,160.812 597.862,156.625C593.846,152.439 588.273,150.345 581.145,150.345C574.017,150.345 568.218,152.495 563.749,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M652.343,222.816C646.176,219.196 641.424,214.076 638.086,207.456C634.748,200.837 633.079,193.115 633.079,184.29C633.079,175.464 634.777,167.685 638.171,160.953C641.565,154.221 646.403,148.988 652.682,145.254C658.962,141.52 666.288,139.653 674.661,139.653C680.432,139.653 686.004,140.643 691.378,142.623C696.753,144.603 701.194,147.347 704.702,150.855L700.119,161.038C695.82,157.643 691.661,155.154 687.645,153.57C683.628,151.986 679.526,151.194 675.34,151.194C666.628,151.194 659.782,154.108 654.804,159.935C649.825,165.762 647.336,173.88 647.336,184.29C647.336,194.586 649.797,202.591 654.719,208.305C659.641,214.019 666.514,216.876 675.34,216.876C679.526,216.876 683.628,216.084 687.645,214.5C691.661,212.916 695.82,210.427 700.119,207.032L704.702,217.215C701.081,220.61 696.527,223.297 691.039,225.277C685.551,227.257 679.866,228.247 673.982,228.247C665.722,228.247 658.509,226.437 652.343,222.816Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M740.682,152.552L740.682,199.225C740.682,205.561 741.984,210.002 744.586,212.548C747.188,215.094 750.866,216.367 755.618,216.367C758.786,216.367 761.841,215.858 764.783,214.839L764.783,226.55C761.275,227.682 757.315,228.247 752.902,228.247C744.756,228.247 738.391,225.956 733.809,221.374C729.226,216.791 726.935,210.031 726.935,201.092L726.935,152.552L710.302,152.552L710.302,141.69L726.935,141.69L726.935,119.796L740.682,114.874L740.682,141.69L765.122,141.69L765.122,152.552L740.682,152.552Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M781.755,227.059L781.755,141.69L795.502,141.69L795.502,227.059L781.755,227.059ZM780.397,105.539L797.199,105.539L797.199,121.154L780.397,121.154L780.397,105.539Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M836.235,222.816C830.125,219.196 825.401,214.047 822.063,207.372C818.726,200.696 817.057,192.889 817.057,183.95C817.057,175.012 818.726,167.204 822.063,160.529C825.401,153.853 830.125,148.705 836.235,145.084C842.345,141.463 849.417,139.653 857.45,139.653C865.484,139.653 872.555,141.463 878.665,145.084C884.775,148.705 889.499,153.853 892.837,160.529C896.175,167.204 897.844,175.012 897.844,183.95C897.844,192.889 896.175,200.696 892.837,207.372C889.499,214.047 884.775,219.196 878.665,222.816C872.555,226.437 865.484,228.247 857.45,228.247C849.417,228.247 842.345,226.437 836.235,222.816ZM876.968,208.475C881.494,202.874 883.757,194.699 883.757,183.95C883.757,173.541 881.437,165.479 876.798,159.765C872.159,154.051 865.71,151.194 857.45,151.194C849.077,151.194 842.571,154.051 837.932,159.765C833.293,165.479 830.974,173.541 830.974,183.95C830.974,194.699 833.265,202.874 837.847,208.475C842.43,214.076 848.964,216.876 857.45,216.876C865.936,216.876 872.442,214.076 876.968,208.475Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M992.548,173.427L992.548,227.059L978.8,227.059L978.8,174.106C978.8,166.186 977.216,160.387 974.048,156.71C970.88,153.033 965.902,151.194 959.113,151.194C951.193,151.194 944.856,153.627 940.104,158.492C935.352,163.357 932.976,169.92 932.976,178.18L932.976,227.059L919.229,227.059L919.229,165.62C919.229,156.795 918.776,148.818 917.871,141.69L930.939,141.69L932.297,156.965C934.899,151.42 938.803,147.149 944.008,144.151C949.213,141.152 955.153,139.653 961.828,139.653C982.308,139.653 992.548,150.911 992.548,173.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1156.84,227.059L1143.6,196L1080.46,196L1067.06,227.059L1052.63,227.059L1105.75,106.218L1117.97,106.218L1171.09,227.059L1156.84,227.059ZM1085.38,184.459L1138.68,184.459L1112.03,122.342L1085.38,184.459Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.349245,0,0,0.349245,82.0207,649.5)">

+        <path d="M127.289,227.059L137.391,98.622L165.712,98.622L157.234,204.15L214.598,204.15L212.794,227.059L127.289,227.059Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M228.127,227.059L235.342,135.602L262.581,135.602L255.366,227.059L228.127,227.059ZM237.507,92.669L266.73,92.669L264.746,118.285L235.523,118.285L237.507,92.669Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M272.142,217.318L280.981,198.377C286.032,201.865 291.443,204.541 297.216,206.405C302.988,208.269 308.761,209.201 314.533,209.201C319.584,209.201 323.312,208.479 325.717,207.036C328.122,205.593 329.325,203.669 329.325,201.264C329.325,198.738 327.912,196.754 325.086,195.311C322.26,193.868 317.66,192.184 311.286,190.26C304.672,188.456 299.26,186.652 295.051,184.848C290.842,183.044 287.204,180.369 284.138,176.821C281.071,173.273 279.538,168.673 279.538,163.021C279.538,157.128 281.191,151.957 284.498,147.508C287.805,143.058 292.496,139.571 298.569,137.045C304.642,134.52 311.587,133.257 319.404,133.257C326.258,133.257 332.963,134.279 339.517,136.324C346.071,138.368 351.573,141.134 356.023,144.622L347.364,162.841C342.914,159.594 338.224,157.128 333.294,155.445C328.363,153.761 323.553,152.919 318.862,152.919C313.932,152.919 310.204,153.641 307.678,155.084C305.153,156.527 303.89,158.511 303.89,161.037C303.89,163.683 305.393,165.787 308.4,167.351C311.406,168.914 315.976,170.537 322.109,172.221C328.724,174.145 334.105,176.009 338.254,177.813C342.403,179.617 346.011,182.293 349.078,185.84C352.144,189.388 353.677,193.988 353.677,199.64C353.677,208.66 350.1,215.725 342.944,220.836C335.789,225.947 326.138,228.502 313.992,228.502C298.358,228.502 284.408,224.774 272.142,217.318Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M404.367,191.523C404.006,196.574 405.028,200.302 407.433,202.707C409.839,205.112 413.146,206.315 417.355,206.315C420.121,206.315 423.187,205.833 426.555,204.871L424.751,225.977C420.662,227.661 415.371,228.502 408.877,228.502C398.534,228.502 390.627,225.736 385.155,220.204C379.684,214.673 376.948,206.856 376.948,196.754C376.948,194.709 377.008,193.146 377.128,192.064L380.014,155.986L362.697,155.986L364.32,135.602L381.638,135.602L383.261,114.136L411.222,105.297L408.877,135.602L432.147,135.602L430.523,155.986L407.253,155.986L404.367,191.523Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M433.409,217.318L442.248,198.377C447.299,201.865 452.711,204.541 458.483,206.405C464.256,208.269 470.028,209.201 475.801,209.201C480.852,209.201 484.58,208.479 486.985,207.036C489.39,205.593 490.593,203.669 490.593,201.264C490.593,198.738 489.18,196.754 486.354,195.311C483.527,193.868 478.928,192.184 472.554,190.26C465.94,188.456 460.528,186.652 456.319,184.848C452.11,183.044 448.472,180.369 445.405,176.821C442.339,173.273 440.805,168.673 440.805,163.021C440.805,157.128 442.459,151.957 445.766,147.508C449.073,143.058 453.763,139.571 459.836,137.045C465.909,134.52 472.854,133.257 480.671,133.257C487.526,133.257 494.231,134.279 500.785,136.324C507.339,138.368 512.841,141.134 517.29,144.622L508.632,162.841C504.182,159.594 499.492,157.128 494.561,155.445C489.631,153.761 484.82,152.919 480.13,152.919C475.199,152.919 471.471,153.641 468.946,155.084C466.421,156.527 465.158,158.511 465.158,161.037C465.158,163.683 466.661,165.787 469.668,167.351C472.674,168.914 477.244,170.537 483.377,172.221C489.991,174.145 495.373,176.009 499.522,177.813C503.671,179.617 507.279,182.293 510.345,185.84C513.412,189.388 514.945,193.988 514.945,199.64C514.945,208.66 511.367,215.725 504.212,220.836C497.057,225.947 487.406,228.502 475.26,228.502C459.626,228.502 445.676,224.774 433.409,217.318Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M581.213,106.218L629.414,106.218C641.86,106.218 651.562,109.217 658.521,115.213C665.479,121.21 668.958,129.47 668.958,139.993C668.958,150.515 665.451,158.803 658.436,164.857C651.421,170.91 641.747,173.937 629.414,173.937L595.13,173.937L595.13,227.059L581.213,227.059L581.213,106.218ZM628.225,162.396C637.164,162.396 643.896,160.472 648.422,156.625C652.948,152.778 655.211,147.234 655.211,139.993C655.211,132.751 652.948,127.235 648.422,123.445C643.896,119.654 637.164,117.759 628.225,117.759L595.13,117.759L595.13,162.396L628.225,162.396Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M762.475,141.69L762.475,227.059L748.897,227.059L748.897,211.615C746.408,216.933 742.646,221.034 737.61,223.919C732.575,226.805 726.72,228.247 720.044,228.247C712.464,228.247 705.816,226.437 700.102,222.816C694.388,219.196 689.976,214.076 686.864,207.456C683.752,200.837 682.197,193.115 682.197,184.29C682.197,175.464 683.781,167.685 686.949,160.953C690.117,154.221 694.558,148.988 700.272,145.254C705.986,141.52 712.577,139.653 720.044,139.653C726.72,139.653 732.547,141.124 737.526,144.066C742.504,147.008 746.295,151.138 748.897,156.455L748.897,141.69L762.475,141.69ZM742.108,208.305C746.634,202.591 748.897,194.473 748.897,183.95C748.897,173.427 746.634,165.337 742.108,159.68C737.582,154.023 731.133,151.194 722.76,151.194C714.387,151.194 707.853,154.108 703.157,159.935C698.462,165.762 696.114,173.88 696.114,184.29C696.114,194.699 698.433,202.733 703.072,208.39C707.711,214.047 714.274,216.876 722.76,216.876C731.133,216.876 737.582,214.019 742.108,208.305Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M865.156,141.69L865.156,226.38C865.156,239.053 861.903,248.642 855.397,255.148C848.891,261.654 839.301,264.907 826.629,264.907C813.617,264.907 802.415,261.965 793.024,256.081L795.4,244.88C800.831,247.935 805.951,250.141 810.76,251.499C815.569,252.857 820.858,253.536 826.629,253.536C834.889,253.536 841.112,251.358 845.298,247.001C849.485,242.645 851.578,236.168 851.578,227.568L851.578,207.372C848.976,212.803 845.157,217.017 840.122,220.016C835.087,223.014 829.118,224.513 822.216,224.513C814.749,224.513 808.101,222.76 802.274,219.252C796.447,215.745 791.949,210.766 788.781,204.317C785.613,197.867 784.029,190.456 784.029,182.083C784.029,173.71 785.613,166.299 788.781,159.85C791.949,153.4 796.447,148.422 802.274,144.914C808.101,141.407 814.749,139.653 822.216,139.653C829.005,139.653 834.917,141.124 839.952,144.066C844.987,147.008 848.806,151.138 851.408,156.455L851.408,141.69L865.156,141.69ZM844.365,204.741C849.06,199.253 851.408,191.701 851.408,182.083C851.408,172.466 849.06,164.913 844.365,159.426C839.669,153.938 833.192,151.194 824.932,151.194C816.559,151.194 809.968,153.938 805.159,159.426C800.351,164.913 797.946,172.466 797.946,182.083C797.946,191.701 800.351,199.253 805.159,204.741C809.968,210.229 816.559,212.972 824.932,212.972C833.192,212.972 839.669,210.229 844.365,204.741Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M963.084,183.95L900.457,183.95C900.571,194.812 903.088,203.015 908.01,208.56C912.932,214.104 920.089,216.876 929.48,216.876C939.437,216.876 948.602,213.538 956.974,206.862L961.557,216.876C957.823,220.384 953.043,223.156 947.216,225.192C941.388,227.229 935.42,228.247 929.31,228.247C915.959,228.247 905.493,224.315 897.912,216.452C890.331,208.588 886.54,197.811 886.54,184.12C886.54,175.408 888.238,167.685 891.632,160.953C895.026,154.221 899.779,148.988 905.889,145.254C911.998,141.52 918.957,139.653 926.764,139.653C938.079,139.653 946.961,143.359 953.41,150.77C959.86,158.181 963.084,168.392 963.084,181.404L963.084,183.95ZM909.538,156.795C905.068,161.094 902.211,167.148 900.967,174.955L950.695,174.955C950.016,166.922 947.668,160.812 943.651,156.625C939.635,152.439 934.062,150.345 926.934,150.345C919.806,150.345 914.007,152.495 909.538,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M978.699,217.215L983.281,207.032C987.92,210.653 992.616,213.255 997.368,214.839C1002.12,216.423 1007.44,217.215 1013.32,217.215C1019.77,217.215 1024.66,216.112 1028,213.906C1031.34,211.7 1033.01,208.503 1033.01,204.317C1033.01,200.922 1031.88,198.207 1029.62,196.17C1027.35,194.133 1023.62,192.549 1018.41,191.418L1003.99,188.023C996.859,186.439 991.343,183.611 987.439,179.537C983.536,175.464 981.584,170.599 981.584,164.941C981.584,157.474 984.582,151.392 990.579,146.696C996.576,142.001 1004.5,139.653 1014.34,139.653C1020.34,139.653 1025.99,140.615 1031.31,142.538C1036.63,144.462 1041.1,147.234 1044.72,150.855L1040.14,160.868C1032.1,154.192 1023.5,150.855 1014.34,150.855C1008.23,150.855 1003.51,152.014 1000.17,154.334C996.831,156.653 995.162,159.906 995.162,164.093C995.162,167.6 996.208,170.373 998.301,172.409C1000.39,174.446 1003.76,176.03 1008.4,177.161L1022.83,180.725C1030.75,182.536 1036.63,185.336 1040.48,189.127C1044.32,192.917 1046.25,197.867 1046.25,203.977C1046.25,211.332 1043.25,217.215 1037.25,221.628C1031.26,226.041 1023.11,228.247 1012.81,228.247C998.443,228.247 987.072,224.57 978.699,217.215Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1161.66,215.349L1188.3,215.349L1188.3,227.059L1120.92,227.059L1120.92,215.349L1147.57,215.349L1147.57,123.53L1122.79,139.314L1122.79,125.906L1153.68,106.218L1161.66,106.218L1161.66,215.349Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1229.38,209.578L1229.38,221.968C1229.38,226.72 1228.58,231.076 1227,235.036C1225.42,238.996 1222.76,242.843 1219.02,246.577L1212.57,241.655C1216.99,236.564 1219.48,231.698 1220.04,227.059L1211.89,227.059L1211.89,209.578L1229.38,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1332.06,215.349L1332.06,227.059L1254.33,227.059L1254.33,216.537L1296.59,169.694C1302.24,163.357 1306.37,157.643 1308.98,152.552C1311.58,147.46 1312.88,142.369 1312.88,137.277C1312.88,130.601 1310.95,125.481 1307.11,121.917C1303.26,118.353 1297.77,116.571 1290.64,116.571C1279.1,116.571 1267.68,121.21 1256.36,130.488L1251.1,119.796C1255.85,115.27 1261.85,111.649 1269.09,108.934C1276.33,106.218 1283.63,104.86 1290.99,104.86C1302.07,104.86 1310.84,107.717 1317.29,113.431C1323.74,119.145 1326.97,126.867 1326.97,136.598C1326.97,143.5 1325.41,150.147 1322.3,156.54C1319.19,162.933 1314.01,170.09 1306.77,178.01L1272.32,215.349L1332.06,215.349Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1370.41,209.578L1370.41,221.968C1370.41,226.72 1369.62,231.076 1368.04,235.036C1366.45,238.996 1363.8,242.843 1360.06,246.577L1353.61,241.655C1358.02,236.564 1360.51,231.698 1361.08,227.059L1352.93,227.059L1352.93,209.578L1370.41,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1465.12,175.464C1468.85,180.443 1470.72,186.722 1470.72,194.303C1470.72,204.826 1467.15,213.114 1460.03,219.167C1452.9,225.221 1443.22,228.247 1431,228.247C1423.2,228.247 1415.7,226.946 1408.52,224.344C1401.33,221.741 1395.25,218.064 1390.27,213.312L1395.7,202.619C1406.9,211.898 1418.56,216.537 1430.66,216.537C1439.26,216.537 1445.8,214.613 1450.27,210.766C1454.74,206.919 1456.97,201.262 1456.97,193.794C1456.97,178.972 1447.69,171.561 1429.14,171.561L1415.22,171.561L1415.22,159.85L1426.42,159.85C1435.36,159.85 1442.21,157.87 1446.96,153.91C1451.71,149.949 1454.09,144.292 1454.09,136.938C1454.09,130.375 1452.13,125.34 1448.23,121.832C1444.33,118.325 1438.81,116.571 1431.68,116.571C1420.14,116.571 1408.71,121.21 1397.4,130.488L1392.14,119.796C1397,115.157 1402.97,111.508 1410.04,108.849C1417.12,106.19 1424.5,104.86 1432.19,104.86C1443.06,104.86 1451.74,107.632 1458.25,113.177C1464.75,118.721 1468,126.189 1468,135.58C1468,142.482 1466.31,148.535 1462.91,153.74C1459.52,158.945 1454.82,162.679 1448.83,164.941C1455.95,166.978 1461.38,170.486 1465.12,175.464Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.922959,-96.1682,447.236)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(201,23,126);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM764.103,106.414L764.103,344.325L1242.29,344.325L1242.29,106.414L764.103,106.414Z"/>

+    </g>

+    <g transform="matrix(0.617288,0,0,0.617288,584.538,514.244)">

+        <path d="M439.513,213.142L444.774,202.45C450.771,207.541 456.881,211.162 463.104,213.312C469.327,215.462 476.569,216.537 484.828,216.537C494.559,216.537 502.055,214.641 507.316,210.851C512.578,207.06 515.208,201.714 515.208,194.812C515.208,190.739 513.936,187.429 511.39,184.884C508.844,182.338 505.506,180.329 501.376,178.859C497.246,177.388 491.73,175.86 484.828,174.276C475.55,172.239 467.913,170.033 461.916,167.657C455.919,165.281 451.054,161.858 447.32,157.389C443.586,152.92 441.719,147.064 441.719,139.823C441.719,132.921 443.53,126.839 447.15,121.578C450.771,116.316 455.891,112.215 462.51,109.273C469.129,106.331 476.852,104.86 485.677,104.86C494.05,104.86 501.857,106.162 509.098,108.764C516.34,111.366 522.45,115.157 527.428,120.135L521.997,130.828C516.34,125.962 510.598,122.398 504.771,120.135C498.944,117.872 492.579,116.741 485.677,116.741C476.286,116.741 468.931,118.749 463.613,122.766C458.295,126.783 455.636,132.299 455.636,139.314C455.636,145.424 457.956,150.006 462.595,153.061C467.234,156.116 474.362,158.775 483.98,161.038C494.389,163.527 502.564,165.818 508.504,167.912C514.445,170.005 519.395,173.173 523.355,177.416C527.315,181.659 529.295,187.288 529.295,194.303C529.295,201.092 527.485,207.06 523.864,212.209C520.243,217.357 515.067,221.345 508.335,224.174C501.602,227.003 493.71,228.417 484.659,228.417C465.763,228.417 450.715,223.325 439.513,213.142Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M621.793,183.95L559.166,183.95C559.279,194.812 561.797,203.015 566.719,208.56C571.641,214.104 578.797,216.876 588.188,216.876C598.145,216.876 607.31,213.538 615.683,206.862L620.266,216.876C616.532,220.384 611.751,223.156 605.924,225.192C600.097,227.229 594.129,228.247 588.019,228.247C574.667,228.247 564.201,224.315 556.62,216.452C549.039,208.588 545.249,197.811 545.249,184.12C545.249,175.408 546.946,167.685 550.341,160.953C553.735,154.221 558.487,148.988 564.597,145.254C570.707,141.52 577.666,139.653 585.473,139.653C596.787,139.653 605.67,143.359 612.119,150.77C618.568,158.181 621.793,168.392 621.793,181.404L621.793,183.95ZM568.246,156.795C563.777,161.094 560.92,167.148 559.675,174.955L609.403,174.955C608.725,166.922 606.377,160.812 602.36,156.625C598.343,152.439 592.771,150.345 585.643,150.345C578.514,150.345 572.715,152.495 568.246,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M656.84,222.816C650.674,219.196 645.922,214.076 642.584,207.456C639.246,200.837 637.577,193.115 637.577,184.29C637.577,175.464 639.274,167.685 642.669,160.953C646.063,154.221 650.9,148.988 657.18,145.254C663.459,141.52 670.786,139.653 679.159,139.653C684.929,139.653 690.502,140.643 695.876,142.623C701.251,144.603 705.692,147.347 709.199,150.855L704.617,161.038C700.317,157.643 696.159,155.154 692.142,153.57C688.126,151.986 684.024,151.194 679.837,151.194C671.125,151.194 664.28,154.108 659.301,159.935C654.323,165.762 651.834,173.88 651.834,184.29C651.834,194.586 654.295,202.591 659.216,208.305C664.138,214.019 671.012,216.876 679.837,216.876C684.024,216.876 688.126,216.084 692.142,214.5C696.159,212.916 700.317,210.427 704.617,207.032L709.199,217.215C705.578,220.61 701.024,223.297 695.537,225.277C690.049,227.257 684.363,228.247 678.48,228.247C670.22,228.247 663.007,226.437 656.84,222.816Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M745.18,152.552L745.18,199.225C745.18,205.561 746.481,210.002 749.084,212.548C751.686,215.094 755.363,216.367 760.115,216.367C763.283,216.367 766.338,215.858 769.28,214.839L769.28,226.55C765.773,227.682 761.813,228.247 757.4,228.247C749.253,228.247 742.889,225.956 738.306,221.374C733.724,216.791 731.433,210.031 731.433,201.092L731.433,152.552L714.8,152.552L714.8,141.69L731.433,141.69L731.433,119.796L745.18,114.874L745.18,141.69L769.62,141.69L769.62,152.552L745.18,152.552Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M786.252,227.059L786.252,141.69L800,141.69L800,227.059L786.252,227.059ZM784.895,105.539L801.697,105.539L801.697,121.154L784.895,121.154L784.895,105.539Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M840.733,222.816C834.623,219.196 829.899,214.047 826.561,207.372C823.223,200.696 821.554,192.889 821.554,183.95C821.554,175.012 823.223,167.204 826.561,160.529C829.899,153.853 834.623,148.705 840.733,145.084C846.843,141.463 853.914,139.653 861.948,139.653C869.981,139.653 877.053,141.463 883.163,145.084C889.273,148.705 893.997,153.853 897.335,160.529C900.672,167.204 902.341,175.012 902.341,183.95C902.341,192.889 900.672,200.696 897.335,207.372C893.997,214.047 889.273,219.196 883.163,222.816C877.053,226.437 869.981,228.247 861.948,228.247C853.914,228.247 846.843,226.437 840.733,222.816ZM881.466,208.475C885.992,202.874 888.254,194.699 888.254,183.95C888.254,173.541 885.935,165.479 881.296,159.765C876.657,154.051 870.208,151.194 861.948,151.194C853.575,151.194 847.069,154.051 842.43,159.765C837.791,165.479 835.471,173.541 835.471,183.95C835.471,194.699 837.763,202.874 842.345,208.475C846.928,214.076 853.462,216.876 861.948,216.876C870.434,216.876 876.94,214.076 881.466,208.475Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M997.045,173.427L997.045,227.059L983.298,227.059L983.298,174.106C983.298,166.186 981.714,160.387 978.546,156.71C975.378,153.033 970.399,151.194 963.61,151.194C955.69,151.194 949.354,153.627 944.602,158.492C939.85,163.357 937.473,169.92 937.473,178.18L937.473,227.059L923.726,227.059L923.726,165.62C923.726,156.795 923.274,148.818 922.368,141.69L935.437,141.69L936.795,156.965C939.397,151.42 943.301,147.149 948.505,144.151C953.71,141.152 959.65,139.653 966.326,139.653C986.806,139.653 997.045,150.911 997.045,173.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1153.7,175.379C1157.55,180.414 1159.47,186.666 1159.47,194.133C1159.47,204.656 1155.96,212.774 1148.94,218.488C1141.93,224.202 1132.03,227.059 1119.24,227.059L1069.01,227.059L1069.01,106.218L1117.55,106.218C1129.88,106.218 1139.47,108.962 1146.32,114.45C1153.16,119.937 1156.58,127.716 1156.58,137.786C1156.58,144.236 1154.91,149.808 1151.58,154.504C1148.24,159.199 1143.57,162.679 1137.57,164.941C1144.48,166.865 1149.85,170.344 1153.7,175.379ZM1082.75,159.85L1115.34,159.85C1124.39,159.85 1131.24,158.039 1135.88,154.419C1140.52,150.798 1142.84,145.48 1142.84,138.465C1142.84,124.661 1133.67,117.759 1115.34,117.759L1082.75,117.759L1082.75,159.85ZM1139.02,210.172C1143.49,206.608 1145.72,201.149 1145.72,193.794C1145.72,178.972 1136.5,171.561 1118.06,171.561L1082.75,171.561L1082.75,215.518L1118.06,215.518C1127.56,215.518 1134.55,213.736 1139.02,210.172Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.339095,0,0,0.339095,803.293,652.189)">

+        <path d="M138.683,227.059L148.187,106.218L174.834,106.218L166.857,205.505L220.828,205.505L219.131,227.059L138.683,227.059Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M233.557,227.059L240.346,141.011L265.974,141.011L259.185,227.059L233.557,227.059ZM242.382,100.617L269.877,100.617L268.01,124.718L240.515,124.718L242.382,100.617Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M274.969,217.894L283.285,200.074C288.037,203.355 293.129,205.872 298.56,207.626C303.991,209.38 309.422,210.257 314.853,210.257C319.605,210.257 323.113,209.578 325.376,208.22C327.639,206.862 328.77,205.052 328.77,202.789C328.77,200.413 327.441,198.546 324.782,197.188C322.123,195.831 317.795,194.247 311.798,192.436C305.575,190.739 300.483,189.042 296.523,187.345C292.563,185.647 289.14,183.13 286.255,179.792C283.37,176.454 281.927,172.126 281.927,166.808C281.927,161.264 283.483,156.399 286.595,152.212C289.706,148.026 294.119,144.745 299.833,142.369C305.547,139.993 312.081,138.804 319.436,138.804C325.885,138.804 332.193,139.766 338.359,141.69C344.526,143.613 349.702,146.216 353.889,149.497L345.742,166.639C341.556,163.584 337.143,161.264 332.504,159.68C327.865,158.096 323.339,157.304 318.926,157.304C314.287,157.304 310.78,157.983 308.404,159.341C306.028,160.698 304.84,162.565 304.84,164.941C304.84,167.431 306.254,169.411 309.083,170.882C311.911,172.353 316.211,173.88 321.981,175.464C328.205,177.274 333.268,179.028 337.171,180.725C341.075,182.423 344.469,184.94 347.355,188.278C350.24,191.616 351.683,195.944 351.683,201.262C351.683,209.748 348.316,216.395 341.584,221.204C334.852,226.013 325.772,228.417 314.344,228.417C299.635,228.417 286.51,224.909 274.969,217.894Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M399.374,193.624C399.035,198.376 399.996,201.884 402.259,204.147C404.522,206.41 407.634,207.541 411.594,207.541C414.196,207.541 417.082,207.089 420.25,206.184L418.552,226.041C414.705,227.625 409.727,228.417 403.617,228.417C393.886,228.417 386.447,225.815 381.299,220.61C376.151,215.405 373.577,208.051 373.577,198.546C373.577,196.623 373.633,195.152 373.746,194.133L376.462,160.189L360.169,160.189L361.696,141.011L377.989,141.011L379.517,120.814L405.823,112.498L403.617,141.011L425.511,141.011L423.984,160.189L402.09,160.189L399.374,193.624Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M426.699,217.894L435.015,200.074C439.768,203.355 444.859,205.872 450.29,207.626C455.721,209.38 461.152,210.257 466.583,210.257C471.336,210.257 474.843,209.578 477.106,208.22C479.369,206.862 480.501,205.052 480.501,202.789C480.501,200.413 479.171,198.546 476.512,197.188C473.853,195.831 469.525,194.247 463.528,192.436C457.305,190.739 452.214,189.042 448.254,187.345C444.293,185.647 440.871,183.13 437.986,179.792C435.1,176.454 433.658,172.126 433.658,166.808C433.658,161.264 435.213,156.399 438.325,152.212C441.436,148.026 445.849,144.745 451.563,142.369C457.277,139.993 463.811,138.804 471.166,138.804C477.615,138.804 483.923,139.766 490.09,141.69C496.256,143.613 501.433,146.216 505.619,149.497L497.473,166.639C493.286,163.584 488.873,161.264 484.234,159.68C479.595,158.096 475.069,157.304 470.657,157.304C466.018,157.304 462.51,157.983 460.134,159.341C457.758,160.698 456.57,162.565 456.57,164.941C456.57,167.431 457.984,169.411 460.813,170.882C463.642,172.353 467.941,173.88 473.712,175.464C479.935,177.274 484.998,179.028 488.902,180.725C492.805,182.423 496.2,184.94 499.085,188.278C501.97,191.616 503.413,195.944 503.413,201.262C503.413,209.748 500.047,216.395 493.314,221.204C486.582,226.013 477.502,228.417 466.074,228.417C451.365,228.417 438.24,224.909 426.699,217.894Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M569.264,106.218L617.465,106.218C629.911,106.218 639.614,109.217 646.572,115.213C653.531,121.21 657.01,129.47 657.01,139.993C657.01,150.515 653.502,158.803 646.487,164.857C639.472,170.91 629.798,173.937 617.465,173.937L583.182,173.937L583.182,227.059L569.264,227.059L569.264,106.218ZM616.277,162.396C625.216,162.396 631.948,160.472 636.474,156.625C641,152.778 643.263,147.234 643.263,139.993C643.263,132.751 641,127.235 636.474,123.445C631.948,119.654 625.216,117.759 616.277,117.759L583.182,117.759L583.182,162.396L616.277,162.396Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M750.526,141.69L750.526,227.059L736.948,227.059L736.948,211.615C734.459,216.933 730.697,221.034 725.662,223.919C720.627,226.805 714.772,228.247 708.096,228.247C700.515,228.247 693.868,226.437 688.154,222.816C682.44,219.196 678.027,214.076 674.916,207.456C671.804,200.837 670.248,193.115 670.248,184.29C670.248,175.464 671.832,167.685 675,160.953C678.169,154.221 682.61,148.988 688.324,145.254C694.037,141.52 700.628,139.653 708.096,139.653C714.772,139.653 720.599,141.124 725.577,144.066C730.556,147.008 734.346,151.138 736.948,156.455L736.948,141.69L750.526,141.69ZM730.16,208.305C734.686,202.591 736.948,194.473 736.948,183.95C736.948,173.427 734.686,165.337 730.16,159.68C725.634,154.023 719.184,151.194 710.812,151.194C702.439,151.194 695.904,154.108 691.209,159.935C686.513,165.762 684.165,173.88 684.165,184.29C684.165,194.699 686.485,202.733 691.124,208.39C695.763,214.047 702.325,216.876 710.812,216.876C719.184,216.876 725.634,214.019 730.16,208.305Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M853.207,141.69L853.207,226.38C853.207,239.053 849.954,248.642 843.448,255.148C836.942,261.654 827.353,264.907 814.681,264.907C801.669,264.907 790.467,261.965 781.076,256.081L783.452,244.88C788.883,247.935 794.003,250.141 798.812,251.499C803.62,252.857 808.91,253.536 814.681,253.536C822.94,253.536 829.163,251.358 833.35,247.001C837.536,242.645 839.63,236.168 839.63,227.568L839.63,207.372C837.027,212.803 833.208,217.017 828.173,220.016C823.138,223.014 817.17,224.513 810.268,224.513C802.8,224.513 796.153,222.76 790.326,219.252C784.499,215.745 780.001,210.766 776.833,204.317C773.665,197.867 772.081,190.456 772.081,182.083C772.081,173.71 773.665,166.299 776.833,159.85C780.001,153.4 784.499,148.422 790.326,144.914C796.153,141.407 802.8,139.653 810.268,139.653C817.057,139.653 822.969,141.124 828.004,144.066C833.039,147.008 836.857,151.138 839.46,156.455L839.46,141.69L853.207,141.69ZM832.416,204.741C837.112,199.253 839.46,191.701 839.46,182.083C839.46,172.466 837.112,164.913 832.416,159.426C827.721,153.938 821.243,151.194 812.983,151.194C804.61,151.194 798.02,153.938 793.211,159.426C788.402,164.913 785.998,172.466 785.998,182.083C785.998,191.701 788.402,199.253 793.211,204.741C798.02,210.229 804.61,212.972 812.983,212.972C821.243,212.972 827.721,210.229 832.416,204.741Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M951.136,183.95L888.509,183.95C888.622,194.812 891.14,203.015 896.062,208.56C900.984,214.104 908.14,216.876 917.531,216.876C927.488,216.876 936.653,213.538 945.026,206.862L949.609,216.876C945.875,220.384 941.094,223.156 935.267,225.192C929.44,227.229 923.472,228.247 917.362,228.247C904.01,228.247 893.544,224.315 885.963,216.452C878.382,208.588 874.592,197.811 874.592,184.12C874.592,175.408 876.289,167.685 879.684,160.953C883.078,154.221 887.83,148.988 893.94,145.254C900.05,141.52 907.009,139.653 914.816,139.653C926.13,139.653 935.013,143.359 941.462,150.77C947.911,158.181 951.136,168.392 951.136,181.404L951.136,183.95ZM897.589,156.795C893.12,161.094 890.263,167.148 889.018,174.955L938.746,174.955C938.068,166.922 935.72,160.812 931.703,156.625C927.686,152.439 922.114,150.345 914.985,150.345C907.857,150.345 902.058,152.495 897.589,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M966.75,217.215L971.333,207.032C975.972,210.653 980.667,213.255 985.42,214.839C990.172,216.423 995.49,217.215 1001.37,217.215C1007.82,217.215 1012.72,216.112 1016.05,213.906C1019.39,211.7 1021.06,208.503 1021.06,204.317C1021.06,200.922 1019.93,198.207 1017.67,196.17C1015.4,194.133 1011.67,192.549 1006.47,191.418L992.039,188.023C984.91,186.439 979.394,183.611 975.491,179.537C971.587,175.464 969.636,170.599 969.636,164.941C969.636,157.474 972.634,151.392 978.631,146.696C984.628,142.001 992.548,139.653 1002.39,139.653C1008.39,139.653 1014.05,140.615 1019.36,142.538C1024.68,144.462 1029.15,147.234 1032.77,150.855L1028.19,160.868C1020.16,154.192 1011.56,150.855 1002.39,150.855C996.282,150.855 991.558,152.014 988.22,154.334C984.882,156.653 983.213,159.906 983.213,164.093C983.213,167.6 984.26,170.373 986.353,172.409C988.446,174.446 991.812,176.03 996.451,177.161L1010.88,180.725C1018.8,182.536 1024.68,185.336 1028.53,189.127C1032.38,192.917 1034.3,197.867 1034.3,203.977C1034.3,211.332 1031.3,217.215 1025.3,221.628C1019.31,226.041 1011.16,228.247 1000.86,228.247C986.494,228.247 975.123,224.57 966.75,217.215Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1183.48,189.212L1183.48,200.753L1165.15,200.753L1165.15,227.059L1151.24,227.059L1151.24,200.753L1095.57,200.753L1095.57,190.23L1153.78,106.218L1165.15,106.218L1165.15,189.212L1183.48,189.212ZM1110,189.212L1151.24,189.212L1151.24,129.809L1110,189.212Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1217.43,209.578L1217.43,221.968C1217.43,226.72 1216.64,231.076 1215.05,235.036C1213.47,238.996 1210.81,242.843 1207.08,246.577L1200.62,241.655C1205.04,236.564 1207.53,231.698 1208.09,227.059L1199.95,227.059L1199.95,209.578L1217.43,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1304.24,156.031C1309.95,159.256 1314.34,163.753 1317.39,169.524C1320.45,175.294 1321.98,181.97 1321.98,189.551C1321.98,197.132 1320.31,203.864 1316.97,209.748C1313.63,215.631 1308.88,220.186 1302.71,223.41C1296.55,226.635 1289.33,228.247 1281.07,228.247C1273.72,228.247 1266.48,226.918 1259.35,224.259C1252.22,221.6 1246.22,217.951 1241.36,213.312L1246.62,202.619C1257.82,211.898 1269.31,216.537 1281.07,216.537C1289.56,216.537 1296.21,214.132 1301.02,209.323C1305.82,204.515 1308.23,197.98 1308.23,189.721C1308.23,181.687 1305.85,175.21 1301.1,170.288C1296.35,165.366 1290.01,162.905 1282.09,162.905C1270.55,162.905 1261.33,167.6 1254.43,176.992L1244.75,176.992L1244.75,106.218L1317.22,106.218L1317.22,117.759L1258.67,117.759L1258.67,160.868C1265.35,154.419 1273.89,151.194 1284.3,151.194C1291.88,151.194 1298.53,152.806 1304.24,156.031Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1358.47,209.578L1358.47,221.968C1358.47,226.72 1357.67,231.076 1356.09,235.036C1354.51,238.996 1351.85,242.843 1348.11,246.577L1341.66,241.655C1346.08,236.564 1348.57,231.698 1349.13,227.059L1340.98,227.059L1340.98,209.578L1358.47,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1444.94,156.031C1450.65,159.256 1455.09,163.782 1458.26,169.609C1461.43,175.436 1463.01,182.083 1463.01,189.551C1463.01,197.019 1461.35,203.694 1458.01,209.578C1454.67,215.462 1450.06,220.072 1444.17,223.41C1438.29,226.748 1431.62,228.417 1424.15,228.417C1409.55,228.417 1398.29,223.325 1390.37,213.142C1382.45,202.959 1378.49,188.476 1378.49,169.694C1378.49,156.116 1380.33,144.462 1384.01,134.731C1387.69,125.001 1393,117.589 1399.96,112.498C1406.92,107.406 1415.27,104.86 1425,104.86C1432.01,104.86 1438.83,106.162 1445.45,108.764C1452.07,111.366 1457.87,115.044 1462.84,119.796L1457.58,130.488C1451.92,125.736 1446.49,122.228 1441.29,119.965C1436.09,117.703 1430.77,116.571 1425.34,116.571C1414.93,116.571 1406.84,121.21 1401.07,130.488C1395.3,139.766 1392.41,152.778 1392.41,169.524L1392.41,172.07C1395.01,165.62 1399.26,160.529 1405.14,156.795C1411.02,153.061 1417.76,151.194 1425.34,151.194C1432.69,151.194 1439.22,152.806 1444.94,156.031ZM1442.14,209.323C1446.89,204.402 1449.27,197.867 1449.27,189.721C1449.27,181.687 1446.86,175.21 1442.05,170.288C1437.24,165.366 1430.99,162.905 1423.3,162.905C1415.38,162.905 1408.93,165.394 1403.95,170.373C1398.97,175.351 1396.48,181.8 1396.48,189.721C1396.48,197.754 1398.97,204.26 1403.95,209.239C1408.93,214.217 1415.43,216.706 1423.47,216.706C1431.16,216.706 1437.39,214.245 1442.14,209.323Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.922959,618.874,447.236)">

+        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(201,23,126);"/>

+        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM764.103,106.414L764.103,344.325L1242.29,344.325L1242.29,106.414L764.103,106.414Z"/>

+    </g>

+    <g transform="matrix(0.617288,0,0,0.617288,1298.32,514.244)">

+        <path d="M439.258,213.142L444.52,202.45C450.517,207.541 456.626,211.162 462.85,213.312C469.073,215.462 476.314,216.537 484.574,216.537C494.304,216.537 501.8,214.641 507.062,210.851C512.323,207.06 514.954,201.714 514.954,194.812C514.954,190.739 513.681,187.429 511.135,184.884C508.589,182.338 505.251,180.329 501.122,178.859C496.992,177.388 491.476,175.86 484.574,174.276C475.296,172.239 467.658,170.033 461.662,167.657C455.665,165.281 450.799,161.858 447.066,157.389C443.332,152.92 441.465,147.064 441.465,139.823C441.465,132.921 443.275,126.839 446.896,121.578C450.517,116.316 455.636,112.215 462.256,109.273C468.875,106.331 476.597,104.86 485.422,104.86C493.795,104.86 501.602,106.162 508.844,108.764C516.085,111.366 522.195,115.157 527.174,120.135L521.743,130.828C516.085,125.962 510.343,122.398 504.516,120.135C498.689,117.872 492.324,116.741 485.422,116.741C476.031,116.741 468.677,118.749 463.359,122.766C458.041,126.783 455.382,132.299 455.382,139.314C455.382,145.424 457.701,150.006 462.34,153.061C466.979,156.116 474.108,158.775 483.725,161.038C494.135,163.527 502.31,165.818 508.25,167.912C514.19,170.005 519.14,173.173 523.1,177.416C527.061,181.659 529.041,187.288 529.041,194.303C529.041,201.092 527.23,207.06 523.61,212.209C519.989,217.357 514.812,221.345 508.08,224.174C501.348,227.003 493.456,228.417 484.404,228.417C465.509,228.417 450.46,223.325 439.258,213.142Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M621.538,183.95L558.911,183.95C559.025,194.812 561.542,203.015 566.464,208.56C571.386,214.104 578.543,216.876 587.934,216.876C597.891,216.876 607.056,213.538 615.428,206.862L620.011,216.876C616.277,220.384 611.497,223.156 605.67,225.192C599.842,227.229 593.874,228.247 587.764,228.247C574.413,228.247 563.947,224.315 556.366,216.452C548.785,208.588 544.994,197.811 544.994,184.12C544.994,175.408 546.692,167.685 550.086,160.953C553.48,154.221 558.233,148.988 564.343,145.254C570.453,141.52 577.411,139.653 585.218,139.653C596.533,139.653 605.415,143.359 611.864,150.77C618.314,158.181 621.538,168.392 621.538,181.404L621.538,183.95ZM567.992,156.795C563.522,161.094 560.665,167.148 559.421,174.955L609.149,174.955C608.47,166.922 606.122,160.812 602.105,156.625C598.089,152.439 592.516,150.345 585.388,150.345C578.26,150.345 572.461,152.495 567.992,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M656.586,222.816C650.419,219.196 645.667,214.076 642.329,207.456C638.991,200.837 637.322,193.115 637.322,184.29C637.322,175.464 639.02,167.685 642.414,160.953C645.808,154.221 650.646,148.988 656.925,145.254C663.205,141.52 670.531,139.653 678.904,139.653C684.675,139.653 690.247,140.643 695.622,142.623C700.996,144.603 705.437,147.347 708.945,150.855L704.362,161.038C700.063,157.643 695.904,155.154 691.888,153.57C687.871,151.986 683.769,151.194 679.583,151.194C670.871,151.194 664.025,154.108 659.047,159.935C654.068,165.762 651.579,173.88 651.579,184.29C651.579,194.586 654.04,202.591 658.962,208.305C663.884,214.019 670.757,216.876 679.583,216.876C683.769,216.876 687.871,216.084 691.888,214.5C695.904,212.916 700.063,210.427 704.362,207.032L708.945,217.215C705.324,220.61 700.77,223.297 695.282,225.277C689.794,227.257 684.109,228.247 678.225,228.247C669.965,228.247 662.752,226.437 656.586,222.816Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M744.925,152.552L744.925,199.225C744.925,205.561 746.227,210.002 748.829,212.548C751.431,215.094 755.109,216.367 759.861,216.367C763.029,216.367 766.084,215.858 769.026,214.839L769.026,226.55C765.518,227.682 761.558,228.247 757.145,228.247C748.999,228.247 742.634,225.956 738.052,221.374C733.469,216.791 731.178,210.031 731.178,201.092L731.178,152.552L714.545,152.552L714.545,141.69L731.178,141.69L731.178,119.796L744.925,114.874L744.925,141.69L769.365,141.69L769.365,152.552L744.925,152.552Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M785.998,227.059L785.998,141.69L799.745,141.69L799.745,227.059L785.998,227.059ZM784.64,105.539L801.442,105.539L801.442,121.154L784.64,121.154L784.64,105.539Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M840.478,222.816C834.368,219.196 829.644,214.047 826.306,207.372C822.969,200.696 821.3,192.889 821.3,183.95C821.3,175.012 822.969,167.204 826.306,160.529C829.644,153.853 834.368,148.705 840.478,145.084C846.588,141.463 853.66,139.653 861.693,139.653C869.727,139.653 876.798,141.463 882.908,145.084C889.018,148.705 893.742,153.853 897.08,160.529C900.418,167.204 902.087,175.012 902.087,183.95C902.087,192.889 900.418,200.696 897.08,207.372C893.742,214.047 889.018,219.196 882.908,222.816C876.798,226.437 869.727,228.247 861.693,228.247C853.66,228.247 846.588,226.437 840.478,222.816ZM881.211,208.475C885.737,202.874 888,194.699 888,183.95C888,173.541 885.68,165.479 881.041,159.765C876.402,154.051 869.953,151.194 861.693,151.194C853.32,151.194 846.814,154.051 842.175,159.765C837.536,165.479 835.217,173.541 835.217,183.95C835.217,194.699 837.508,202.874 842.09,208.475C846.673,214.076 853.207,216.876 861.693,216.876C870.179,216.876 876.685,214.076 881.211,208.475Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M996.791,173.427L996.791,227.059L983.043,227.059L983.043,174.106C983.043,166.186 981.459,160.387 978.291,156.71C975.123,153.033 970.145,151.194 963.356,151.194C955.436,151.194 949.099,153.627 944.347,158.492C939.595,163.357 937.219,169.92 937.219,178.18L937.219,227.059L923.472,227.059L923.472,165.62C923.472,156.795 923.019,148.818 922.114,141.69L935.182,141.69L936.54,156.965C939.142,151.42 943.046,147.149 948.251,144.151C953.456,141.152 959.396,139.653 966.071,139.653C986.551,139.653 996.791,150.911 996.791,173.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1090.56,220.949C1082.13,215.971 1075.65,208.814 1071.13,199.48C1066.6,190.145 1064.34,179.141 1064.34,166.469C1064.34,153.796 1066.6,142.849 1071.13,133.628C1075.65,124.407 1082.13,117.307 1090.56,112.328C1098.99,107.35 1108.92,104.86 1120.35,104.86C1128.72,104.86 1136.39,106.133 1143.35,108.679C1150.3,111.225 1156.33,115.044 1161.42,120.135L1156.16,130.828C1150.39,125.849 1144.7,122.285 1139.1,120.135C1133.5,117.985 1127.31,116.911 1120.52,116.911C1107.28,116.911 1097.01,121.21 1089.71,129.809C1082.41,138.408 1078.77,150.628 1078.77,166.469C1078.77,182.423 1082.39,194.727 1089.63,203.383C1096.87,212.039 1107.17,216.367 1120.52,216.367C1127.31,216.367 1133.5,215.292 1139.1,213.142C1144.7,210.992 1150.39,207.428 1156.16,202.45L1161.42,213.142C1156.33,218.234 1150.3,222.052 1143.35,224.598C1136.39,227.144 1128.72,228.417 1120.35,228.417C1108.92,228.417 1098.99,225.928 1090.56,220.949Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.347283,0,0,0.347283,1511.01,651.331)">

+        <path d="M138.683,227.059L148.187,106.218L174.834,106.218L166.857,205.505L220.828,205.505L219.131,227.059L138.683,227.059Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M233.557,227.059L240.346,141.011L265.974,141.011L259.185,227.059L233.557,227.059ZM242.382,100.617L269.877,100.617L268.01,124.718L240.515,124.718L242.382,100.617Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M274.969,217.894L283.285,200.074C288.037,203.355 293.129,205.872 298.56,207.626C303.991,209.38 309.422,210.257 314.853,210.257C319.605,210.257 323.113,209.578 325.376,208.22C327.639,206.862 328.77,205.052 328.77,202.789C328.77,200.413 327.441,198.546 324.782,197.188C322.123,195.831 317.795,194.247 311.798,192.436C305.575,190.739 300.483,189.042 296.523,187.345C292.563,185.647 289.14,183.13 286.255,179.792C283.37,176.454 281.927,172.126 281.927,166.808C281.927,161.264 283.483,156.399 286.595,152.212C289.706,148.026 294.119,144.745 299.833,142.369C305.547,139.993 312.081,138.804 319.436,138.804C325.885,138.804 332.193,139.766 338.359,141.69C344.526,143.613 349.702,146.216 353.889,149.497L345.742,166.639C341.556,163.584 337.143,161.264 332.504,159.68C327.865,158.096 323.339,157.304 318.926,157.304C314.287,157.304 310.78,157.983 308.404,159.341C306.028,160.698 304.84,162.565 304.84,164.941C304.84,167.431 306.254,169.411 309.083,170.882C311.911,172.353 316.211,173.88 321.981,175.464C328.205,177.274 333.268,179.028 337.171,180.725C341.075,182.423 344.469,184.94 347.355,188.278C350.24,191.616 351.683,195.944 351.683,201.262C351.683,209.748 348.316,216.395 341.584,221.204C334.852,226.013 325.772,228.417 314.344,228.417C299.635,228.417 286.51,224.909 274.969,217.894Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M399.374,193.624C399.035,198.376 399.996,201.884 402.259,204.147C404.522,206.41 407.634,207.541 411.594,207.541C414.196,207.541 417.082,207.089 420.25,206.184L418.552,226.041C414.705,227.625 409.727,228.417 403.617,228.417C393.886,228.417 386.447,225.815 381.299,220.61C376.151,215.405 373.577,208.051 373.577,198.546C373.577,196.623 373.633,195.152 373.746,194.133L376.462,160.189L360.169,160.189L361.696,141.011L377.989,141.011L379.517,120.814L405.823,112.498L403.617,141.011L425.511,141.011L423.984,160.189L402.09,160.189L399.374,193.624Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M426.699,217.894L435.015,200.074C439.768,203.355 444.859,205.872 450.29,207.626C455.721,209.38 461.152,210.257 466.583,210.257C471.336,210.257 474.843,209.578 477.106,208.22C479.369,206.862 480.501,205.052 480.501,202.789C480.501,200.413 479.171,198.546 476.512,197.188C473.853,195.831 469.525,194.247 463.528,192.436C457.305,190.739 452.214,189.042 448.254,187.345C444.293,185.647 440.871,183.13 437.986,179.792C435.1,176.454 433.658,172.126 433.658,166.808C433.658,161.264 435.213,156.399 438.325,152.212C441.436,148.026 445.849,144.745 451.563,142.369C457.277,139.993 463.811,138.804 471.166,138.804C477.615,138.804 483.923,139.766 490.09,141.69C496.256,143.613 501.433,146.216 505.619,149.497L497.473,166.639C493.286,163.584 488.873,161.264 484.234,159.68C479.595,158.096 475.069,157.304 470.657,157.304C466.018,157.304 462.51,157.983 460.134,159.341C457.758,160.698 456.57,162.565 456.57,164.941C456.57,167.431 457.984,169.411 460.813,170.882C463.642,172.353 467.941,173.88 473.712,175.464C479.935,177.274 484.998,179.028 488.902,180.725C492.805,182.423 496.2,184.94 499.085,188.278C501.97,191.616 503.413,195.944 503.413,201.262C503.413,209.748 500.047,216.395 493.314,221.204C486.582,226.013 477.502,228.417 466.074,228.417C451.365,228.417 438.24,224.909 426.699,217.894Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M569.264,106.218L617.465,106.218C629.911,106.218 639.614,109.217 646.572,115.213C653.531,121.21 657.01,129.47 657.01,139.993C657.01,150.515 653.502,158.803 646.487,164.857C639.472,170.91 629.798,173.937 617.465,173.937L583.182,173.937L583.182,227.059L569.264,227.059L569.264,106.218ZM616.277,162.396C625.216,162.396 631.948,160.472 636.474,156.625C641,152.778 643.263,147.234 643.263,139.993C643.263,132.751 641,127.235 636.474,123.445C631.948,119.654 625.216,117.759 616.277,117.759L583.182,117.759L583.182,162.396L616.277,162.396Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M750.526,141.69L750.526,227.059L736.948,227.059L736.948,211.615C734.459,216.933 730.697,221.034 725.662,223.919C720.627,226.805 714.772,228.247 708.096,228.247C700.515,228.247 693.868,226.437 688.154,222.816C682.44,219.196 678.027,214.076 674.916,207.456C671.804,200.837 670.248,193.115 670.248,184.29C670.248,175.464 671.832,167.685 675,160.953C678.169,154.221 682.61,148.988 688.324,145.254C694.037,141.52 700.628,139.653 708.096,139.653C714.772,139.653 720.599,141.124 725.577,144.066C730.556,147.008 734.346,151.138 736.948,156.455L736.948,141.69L750.526,141.69ZM730.16,208.305C734.686,202.591 736.948,194.473 736.948,183.95C736.948,173.427 734.686,165.337 730.16,159.68C725.634,154.023 719.184,151.194 710.812,151.194C702.439,151.194 695.904,154.108 691.209,159.935C686.513,165.762 684.165,173.88 684.165,184.29C684.165,194.699 686.485,202.733 691.124,208.39C695.763,214.047 702.325,216.876 710.812,216.876C719.184,216.876 725.634,214.019 730.16,208.305Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M853.207,141.69L853.207,226.38C853.207,239.053 849.954,248.642 843.448,255.148C836.942,261.654 827.353,264.907 814.681,264.907C801.669,264.907 790.467,261.965 781.076,256.081L783.452,244.88C788.883,247.935 794.003,250.141 798.812,251.499C803.62,252.857 808.91,253.536 814.681,253.536C822.94,253.536 829.163,251.358 833.35,247.001C837.536,242.645 839.63,236.168 839.63,227.568L839.63,207.372C837.027,212.803 833.208,217.017 828.173,220.016C823.138,223.014 817.17,224.513 810.268,224.513C802.8,224.513 796.153,222.76 790.326,219.252C784.499,215.745 780.001,210.766 776.833,204.317C773.665,197.867 772.081,190.456 772.081,182.083C772.081,173.71 773.665,166.299 776.833,159.85C780.001,153.4 784.499,148.422 790.326,144.914C796.153,141.407 802.8,139.653 810.268,139.653C817.057,139.653 822.969,141.124 828.004,144.066C833.039,147.008 836.857,151.138 839.46,156.455L839.46,141.69L853.207,141.69ZM832.416,204.741C837.112,199.253 839.46,191.701 839.46,182.083C839.46,172.466 837.112,164.913 832.416,159.426C827.721,153.938 821.243,151.194 812.983,151.194C804.61,151.194 798.02,153.938 793.211,159.426C788.402,164.913 785.998,172.466 785.998,182.083C785.998,191.701 788.402,199.253 793.211,204.741C798.02,210.229 804.61,212.972 812.983,212.972C821.243,212.972 827.721,210.229 832.416,204.741Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M951.136,183.95L888.509,183.95C888.622,194.812 891.14,203.015 896.062,208.56C900.984,214.104 908.14,216.876 917.531,216.876C927.488,216.876 936.653,213.538 945.026,206.862L949.609,216.876C945.875,220.384 941.094,223.156 935.267,225.192C929.44,227.229 923.472,228.247 917.362,228.247C904.01,228.247 893.544,224.315 885.963,216.452C878.382,208.588 874.592,197.811 874.592,184.12C874.592,175.408 876.289,167.685 879.684,160.953C883.078,154.221 887.83,148.988 893.94,145.254C900.05,141.52 907.009,139.653 914.816,139.653C926.13,139.653 935.013,143.359 941.462,150.77C947.911,158.181 951.136,168.392 951.136,181.404L951.136,183.95ZM897.589,156.795C893.12,161.094 890.263,167.148 889.018,174.955L938.746,174.955C938.068,166.922 935.72,160.812 931.703,156.625C927.686,152.439 922.114,150.345 914.985,150.345C907.857,150.345 902.058,152.495 897.589,156.795Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M966.75,217.215L971.333,207.032C975.972,210.653 980.667,213.255 985.42,214.839C990.172,216.423 995.49,217.215 1001.37,217.215C1007.82,217.215 1012.72,216.112 1016.05,213.906C1019.39,211.7 1021.06,208.503 1021.06,204.317C1021.06,200.922 1019.93,198.207 1017.67,196.17C1015.4,194.133 1011.67,192.549 1006.47,191.418L992.039,188.023C984.91,186.439 979.394,183.611 975.491,179.537C971.587,175.464 969.636,170.599 969.636,164.941C969.636,157.474 972.634,151.392 978.631,146.696C984.628,142.001 992.548,139.653 1002.39,139.653C1008.39,139.653 1014.05,140.615 1019.36,142.538C1024.68,144.462 1029.15,147.234 1032.77,150.855L1028.19,160.868C1020.16,154.192 1011.56,150.855 1002.39,150.855C996.282,150.855 991.558,152.014 988.22,154.334C984.882,156.653 983.213,159.906 983.213,164.093C983.213,167.6 984.26,170.373 986.353,172.409C988.446,174.446 991.812,176.03 996.451,177.161L1010.88,180.725C1018.8,182.536 1024.68,185.336 1028.53,189.127C1032.38,192.917 1034.3,197.867 1034.3,203.977C1034.3,211.332 1031.3,217.215 1025.3,221.628C1019.31,226.041 1011.16,228.247 1000.86,228.247C986.494,228.247 975.123,224.57 966.75,217.215Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1098.28,106.218L1178.05,106.218L1178.05,116.571L1121.37,227.059L1106.43,227.059L1162.78,117.929L1098.28,117.929L1098.28,106.218Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1217.43,209.578L1217.43,221.968C1217.43,226.72 1216.64,231.076 1215.05,235.036C1213.47,238.996 1210.81,242.843 1207.08,246.577L1200.62,241.655C1205.04,236.564 1207.53,231.698 1208.09,227.059L1199.95,227.059L1199.95,209.578L1217.43,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1315.95,176.058C1320.31,181.32 1322.49,187.627 1322.49,194.982C1322.49,205.278 1318.58,213.397 1310.77,219.337C1302.97,225.277 1292.44,228.247 1279.21,228.247C1265.97,228.247 1255.44,225.277 1247.64,219.337C1239.83,213.397 1235.93,205.278 1235.93,194.982C1235.93,187.627 1238.16,181.291 1242.63,175.973C1247.1,170.655 1253.24,166.978 1261.05,164.941C1253.81,162.792 1248.26,159.256 1244.41,154.334C1240.57,149.412 1238.64,143.613 1238.64,136.938C1238.64,130.488 1240.34,124.859 1243.73,120.05C1247.13,115.242 1251.91,111.508 1258.08,108.849C1264.24,106.19 1271.29,104.86 1279.21,104.86C1287.13,104.86 1294.17,106.19 1300.34,108.849C1306.5,111.508 1311.28,115.242 1314.68,120.05C1318.07,124.859 1319.77,130.488 1319.77,136.938C1319.77,143.613 1317.82,149.412 1313.91,154.334C1310.01,159.256 1304.55,162.792 1297.54,164.941C1305.46,167.091 1311.59,170.797 1315.95,176.058ZM1259.77,153.655C1264.58,157.672 1271.06,160.133 1279.21,161.038C1287.35,160.133 1293.83,157.672 1298.64,153.655C1303.45,149.638 1305.85,144.405 1305.85,137.956C1305.85,131.28 1303.5,126.019 1298.81,122.172C1294.11,118.325 1287.58,116.401 1279.21,116.401C1270.83,116.401 1264.3,118.325 1259.6,122.172C1254.91,126.019 1252.56,131.28 1252.56,137.956C1252.56,144.405 1254.96,149.638 1259.77,153.655ZM1301.1,210.936C1306.19,207.089 1308.74,201.488 1308.74,194.133C1308.74,187.458 1306.05,182.112 1300.68,178.095C1295.3,174.078 1288.14,171.617 1279.21,170.712C1270.27,171.617 1263.11,174.078 1257.74,178.095C1252.36,182.112 1249.67,187.458 1249.67,194.133C1249.67,201.488 1252.22,207.089 1257.31,210.936C1262.4,214.783 1269.7,216.706 1279.21,216.706C1288.71,216.706 1296.01,214.783 1301.1,210.936Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1358.47,209.578L1358.47,221.968C1358.47,226.72 1357.67,231.076 1356.09,235.036C1354.51,238.996 1351.85,242.843 1348.11,246.577L1341.66,241.655C1346.08,236.564 1348.57,231.698 1349.13,227.059L1340.98,227.059L1340.98,209.578L1358.47,209.578Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        <path d="M1450.29,120.135C1458.2,130.318 1462.16,144.801 1462.16,163.584C1462.16,184.063 1458.06,199.989 1449.86,211.36C1441.66,222.731 1430.2,228.417 1415.49,228.417C1408.59,228.417 1401.83,227.116 1395.21,224.513C1388.59,221.911 1382.74,218.234 1377.64,213.482L1383.08,202.789C1388.85,207.655 1394.33,211.19 1399.54,213.397C1404.74,215.603 1410,216.706 1415.32,216.706C1425.73,216.706 1433.79,212.067 1439.51,202.789C1445.22,193.511 1448.08,180.499 1448.08,163.753L1448.08,161.547C1445.48,167.883 1441.23,172.89 1435.35,176.567C1429.46,180.245 1422.73,182.083 1415.15,182.083C1407.8,182.083 1401.29,180.471 1395.63,177.246C1389.98,174.022 1385.56,169.496 1382.4,163.669C1379.23,157.841 1377.64,151.194 1377.64,143.726C1377.64,136.259 1379.31,129.583 1382.65,123.699C1385.99,117.816 1390.6,113.205 1396.48,109.867C1402.37,106.529 1409.04,104.86 1416.51,104.86C1431.11,104.86 1442.36,109.952 1450.29,120.135ZM1436.71,162.905C1441.68,157.926 1444.17,151.477 1444.17,143.557C1444.17,135.523 1441.68,129.017 1436.71,124.039C1431.73,119.06 1425.22,116.571 1417.19,116.571C1409.5,116.571 1403.27,119.032 1398.52,123.954C1393.77,128.876 1391.39,135.41 1391.39,143.557C1391.39,151.59 1393.77,158.068 1398.52,162.99C1403.27,167.912 1409.55,170.373 1417.36,170.373C1425.28,170.373 1431.73,167.883 1436.71,162.905Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,-46.5234,169.171)">

+        <path d="M224.566,862.452L251.212,862.452L251.212,874.163L183.833,874.163L183.833,862.452L210.479,862.452L210.479,770.633L185.7,786.417L185.7,773.009L216.589,753.321L224.566,753.321L224.566,862.452Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,162.243,169.171)">

+        <path d="M253.927,862.452L253.927,874.163L176.195,874.163L176.195,863.64L218.456,816.797C224.113,810.461 228.243,804.747 230.845,799.655C233.448,794.564 234.749,789.472 234.749,784.38C234.749,777.705 232.825,772.585 228.978,769.021C225.131,765.456 219.644,763.674 212.515,763.674C200.974,763.674 189.547,768.313 178.232,777.592L172.97,766.899C177.723,762.373 183.719,758.753 190.961,756.037C198.202,753.321 205.5,751.964 212.855,751.964C223.943,751.964 232.712,754.821 239.162,760.535C245.611,766.249 248.836,773.971 248.836,783.701C248.836,790.603 247.28,797.251 244.168,803.644C241.057,810.036 235.88,817.193 228.639,825.113L194.186,862.452L253.927,862.452Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,374.061,169.171)">

+        <path d="M245.95,822.567C249.684,827.546 251.551,833.826 251.551,841.406C251.551,851.929 247.987,860.217 240.859,866.271C233.73,872.324 224.056,875.351 211.837,875.351C204.029,875.351 196.533,874.049 189.349,871.447C182.164,868.845 176.082,865.167 171.104,860.415L176.535,849.723C187.736,859.001 199.39,863.64 211.497,863.64C220.096,863.64 226.631,861.716 231.1,857.869C235.569,854.022 237.804,848.365 237.804,840.897C237.804,826.075 228.526,818.664 209.97,818.664L196.052,818.664L196.052,806.953L207.254,806.953C216.193,806.953 223.038,804.973 227.79,801.013C232.542,797.053 234.919,791.395 234.919,784.041C234.919,777.478 232.967,772.443 229.063,768.936C225.16,765.428 219.644,763.674 212.515,763.674C200.974,763.674 189.547,768.313 178.232,777.592L172.97,766.899C177.836,762.26 183.804,758.611 190.876,755.952C197.948,753.293 205.331,751.964 213.025,751.964C223.887,751.964 232.571,754.736 239.077,760.28C245.583,765.824 248.836,773.292 248.836,782.683C248.836,789.585 247.138,795.638 243.744,800.843C240.35,806.048 235.654,809.782 229.657,812.045C236.785,814.081 242.217,817.589 245.95,822.567Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,664.984,170.849)">

+        <path d="M258.34,836.315L258.34,847.856L240.01,847.856L240.01,874.163L226.093,874.163L226.093,847.856L170.425,847.856L170.425,837.333L228.639,753.321L240.01,753.321L240.01,836.315L258.34,836.315ZM184.851,836.315L226.093,836.315L226.093,776.913L184.851,836.315Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,873.65,170.849)">

+        <path d="M238.058,803.134C243.772,806.359 248.157,810.857 251.212,816.627C254.267,822.398 255.794,829.073 255.794,836.654C255.794,844.235 254.125,850.967 250.787,856.851C247.45,862.735 242.697,867.289 236.531,870.514C230.364,873.738 223.151,875.351 214.891,875.351C207.537,875.351 200.296,874.021 193.167,871.362C186.039,868.703 180.042,865.054 175.177,860.415L180.438,849.723C191.64,859.001 203.124,863.64 214.891,863.64C223.378,863.64 230.025,861.236 234.834,856.427C239.642,851.618 242.047,845.084 242.047,836.824C242.047,828.791 239.671,822.313 234.919,817.391C230.166,812.469 223.83,810.008 215.91,810.008C204.369,810.008 195.147,814.704 188.245,824.095L178.571,824.095L178.571,753.321L251.042,753.321L251.042,764.862L192.488,764.862L192.488,807.972C199.164,801.522 207.707,798.297 218.116,798.297C225.697,798.297 232.344,799.91 238.058,803.134Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,1086.71,170.849)">

+        <path d="M237.719,803.134C243.433,806.359 247.874,810.885 251.042,816.712C254.21,822.539 255.794,829.187 255.794,836.654C255.794,844.122 254.125,850.798 250.787,856.681C247.45,862.565 242.839,867.176 236.955,870.514C231.072,873.851 224.396,875.52 216.928,875.52C202.332,875.52 191.074,870.429 183.154,860.245C175.233,850.062 171.273,835.579 171.273,816.797C171.273,803.219 173.112,791.565 176.789,781.835C180.466,772.104 185.784,764.693 192.743,759.601C199.701,754.509 208.046,751.964 217.777,751.964C224.792,751.964 231.609,753.265 238.228,755.867C244.847,758.47 250.646,762.147 255.624,766.899L250.363,777.592C244.706,772.839 239.275,769.332 234.07,767.069C228.865,764.806 223.547,763.674 218.116,763.674C207.707,763.674 199.617,768.313 193.846,777.592C188.076,786.87 185.19,799.881 185.19,816.627L185.19,819.173C187.793,812.724 192.036,807.632 197.919,803.898C203.803,800.164 210.535,798.297 218.116,798.297C225.471,798.297 232.005,799.91 237.719,803.134ZM234.919,856.427C239.671,851.505 242.047,844.971 242.047,836.824C242.047,828.791 239.642,822.313 234.834,817.391C230.025,812.469 223.774,810.008 216.08,810.008C208.159,810.008 201.71,812.497 196.731,817.476C191.753,822.454 189.264,828.904 189.264,836.824C189.264,844.857 191.753,851.363 196.731,856.342C201.71,861.32 208.216,863.81 216.249,863.81C223.943,863.81 230.166,861.349 234.919,856.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,1386.78,168.615)">

+        <path d="M173.14,753.321L252.909,753.321L252.909,763.674L196.222,874.163L181.287,874.163L237.634,765.032L173.14,765.032L173.14,753.321Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,1596.01,169.877)">

+        <path d="M249.769,823.162C254.125,828.423 256.303,834.731 256.303,842.085C256.303,852.382 252.4,860.5 244.593,866.44C236.785,872.381 226.263,875.351 213.025,875.351C199.786,875.351 189.264,872.381 181.457,866.44C173.649,860.5 169.746,852.382 169.746,842.085C169.746,834.731 171.98,828.395 176.45,823.077C180.919,817.759 187.057,814.081 194.864,812.045C187.623,809.895 182.079,806.359 178.232,801.437C174.385,796.515 172.461,790.717 172.461,784.041C172.461,777.592 174.159,771.962 177.553,767.154C180.947,762.345 185.728,758.611 191.894,755.952C198.061,753.293 205.104,751.964 213.025,751.964C220.945,751.964 227.988,753.293 234.155,755.952C240.321,758.611 245.102,762.345 248.496,767.154C251.891,771.962 253.588,777.592 253.588,784.041C253.588,790.717 251.636,796.515 247.732,801.437C243.829,806.359 238.37,809.895 231.354,812.045C239.275,814.195 245.413,817.9 249.769,823.162ZM193.592,800.758C198.4,804.775 204.878,807.236 213.025,808.141C221.171,807.236 227.649,804.775 232.458,800.758C237.266,796.742 239.671,791.509 239.671,785.059C239.671,778.384 237.323,773.122 232.627,769.275C227.932,765.428 221.397,763.505 213.025,763.505C204.652,763.505 198.117,765.428 193.422,769.275C188.726,773.122 186.378,778.384 186.378,785.059C186.378,791.509 188.783,796.742 193.592,800.758ZM234.919,858.039C240.01,854.192 242.556,848.591 242.556,841.237C242.556,834.561 239.869,829.215 234.494,825.198C229.12,821.181 221.963,818.72 213.025,817.815C204.086,818.72 196.929,821.181 191.555,825.198C186.18,829.215 183.493,834.561 183.493,841.237C183.493,848.591 186.039,854.192 191.131,858.039C196.222,861.886 203.52,863.81 213.025,863.81C222.529,863.81 229.827,861.886 234.919,858.039Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(0.92983,0,0,0.92983,1799.28,168.615)">

+        <path d="M243.065,767.239C250.985,777.422 254.946,791.905 254.946,810.687C254.946,831.167 250.844,847.092 242.641,858.463C234.438,869.835 222.982,875.52 208.272,875.52C201.37,875.52 194.61,874.219 187.991,871.617C181.372,869.014 175.516,865.337 170.425,860.585L175.856,849.893C181.626,854.758 187.114,858.294 192.319,860.5C197.523,862.706 202.785,863.81 208.103,863.81C218.512,863.81 226.574,859.171 232.288,849.893C238.002,840.614 240.859,827.603 240.859,810.857L240.859,808.65C238.256,814.987 234.013,819.993 228.13,823.671C222.246,827.348 215.514,829.187 207.933,829.187C200.578,829.187 194.072,827.574 188.415,824.35C182.758,821.125 178.345,816.599 175.177,810.772C172.009,804.945 170.425,798.297 170.425,790.83C170.425,783.362 172.094,776.686 175.431,770.803C178.769,764.919 183.38,760.308 189.264,756.97C195.147,753.633 201.823,751.964 209.291,751.964C223.887,751.964 235.145,757.055 243.065,767.239ZM229.487,810.008C234.466,805.03 236.955,798.58 236.955,790.66C236.955,782.627 234.466,776.121 229.487,771.142C224.509,766.164 218.003,763.674 209.97,763.674C202.276,763.674 196.052,766.135 191.3,771.057C186.548,775.979 184.172,782.513 184.172,790.66C184.172,798.693 186.548,805.171 191.3,810.093C196.052,815.015 202.332,817.476 210.139,817.476C218.06,817.476 224.509,814.987 229.487,810.008Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,1.17016,-233.077,-107.087)">

+        <path d="M1120.2,396.615L1120.2,552.949L1120.2,474.16L509.798,474.16L509.798,552.949" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,1.17016,-233.077,-107.087)">

+        <path d="M1120.2,474.782L1729.96,474.782L1729.96,552.949" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.594821,-233.077,326.47)">

+        <path d="M331.99,802.778L331.99,859.94" style="fill:none;stroke:black;stroke-width:5.93px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,1.17016,-233.077,-168.289)">

+        <path d="M509.68,802.778L509.68,859.94" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.594821,-233.077,326.47)">

+        <path d="M688.806,802.778L688.806,859.94" style="fill:none;stroke:black;stroke-width:5.93px;"/>

+    </g>

+    <g transform="matrix(0.902494,0,0,0.902494,2027.65,-1280.25)">

+        <g>

+            <g>

+                <g>

+                    <g transform="matrix(1.17719,0,0,0.817775,-122.471,1454.31)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,131,192);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM764.58,107.907L764.58,342.832L1241.81,342.832L1241.81,107.907L764.58,107.907Z"/>

+                    </g>

+                    <g transform="matrix(1.0988,0,0,0.502285,-698.084,1726.61)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(201,23,126);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM764.949,112.588L764.949,338.151L1241.44,338.151L1241.44,112.588L764.949,112.588Z"/>

+                    </g>

+                    <g transform="matrix(1.09385,0,0,0.502285,-34.0849,1726.61)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(201,23,126);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM764.975,112.588L764.975,338.151L1241.42,338.151L1241.42,112.588L764.975,112.588Z"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1001.57,1238.26L1001.57,1256.06L814.157,1256.06L814.157,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.08821,0,0,0.502285,624.555,1726.61)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(201,23,126);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM765.003,112.588L765.003,338.151L1241.39,338.151L1241.39,112.588L765.003,112.588Z"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,123.947,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.243,113.327L788.243,337.412L1218.15,337.412L1218.15,113.327L788.243,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,201.091,1493.51)">

+                        <path d="M245.95,822.567C249.684,827.546 251.551,833.826 251.551,841.406C251.551,851.929 247.987,860.217 240.859,866.271C233.73,872.324 224.056,875.351 211.837,875.351C204.029,875.351 196.533,874.049 189.349,871.447C182.164,868.845 176.082,865.167 171.104,860.415L176.535,849.723C187.736,859.001 199.39,863.64 211.497,863.64C220.096,863.64 226.631,861.716 231.1,857.869C235.569,854.022 237.804,848.365 237.804,840.897C237.804,826.075 228.526,818.664 209.97,818.664L196.052,818.664L196.052,806.953L207.254,806.953C216.193,806.953 223.038,804.973 227.79,801.013C232.542,797.053 234.919,791.395 234.919,784.041C234.919,777.478 232.967,772.443 229.063,768.936C225.16,765.428 219.644,763.674 212.515,763.674C200.974,763.674 189.547,768.313 178.232,777.592L172.97,766.899C177.836,762.26 183.804,758.611 190.876,755.952C197.948,753.293 205.331,751.964 213.025,751.964C223.887,751.964 232.571,754.736 239.077,760.28C245.583,765.824 248.836,773.292 248.836,782.683C248.836,789.585 247.138,795.638 243.744,800.843C240.35,806.048 235.654,809.782 229.657,812.045C236.785,814.081 242.217,817.589 245.95,822.567Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,267.401,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.243,113.327L788.243,337.412L1218.15,337.412L1218.15,113.327L788.243,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,344.545,1493.51)">

+                        <path d="M238.058,803.134C243.772,806.359 248.157,810.857 251.212,816.627C254.267,822.398 255.794,829.073 255.794,836.654C255.794,844.235 254.125,850.967 250.787,856.851C247.45,862.735 242.697,867.289 236.531,870.514C230.364,873.738 223.151,875.351 214.891,875.351C207.537,875.351 200.296,874.021 193.167,871.362C186.039,868.703 180.042,865.054 175.177,860.415L180.438,849.723C191.64,859.001 203.124,863.64 214.891,863.64C223.378,863.64 230.025,861.236 234.834,856.427C239.642,851.618 242.047,845.084 242.047,836.824C242.047,828.791 239.671,822.313 234.919,817.391C230.166,812.469 223.83,810.008 215.91,810.008C204.369,810.008 195.147,814.704 188.245,824.095L178.571,824.095L178.571,753.321L251.042,753.321L251.042,764.862L192.488,764.862L192.488,807.972C199.164,801.522 207.707,798.297 218.116,798.297C225.697,798.297 232.344,799.91 238.058,803.134Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,411.536,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.243,113.327L788.243,337.412L1218.15,337.412L1218.15,113.327L788.243,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,488.68,1493.51)">

+                        <path d="M237.719,803.134C243.433,806.359 247.874,810.885 251.042,816.712C254.21,822.539 255.794,829.187 255.794,836.654C255.794,844.122 254.125,850.798 250.787,856.681C247.45,862.565 242.839,867.176 236.955,870.514C231.072,873.851 224.396,875.52 216.928,875.52C202.332,875.52 191.074,870.429 183.154,860.245C175.233,850.062 171.273,835.579 171.273,816.797C171.273,803.219 173.112,791.565 176.789,781.835C180.466,772.104 185.784,764.693 192.743,759.601C199.701,754.509 208.046,751.964 217.777,751.964C224.792,751.964 231.609,753.265 238.228,755.867C244.847,758.47 250.646,762.147 255.624,766.899L250.363,777.592C244.706,772.839 239.275,769.332 234.07,767.069C228.865,764.806 223.547,763.674 218.116,763.674C207.707,763.674 199.617,768.313 193.846,777.592C188.076,786.87 185.19,799.881 185.19,816.627L185.19,819.173C187.793,812.724 192.036,807.632 197.919,803.898C203.803,800.164 210.535,798.297 218.116,798.297C225.471,798.297 232.005,799.91 237.719,803.134ZM234.919,856.427C239.671,851.505 242.047,844.971 242.047,836.824C242.047,828.791 239.642,822.313 234.834,817.391C230.025,812.469 223.774,810.008 216.08,810.008C208.159,810.008 201.71,812.497 196.731,817.476C191.753,822.454 189.264,828.904 189.264,836.824C189.264,844.857 191.753,851.363 196.731,856.342C201.71,861.32 208.216,863.81 216.249,863.81C223.943,863.81 230.166,861.349 234.919,856.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,-23.3963,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.244,113.327L788.244,337.412L1218.15,337.412L1218.15,113.327L788.244,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,53.7475,1493.51)">

+                        <path d="M224.566,862.452L251.212,862.452L251.212,874.163L183.833,874.163L183.833,862.452L210.479,862.452L210.479,770.633L185.7,786.417L185.7,773.009L216.589,753.321L224.566,753.321L224.566,862.452Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,633.784,1896.21)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.244,113.327L788.244,337.412L1218.15,337.412L1218.15,113.327L788.244,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,712.136,1493.44)">

+                        <path d="M253.927,862.452L253.927,874.163L176.195,874.163L176.195,863.64L218.456,816.797C224.113,810.461 228.243,804.747 230.845,799.655C233.448,794.564 234.749,789.472 234.749,784.38C234.749,777.705 232.825,772.585 228.978,769.021C225.131,765.456 219.644,763.674 212.515,763.674C200.974,763.674 189.547,768.313 178.232,777.592L172.97,766.899C177.723,762.373 183.719,758.753 190.961,756.037C198.202,753.321 205.5,751.964 212.855,751.964C223.943,751.964 232.712,754.821 239.162,760.535C245.611,766.249 248.836,773.971 248.836,783.701C248.836,790.603 247.28,797.251 244.168,803.644C241.057,810.036 235.88,817.193 228.639,825.113L194.186,862.452L253.927,862.452Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,781.127,1896.21)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.243,113.327L788.243,337.412L1218.15,337.412L1218.15,113.327L788.243,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,856.93,1493.46)">

+                        <path d="M258.34,836.315L258.34,847.856L240.01,847.856L240.01,874.163L226.093,874.163L226.093,847.856L170.425,847.856L170.425,837.333L228.639,753.321L240.01,753.321L240.01,836.315L258.34,836.315ZM184.851,836.315L226.093,836.315L226.093,776.913L184.851,836.315Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,107.033,497.127)">

+                        <path d="M71.23,1159.88L71.23,1132.92L60.814,1132.92L60.814,1129.98L85.132,1129.98L85.132,1132.92L74.716,1132.92L74.716,1159.88L71.23,1159.88Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M103.36,1149.21L87.862,1149.21C87.89,1151.9 88.513,1153.93 89.731,1155.3C90.949,1156.67 92.72,1157.36 95.044,1157.36C97.508,1157.36 99.776,1156.53 101.848,1154.88L102.982,1157.36C102.058,1158.23 100.875,1158.91 99.433,1159.42C97.991,1159.92 96.514,1160.17 95.002,1160.17C91.698,1160.17 89.108,1159.2 87.232,1157.26C85.356,1155.31 84.418,1152.64 84.418,1149.25C84.418,1147.1 84.838,1145.19 85.678,1143.52C86.518,1141.86 87.694,1140.56 89.206,1139.64C90.718,1138.71 92.44,1138.25 94.372,1138.25C97.172,1138.25 99.37,1139.17 100.966,1141C102.562,1142.84 103.36,1145.36 103.36,1148.58L103.36,1149.21ZM90.109,1142.49C89.003,1143.56 88.296,1145.05 87.988,1146.99L100.294,1146.99C100.126,1145 99.545,1143.49 98.551,1142.45C97.557,1141.41 96.178,1140.9 94.414,1140.9C92.65,1140.9 91.215,1141.43 90.109,1142.49Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M120.286,1138.5L120.202,1141.61C119.558,1141.39 118.816,1141.27 117.976,1141.27C115.932,1141.27 114.413,1141.91 113.419,1143.18C112.425,1144.46 111.928,1146.01 111.928,1147.83L111.928,1159.88L108.526,1159.88L108.526,1144.68C108.526,1142.49 108.414,1140.52 108.19,1138.75L111.424,1138.75L111.76,1142.66C112.292,1141.23 113.146,1140.14 114.322,1139.38C115.498,1138.63 116.842,1138.25 118.354,1138.25C119.054,1138.25 119.698,1138.33 120.286,1138.5Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M154.18,1146.61L154.18,1159.88L150.778,1159.88L150.778,1146.78C150.778,1144.79 150.435,1143.35 149.749,1142.45C149.063,1141.55 147.95,1141.11 146.41,1141.11C144.618,1141.11 143.218,1141.71 142.21,1142.91C141.202,1144.12 140.698,1145.75 140.698,1147.83L140.698,1159.88L137.296,1159.88L137.296,1146.78C137.296,1144.82 136.946,1143.38 136.246,1142.47C135.546,1141.56 134.426,1141.11 132.886,1141.11C131.094,1141.11 129.687,1141.71 128.665,1142.91C127.643,1144.12 127.132,1145.75 127.132,1147.83L127.132,1159.88L123.73,1159.88L123.73,1144.68C123.73,1142.49 123.618,1140.52 123.394,1138.75L126.628,1138.75L126.964,1142.45C127.552,1141.11 128.427,1140.07 129.589,1139.34C130.751,1138.61 132.102,1138.25 133.642,1138.25C135.322,1138.25 136.694,1138.59 137.758,1139.26C138.822,1139.93 139.606,1140.97 140.11,1142.37C140.754,1141.11 141.699,1140.11 142.945,1139.36C144.191,1138.62 145.598,1138.25 147.166,1138.25C151.842,1138.25 154.18,1141.04 154.18,1146.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M183.79,1156.98L190.384,1156.98L190.384,1159.88L173.71,1159.88L173.71,1156.98L180.304,1156.98L180.304,1134.26L174.172,1138.17L174.172,1134.85L181.816,1129.98L183.79,1129.98L183.79,1156.98Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M196.222,1139.22L200.548,1139.22L200.548,1143.58L196.222,1143.58L196.222,1139.22ZM196.222,1155.55L200.548,1155.55L200.548,1158.62C200.548,1159.8 200.352,1160.87 199.96,1161.85C199.568,1162.83 198.91,1163.79 197.986,1164.71L196.39,1163.49C197.482,1162.23 198.098,1161.03 198.238,1159.88L196.222,1159.88L196.222,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M216.382,1159.88L218.734,1129.98L225.328,1129.98L223.354,1154.55L236.71,1154.55L236.29,1159.88L216.382,1159.88Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M239.86,1159.88L241.54,1138.59L247.882,1138.59L246.202,1159.88L239.86,1159.88ZM242.044,1128.59L248.848,1128.59L248.386,1134.55L241.582,1134.55L242.044,1128.59Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M250.108,1157.61L252.166,1153.2C253.342,1154.01 254.602,1154.64 255.946,1155.07C257.29,1155.51 258.634,1155.72 259.978,1155.72C261.154,1155.72 262.022,1155.55 262.582,1155.22C263.142,1154.88 263.422,1154.43 263.422,1153.87C263.422,1153.29 263.093,1152.82 262.435,1152.49C261.777,1152.15 260.706,1151.76 259.222,1151.31C257.682,1150.89 256.422,1150.47 255.442,1150.05C254.462,1149.63 253.615,1149.01 252.901,1148.18C252.187,1147.36 251.83,1146.29 251.83,1144.97C251.83,1143.6 252.215,1142.39 252.985,1141.36C253.755,1140.32 254.847,1139.51 256.261,1138.92C257.675,1138.33 259.292,1138.04 261.112,1138.04C262.708,1138.04 264.269,1138.28 265.795,1138.75C267.321,1139.23 268.602,1139.87 269.638,1140.69L267.622,1144.93C266.586,1144.17 265.494,1143.6 264.346,1143.21C263.198,1142.81 262.078,1142.62 260.986,1142.62C259.838,1142.62 258.97,1142.79 258.382,1143.12C257.794,1143.46 257.5,1143.92 257.5,1144.51C257.5,1145.12 257.85,1145.61 258.55,1145.98C259.25,1146.34 260.314,1146.72 261.742,1147.11C263.282,1147.56 264.535,1147.99 265.501,1148.41C266.467,1148.83 267.307,1149.46 268.021,1150.28C268.735,1151.11 269.092,1152.18 269.092,1153.5C269.092,1155.6 268.259,1157.24 266.593,1158.43C264.927,1159.62 262.68,1160.22 259.852,1160.22C256.212,1160.22 252.964,1159.35 250.108,1157.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M280.894,1151.61C280.81,1152.78 281.048,1153.65 281.608,1154.21C282.168,1154.77 282.938,1155.05 283.918,1155.05C284.562,1155.05 285.276,1154.94 286.06,1154.71L285.64,1159.63C284.688,1160.02 283.456,1160.22 281.944,1160.22C279.536,1160.22 277.695,1159.57 276.421,1158.28C275.147,1157 274.51,1155.18 274.51,1152.82C274.51,1152.35 274.524,1151.98 274.552,1151.73L275.224,1143.33L271.192,1143.33L271.57,1138.59L275.602,1138.59L275.98,1133.59L282.49,1131.53L281.944,1138.59L287.362,1138.59L286.984,1143.33L281.566,1143.33L280.894,1151.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M287.656,1157.61L289.714,1153.2C290.89,1154.01 292.15,1154.64 293.494,1155.07C294.838,1155.51 296.182,1155.72 297.526,1155.72C298.702,1155.72 299.57,1155.55 300.13,1155.22C300.69,1154.88 300.97,1154.43 300.97,1153.87C300.97,1153.29 300.641,1152.82 299.983,1152.49C299.325,1152.15 298.254,1151.76 296.77,1151.31C295.23,1150.89 293.97,1150.47 292.99,1150.05C292.01,1149.63 291.163,1149.01 290.449,1148.18C289.735,1147.36 289.378,1146.29 289.378,1144.97C289.378,1143.6 289.763,1142.39 290.533,1141.36C291.303,1140.32 292.395,1139.51 293.809,1138.92C295.223,1138.33 296.84,1138.04 298.66,1138.04C300.256,1138.04 301.817,1138.28 303.343,1138.75C304.869,1139.23 306.15,1139.87 307.186,1140.69L305.17,1144.93C304.134,1144.17 303.042,1143.6 301.894,1143.21C300.746,1142.81 299.626,1142.62 298.534,1142.62C297.386,1142.62 296.518,1142.79 295.93,1143.12C295.342,1143.46 295.048,1143.92 295.048,1144.51C295.048,1145.12 295.398,1145.61 296.098,1145.98C296.798,1146.34 297.862,1146.72 299.29,1147.11C300.83,1147.56 302.083,1147.99 303.049,1148.41C304.015,1148.83 304.855,1149.46 305.569,1150.28C306.283,1151.11 306.64,1152.18 306.64,1153.5C306.64,1155.6 305.807,1157.24 304.141,1158.43C302.475,1159.62 300.228,1160.22 297.4,1160.22C293.76,1160.22 290.512,1159.35 287.656,1157.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M334.696,1156.98L341.29,1156.98L341.29,1159.88L324.616,1159.88L324.616,1156.98L331.21,1156.98L331.21,1134.26L325.078,1138.17L325.078,1134.85L332.722,1129.98L334.696,1129.98L334.696,1156.98Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M351.454,1155.55L351.454,1158.62C351.454,1159.8 351.258,1160.87 350.866,1161.85C350.474,1162.83 349.816,1163.79 348.892,1164.71L347.296,1163.49C348.388,1162.23 349.004,1161.03 349.144,1159.88L347.128,1159.88L347.128,1155.55L351.454,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M374.89,1147.11C375.814,1148.34 376.276,1149.9 376.276,1151.77C376.276,1154.38 375.394,1156.43 373.63,1157.93C371.866,1159.42 369.472,1160.17 366.448,1160.17C364.516,1160.17 362.661,1159.85 360.883,1159.21C359.105,1158.56 357.6,1157.65 356.368,1156.48L357.712,1153.83C360.484,1156.13 363.368,1157.28 366.364,1157.28C368.492,1157.28 370.109,1156.8 371.215,1155.85C372.321,1154.9 372.874,1153.5 372.874,1151.65C372.874,1147.98 370.578,1146.15 365.986,1146.15L362.542,1146.15L362.542,1143.25L365.314,1143.25C367.526,1143.25 369.22,1142.76 370.396,1141.78C371.572,1140.8 372.16,1139.4 372.16,1137.58C372.16,1135.95 371.677,1134.71 370.711,1133.84C369.745,1132.97 368.38,1132.54 366.616,1132.54C363.76,1132.54 360.932,1133.69 358.132,1135.98L356.83,1133.34C358.034,1132.19 359.511,1131.29 361.261,1130.63C363.011,1129.97 364.838,1129.64 366.742,1129.64C369.43,1129.64 371.579,1130.33 373.189,1131.7C374.799,1133.07 375.604,1134.92 375.604,1137.24C375.604,1138.95 375.184,1140.45 374.344,1141.74C373.504,1143.02 372.342,1143.95 370.858,1144.51C372.622,1145.01 373.966,1145.88 374.89,1147.11Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M386.356,1155.55L386.356,1158.62C386.356,1159.8 386.16,1160.87 385.768,1161.85C385.376,1162.83 384.718,1163.79 383.794,1164.71L382.198,1163.49C383.29,1162.23 383.906,1161.03 384.046,1159.88L382.03,1159.88L382.03,1155.55L386.356,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M412.858,1150.51L412.858,1153.37L408.322,1153.37L408.322,1159.88L404.878,1159.88L404.878,1153.37L391.102,1153.37L391.102,1150.77L405.508,1129.98L408.322,1129.98L408.322,1150.51L412.858,1150.51ZM394.672,1150.51L404.878,1150.51L404.878,1135.81L394.672,1150.51Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M421.258,1155.55L421.258,1158.62C421.258,1159.8 421.062,1160.87 420.67,1161.85C420.278,1162.83 419.62,1163.79 418.696,1164.71L417.1,1163.49C418.192,1162.23 418.808,1161.03 418.948,1159.88L416.932,1159.88L416.932,1155.55L421.258,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M442.741,1142.3C444.155,1143.1 445.24,1144.21 445.996,1145.64C446.752,1147.07 447.13,1148.72 447.13,1150.6C447.13,1152.47 446.717,1154.14 445.891,1155.6C445.065,1157.05 443.889,1158.18 442.363,1158.98C440.837,1159.78 439.052,1160.17 437.008,1160.17C435.188,1160.17 433.396,1159.85 431.632,1159.19C429.868,1158.53 428.384,1157.63 427.18,1156.48L428.482,1153.83C431.254,1156.13 434.096,1157.28 437.008,1157.28C439.108,1157.28 440.753,1156.68 441.943,1155.49C443.133,1154.3 443.728,1152.68 443.728,1150.64C443.728,1148.65 443.14,1147.05 441.964,1145.83C440.788,1144.61 439.22,1144 437.26,1144C434.404,1144 432.122,1145.17 430.414,1147.49L428.02,1147.49L428.02,1129.98L445.954,1129.98L445.954,1132.83L431.464,1132.83L431.464,1143.5C433.116,1141.9 435.23,1141.11 437.806,1141.11C439.682,1141.11 441.327,1141.51 442.741,1142.3Z" style="fill:white;fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,766.077,497.426)">

+                        <path d="M71.23,1159.88L71.23,1132.92L60.814,1132.92L60.814,1129.98L85.132,1129.98L85.132,1132.92L74.716,1132.92L74.716,1159.88L71.23,1159.88Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M103.36,1149.21L87.862,1149.21C87.89,1151.9 88.513,1153.93 89.731,1155.3C90.949,1156.67 92.72,1157.36 95.044,1157.36C97.508,1157.36 99.776,1156.53 101.848,1154.88L102.982,1157.36C102.058,1158.23 100.875,1158.91 99.433,1159.42C97.991,1159.92 96.514,1160.17 95.002,1160.17C91.698,1160.17 89.108,1159.2 87.232,1157.26C85.356,1155.31 84.418,1152.64 84.418,1149.25C84.418,1147.1 84.838,1145.19 85.678,1143.52C86.518,1141.86 87.694,1140.56 89.206,1139.64C90.718,1138.71 92.44,1138.25 94.372,1138.25C97.172,1138.25 99.37,1139.17 100.966,1141C102.562,1142.84 103.36,1145.36 103.36,1148.58L103.36,1149.21ZM90.109,1142.49C89.003,1143.56 88.296,1145.05 87.988,1146.99L100.294,1146.99C100.126,1145 99.545,1143.49 98.551,1142.45C97.557,1141.41 96.178,1140.9 94.414,1140.9C92.65,1140.9 91.215,1141.43 90.109,1142.49Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M120.286,1138.5L120.202,1141.61C119.558,1141.39 118.816,1141.27 117.976,1141.27C115.932,1141.27 114.413,1141.91 113.419,1143.18C112.425,1144.46 111.928,1146.01 111.928,1147.83L111.928,1159.88L108.526,1159.88L108.526,1144.68C108.526,1142.49 108.414,1140.52 108.19,1138.75L111.424,1138.75L111.76,1142.66C112.292,1141.23 113.146,1140.14 114.322,1139.38C115.498,1138.63 116.842,1138.25 118.354,1138.25C119.054,1138.25 119.698,1138.33 120.286,1138.5Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M154.18,1146.61L154.18,1159.88L150.778,1159.88L150.778,1146.78C150.778,1144.79 150.435,1143.35 149.749,1142.45C149.063,1141.55 147.95,1141.11 146.41,1141.11C144.618,1141.11 143.218,1141.71 142.21,1142.91C141.202,1144.12 140.698,1145.75 140.698,1147.83L140.698,1159.88L137.296,1159.88L137.296,1146.78C137.296,1144.82 136.946,1143.38 136.246,1142.47C135.546,1141.56 134.426,1141.11 132.886,1141.11C131.094,1141.11 129.687,1141.71 128.665,1142.91C127.643,1144.12 127.132,1145.75 127.132,1147.83L127.132,1159.88L123.73,1159.88L123.73,1144.68C123.73,1142.49 123.618,1140.52 123.394,1138.75L126.628,1138.75L126.964,1142.45C127.552,1141.11 128.427,1140.07 129.589,1139.34C130.751,1138.61 132.102,1138.25 133.642,1138.25C135.322,1138.25 136.694,1138.59 137.758,1139.26C138.822,1139.93 139.606,1140.97 140.11,1142.37C140.754,1141.11 141.699,1140.11 142.945,1139.36C144.191,1138.62 145.598,1138.25 147.166,1138.25C151.842,1138.25 154.18,1141.04 154.18,1146.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M191.056,1156.98L191.056,1159.88L171.82,1159.88L171.82,1157.28L182.278,1145.68C183.678,1144.12 184.7,1142.7 185.344,1141.44C185.988,1140.18 186.31,1138.92 186.31,1137.66C186.31,1136.01 185.834,1134.74 184.882,1133.86C183.93,1132.98 182.572,1132.54 180.808,1132.54C177.952,1132.54 175.124,1133.69 172.324,1135.98L171.022,1133.34C172.198,1132.22 173.682,1131.32 175.474,1130.65C177.266,1129.98 179.072,1129.64 180.892,1129.64C183.636,1129.64 185.806,1130.35 187.402,1131.76C188.998,1133.17 189.796,1135.09 189.796,1137.49C189.796,1139.2 189.411,1140.85 188.641,1142.43C187.871,1144.01 186.59,1145.78 184.798,1147.74L176.272,1156.98L191.056,1156.98Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M196.222,1139.22L200.548,1139.22L200.548,1143.58L196.222,1143.58L196.222,1139.22ZM196.222,1155.55L200.548,1155.55L200.548,1158.62C200.548,1159.8 200.352,1160.87 199.96,1161.85C199.568,1162.83 198.91,1163.79 197.986,1164.71L196.39,1163.49C197.482,1162.23 198.098,1161.03 198.238,1159.88L196.222,1159.88L196.222,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M216.382,1159.88L218.734,1129.98L225.328,1129.98L223.354,1154.55L236.71,1154.55L236.29,1159.88L216.382,1159.88Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M239.86,1159.88L241.54,1138.59L247.882,1138.59L246.202,1159.88L239.86,1159.88ZM242.044,1128.59L248.848,1128.59L248.386,1134.55L241.582,1134.55L242.044,1128.59Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M250.108,1157.61L252.166,1153.2C253.342,1154.01 254.602,1154.64 255.946,1155.07C257.29,1155.51 258.634,1155.72 259.978,1155.72C261.154,1155.72 262.022,1155.55 262.582,1155.22C263.142,1154.88 263.422,1154.43 263.422,1153.87C263.422,1153.29 263.093,1152.82 262.435,1152.49C261.777,1152.15 260.706,1151.76 259.222,1151.31C257.682,1150.89 256.422,1150.47 255.442,1150.05C254.462,1149.63 253.615,1149.01 252.901,1148.18C252.187,1147.36 251.83,1146.29 251.83,1144.97C251.83,1143.6 252.215,1142.39 252.985,1141.36C253.755,1140.32 254.847,1139.51 256.261,1138.92C257.675,1138.33 259.292,1138.04 261.112,1138.04C262.708,1138.04 264.269,1138.28 265.795,1138.75C267.321,1139.23 268.602,1139.87 269.638,1140.69L267.622,1144.93C266.586,1144.17 265.494,1143.6 264.346,1143.21C263.198,1142.81 262.078,1142.62 260.986,1142.62C259.838,1142.62 258.97,1142.79 258.382,1143.12C257.794,1143.46 257.5,1143.92 257.5,1144.51C257.5,1145.12 257.85,1145.61 258.55,1145.98C259.25,1146.34 260.314,1146.72 261.742,1147.11C263.282,1147.56 264.535,1147.99 265.501,1148.41C266.467,1148.83 267.307,1149.46 268.021,1150.28C268.735,1151.11 269.092,1152.18 269.092,1153.5C269.092,1155.6 268.259,1157.24 266.593,1158.43C264.927,1159.62 262.68,1160.22 259.852,1160.22C256.212,1160.22 252.964,1159.35 250.108,1157.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M280.894,1151.61C280.81,1152.78 281.048,1153.65 281.608,1154.21C282.168,1154.77 282.938,1155.05 283.918,1155.05C284.562,1155.05 285.276,1154.94 286.06,1154.71L285.64,1159.63C284.688,1160.02 283.456,1160.22 281.944,1160.22C279.536,1160.22 277.695,1159.57 276.421,1158.28C275.147,1157 274.51,1155.18 274.51,1152.82C274.51,1152.35 274.524,1151.98 274.552,1151.73L275.224,1143.33L271.192,1143.33L271.57,1138.59L275.602,1138.59L275.98,1133.59L282.49,1131.53L281.944,1138.59L287.362,1138.59L286.984,1143.33L281.566,1143.33L280.894,1151.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M287.656,1157.61L289.714,1153.2C290.89,1154.01 292.15,1154.64 293.494,1155.07C294.838,1155.51 296.182,1155.72 297.526,1155.72C298.702,1155.72 299.57,1155.55 300.13,1155.22C300.69,1154.88 300.97,1154.43 300.97,1153.87C300.97,1153.29 300.641,1152.82 299.983,1152.49C299.325,1152.15 298.254,1151.76 296.77,1151.31C295.23,1150.89 293.97,1150.47 292.99,1150.05C292.01,1149.63 291.163,1149.01 290.449,1148.18C289.735,1147.36 289.378,1146.29 289.378,1144.97C289.378,1143.6 289.763,1142.39 290.533,1141.36C291.303,1140.32 292.395,1139.51 293.809,1138.92C295.223,1138.33 296.84,1138.04 298.66,1138.04C300.256,1138.04 301.817,1138.28 303.343,1138.75C304.869,1139.23 306.15,1139.87 307.186,1140.69L305.17,1144.93C304.134,1144.17 303.042,1143.6 301.894,1143.21C300.746,1142.81 299.626,1142.62 298.534,1142.62C297.386,1142.62 296.518,1142.79 295.93,1143.12C295.342,1143.46 295.048,1143.92 295.048,1144.51C295.048,1145.12 295.398,1145.61 296.098,1145.98C296.798,1146.34 297.862,1146.72 299.29,1147.11C300.83,1147.56 302.083,1147.99 303.049,1148.41C304.015,1148.83 304.855,1149.46 305.569,1150.28C306.283,1151.11 306.64,1152.18 306.64,1153.5C306.64,1155.6 305.807,1157.24 304.141,1158.43C302.475,1159.62 300.228,1160.22 297.4,1160.22C293.76,1160.22 290.512,1159.35 287.656,1157.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M341.962,1156.98L341.962,1159.88L322.726,1159.88L322.726,1157.28L333.184,1145.68C334.584,1144.12 335.606,1142.7 336.25,1141.44C336.894,1140.18 337.216,1138.92 337.216,1137.66C337.216,1136.01 336.74,1134.74 335.788,1133.86C334.836,1132.98 333.478,1132.54 331.714,1132.54C328.858,1132.54 326.03,1133.69 323.23,1135.98L321.928,1133.34C323.104,1132.22 324.588,1131.32 326.38,1130.65C328.172,1129.98 329.978,1129.64 331.798,1129.64C334.542,1129.64 336.712,1130.35 338.308,1131.76C339.904,1133.17 340.702,1135.09 340.702,1137.49C340.702,1139.2 340.317,1140.85 339.547,1142.43C338.777,1144.01 337.496,1145.78 335.704,1147.74L327.178,1156.98L341.962,1156.98Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M351.454,1155.55L351.454,1158.62C351.454,1159.8 351.258,1160.87 350.866,1161.85C350.474,1162.83 349.816,1163.79 348.892,1164.71L347.296,1163.49C348.388,1162.23 349.004,1161.03 349.144,1159.88L347.128,1159.88L347.128,1155.55L351.454,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M377.956,1150.51L377.956,1153.37L373.42,1153.37L373.42,1159.88L369.976,1159.88L369.976,1153.37L356.2,1153.37L356.2,1150.77L370.606,1129.98L373.42,1129.98L373.42,1150.51L377.956,1150.51ZM359.77,1150.51L369.976,1150.51L369.976,1135.81L359.77,1150.51Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M386.356,1155.55L386.356,1158.62C386.356,1159.8 386.16,1160.87 385.768,1161.85C385.376,1162.83 384.718,1163.79 383.794,1164.71L382.198,1163.49C383.29,1162.23 383.906,1161.03 384.046,1159.88L382.03,1159.88L382.03,1155.55L386.356,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M407.839,1142.3C409.253,1143.1 410.338,1144.21 411.094,1145.64C411.85,1147.07 412.228,1148.72 412.228,1150.6C412.228,1152.47 411.815,1154.14 410.989,1155.6C410.163,1157.05 408.987,1158.18 407.461,1158.98C405.935,1159.78 404.15,1160.17 402.106,1160.17C400.286,1160.17 398.494,1159.85 396.73,1159.19C394.966,1158.53 393.482,1157.63 392.278,1156.48L393.58,1153.83C396.352,1156.13 399.194,1157.28 402.106,1157.28C404.206,1157.28 405.851,1156.68 407.041,1155.49C408.231,1154.3 408.826,1152.68 408.826,1150.64C408.826,1148.65 408.238,1147.05 407.062,1145.83C405.886,1144.61 404.318,1144 402.358,1144C399.502,1144 397.22,1145.17 395.512,1147.49L393.118,1147.49L393.118,1129.98L411.052,1129.98L411.052,1132.83L396.562,1132.83L396.562,1143.5C398.214,1141.9 400.328,1141.11 402.904,1141.11C404.78,1141.11 406.425,1141.51 407.839,1142.3Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M421.258,1155.55L421.258,1158.62C421.258,1159.8 421.062,1160.87 420.67,1161.85C420.278,1162.83 419.62,1163.79 418.696,1164.71L417.1,1163.49C418.192,1162.23 418.808,1161.03 418.948,1159.88L416.932,1159.88L416.932,1155.55L421.258,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M445.639,1147.26C446.717,1148.56 447.256,1150.12 447.256,1151.94C447.256,1154.49 446.29,1156.5 444.358,1157.97C442.426,1159.44 439.822,1160.17 436.546,1160.17C433.27,1160.17 430.666,1159.44 428.734,1157.97C426.802,1156.5 425.836,1154.49 425.836,1151.94C425.836,1150.12 426.389,1148.55 427.495,1147.24C428.601,1145.92 430.12,1145.01 432.052,1144.51C430.26,1143.98 428.888,1143.1 427.936,1141.88C426.984,1140.66 426.508,1139.23 426.508,1137.58C426.508,1135.98 426.928,1134.59 427.768,1133.4C428.608,1132.21 429.791,1131.29 431.317,1130.63C432.843,1129.97 434.586,1129.64 436.546,1129.64C438.506,1129.64 440.249,1129.97 441.775,1130.63C443.301,1131.29 444.484,1132.21 445.324,1133.4C446.164,1134.59 446.584,1135.98 446.584,1137.58C446.584,1139.23 446.101,1140.66 445.135,1141.88C444.169,1143.1 442.818,1143.98 441.082,1144.51C443.042,1145.04 444.561,1145.96 445.639,1147.26ZM431.737,1141.71C432.927,1142.71 434.53,1143.32 436.546,1143.54C438.562,1143.32 440.165,1142.71 441.355,1141.71C442.545,1140.72 443.14,1139.43 443.14,1137.83C443.14,1136.18 442.559,1134.88 441.397,1133.92C440.235,1132.97 438.618,1132.5 436.546,1132.5C434.474,1132.5 432.857,1132.97 431.695,1133.92C430.533,1134.88 429.952,1136.18 429.952,1137.83C429.952,1139.43 430.547,1140.72 431.737,1141.71ZM441.964,1155.89C443.224,1154.94 443.854,1153.55 443.854,1151.73C443.854,1150.08 443.189,1148.76 441.859,1147.76C440.529,1146.77 438.758,1146.16 436.546,1145.94C434.334,1146.16 432.563,1146.77 431.233,1147.76C429.903,1148.76 429.238,1150.08 429.238,1151.73C429.238,1153.55 429.868,1154.94 431.128,1155.89C432.388,1156.84 434.194,1157.32 436.546,1157.32C438.898,1157.32 440.704,1156.84 441.964,1155.89Z" style="fill:white;fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,1419.05,497.426)">

+                        <path d="M71.23,1159.88L71.23,1132.92L60.814,1132.92L60.814,1129.98L85.132,1129.98L85.132,1132.92L74.716,1132.92L74.716,1159.88L71.23,1159.88Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M103.36,1149.21L87.862,1149.21C87.89,1151.9 88.513,1153.93 89.731,1155.3C90.949,1156.67 92.72,1157.36 95.044,1157.36C97.508,1157.36 99.776,1156.53 101.848,1154.88L102.982,1157.36C102.058,1158.23 100.875,1158.91 99.433,1159.42C97.991,1159.92 96.514,1160.17 95.002,1160.17C91.698,1160.17 89.108,1159.2 87.232,1157.26C85.356,1155.31 84.418,1152.64 84.418,1149.25C84.418,1147.1 84.838,1145.19 85.678,1143.52C86.518,1141.86 87.694,1140.56 89.206,1139.64C90.718,1138.71 92.44,1138.25 94.372,1138.25C97.172,1138.25 99.37,1139.17 100.966,1141C102.562,1142.84 103.36,1145.36 103.36,1148.58L103.36,1149.21ZM90.109,1142.49C89.003,1143.56 88.296,1145.05 87.988,1146.99L100.294,1146.99C100.126,1145 99.545,1143.49 98.551,1142.45C97.557,1141.41 96.178,1140.9 94.414,1140.9C92.65,1140.9 91.215,1141.43 90.109,1142.49Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M120.286,1138.5L120.202,1141.61C119.558,1141.39 118.816,1141.27 117.976,1141.27C115.932,1141.27 114.413,1141.91 113.419,1143.18C112.425,1144.46 111.928,1146.01 111.928,1147.83L111.928,1159.88L108.526,1159.88L108.526,1144.68C108.526,1142.49 108.414,1140.52 108.19,1138.75L111.424,1138.75L111.76,1142.66C112.292,1141.23 113.146,1140.14 114.322,1139.38C115.498,1138.63 116.842,1138.25 118.354,1138.25C119.054,1138.25 119.698,1138.33 120.286,1138.5Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M154.18,1146.61L154.18,1159.88L150.778,1159.88L150.778,1146.78C150.778,1144.79 150.435,1143.35 149.749,1142.45C149.063,1141.55 147.95,1141.11 146.41,1141.11C144.618,1141.11 143.218,1141.71 142.21,1142.91C141.202,1144.12 140.698,1145.75 140.698,1147.83L140.698,1159.88L137.296,1159.88L137.296,1146.78C137.296,1144.82 136.946,1143.38 136.246,1142.47C135.546,1141.56 134.426,1141.11 132.886,1141.11C131.094,1141.11 129.687,1141.71 128.665,1142.91C127.643,1144.12 127.132,1145.75 127.132,1147.83L127.132,1159.88L123.73,1159.88L123.73,1144.68C123.73,1142.49 123.618,1140.52 123.394,1138.75L126.628,1138.75L126.964,1142.45C127.552,1141.11 128.427,1140.07 129.589,1139.34C130.751,1138.61 132.102,1138.25 133.642,1138.25C135.322,1138.25 136.694,1138.59 137.758,1139.26C138.822,1139.93 139.606,1140.97 140.11,1142.37C140.754,1141.11 141.699,1140.11 142.945,1139.36C144.191,1138.62 145.598,1138.25 147.166,1138.25C151.842,1138.25 154.18,1141.04 154.18,1146.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M189.082,1147.11C190.006,1148.34 190.468,1149.9 190.468,1151.77C190.468,1154.38 189.586,1156.43 187.822,1157.93C186.058,1159.42 183.664,1160.17 180.64,1160.17C178.708,1160.17 176.853,1159.85 175.075,1159.21C173.297,1158.56 171.792,1157.65 170.56,1156.48L171.904,1153.83C174.676,1156.13 177.56,1157.28 180.556,1157.28C182.684,1157.28 184.301,1156.8 185.407,1155.85C186.513,1154.9 187.066,1153.5 187.066,1151.65C187.066,1147.98 184.77,1146.15 180.178,1146.15L176.734,1146.15L176.734,1143.25L179.506,1143.25C181.718,1143.25 183.412,1142.76 184.588,1141.78C185.764,1140.8 186.352,1139.4 186.352,1137.58C186.352,1135.95 185.869,1134.71 184.903,1133.84C183.937,1132.97 182.572,1132.54 180.808,1132.54C177.952,1132.54 175.124,1133.69 172.324,1135.98L171.022,1133.34C172.226,1132.19 173.703,1131.29 175.453,1130.63C177.203,1129.97 179.03,1129.64 180.934,1129.64C183.622,1129.64 185.771,1130.33 187.381,1131.7C188.991,1133.07 189.796,1134.92 189.796,1137.24C189.796,1138.95 189.376,1140.45 188.536,1141.74C187.696,1143.02 186.534,1143.95 185.05,1144.51C186.814,1145.01 188.158,1145.88 189.082,1147.11Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M196.222,1139.22L200.548,1139.22L200.548,1143.58L196.222,1143.58L196.222,1139.22ZM196.222,1155.55L200.548,1155.55L200.548,1158.62C200.548,1159.8 200.352,1160.87 199.96,1161.85C199.568,1162.83 198.91,1163.79 197.986,1164.71L196.39,1163.49C197.482,1162.23 198.098,1161.03 198.238,1159.88L196.222,1159.88L196.222,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M216.382,1159.88L218.734,1129.98L225.328,1129.98L223.354,1154.55L236.71,1154.55L236.29,1159.88L216.382,1159.88Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M239.86,1159.88L241.54,1138.59L247.882,1138.59L246.202,1159.88L239.86,1159.88ZM242.044,1128.59L248.848,1128.59L248.386,1134.55L241.582,1134.55L242.044,1128.59Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M250.108,1157.61L252.166,1153.2C253.342,1154.01 254.602,1154.64 255.946,1155.07C257.29,1155.51 258.634,1155.72 259.978,1155.72C261.154,1155.72 262.022,1155.55 262.582,1155.22C263.142,1154.88 263.422,1154.43 263.422,1153.87C263.422,1153.29 263.093,1152.82 262.435,1152.49C261.777,1152.15 260.706,1151.76 259.222,1151.31C257.682,1150.89 256.422,1150.47 255.442,1150.05C254.462,1149.63 253.615,1149.01 252.901,1148.18C252.187,1147.36 251.83,1146.29 251.83,1144.97C251.83,1143.6 252.215,1142.39 252.985,1141.36C253.755,1140.32 254.847,1139.51 256.261,1138.92C257.675,1138.33 259.292,1138.04 261.112,1138.04C262.708,1138.04 264.269,1138.28 265.795,1138.75C267.321,1139.23 268.602,1139.87 269.638,1140.69L267.622,1144.93C266.586,1144.17 265.494,1143.6 264.346,1143.21C263.198,1142.81 262.078,1142.62 260.986,1142.62C259.838,1142.62 258.97,1142.79 258.382,1143.12C257.794,1143.46 257.5,1143.92 257.5,1144.51C257.5,1145.12 257.85,1145.61 258.55,1145.98C259.25,1146.34 260.314,1146.72 261.742,1147.11C263.282,1147.56 264.535,1147.99 265.501,1148.41C266.467,1148.83 267.307,1149.46 268.021,1150.28C268.735,1151.11 269.092,1152.18 269.092,1153.5C269.092,1155.6 268.259,1157.24 266.593,1158.43C264.927,1159.62 262.68,1160.22 259.852,1160.22C256.212,1160.22 252.964,1159.35 250.108,1157.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M280.894,1151.61C280.81,1152.78 281.048,1153.65 281.608,1154.21C282.168,1154.77 282.938,1155.05 283.918,1155.05C284.562,1155.05 285.276,1154.94 286.06,1154.71L285.64,1159.63C284.688,1160.02 283.456,1160.22 281.944,1160.22C279.536,1160.22 277.695,1159.57 276.421,1158.28C275.147,1157 274.51,1155.18 274.51,1152.82C274.51,1152.35 274.524,1151.98 274.552,1151.73L275.224,1143.33L271.192,1143.33L271.57,1138.59L275.602,1138.59L275.98,1133.59L282.49,1131.53L281.944,1138.59L287.362,1138.59L286.984,1143.33L281.566,1143.33L280.894,1151.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M287.656,1157.61L289.714,1153.2C290.89,1154.01 292.15,1154.64 293.494,1155.07C294.838,1155.51 296.182,1155.72 297.526,1155.72C298.702,1155.72 299.57,1155.55 300.13,1155.22C300.69,1154.88 300.97,1154.43 300.97,1153.87C300.97,1153.29 300.641,1152.82 299.983,1152.49C299.325,1152.15 298.254,1151.76 296.77,1151.31C295.23,1150.89 293.97,1150.47 292.99,1150.05C292.01,1149.63 291.163,1149.01 290.449,1148.18C289.735,1147.36 289.378,1146.29 289.378,1144.97C289.378,1143.6 289.763,1142.39 290.533,1141.36C291.303,1140.32 292.395,1139.51 293.809,1138.92C295.223,1138.33 296.84,1138.04 298.66,1138.04C300.256,1138.04 301.817,1138.28 303.343,1138.75C304.869,1139.23 306.15,1139.87 307.186,1140.69L305.17,1144.93C304.134,1144.17 303.042,1143.6 301.894,1143.21C300.746,1142.81 299.626,1142.62 298.534,1142.62C297.386,1142.62 296.518,1142.79 295.93,1143.12C295.342,1143.46 295.048,1143.92 295.048,1144.51C295.048,1145.12 295.398,1145.61 296.098,1145.98C296.798,1146.34 297.862,1146.72 299.29,1147.11C300.83,1147.56 302.083,1147.99 303.049,1148.41C304.015,1148.83 304.855,1149.46 305.569,1150.28C306.283,1151.11 306.64,1152.18 306.64,1153.5C306.64,1155.6 305.807,1157.24 304.141,1158.43C302.475,1159.62 300.228,1160.22 297.4,1160.22C293.76,1160.22 290.512,1159.35 287.656,1157.61Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M343.054,1150.51L343.054,1153.37L338.518,1153.37L338.518,1159.88L335.074,1159.88L335.074,1153.37L321.298,1153.37L321.298,1150.77L335.704,1129.98L338.518,1129.98L338.518,1150.51L343.054,1150.51ZM324.868,1150.51L335.074,1150.51L335.074,1135.81L324.868,1150.51Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M351.454,1155.55L351.454,1158.62C351.454,1159.8 351.258,1160.87 350.866,1161.85C350.474,1162.83 349.816,1163.79 348.892,1164.71L347.296,1163.49C348.388,1162.23 349.004,1161.03 349.144,1159.88L347.128,1159.88L347.128,1155.55L351.454,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M372.853,1142.3C374.267,1143.1 375.366,1144.22 376.15,1145.66C376.934,1147.11 377.326,1148.75 377.326,1150.6C377.326,1152.45 376.913,1154.1 376.087,1155.55C375.261,1157.01 374.12,1158.15 372.664,1158.98C371.208,1159.8 369.556,1160.22 367.708,1160.22C364.096,1160.22 361.31,1158.96 359.35,1156.44C357.39,1153.92 356.41,1150.33 356.41,1145.68C356.41,1142.32 356.865,1139.44 357.775,1137.03C358.685,1134.62 360.001,1132.79 361.723,1131.53C363.445,1130.27 365.51,1129.64 367.918,1129.64C369.654,1129.64 371.341,1129.96 372.979,1130.61C374.617,1131.25 376.052,1132.16 377.284,1133.34L375.982,1135.98C374.582,1134.81 373.238,1133.94 371.95,1133.38C370.662,1132.82 369.346,1132.54 368.002,1132.54C365.426,1132.54 363.424,1133.69 361.996,1135.98C360.568,1138.28 359.854,1141.5 359.854,1145.64L359.854,1146.27C360.498,1144.68 361.548,1143.42 363.004,1142.49C364.46,1141.57 366.126,1141.11 368.002,1141.11C369.822,1141.11 371.439,1141.51 372.853,1142.3ZM372.16,1155.49C373.336,1154.27 373.924,1152.66 373.924,1150.64C373.924,1148.65 373.329,1147.05 372.139,1145.83C370.949,1144.61 369.402,1144 367.498,1144C365.538,1144 363.942,1144.62 362.71,1145.85C361.478,1147.08 360.862,1148.68 360.862,1150.64C360.862,1152.63 361.478,1154.24 362.71,1155.47C363.942,1156.7 365.552,1157.32 367.54,1157.32C369.444,1157.32 370.984,1156.71 372.16,1155.49Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M386.356,1155.55L386.356,1158.62C386.356,1159.8 386.16,1160.87 385.768,1161.85C385.376,1162.83 384.718,1163.79 383.794,1164.71L382.198,1163.49C383.29,1162.23 383.906,1161.03 384.046,1159.88L382.03,1159.88L382.03,1155.55L386.356,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M391.774,1129.98L411.514,1129.98L411.514,1132.54L397.486,1159.88L393.79,1159.88L407.734,1132.87L391.774,1132.87L391.774,1129.98Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M421.258,1155.55L421.258,1158.62C421.258,1159.8 421.062,1160.87 420.67,1161.85C420.278,1162.83 419.62,1163.79 418.696,1164.71L417.1,1163.49C418.192,1162.23 418.808,1161.03 418.948,1159.88L416.932,1159.88L416.932,1155.55L421.258,1155.55Z" style="fill:white;fill-rule:nonzero;"/>

+                        <path d="M443.98,1133.42C445.94,1135.94 446.92,1139.52 446.92,1144.17C446.92,1149.24 445.905,1153.18 443.875,1156C441.845,1158.81 439.01,1160.22 435.37,1160.22C433.662,1160.22 431.989,1159.89 430.351,1159.25C428.713,1158.61 427.264,1157.7 426.004,1156.52L427.348,1153.87C428.776,1155.08 430.134,1155.95 431.422,1156.5C432.71,1157.05 434.012,1157.32 435.328,1157.32C437.904,1157.32 439.899,1156.17 441.313,1153.87C442.727,1151.58 443.434,1148.36 443.434,1144.21L443.434,1143.67C442.79,1145.24 441.74,1146.48 440.284,1147.38C438.828,1148.3 437.162,1148.75 435.286,1148.75C433.466,1148.75 431.856,1148.35 430.456,1147.55C429.056,1146.76 427.964,1145.63 427.18,1144.19C426.396,1142.75 426.004,1141.11 426.004,1139.26C426.004,1137.41 426.417,1135.76 427.243,1134.3C428.069,1132.85 429.21,1131.7 430.666,1130.88C432.122,1130.05 433.774,1129.64 435.622,1129.64C439.234,1129.64 442.02,1130.9 443.98,1133.42ZM440.62,1144C441.852,1142.77 442.468,1141.18 442.468,1139.22C442.468,1137.23 441.852,1135.62 440.62,1134.39C439.388,1133.15 437.778,1132.54 435.79,1132.54C433.886,1132.54 432.346,1133.15 431.17,1134.37C429.994,1135.58 429.406,1137.2 429.406,1139.22C429.406,1141.2 429.994,1142.81 431.17,1144.03C432.346,1145.24 433.9,1145.85 435.832,1145.85C437.792,1145.85 439.388,1145.24 440.62,1144Z" style="fill:white;fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,924.581,1896.21)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.243,113.327L788.243,337.412L1218.15,337.412L1218.15,113.327L788.243,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,1000.38,1493.46)">

+                        <path d="M238.058,803.134C243.772,806.359 248.157,810.857 251.212,816.627C254.267,822.398 255.794,829.073 255.794,836.654C255.794,844.235 254.125,850.967 250.787,856.851C247.45,862.735 242.697,867.289 236.531,870.514C230.364,873.738 223.151,875.351 214.891,875.351C207.537,875.351 200.296,874.021 193.167,871.362C186.039,868.703 180.042,865.054 175.177,860.415L180.438,849.723C191.64,859.001 203.124,863.64 214.891,863.64C223.378,863.64 230.025,861.236 234.834,856.427C239.642,851.618 242.047,845.084 242.047,836.824C242.047,828.791 239.671,822.313 234.919,817.391C230.166,812.469 223.83,810.008 215.91,810.008C204.369,810.008 195.147,814.704 188.245,824.095L178.571,824.095L178.571,753.321L251.042,753.321L251.042,764.862L192.488,764.862L192.488,807.972C199.164,801.522 207.707,798.297 218.116,798.297C225.697,798.297 232.344,799.91 238.058,803.134Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,1068.72,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.243,113.327L788.243,337.412L1218.15,337.412L1218.15,113.327L788.243,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,1144.52,1493.88)">

+                        <path d="M249.769,823.162C254.125,828.423 256.303,834.731 256.303,842.085C256.303,852.382 252.4,860.5 244.593,866.44C236.785,872.381 226.263,875.351 213.025,875.351C199.786,875.351 189.264,872.381 181.457,866.44C173.649,860.5 169.746,852.382 169.746,842.085C169.746,834.731 171.98,828.395 176.45,823.077C180.919,817.759 187.057,814.081 194.864,812.045C187.623,809.895 182.079,806.359 178.232,801.437C174.385,796.515 172.461,790.717 172.461,784.041C172.461,777.592 174.159,771.962 177.553,767.154C180.947,762.345 185.728,758.611 191.894,755.952C198.061,753.293 205.104,751.964 213.025,751.964C220.945,751.964 227.988,753.293 234.155,755.952C240.321,758.611 245.102,762.345 248.496,767.154C251.891,771.962 253.588,777.592 253.588,784.041C253.588,790.717 251.636,796.515 247.732,801.437C243.829,806.359 238.37,809.895 231.354,812.045C239.275,814.195 245.413,817.9 249.769,823.162ZM193.592,800.758C198.4,804.775 204.878,807.236 213.025,808.141C221.171,807.236 227.649,804.775 232.458,800.758C237.266,796.742 239.671,791.509 239.671,785.059C239.671,778.384 237.323,773.122 232.627,769.275C227.932,765.428 221.397,763.505 213.025,763.505C204.652,763.505 198.117,765.428 193.422,769.275C188.726,773.122 186.378,778.384 186.378,785.059C186.378,791.509 188.783,796.742 193.592,800.758ZM234.919,858.039C240.01,854.192 242.556,848.591 242.556,841.237C242.556,834.561 239.869,829.215 234.494,825.198C229.12,821.181 221.963,818.72 213.025,817.815C204.086,818.72 196.929,821.181 191.555,825.198C186.18,829.215 183.493,834.561 183.493,841.237C183.493,848.591 186.039,854.192 191.131,858.039C196.222,861.886 203.52,863.81 213.025,863.81C222.529,863.81 229.827,861.886 234.919,858.039Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,1288.44,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.244,113.327L788.244,337.412L1218.15,337.412L1218.15,113.327L788.244,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,1364.24,1493.88)">

+                        <path d="M258.34,836.315L258.34,847.856L240.01,847.856L240.01,874.163L226.093,874.163L226.093,847.856L170.425,847.856L170.425,837.333L228.639,753.321L240.01,753.321L240.01,836.315L258.34,836.315ZM184.851,836.315L226.093,836.315L226.093,776.913L184.851,836.315Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,1435.79,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.244,113.327L788.244,337.412L1218.15,337.412L1218.15,113.327L788.244,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,1511.59,1493.88)">

+                        <path d="M237.719,803.134C243.433,806.359 247.874,810.885 251.042,816.712C254.21,822.539 255.794,829.187 255.794,836.654C255.794,844.122 254.125,850.798 250.787,856.681C247.45,862.565 242.839,867.176 236.955,870.514C231.072,873.851 224.396,875.52 216.928,875.52C202.332,875.52 191.074,870.429 183.154,860.245C175.233,850.062 171.273,835.579 171.273,816.797C171.273,803.219 173.112,791.565 176.789,781.835C180.466,772.104 185.784,764.693 192.743,759.601C199.701,754.509 208.046,751.964 217.777,751.964C224.792,751.964 231.609,753.265 238.228,755.867C244.847,758.47 250.646,762.147 255.624,766.899L250.363,777.592C244.706,772.839 239.275,769.332 234.07,767.069C228.865,764.806 223.547,763.674 218.116,763.674C207.707,763.674 199.617,768.313 193.846,777.592C188.076,786.87 185.19,799.881 185.19,816.627L185.19,819.173C187.793,812.724 192.036,807.632 197.919,803.898C203.803,800.164 210.535,798.297 218.116,798.297C225.471,798.297 232.005,799.91 237.719,803.134ZM234.919,856.427C239.671,851.505 242.047,844.971 242.047,836.824C242.047,828.791 239.642,822.313 234.834,817.391C230.025,812.469 223.774,810.008 216.08,810.008C208.159,810.008 201.71,812.497 196.731,817.476C191.753,822.454 189.264,828.904 189.264,836.824C189.264,844.857 191.753,851.363 196.731,856.342C201.71,861.32 208.216,863.81 216.249,863.81C223.943,863.81 230.166,861.349 234.919,856.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,1579.24,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.244,113.327L788.244,337.412L1218.15,337.412L1218.15,113.327L788.244,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,1657.86,1494.73)">

+                        <path d="M173.14,753.321L252.909,753.321L252.909,763.674L196.222,874.163L181.287,874.163L237.634,765.032L173.14,765.032L173.14,753.321Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.211311,0,0,0.473437,1723.37,1896.64)">

+                        <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                        <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM788.243,113.327L788.243,337.412L1218.15,337.412L1218.15,113.327L788.243,113.327Z"/>

+                    </g>

+                    <g transform="matrix(0.626068,0,0,0.626068,1799.18,1493.88)">

+                        <path d="M243.065,767.239C250.985,777.422 254.946,791.905 254.946,810.687C254.946,831.167 250.844,847.092 242.641,858.463C234.438,869.835 222.982,875.52 208.272,875.52C201.37,875.52 194.61,874.219 187.991,871.617C181.372,869.014 175.516,865.337 170.425,860.585L175.856,849.893C181.626,854.758 187.114,858.294 192.319,860.5C197.523,862.706 202.785,863.81 208.103,863.81C218.512,863.81 226.574,859.171 232.288,849.893C238.002,840.614 240.859,827.603 240.859,810.857L240.859,808.65C238.256,814.987 234.013,819.993 228.13,823.671C222.246,827.348 215.514,829.187 207.933,829.187C200.578,829.187 194.072,827.574 188.415,824.35C182.758,821.125 178.345,816.599 175.177,810.772C172.009,804.945 170.425,798.297 170.425,790.83C170.425,783.362 172.094,776.686 175.431,770.803C178.769,764.919 183.38,760.308 189.264,756.97C195.147,753.633 201.823,751.964 209.291,751.964C223.887,751.964 235.145,757.055 243.065,767.239ZM229.487,810.008C234.466,805.03 236.955,798.58 236.955,790.66C236.955,782.627 234.466,776.121 229.487,771.142C224.509,766.164 218.003,763.674 209.97,763.674C202.276,763.674 196.052,766.135 191.3,771.057C186.548,775.979 184.172,782.513 184.172,790.66C184.172,798.693 186.548,805.171 191.3,810.093C196.052,815.015 202.332,817.476 210.139,817.476C218.06,817.476 224.509,814.987 229.487,810.008Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1000,1100L1000,1131.02L1000,1115.54L437.697,1115.54L437.697,1131.02" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1000,1115.51L1559.46,1115.51L1559.46,1131.02" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M438.385,1238.26L438.385,1255.91L252.909,1255.91L252.909,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M378.697,1256.06L378.697,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M438.385,1256.06L623.174,1256.06L623.174,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M501.146,1256.06L501.146,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M941.433,1256.06L941.433,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1001.57,1256.06L1183.44,1256.06L1183.44,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1062.39,1256.06L1062.39,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1559.46,1238.26L1559.46,1256.06L1374.65,1256.06L1374.65,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1498.49,1256.06L1498.49,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1559.46,1256.06L1744.68,1256.06L1744.68,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(1.17016,0,0,1.17016,-106.926,453.583)">

+                        <path d="M1621.13,1256.06L1621.13,1273.85" style="fill:none;stroke:black;stroke-width:5.21px;"/>

+                    </g>

+                    <g transform="matrix(0.819173,0,0,0.819173,395.392,1435.61)">

+                        <path d="M605.323,227.059L605.323,168.366L582.65,168.366L582.65,161.967L635.584,161.967L635.584,168.366L612.911,168.366L612.911,227.059L605.323,227.059Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M677.272,181.074L677.272,227.059L669.958,227.059L669.958,218.74C668.618,221.604 666.591,223.814 663.879,225.368C661.167,226.922 658.013,227.699 654.417,227.699C650.333,227.699 646.752,226.724 643.675,224.774C640.597,222.823 638.22,220.065 636.544,216.5C634.868,212.935 634.03,208.775 634.03,204.021C634.03,199.267 634.883,195.077 636.589,191.45C638.296,187.824 640.688,185.005 643.766,182.994C646.844,180.983 650.394,179.977 654.417,179.977C658.013,179.977 661.151,180.769 663.833,182.354C666.515,183.939 668.557,186.163 669.958,189.028L669.958,181.074L677.272,181.074ZM666.302,216.957C668.739,213.879 669.958,209.506 669.958,203.838C669.958,198.17 668.739,193.812 666.302,190.765C663.864,187.717 660.39,186.194 655.879,186.194C651.369,186.194 647.85,187.763 645.32,190.902C642.791,194.041 641.526,198.414 641.526,204.021C641.526,209.628 642.776,213.955 645.274,217.003C647.773,220.05 651.308,221.574 655.879,221.574C660.39,221.574 663.864,220.035 666.302,216.957Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M713.384,203.381L732.308,227.059L723.44,227.059L708.904,208.958L694.551,227.059L685.5,227.059L704.607,203.381L686.597,181.074L695.557,181.074L708.904,197.987L722.252,181.074L731.302,181.074L713.384,203.381Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M747.21,224.774C743.919,222.823 741.374,220.05 739.576,216.454C737.778,212.858 736.879,208.653 736.879,203.838C736.879,199.023 737.778,194.818 739.576,191.222C741.374,187.626 743.919,184.853 747.21,182.902C750.501,180.952 754.31,179.977 758.638,179.977C762.965,179.977 766.774,180.952 770.065,182.902C773.357,184.853 775.901,187.626 777.699,191.222C779.497,194.818 780.396,199.023 780.396,203.838C780.396,208.653 779.497,212.858 777.699,216.454C775.901,220.05 773.357,222.823 770.065,224.774C766.774,226.724 762.965,227.699 758.638,227.699C754.31,227.699 750.501,226.724 747.21,224.774ZM769.151,217.049C771.589,214.032 772.808,209.628 772.808,203.838C772.808,198.231 771.559,193.888 769.06,190.81C766.561,187.733 763.087,186.194 758.638,186.194C754.128,186.194 750.623,187.733 748.124,190.81C745.625,193.888 744.376,198.231 744.376,203.838C744.376,209.628 745.61,214.032 748.078,217.049C750.547,220.065 754.067,221.574 758.638,221.574C763.209,221.574 766.713,220.065 769.151,217.049Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M831.41,198.17L831.41,227.059L824.004,227.059L824.004,198.536C824.004,194.269 823.151,191.146 821.445,189.165C819.738,187.184 817.056,186.194 813.399,186.194C809.133,186.194 805.72,187.504 803.16,190.125C800.6,192.746 799.32,196.281 799.32,200.73L799.32,227.059L791.915,227.059L791.915,193.964C791.915,189.211 791.671,184.914 791.184,181.074L798.223,181.074L798.955,189.302C800.357,186.316 802.459,184.015 805.263,182.4C808.066,180.785 811.266,179.977 814.862,179.977C825.894,179.977 831.41,186.041 831.41,198.17Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M852.985,224.774C849.694,222.823 847.149,220.05 845.351,216.454C843.553,212.858 842.654,208.653 842.654,203.838C842.654,199.023 843.553,194.818 845.351,191.222C847.149,187.626 849.694,184.853 852.985,182.902C856.276,180.952 860.086,179.977 864.413,179.977C868.74,179.977 872.549,180.952 875.841,182.902C879.132,184.853 881.676,187.626 883.474,191.222C885.272,194.818 886.171,199.023 886.171,203.838C886.171,208.653 885.272,212.858 883.474,216.454C881.676,220.05 879.132,222.823 875.841,224.774C872.549,226.724 868.74,227.699 864.413,227.699C860.086,227.699 856.276,226.724 852.985,224.774ZM874.926,217.049C877.364,214.032 878.583,209.628 878.583,203.838C878.583,198.231 877.334,193.888 874.835,190.81C872.336,187.733 868.862,186.194 864.413,186.194C859.903,186.194 856.398,187.733 853.899,190.81C851.4,193.888 850.151,198.231 850.151,203.838C850.151,209.628 851.385,214.032 853.854,217.049C856.322,220.065 859.842,221.574 864.413,221.574C868.984,221.574 872.488,220.065 874.926,217.049Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M963.971,198.17L963.971,227.059L956.566,227.059L956.566,198.536C956.566,194.208 955.82,191.069 954.326,189.119C952.833,187.169 950.41,186.194 947.058,186.194C943.158,186.194 940.11,187.504 937.916,190.125C935.722,192.746 934.625,196.311 934.625,200.821L934.625,227.059L927.22,227.059L927.22,198.536C927.22,194.269 926.458,191.146 924.934,189.165C923.41,187.184 920.973,186.194 917.62,186.194C913.72,186.194 910.657,187.504 908.432,190.125C906.208,192.746 905.096,196.311 905.096,200.821L905.096,227.059L897.69,227.059L897.69,193.964C897.69,189.211 897.447,184.914 896.959,181.074L903.999,181.074L904.73,189.119C906.01,186.194 907.914,183.939 910.444,182.354C912.973,180.769 915.914,179.977 919.266,179.977C922.923,179.977 925.909,180.708 928.225,182.171C930.541,183.634 932.248,185.889 933.345,188.936C934.747,186.194 936.804,184.015 939.516,182.4C942.228,180.785 945.291,179.977 948.704,179.977C958.882,179.977 963.971,186.041 963.971,198.17Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M1018.46,181.074L996.975,231.265C994.72,236.506 991.885,240.346 988.472,242.784C985.059,245.222 980.854,246.898 975.856,247.812L974.302,242.052C978.629,241.077 981.905,239.782 984.13,238.167C986.354,236.552 988.198,234.068 989.661,230.716L991.489,226.602L972.016,181.074L979.787,181.074L995.329,219.014L1011.05,181.074L1018.46,181.074Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                    <g transform="matrix(0.819173,0,0,0.819173,396.058,1512.7)">

+                        <path d="M518.311,227.059L522.401,175.053L533.868,175.053L530.436,217.783L553.663,217.783L552.933,227.059L518.311,227.059Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M559.141,227.059L562.063,190.027L573.092,190.027L570.17,227.059L559.141,227.059ZM562.939,172.643L574.772,172.643L573.969,183.015L562.136,183.015L562.939,172.643Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M576.963,223.115L580.542,215.446C582.588,216.858 584.779,217.941 587.116,218.696C589.454,219.451 591.791,219.828 594.128,219.828C596.173,219.828 597.683,219.536 598.657,218.952C599.631,218.367 600.118,217.588 600.118,216.614C600.118,215.592 599.546,214.788 598.401,214.204C597.257,213.619 595.394,212.938 592.814,212.159C590.135,211.428 587.944,210.698 586.24,209.967C584.535,209.237 583.062,208.153 581.821,206.717C580.579,205.28 579.958,203.418 579.958,201.129C579.958,198.743 580.628,196.649 581.967,194.848C583.306,193.046 585.205,191.634 587.664,190.611C590.123,189.589 592.935,189.077 596.1,189.077C598.876,189.077 601.591,189.491 604.245,190.319C606.898,191.147 609.126,192.267 610.928,193.679L607.422,201.056C605.62,199.741 603.721,198.743 601.725,198.061C599.728,197.38 597.78,197.039 595.881,197.039C593.885,197.039 592.375,197.331 591.353,197.915C590.33,198.5 589.819,199.303 589.819,200.326C589.819,201.397 590.427,202.249 591.645,202.882C592.862,203.515 594.713,204.173 597.196,204.854C599.874,205.634 602.053,206.388 603.733,207.119C605.413,207.849 606.874,208.933 608.116,210.369C609.358,211.806 609.978,213.668 609.978,215.957C609.978,219.609 608.53,222.47 605.632,224.539C602.735,226.609 598.827,227.644 593.909,227.644C587.579,227.644 581.93,226.134 576.963,223.115Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M630.503,212.67C630.357,214.715 630.771,216.225 631.745,217.199C632.719,218.172 634.058,218.659 635.762,218.659C636.882,218.659 638.124,218.465 639.487,218.075L638.757,226.621C637.101,227.303 634.959,227.644 632.329,227.644C628.142,227.644 624.94,226.524 622.724,224.284C620.509,222.044 619.401,218.879 619.401,214.788C619.401,213.96 619.425,213.327 619.474,212.889L620.643,198.281L613.631,198.281L614.288,190.027L621.3,190.027L621.957,181.335L633.279,177.756L632.329,190.027L641.752,190.027L641.094,198.281L631.672,198.281L630.503,212.67Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M642.263,223.115L645.842,215.446C647.887,216.858 650.079,217.941 652.416,218.696C654.753,219.451 657.091,219.828 659.428,219.828C661.473,219.828 662.983,219.536 663.957,218.952C664.93,218.367 665.417,217.588 665.417,216.614C665.417,215.592 664.845,214.788 663.701,214.204C662.557,213.619 660.694,212.938 658.113,212.159C655.435,211.428 653.244,210.698 651.539,209.967C649.835,209.237 648.362,208.153 647.12,206.717C645.879,205.28 645.258,203.418 645.258,201.129C645.258,198.743 645.927,196.649 647.266,194.848C648.606,193.046 650.505,191.634 652.964,190.611C655.423,189.589 658.235,189.077 661.4,189.077C664.176,189.077 666.89,189.491 669.544,190.319C672.198,191.147 674.426,192.267 676.228,193.679L672.722,201.056C670.92,199.741 669.021,198.743 667.024,198.061C665.028,197.38 663.08,197.039 661.181,197.039C659.184,197.039 657.675,197.331 656.652,197.915C655.63,198.5 655.118,199.303 655.118,200.326C655.118,201.397 655.727,202.249 656.945,202.882C658.162,203.515 660.012,204.173 662.496,204.854C665.174,205.634 667.353,206.388 669.033,207.119C670.713,207.849 672.174,208.933 673.416,210.369C674.657,211.806 675.278,213.668 675.278,215.957C675.278,219.609 673.829,222.47 670.932,224.539C668.035,226.609 664.127,227.644 659.209,227.644C652.879,227.644 647.23,226.134 642.263,223.115Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M716.182,227.059L716.182,180.166L698.067,180.166L698.067,175.053L740.359,175.053L740.359,180.166L722.244,180.166L722.244,227.059L716.182,227.059Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M772.059,208.507L745.106,208.507C745.155,213.181 746.239,216.712 748.357,219.098C750.475,221.484 753.555,222.677 757.597,222.677C761.882,222.677 765.826,221.24 769.429,218.367L771.402,222.677C769.795,224.186 767.737,225.379 765.23,226.256C762.722,227.132 760.153,227.571 757.524,227.571C751.778,227.571 747.273,225.878 744.011,222.494C740.748,219.11 739.117,214.472 739.117,208.58C739.117,204.83 739.847,201.507 741.308,198.609C742.769,195.712 744.814,193.46 747.444,191.853C750.073,190.246 753.068,189.443 756.428,189.443C761.297,189.443 765.12,191.037 767.896,194.227C770.671,197.416 772.059,201.811 772.059,207.411L772.059,208.507ZM749.014,196.82C747.091,198.67 745.861,201.275 745.326,204.635L766.727,204.635C766.435,201.178 765.424,198.548 763.696,196.747C761.967,194.945 759.569,194.044 756.501,194.044C753.433,194.044 750.938,194.969 749.014,196.82Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M801.495,189.881L801.349,195.286C800.229,194.896 798.938,194.702 797.478,194.702C793.923,194.702 791.281,195.809 789.553,198.025C787.824,200.241 786.96,202.931 786.96,206.096L786.96,227.059L781.043,227.059L781.043,200.618C781.043,196.82 780.848,193.387 780.459,190.319L786.083,190.319L786.667,197.112C787.593,194.629 789.078,192.729 791.123,191.415C793.168,190.1 795.506,189.443 798.135,189.443C799.352,189.443 800.472,189.589 801.495,189.881Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M860.44,203.978L860.44,227.059L854.524,227.059L854.524,204.27C854.524,200.813 853.927,198.305 852.734,196.747C851.541,195.189 849.605,194.409 846.927,194.409C843.811,194.409 841.376,195.456 839.623,197.55C837.87,199.644 836.993,202.493 836.993,206.096L836.993,227.059L831.077,227.059L831.077,204.27C831.077,200.861 830.468,198.366 829.251,196.783C828.034,195.201 826.086,194.409 823.408,194.409C820.291,194.409 817.844,195.456 816.067,197.55C814.29,199.644 813.401,202.493 813.401,206.096L813.401,227.059L807.484,227.059L807.484,200.618C807.484,196.82 807.29,193.387 806.9,190.319L812.524,190.319L813.109,196.747C814.131,194.409 815.653,192.608 817.674,191.342C819.695,190.076 822.044,189.443 824.722,189.443C827.644,189.443 830.03,190.027 831.88,191.196C833.731,192.364 835.094,194.166 835.971,196.601C837.091,194.409 838.734,192.669 840.901,191.378C843.068,190.088 845.515,189.443 848.242,189.443C856.374,189.443 860.44,194.288 860.44,203.978Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M869.424,222.823L871.396,218.44C873.393,219.998 875.414,221.118 877.459,221.8C879.504,222.482 881.793,222.823 884.325,222.823C887.1,222.823 889.206,222.348 890.643,221.398C892.079,220.449 892.798,219.073 892.798,217.272C892.798,215.811 892.311,214.642 891.337,213.766C890.363,212.889 888.756,212.207 886.516,211.72L880.307,210.26C877.24,209.578 874.866,208.36 873.186,206.607C871.506,204.854 870.666,202.761 870.666,200.326C870.666,197.112 871.956,194.495 874.537,192.474C877.118,190.453 880.527,189.443 884.763,189.443C887.344,189.443 889.779,189.856 892.067,190.684C894.356,191.512 896.279,192.705 897.838,194.263L895.865,198.573C892.408,195.7 888.707,194.263 884.763,194.263C882.134,194.263 880.1,194.762 878.664,195.761C877.228,196.759 876.509,198.159 876.509,199.961C876.509,201.47 876.96,202.663 877.861,203.54C878.761,204.416 880.21,205.098 882.207,205.585L888.415,207.119C891.824,207.898 894.356,209.103 896.012,210.734C897.667,212.366 898.495,214.496 898.495,217.125C898.495,220.291 897.205,222.823 894.624,224.722C892.043,226.621 888.537,227.571 884.106,227.571C877.921,227.571 873.028,225.988 869.424,222.823Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M948.164,222.019L959.631,222.019L959.631,227.059L930.633,227.059L930.633,222.019L942.101,222.019L942.101,182.504L931.437,189.296L931.437,183.526L944.731,175.053L948.164,175.053L948.164,222.019Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M977.307,219.536L977.307,224.868C977.307,226.913 976.967,228.788 976.285,230.492C975.603,232.197 974.459,233.852 972.852,235.459L970.076,233.341C971.975,231.15 973.047,229.056 973.29,227.059L969.784,227.059L969.784,219.536L977.307,219.536Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M1021.5,222.019L1021.5,227.059L988.045,227.059L988.045,222.531L1006.23,202.371C1008.67,199.644 1010.44,197.185 1011.56,194.994C1012.68,192.802 1013.24,190.611 1013.24,188.42C1013.24,185.547 1012.42,183.344 1010.76,181.81C1009.11,180.276 1006.74,179.509 1003.68,179.509C998.709,179.509 993.791,181.505 988.921,185.498L986.657,180.897C988.702,178.949 991.283,177.391 994.399,176.222C997.516,175.053 1000.66,174.469 1003.82,174.469C1008.59,174.469 1012.37,175.698 1015.14,178.158C1017.92,180.617 1019.31,183.94 1019.31,188.128C1019.31,191.098 1018.64,193.959 1017.3,196.71C1015.96,199.461 1013.73,202.541 1010.62,205.95L995.787,222.019L1021.5,222.019Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M1038.01,219.536L1038.01,224.868C1038.01,226.913 1037.66,228.788 1036.98,230.492C1036.3,232.197 1035.16,233.852 1033.55,235.459L1030.77,233.341C1032.67,231.15 1033.75,229.056 1033.99,227.059L1030.48,227.059L1030.48,219.536L1038.01,219.536Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                        <path d="M1078.76,204.854C1080.37,206.997 1081.17,209.7 1081.17,212.962C1081.17,217.491 1079.64,221.058 1076.57,223.663C1073.5,226.268 1069.34,227.571 1064.08,227.571C1060.72,227.571 1057.5,227.011 1054.4,225.891C1051.31,224.771 1048.69,223.188 1046.55,221.143L1048.89,216.541C1053.71,220.534 1058.72,222.531 1063.93,222.531C1067.64,222.531 1070.45,221.703 1072.37,220.047C1074.3,218.392 1075.26,215.957 1075.26,212.743C1075.26,206.364 1071.26,203.174 1063.28,203.174L1057.29,203.174L1057.29,198.135L1062.11,198.135C1065.96,198.135 1068.9,197.282 1070.95,195.578C1072.99,193.874 1074.02,191.439 1074.02,188.274C1074.02,185.45 1073.17,183.283 1071.5,181.773C1069.82,180.264 1067.44,179.509 1064.37,179.509C1059.41,179.509 1054.49,181.505 1049.62,185.498L1047.36,180.897C1049.45,178.9 1052.02,177.33 1055.06,176.185C1058.1,175.041 1061.28,174.469 1064.59,174.469C1069.27,174.469 1073.01,175.662 1075.81,178.048C1078.61,180.434 1080.01,183.648 1080.01,187.69C1080.01,190.66 1079.27,193.265 1077.81,195.505C1076.35,197.745 1074.33,199.352 1071.75,200.326C1074.82,201.202 1077.16,202.712 1078.76,204.854Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+                    </g>

+                </g>

+            </g>

+        </g>

+    </g>

+    <g transform="matrix(1.04093,0,0,1.04093,1943.89,-1055.94)">

+        <g transform="matrix(0.838555,0,0,0.571615,148.452,1635.59)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,131,192);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM765.704,109.699L765.704,341.04L1240.69,341.04L1240.69,109.699L765.704,109.699Z"/>

+        </g>

+        <g transform="matrix(1.59331,0,0,1.59331,562.512,-689.213)">

+            <path d="M153.743,1571.85L155.087,1554.76L158.855,1554.76L157.727,1568.8L165.359,1568.8L165.119,1571.85L153.743,1571.85Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M167.159,1571.85L168.119,1559.68L171.743,1559.68L170.783,1571.85L167.159,1571.85ZM168.407,1553.97L172.295,1553.97L172.031,1557.38L168.143,1557.38L168.407,1553.97Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M173.015,1570.55L174.191,1568.03C174.863,1568.5 175.583,1568.85 176.351,1569.1C177.119,1569.35 177.887,1569.47 178.655,1569.47C179.327,1569.47 179.823,1569.38 180.143,1569.19C180.463,1568.99 180.623,1568.74 180.623,1568.42C180.623,1568.08 180.435,1567.82 180.059,1567.63C179.683,1567.43 179.071,1567.21 178.223,1566.95C177.343,1566.71 176.623,1566.47 176.063,1566.23C175.503,1565.99 175.019,1565.64 174.611,1565.17C174.203,1564.69 173.999,1564.08 173.999,1563.33C173.999,1562.55 174.219,1561.86 174.659,1561.27C175.099,1560.67 175.723,1560.21 176.531,1559.87C177.339,1559.54 178.263,1559.37 179.303,1559.37C180.215,1559.37 181.107,1559.51 181.979,1559.78C182.851,1560.05 183.583,1560.42 184.175,1560.88L183.023,1563.31C182.431,1562.87 181.807,1562.55 181.151,1562.32C180.495,1562.1 179.855,1561.99 179.231,1561.99C178.575,1561.99 178.079,1562.08 177.743,1562.27C177.407,1562.47 177.239,1562.73 177.239,1563.07C177.239,1563.42 177.439,1563.7 177.839,1563.91C178.239,1564.11 178.847,1564.33 179.663,1564.55C180.543,1564.81 181.259,1565.06 181.811,1565.3C182.363,1565.54 182.843,1565.89 183.251,1566.37C183.659,1566.84 183.863,1567.45 183.863,1568.2C183.863,1569.4 183.387,1570.34 182.435,1571.02C181.483,1571.7 180.199,1572.04 178.583,1572.04C176.503,1572.04 174.647,1571.55 173.015,1570.55Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M190.607,1567.12C190.559,1567.79 190.695,1568.29 191.015,1568.61C191.335,1568.93 191.775,1569.09 192.335,1569.09C192.703,1569.09 193.111,1569.03 193.559,1568.9L193.319,1571.71C192.775,1571.93 192.071,1572.04 191.207,1572.04C189.831,1572.04 188.779,1571.67 188.051,1570.94C187.323,1570.2 186.959,1569.16 186.959,1567.82C186.959,1567.55 186.967,1567.34 186.983,1567.19L187.367,1562.39L185.063,1562.39L185.279,1559.68L187.583,1559.68L187.799,1556.83L191.519,1555.65L191.207,1559.68L194.303,1559.68L194.087,1562.39L190.991,1562.39L190.607,1567.12Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M194.471,1570.55L195.647,1568.03C196.319,1568.5 197.039,1568.85 197.807,1569.1C198.575,1569.35 199.343,1569.47 200.111,1569.47C200.783,1569.47 201.279,1569.38 201.599,1569.19C201.919,1568.99 202.079,1568.74 202.079,1568.42C202.079,1568.08 201.891,1567.82 201.515,1567.63C201.139,1567.43 200.527,1567.21 199.679,1566.95C198.799,1566.71 198.079,1566.47 197.519,1566.23C196.959,1565.99 196.475,1565.64 196.067,1565.17C195.659,1564.69 195.455,1564.08 195.455,1563.33C195.455,1562.55 195.675,1561.86 196.115,1561.27C196.555,1560.67 197.179,1560.21 197.987,1559.87C198.795,1559.54 199.719,1559.37 200.759,1559.37C201.671,1559.37 202.563,1559.51 203.435,1559.78C204.307,1560.05 205.039,1560.42 205.631,1560.88L204.479,1563.31C203.887,1562.87 203.263,1562.55 202.607,1562.32C201.951,1562.1 201.311,1561.99 200.687,1561.99C200.031,1561.99 199.535,1562.08 199.199,1562.27C198.863,1562.47 198.695,1562.73 198.695,1563.07C198.695,1563.42 198.895,1563.7 199.295,1563.91C199.695,1564.11 200.303,1564.33 201.119,1564.55C201.999,1564.81 202.715,1565.06 203.267,1565.3C203.819,1565.54 204.299,1565.89 204.707,1566.37C205.115,1566.84 205.319,1567.45 205.319,1568.2C205.319,1569.4 204.843,1570.34 203.891,1571.02C202.939,1571.7 201.655,1572.04 200.039,1572.04C197.959,1572.04 196.103,1571.55 194.471,1570.55Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M221.351,1570.19L225.119,1570.19L225.119,1571.85L215.591,1571.85L215.591,1570.19L219.359,1570.19L219.359,1557.21L215.855,1559.44L215.855,1557.55L220.223,1554.76L221.351,1554.76L221.351,1570.19Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M230.927,1569.38L230.927,1571.13C230.927,1571.8 230.815,1572.42 230.591,1572.98C230.367,1573.54 229.991,1574.08 229.463,1574.61L228.551,1573.91C229.175,1573.19 229.527,1572.51 229.607,1571.85L228.455,1571.85L228.455,1569.38L230.927,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M245.447,1570.19L245.447,1571.85L234.455,1571.85L234.455,1570.36L240.431,1563.74C241.231,1562.84 241.815,1562.03 242.183,1561.31C242.551,1560.59 242.735,1559.87 242.735,1559.15C242.735,1558.21 242.463,1557.49 241.919,1556.98C241.375,1556.48 240.599,1556.23 239.591,1556.23C237.959,1556.23 236.343,1556.88 234.743,1558.19L233.999,1556.68C234.671,1556.04 235.519,1555.53 236.543,1555.15C237.567,1554.76 238.599,1554.57 239.639,1554.57C241.207,1554.57 242.447,1554.97 243.359,1555.78C244.271,1556.59 244.727,1557.68 244.727,1559.06C244.727,1560.03 244.507,1560.97 244.067,1561.88C243.627,1562.78 242.895,1563.79 241.871,1564.91L236.999,1570.19L245.447,1570.19Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M250.871,1569.38L250.871,1571.13C250.871,1571.8 250.759,1572.42 250.535,1572.98C250.311,1573.54 249.935,1574.08 249.407,1574.61L248.495,1573.91C249.119,1573.19 249.471,1572.51 249.551,1571.85L248.399,1571.85L248.399,1569.38L250.871,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M264.263,1564.55C264.791,1565.26 265.055,1566.15 265.055,1567.22C265.055,1568.71 264.551,1569.88 263.543,1570.73C262.535,1571.59 261.167,1572.02 259.439,1572.02C258.335,1572.02 257.275,1571.83 256.259,1571.47C255.243,1571.1 254.383,1570.58 253.679,1569.91L254.447,1568.39C256.031,1569.71 257.679,1570.36 259.391,1570.36C260.607,1570.36 261.531,1570.09 262.163,1569.55C262.795,1569 263.111,1568.2 263.111,1567.15C263.111,1565.05 261.799,1564 259.175,1564L257.207,1564L257.207,1562.35L258.791,1562.35C260.055,1562.35 261.023,1562.07 261.695,1561.51C262.367,1560.95 262.703,1560.15 262.703,1559.11C262.703,1558.18 262.427,1557.47 261.875,1556.97C261.323,1556.47 260.543,1556.23 259.535,1556.23C257.903,1556.23 256.287,1556.88 254.687,1558.19L253.943,1556.68C254.631,1556.03 255.475,1555.51 256.475,1555.13C257.475,1554.76 258.519,1554.57 259.607,1554.57C261.143,1554.57 262.371,1554.96 263.291,1555.75C264.211,1556.53 264.671,1557.59 264.671,1558.91C264.671,1559.89 264.431,1560.75 263.951,1561.48C263.471,1562.22 262.807,1562.75 261.959,1563.07C262.967,1563.35 263.735,1563.85 264.263,1564.55Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M270.815,1569.38L270.815,1571.13C270.815,1571.8 270.703,1572.42 270.479,1572.98C270.255,1573.54 269.879,1574.08 269.351,1574.61L268.439,1573.91C269.063,1573.19 269.415,1572.51 269.495,1571.85L268.343,1571.85L268.343,1569.38L270.815,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M285.959,1566.5L285.959,1568.13L283.367,1568.13L283.367,1571.85L281.399,1571.85L281.399,1568.13L273.527,1568.13L273.527,1566.64L281.759,1554.76L283.367,1554.76L283.367,1566.5L285.959,1566.5ZM275.567,1566.5L281.399,1566.5L281.399,1558.1L275.567,1566.5Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M290.759,1569.38L290.759,1571.13C290.759,1571.8 290.647,1572.42 290.423,1572.98C290.199,1573.54 289.823,1574.08 289.295,1574.61L288.383,1573.91C289.007,1573.19 289.359,1572.51 289.439,1571.85L288.287,1571.85L288.287,1569.38L290.759,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M303.035,1561.81C303.843,1562.26 304.463,1562.9 304.895,1563.71C305.327,1564.53 305.543,1565.47 305.543,1566.55C305.543,1567.62 305.307,1568.57 304.835,1569.4C304.363,1570.23 303.691,1570.88 302.819,1571.33C301.947,1571.79 300.927,1572.02 299.759,1572.02C298.719,1572.02 297.695,1571.83 296.687,1571.45C295.679,1571.08 294.831,1570.56 294.143,1569.91L294.887,1568.39C296.471,1569.71 298.095,1570.36 299.759,1570.36C300.959,1570.36 301.899,1570.02 302.579,1569.34C303.259,1568.66 303.599,1567.74 303.599,1566.57C303.599,1565.43 303.263,1564.52 302.591,1563.82C301.919,1563.13 301.023,1562.78 299.903,1562.78C298.271,1562.78 296.967,1563.44 295.991,1564.77L294.623,1564.77L294.623,1554.76L304.871,1554.76L304.871,1556.39L296.591,1556.39L296.591,1562.49C297.535,1561.58 298.743,1561.12 300.215,1561.12C301.287,1561.12 302.227,1561.35 303.035,1561.81Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M310.703,1569.38L310.703,1571.13C310.703,1571.8 310.591,1572.42 310.367,1572.98C310.143,1573.54 309.767,1574.08 309.239,1574.61L308.327,1573.91C308.951,1573.19 309.303,1572.51 309.383,1571.85L308.231,1571.85L308.231,1569.38L310.703,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M322.931,1561.81C323.739,1562.26 324.367,1562.9 324.815,1563.73C325.263,1564.55 325.487,1565.49 325.487,1566.55C325.487,1567.6 325.251,1568.55 324.779,1569.38C324.307,1570.21 323.655,1570.86 322.823,1571.33C321.991,1571.81 321.047,1572.04 319.991,1572.04C317.927,1572.04 316.335,1571.32 315.215,1569.88C314.095,1568.44 313.535,1566.39 313.535,1563.74C313.535,1561.82 313.795,1560.17 314.315,1558.79C314.835,1557.42 315.587,1556.37 316.571,1555.65C317.555,1554.93 318.735,1554.57 320.111,1554.57C321.103,1554.57 322.067,1554.75 323.003,1555.12C323.939,1555.49 324.759,1556.01 325.463,1556.68L324.719,1558.19C323.919,1557.52 323.151,1557.03 322.415,1556.71C321.679,1556.39 320.927,1556.23 320.159,1556.23C318.687,1556.23 317.543,1556.88 316.727,1558.19C315.911,1559.51 315.503,1561.35 315.503,1563.71L315.503,1564.07C315.871,1563.16 316.471,1562.44 317.303,1561.91C318.135,1561.39 319.087,1561.12 320.159,1561.12C321.199,1561.12 322.123,1561.35 322.931,1561.81ZM322.535,1569.34C323.207,1568.65 323.543,1567.72 323.543,1566.57C323.543,1565.43 323.203,1564.52 322.523,1563.82C321.843,1563.13 320.959,1562.78 319.871,1562.78C318.751,1562.78 317.839,1563.13 317.135,1563.83C316.431,1564.54 316.079,1565.45 316.079,1566.57C316.079,1567.71 316.431,1568.63 317.135,1569.33C317.839,1570.03 318.759,1570.39 319.895,1570.39C320.983,1570.39 321.863,1570.04 322.535,1569.34Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M330.647,1569.38L330.647,1571.13C330.647,1571.8 330.535,1572.42 330.311,1572.98C330.087,1573.54 329.711,1574.08 329.183,1574.61L328.271,1573.91C328.895,1573.19 329.247,1572.51 329.327,1571.85L328.175,1571.85L328.175,1569.38L330.647,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M333.743,1554.76L345.023,1554.76L345.023,1556.23L337.007,1571.85L334.895,1571.85L342.863,1556.42L333.743,1556.42L333.743,1554.76Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M350.591,1569.38L350.591,1571.13C350.591,1571.8 350.479,1572.42 350.255,1572.98C350.031,1573.54 349.655,1574.08 349.127,1574.61L348.215,1573.91C348.839,1573.19 349.191,1572.51 349.271,1571.85L348.119,1571.85L348.119,1569.38L350.591,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M364.523,1564.64C365.139,1565.38 365.447,1566.27 365.447,1567.31C365.447,1568.77 364.895,1569.92 363.791,1570.76C362.687,1571.6 361.199,1572.02 359.327,1572.02C357.455,1572.02 355.967,1571.6 354.863,1570.76C353.759,1569.92 353.207,1568.77 353.207,1567.31C353.207,1566.27 353.523,1565.38 354.155,1564.63C354.787,1563.87 355.655,1563.35 356.759,1563.07C355.735,1562.76 354.951,1562.26 354.407,1561.57C353.863,1560.87 353.591,1560.05 353.591,1559.11C353.591,1558.19 353.831,1557.4 354.311,1556.72C354.791,1556.04 355.467,1555.51 356.339,1555.13C357.211,1554.76 358.207,1554.57 359.327,1554.57C360.447,1554.57 361.443,1554.76 362.315,1555.13C363.187,1555.51 363.863,1556.04 364.343,1556.72C364.823,1557.4 365.063,1558.19 365.063,1559.11C365.063,1560.05 364.787,1560.87 364.235,1561.57C363.683,1562.26 362.911,1562.76 361.919,1563.07C363.039,1563.37 363.907,1563.89 364.523,1564.64ZM356.579,1561.47C357.259,1562.04 358.175,1562.39 359.327,1562.51C360.479,1562.39 361.395,1562.04 362.075,1561.47C362.755,1560.9 363.095,1560.16 363.095,1559.25C363.095,1558.31 362.763,1557.56 362.099,1557.02C361.435,1556.47 360.511,1556.2 359.327,1556.2C358.143,1556.2 357.219,1556.47 356.555,1557.02C355.891,1557.56 355.559,1558.31 355.559,1559.25C355.559,1560.16 355.899,1560.9 356.579,1561.47ZM362.423,1569.57C363.143,1569.03 363.503,1568.23 363.503,1567.19C363.503,1566.25 363.123,1565.49 362.363,1564.93C361.603,1564.36 360.591,1564.01 359.327,1563.88C358.063,1564.01 357.051,1564.36 356.291,1564.93C355.531,1565.49 355.151,1566.25 355.151,1567.19C355.151,1568.23 355.511,1569.03 356.231,1569.57C356.951,1570.11 357.983,1570.39 359.327,1570.39C360.671,1570.39 361.703,1570.11 362.423,1569.57Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M370.535,1569.38L370.535,1571.13C370.535,1571.8 370.423,1572.42 370.199,1572.98C369.975,1573.54 369.599,1574.08 369.071,1574.61L368.159,1573.91C368.783,1573.19 369.135,1572.51 369.215,1571.85L368.063,1571.85L368.063,1569.38L370.535,1569.38Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M383.519,1556.73C384.639,1558.17 385.199,1560.22 385.199,1562.87C385.199,1565.77 384.619,1568.02 383.459,1569.63C382.299,1571.24 380.679,1572.04 378.599,1572.04C377.623,1572.04 376.667,1571.86 375.731,1571.49C374.795,1571.12 373.967,1570.6 373.247,1569.93L374.015,1568.42C374.831,1569.11 375.607,1569.61 376.343,1569.92C377.079,1570.23 377.823,1570.39 378.575,1570.39C380.047,1570.39 381.187,1569.73 381.995,1568.42C382.803,1567.11 383.207,1565.27 383.207,1562.9L383.207,1562.59C382.839,1563.48 382.239,1564.19 381.407,1564.71C380.575,1565.23 379.623,1565.49 378.551,1565.49C377.511,1565.49 376.591,1565.26 375.791,1564.81C374.991,1564.35 374.367,1563.71 373.919,1562.89C373.471,1562.06 373.247,1561.12 373.247,1560.07C373.247,1559.01 373.483,1558.07 373.955,1557.23C374.427,1556.4 375.079,1555.75 375.911,1555.28C376.743,1554.81 377.687,1554.57 378.743,1554.57C380.807,1554.57 382.399,1555.29 383.519,1556.73ZM381.599,1562.78C382.303,1562.07 382.655,1561.16 382.655,1560.04C382.655,1558.91 382.303,1557.99 381.599,1557.28C380.895,1556.58 379.975,1556.23 378.839,1556.23C377.751,1556.23 376.871,1556.57 376.199,1557.27C375.527,1557.97 375.191,1558.89 375.191,1560.04C375.191,1561.18 375.527,1562.09 376.199,1562.79C376.871,1563.49 377.759,1563.83 378.863,1563.83C379.983,1563.83 380.895,1563.48 381.599,1562.78Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(1.92666,0,0,1.92666,-562.222,1327.03)">

+            <path d="M790.995,227.059L788.425,227.059L785.825,220.057C785.51,219.19 785.071,218.609 784.51,218.314C783.949,218.018 783.156,217.871 782.131,217.871L776.872,217.871L776.872,227.059L774.479,227.059L774.479,206.023L782.841,206.023C785.106,206.023 786.844,206.525 788.055,207.53C789.267,208.534 789.872,209.982 789.872,211.873C789.872,213.252 789.513,214.409 788.794,215.344C788.075,216.28 787.036,216.945 785.677,217.339C786.288,217.437 786.81,217.698 787.243,218.122C787.676,218.545 788.041,219.151 788.336,219.939L790.995,227.059ZM782.634,215.861C785.864,215.861 787.479,214.542 787.479,211.902C787.479,210.602 787.085,209.632 786.297,208.992C785.51,208.352 784.288,208.032 782.634,208.032L776.872,208.032L776.872,215.861L782.634,215.861Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M793.743,224.636L794.659,222.775C795.703,223.661 796.766,224.292 797.85,224.666C798.933,225.04 800.194,225.227 801.632,225.227C803.326,225.227 804.631,224.897 805.546,224.238C806.462,223.578 806.92,222.647 806.92,221.446C806.92,220.736 806.699,220.16 806.256,219.717C805.812,219.274 805.231,218.924 804.512,218.668C803.793,218.412 802.833,218.146 801.632,217.871C800.016,217.516 798.687,217.132 797.643,216.718C796.599,216.305 795.752,215.709 795.102,214.931C794.452,214.153 794.127,213.133 794.127,211.873C794.127,210.671 794.442,209.613 795.072,208.697C795.703,207.781 796.594,207.067 797.746,206.555C798.899,206.042 800.243,205.786 801.779,205.786C803.237,205.786 804.596,206.013 805.857,206.466C807.117,206.919 808.181,207.579 809.048,208.445L808.102,210.307C807.117,209.46 806.118,208.839 805.103,208.445C804.089,208.052 802.981,207.855 801.779,207.855C800.144,207.855 798.864,208.204 797.938,208.903C797.013,209.603 796.55,210.563 796.55,211.784C796.55,212.848 796.954,213.645 797.761,214.177C798.569,214.709 799.81,215.172 801.484,215.566C803.296,215.999 804.719,216.398 805.753,216.763C806.787,217.127 807.649,217.678 808.338,218.417C809.028,219.156 809.373,220.136 809.373,221.357C809.373,222.539 809.057,223.578 808.427,224.474C807.797,225.37 806.896,226.065 805.724,226.557C804.552,227.049 803.178,227.296 801.602,227.296C798.313,227.296 795.693,226.409 793.743,224.636Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+            <path d="M812.15,224.636L813.066,222.775C814.11,223.661 815.173,224.292 816.257,224.666C817.34,225.04 818.601,225.227 820.039,225.227C821.733,225.227 823.037,224.897 823.953,224.238C824.869,223.578 825.327,222.647 825.327,221.446C825.327,220.736 825.106,220.16 824.662,219.717C824.219,219.274 823.638,218.924 822.919,218.668C822.2,218.412 821.24,218.146 820.039,217.871C818.423,217.516 817.094,217.132 816.05,216.718C815.006,216.305 814.159,215.709 813.509,214.931C812.859,214.153 812.534,213.133 812.534,211.873C812.534,210.671 812.849,209.613 813.479,208.697C814.11,207.781 815.001,207.067 816.153,206.555C817.306,206.042 818.65,205.786 820.186,205.786C821.644,205.786 823.003,206.013 824.264,206.466C825.524,206.919 826.588,207.579 827.455,208.445L826.509,210.307C825.524,209.46 824.525,208.839 823.51,208.445C822.496,208.052 821.388,207.855 820.186,207.855C818.551,207.855 817.271,208.204 816.345,208.903C815.42,209.603 814.957,210.563 814.957,211.784C814.957,212.848 815.361,213.645 816.168,214.177C816.976,214.709 818.217,215.172 819.891,215.566C821.703,215.999 823.126,216.398 824.16,216.763C825.194,217.127 826.056,217.678 826.745,218.417C827.435,219.156 827.78,220.136 827.78,221.357C827.78,222.539 827.464,223.578 826.834,224.474C826.204,225.37 825.303,226.065 824.131,226.557C822.959,227.049 821.585,227.296 820.009,227.296C816.72,227.296 814.1,226.409 812.15,224.636Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,410.646,1827.37)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.431,112.072L785.431,338.667L1220.96,338.667L1220.96,112.072L785.431,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,485.918,1441.27)">

+            <path d="M253.927,862.452L253.927,874.163L176.195,874.163L176.195,863.64L218.456,816.797C224.113,810.461 228.243,804.747 230.845,799.655C233.448,794.564 234.749,789.472 234.749,784.38C234.749,777.705 232.825,772.585 228.978,769.021C225.131,765.456 219.644,763.674 212.515,763.674C200.974,763.674 189.547,768.313 178.232,777.592L172.97,766.899C177.723,762.373 183.719,758.753 190.961,756.037C198.202,753.321 205.5,751.964 212.855,751.964C223.943,751.964 232.712,754.821 239.162,760.535C245.611,766.249 248.836,773.971 248.836,783.701C248.836,790.603 247.28,797.251 244.168,803.644C241.057,810.036 235.88,817.193 228.639,825.113L194.186,862.452L253.927,862.452Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,532.111,1827.37)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.432,112.072L785.432,338.667L1220.96,338.667L1220.96,112.072L785.432,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,608.659,1439.74)">

+            <path d="M245.95,822.567C249.684,827.546 251.551,833.826 251.551,841.406C251.551,851.929 247.987,860.217 240.859,866.271C233.73,872.324 224.056,875.351 211.837,875.351C204.029,875.351 196.533,874.049 189.349,871.447C182.164,868.845 176.082,865.167 171.104,860.415L176.535,849.723C187.736,859.001 199.39,863.64 211.497,863.64C220.096,863.64 226.631,861.716 231.1,857.869C235.569,854.022 237.804,848.365 237.804,840.897C237.804,826.075 228.526,818.664 209.97,818.664L196.052,818.664L196.052,806.953L207.254,806.953C216.193,806.953 223.038,804.973 227.79,801.013C232.542,797.053 234.919,791.395 234.919,784.041C234.919,777.478 232.967,772.443 229.063,768.936C225.16,765.428 219.644,763.674 212.515,763.674C200.974,763.674 189.547,768.313 178.232,777.592L172.97,766.899C177.836,762.26 183.804,758.611 190.876,755.952C197.948,753.293 205.331,751.964 213.025,751.964C223.887,751.964 232.571,754.736 239.077,760.28C245.583,765.824 248.836,773.292 248.836,782.683C248.836,789.585 247.138,795.638 243.744,800.843C240.35,806.048 235.654,809.782 229.657,812.045C236.785,814.081 242.217,817.589 245.95,822.567Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,654.23,1827.73)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.431,112.072L785.431,338.667L1220.96,338.667L1220.96,112.072L785.431,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,728.341,1440.45)">

+            <path d="M258.34,836.315L258.34,847.856L240.01,847.856L240.01,874.163L226.093,874.163L226.093,847.856L170.425,847.856L170.425,837.333L228.639,753.321L240.01,753.321L240.01,836.315L258.34,836.315ZM184.851,836.315L226.093,836.315L226.093,776.913L184.851,836.315Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,284.446,1827.73)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.432,112.072L785.432,338.667L1220.96,338.667L1220.96,112.072L785.432,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,358.557,1440.45)">

+            <path d="M224.566,862.452L251.212,862.452L251.212,874.163L183.833,874.163L183.833,862.452L210.479,862.452L210.479,770.633L185.7,786.417L185.7,773.009L216.589,753.321L224.566,753.321L224.566,862.452Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,779.778,1828.36)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.431,112.072L785.431,338.667L1220.96,338.667L1220.96,112.072L785.431,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,855.05,1441.43)">

+            <path d="M238.058,803.134C243.772,806.359 248.157,810.857 251.212,816.627C254.267,822.398 255.794,829.073 255.794,836.654C255.794,844.235 254.125,850.967 250.787,856.851C247.45,862.735 242.697,867.289 236.531,870.514C230.364,873.738 223.151,875.351 214.891,875.351C207.537,875.351 200.296,874.021 193.167,871.362C186.039,868.703 180.042,865.054 175.177,860.415L180.438,849.723C191.64,859.001 203.124,863.64 214.891,863.64C223.378,863.64 230.025,861.236 234.834,856.427C239.642,851.618 242.047,845.084 242.047,836.824C242.047,828.791 239.671,822.313 234.919,817.391C230.166,812.469 223.83,810.008 215.91,810.008C204.369,810.008 195.147,814.704 188.245,824.095L178.571,824.095L178.571,753.321L251.042,753.321L251.042,764.862L192.488,764.862L192.488,807.972C199.164,801.522 207.707,798.297 218.116,798.297C225.697,798.297 232.344,799.91 238.058,803.134Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,913.042,1828.36)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.431,112.072L785.431,338.667L1220.96,338.667L1220.96,112.072L785.431,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,985.864,1441.44)">

+            <path d="M237.719,803.134C243.433,806.359 247.874,810.885 251.042,816.712C254.21,822.539 255.794,829.187 255.794,836.654C255.794,844.122 254.125,850.798 250.787,856.681C247.45,862.565 242.839,867.176 236.955,870.514C231.072,873.851 224.396,875.52 216.928,875.52C202.332,875.52 191.074,870.429 183.154,860.245C175.233,850.062 171.273,835.579 171.273,816.797C171.273,803.219 173.112,791.565 176.789,781.835C180.466,772.104 185.784,764.693 192.743,759.601C199.701,754.509 208.046,751.964 217.777,751.964C224.792,751.964 231.609,753.265 238.228,755.867C244.847,758.47 250.646,762.147 255.624,766.899L250.363,777.592C244.706,772.839 239.275,769.332 234.07,767.069C228.865,764.806 223.547,763.674 218.116,763.674C207.707,763.674 199.617,768.313 193.846,777.592C188.076,786.87 185.19,799.881 185.19,816.627L185.19,819.173C187.793,812.724 192.036,807.632 197.919,803.898C203.803,800.164 210.535,798.297 218.116,798.297C225.471,798.297 232.005,799.91 237.719,803.134ZM234.919,856.427C239.671,851.505 242.047,844.971 242.047,836.824C242.047,828.791 239.642,822.313 234.834,817.391C230.025,812.469 223.774,810.008 216.08,810.008C208.159,810.008 201.71,812.497 196.731,817.476C191.753,822.454 189.264,828.904 189.264,836.824C189.264,844.857 191.753,851.363 196.731,856.342C201.71,861.32 208.216,863.81 216.249,863.81C223.943,863.81 230.166,861.349 234.919,856.427Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,1043.49,1828.36)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.43,112.072L785.43,338.667L1220.96,338.667L1220.96,112.072L785.43,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,1116.31,1441.44)">

+            <path d="M173.14,753.321L252.909,753.321L252.909,763.674L196.222,874.163L181.287,874.163L237.634,765.032L173.14,765.032L173.14,753.321Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,1174.2,1828.36)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.431,112.072L785.431,338.667L1220.96,338.667L1220.96,112.072L785.431,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,1247.02,1441.44)">

+            <path d="M249.769,823.162C254.125,828.423 256.303,834.731 256.303,842.085C256.303,852.382 252.4,860.5 244.593,866.44C236.785,872.381 226.263,875.351 213.025,875.351C199.786,875.351 189.264,872.381 181.457,866.44C173.649,860.5 169.746,852.382 169.746,842.085C169.746,834.731 171.98,828.395 176.45,823.077C180.919,817.759 187.057,814.081 194.864,812.045C187.623,809.895 182.079,806.359 178.232,801.437C174.385,796.515 172.461,790.717 172.461,784.041C172.461,777.592 174.159,771.962 177.553,767.154C180.947,762.345 185.728,758.611 191.894,755.952C198.061,753.293 205.104,751.964 213.025,751.964C220.945,751.964 227.988,753.293 234.155,755.952C240.321,758.611 245.102,762.345 248.496,767.154C251.891,771.962 253.588,777.592 253.588,784.041C253.588,790.717 251.636,796.515 247.732,801.437C243.829,806.359 238.37,809.895 231.354,812.045C239.275,814.195 245.413,817.9 249.769,823.162ZM193.592,800.758C198.4,804.775 204.878,807.236 213.025,808.141C221.171,807.236 227.649,804.775 232.458,800.758C237.266,796.742 239.671,791.509 239.671,785.059C239.671,778.384 237.323,773.122 232.627,769.275C227.932,765.428 221.397,763.505 213.025,763.505C204.652,763.505 198.117,765.428 193.422,769.275C188.726,773.122 186.378,778.384 186.378,785.059C186.378,791.509 188.783,796.742 193.592,800.758ZM234.919,858.039C240.01,854.192 242.556,848.591 242.556,841.237C242.556,834.561 239.869,829.215 234.494,825.198C229.12,821.181 221.963,818.72 213.025,817.815C204.086,818.72 196.929,821.181 191.555,825.198C186.18,829.215 183.493,834.561 183.493,841.237C183.493,848.591 186.039,854.192 191.131,858.039C196.222,861.886 203.52,863.81 213.025,863.81C222.529,863.81 229.827,861.886 234.919,858.039Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(0.203003,0,0,0.454823,1310.06,1828.36)">

+            <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+            <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM785.431,112.072L785.431,338.667L1220.96,338.667L1220.96,112.072L785.431,112.072Z"/>

+        </g>

+        <g transform="matrix(0.601453,0,0,0.601453,1382.88,1441.44)">

+            <path d="M243.065,767.239C250.985,777.422 254.946,791.905 254.946,810.687C254.946,831.167 250.844,847.092 242.641,858.463C234.438,869.835 222.982,875.52 208.272,875.52C201.37,875.52 194.61,874.219 187.991,871.617C181.372,869.014 175.516,865.337 170.425,860.585L175.856,849.893C181.626,854.758 187.114,858.294 192.319,860.5C197.523,862.706 202.785,863.81 208.103,863.81C218.512,863.81 226.574,859.171 232.288,849.893C238.002,840.614 240.859,827.603 240.859,810.857L240.859,808.65C238.256,814.987 234.013,819.993 228.13,823.671C222.246,827.348 215.514,829.187 207.933,829.187C200.578,829.187 194.072,827.574 188.415,824.35C182.758,821.125 178.345,816.599 175.177,810.772C172.009,804.945 170.425,798.297 170.425,790.83C170.425,783.362 172.094,776.686 175.431,770.803C178.769,764.919 183.38,760.308 189.264,756.97C195.147,753.633 201.823,751.964 209.291,751.964C223.887,751.964 235.145,757.055 243.065,767.239ZM229.487,810.008C234.466,805.03 236.955,798.58 236.955,790.66C236.955,782.627 234.466,776.121 229.487,771.142C224.509,766.164 218.003,763.674 209.97,763.674C202.276,763.674 196.052,766.135 191.3,771.057C186.548,775.979 184.172,782.513 184.172,790.66C184.172,798.693 186.548,805.171 191.3,810.093C196.052,815.015 202.332,817.476 210.139,817.476C218.06,817.476 224.509,814.987 229.487,810.008Z" style="fill:rgb(242,242,242);fill-rule:nonzero;"/>

+        </g>

+        <g transform="matrix(1.12416,0,0,0.562078,203.296,970.539)">

+            <path d="M253.227,1575.22L253.227,1607.45" style="fill:none;stroke:black;stroke-width:5.95px;"/>

+        </g>

+        <g transform="matrix(1,0,0,1,327.452,-60.2647)">

+            <path d="M657.203,1916.2L160.511,1916.2" style="fill:none;stroke:black;stroke-width:5.28px;"/>

+        </g>

+        <g transform="matrix(1.12416,0,0,0.562078,203.296,970.539)">

+            <path d="M366.126,1575.22L366.126,1607.45" style="fill:none;stroke:black;stroke-width:5.95px;"/>

+        </g>

+        <g transform="matrix(1.12416,0,0,0.562078,203.296,970.539)">

+            <path d="M472.919,1575.22L472.919,1607.45" style="fill:none;stroke:black;stroke-width:5.95px;"/>

+        </g>

+        <g transform="matrix(1.12416,0,0,0.562078,203.296,970.539)">

+            <path d="M582.288,1575.22L582.288,1607.45" style="fill:none;stroke:black;stroke-width:5.95px;"/>

+        </g>

+        <g transform="matrix(1.11822,0,0,1.12416,210.208,67.0263)">

+            <path d="M691.478,1575.22L691.478,1591.33L1163.66,1591.33L1163.66,1607.45" style="fill:none;stroke:black;stroke-width:4.71px;"/>

+        </g>

+        <g transform="matrix(1.12416,0,0,1.12416,203.296,67.0263)">

+            <path d="M1042.22,1591.33L1042.22,1607.45" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+        </g>

+        <g transform="matrix(1.12416,0,0,1.12416,203.296,67.0263)">

+            <path d="M927.57,1591.33L927.57,1607.45" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+        </g>

+        <g transform="matrix(1.12416,0,0,1.12416,203.296,67.0263)">

+            <path d="M812.587,1591.33L812.587,1607.45" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+        </g>

+    </g>

+    <g transform="matrix(1.17016,0,0,1.17016,-234.903,-166.612)">

+        <path d="M1120.2,802.778L1120.2,859.94" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.576838,-234.903,343.611)">

+        <path d="M1294.85,802.778L1294.85,859.94" style="fill:none;stroke:black;stroke-width:5.96px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.537752,-233.077,374.989)">

+        <path d="M1552.85,802.778L1552.85,859.94" style="fill:none;stroke:black;stroke-width:6.04px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,1.17016,-233.077,-168.846)">

+        <path d="M1729.39,859.94L1729.39,802.778" style="fill:none;stroke:black;stroke-width:4.7px;"/>

+    </g>

+    <g transform="matrix(1.17016,0,0,0.537752,-233.077,374.989)">

+        <path d="M1909.1,859.94L1909.1,802.778" style="fill:none;stroke:black;stroke-width:6.04px;"/>

+    </g>

+    <g transform="matrix(-0.849549,0,0,0.561845,1662.41,418.175)">

+        <path d="M928.049,750L929.086,691.489" style="fill:none;stroke:black;stroke-width:7.64px;"/>

+    </g>

+    <g transform="matrix(0.921744,0,0,0.921744,1374.93,-23.3561)">

+        <g transform="matrix(0.160763,0,0,0.360187,182.349,102.289)">

+            <g>

+                <g>

+                    <rect x="759.403" y="100.455" width="487.587" height="249.829" style="fill:rgb(0,168,138);"/>

+                    <path d="M1246.99,350.284L759.403,350.284L759.403,100.455L1246.99,100.455L1246.99,350.284ZM796.52,117.021L796.52,333.718L1209.87,333.718L1209.87,117.021L796.52,117.021Z"/>

+                </g>

+            </g>

+        </g>

+        <g transform="matrix(0.353176,0,0,0.353176,612.173,-130.648)">

+            <path d="M-499.304,862.116L-499.304,872.808L-582.806,872.808L-582.806,862.116L-499.304,862.116ZM-499.304,896.399L-499.304,907.092L-582.806,907.092L-582.806,896.399L-499.304,896.399Z" style="fill-rule:nonzero;"/>

+            <path d="M-409.097,927.288C-417.979,922.197 -424.796,914.984 -429.548,905.649C-434.301,896.314 -436.677,885.367 -436.677,872.808C-436.677,860.362 -434.301,849.471 -429.548,840.137C-424.796,830.802 -417.979,823.617 -409.097,818.582C-400.215,813.547 -389.834,811.03 -377.953,811.03C-369.807,811.03 -362.141,812.303 -354.956,814.848C-347.771,817.394 -341.803,820.93 -337.051,825.456L-344.179,841.41C-349.61,836.997 -355.013,833.8 -360.387,831.82C-365.762,829.84 -371.504,828.85 -377.614,828.85C-389.268,828.85 -398.292,832.641 -404.684,840.222C-411.077,847.802 -414.274,858.665 -414.274,872.808C-414.274,887.064 -411.105,898.011 -404.769,905.649C-398.433,913.286 -389.381,917.105 -377.614,917.105C-371.504,917.105 -365.762,916.115 -360.387,914.135C-355.013,912.155 -349.61,908.958 -344.179,904.546L-337.051,920.499C-341.803,925.025 -347.771,928.561 -354.956,931.107C-362.141,933.653 -369.807,934.926 -377.953,934.926C-389.834,934.926 -400.215,932.38 -409.097,927.288Z" style="fill-rule:nonzero;"/>

+            <path d="M-303.87,929.325C-310.489,925.704 -315.581,920.528 -319.145,913.796C-322.709,907.063 -324.491,899.171 -324.491,890.119C-324.491,881.068 -322.709,873.176 -319.145,866.443C-315.581,859.711 -310.489,854.535 -303.87,850.914C-297.251,847.293 -289.585,845.483 -280.873,845.483C-272.274,845.483 -264.693,847.293 -258.131,850.914C-251.568,854.535 -246.505,859.711 -242.941,866.443C-239.376,873.176 -237.594,881.068 -237.594,890.119C-237.594,899.171 -239.376,907.063 -242.941,913.796C-246.505,920.528 -251.568,925.704 -258.131,929.325C-264.693,932.946 -272.274,934.756 -280.873,934.756C-289.585,934.756 -297.251,932.946 -303.87,929.325ZM-264.495,911.08C-260.705,906.384 -258.809,899.398 -258.809,890.119C-258.809,880.955 -260.733,873.968 -264.58,869.159C-268.427,864.35 -273.858,861.946 -280.873,861.946C-288.001,861.946 -293.489,864.35 -297.336,869.159C-301.183,873.968 -303.107,880.955 -303.107,890.119C-303.107,899.398 -301.211,906.384 -297.421,911.08C-293.63,915.776 -288.171,918.123 -281.043,918.123C-273.801,918.123 -268.286,915.776 -264.495,911.08Z" style="fill-rule:nonzero;"/>

+            <path d="M-139.496,880.785L-139.496,933.398L-160.711,933.398L-160.711,881.803C-160.711,875.014 -162.012,870.064 -164.614,866.953C-167.217,863.841 -171.234,862.285 -176.665,862.285C-183.114,862.285 -188.319,864.35 -192.279,868.48C-196.239,872.61 -198.219,878.069 -198.219,884.858L-198.219,933.398L-219.265,933.398L-219.265,871.959C-219.265,862.908 -219.717,854.818 -220.622,847.689L-200.765,847.689L-199.237,861.776C-196.296,856.571 -192.307,852.555 -187.272,849.726C-182.237,846.897 -176.551,845.483 -170.215,845.483C-149.736,845.483 -139.496,857.25 -139.496,880.785Z" style="fill-rule:nonzero;"/>

+            <path d="M-89.937,863.643L-89.937,902C-89.937,912.07 -85.242,917.105 -75.851,917.105C-73.248,917.105 -70.419,916.652 -67.364,915.747L-67.364,932.55C-71.098,933.907 -75.624,934.586 -80.942,934.586C-90.673,934.586 -98.141,931.871 -103.345,926.44C-108.55,921.009 -111.152,913.201 -111.152,903.018L-111.152,863.643L-127.615,863.643L-127.615,847.689L-111.152,847.689L-111.152,826.814L-89.937,819.685L-89.937,847.689L-67.195,847.689L-67.195,863.643L-89.937,863.643Z" style="fill-rule:nonzero;"/>

+            <path d="M22.418,891.647L-36.645,891.647C-36.192,900.812 -33.901,907.572 -29.771,911.929C-25.641,916.285 -19.503,918.463 -11.357,918.463C-1.965,918.463 6.747,915.408 14.78,909.298L20.89,923.894C16.817,927.175 11.81,929.806 5.87,931.786C-0.07,933.766 -6.095,934.756 -12.205,934.756C-26.236,934.756 -37.267,930.796 -45.301,922.876C-53.334,914.955 -57.351,904.093 -57.351,890.289C-57.351,881.577 -55.597,873.826 -52.09,867.037C-48.582,860.249 -43.66,854.959 -37.324,851.169C-30.988,847.378 -23.803,845.483 -15.769,845.483C-4.002,845.483 5.304,849.302 12.15,856.939C18.995,864.577 22.418,875.071 22.418,888.422L22.418,891.647ZM-29.092,865.765C-32.657,869.102 -34.948,873.939 -35.966,880.276L3.918,880.276C3.239,873.826 1.288,868.961 -1.937,865.68C-5.162,862.398 -9.603,860.758 -15.26,860.758C-20.918,860.758 -25.528,862.427 -29.092,865.765Z" style="fill-rule:nonzero;"/>

+            <path d="M120.177,880.785L120.177,933.398L98.962,933.398L98.962,881.803C98.962,875.014 97.661,870.064 95.058,866.953C92.456,863.841 88.439,862.285 83.008,862.285C76.559,862.285 71.354,864.35 67.394,868.48C63.434,872.61 61.454,878.069 61.454,884.858L61.454,933.398L40.408,933.398L40.408,871.959C40.408,862.908 39.956,854.818 39.05,847.689L58.908,847.689L60.435,861.776C63.377,856.571 67.365,852.555 72.4,849.726C77.436,846.897 83.121,845.483 89.457,845.483C109.937,845.483 120.177,857.25 120.177,880.785Z" style="fill-rule:nonzero;"/>

+            <path d="M169.735,863.643L169.735,902C169.735,912.07 174.431,917.105 183.822,917.105C186.425,917.105 189.253,916.652 192.308,915.747L192.308,932.55C188.574,933.907 184.048,934.586 178.731,934.586C169,934.586 161.532,931.871 156.327,926.44C151.123,921.009 148.52,913.201 148.52,903.018L148.52,863.643L132.057,863.643L132.057,847.689L148.52,847.689L148.52,826.814L169.735,819.685L169.735,847.689L192.478,847.689L192.478,863.643L169.735,863.643Z" style="fill-rule:nonzero;"/>

+            <path d="M255.105,812.557L307.549,812.557C320.56,812.557 330.687,815.697 337.929,821.977C345.17,828.256 348.791,836.827 348.791,847.689C348.791,858.551 345.142,867.151 337.844,873.487C330.546,879.823 320.447,882.991 307.549,882.991L276.999,882.991L276.999,933.398L255.105,933.398L255.105,812.557ZM305.003,866.019C312.584,866.019 318.326,864.463 322.229,861.352C326.133,858.24 328.085,853.743 328.085,847.859C328.085,841.862 326.161,837.308 322.314,834.197C318.467,831.085 312.697,829.529 305.003,829.529L276.999,829.529L276.999,866.019L305.003,866.019Z" style="fill-rule:nonzero;"/>

+            <path d="M445.362,847.689L445.362,933.398L424.486,933.398L424.486,919.651C421.884,924.403 418.15,928.109 413.284,930.768C408.419,933.427 402.875,934.756 396.652,934.756C389.184,934.756 382.565,932.946 376.795,929.325C371.024,925.704 366.555,920.556 363.387,913.88C360.218,907.205 358.634,899.454 358.634,890.629C358.634,881.803 360.247,873.968 363.471,867.122C366.696,860.277 371.194,854.959 376.964,851.169C382.735,847.378 389.297,845.483 396.652,845.483C402.875,845.483 408.419,846.812 413.284,849.471C418.15,852.13 421.884,855.836 424.486,860.588L424.486,847.689L445.362,847.689ZM418.716,910.825C422.563,905.96 424.486,899.115 424.486,890.289C424.486,881.237 422.563,874.279 418.716,869.414C414.869,864.548 409.381,862.116 402.253,862.116C395.238,862.116 389.778,864.633 385.875,869.668C381.971,874.703 380.019,881.69 380.019,890.629C380.019,899.454 381.971,906.243 385.875,910.995C389.778,915.747 395.294,918.123 402.422,918.123C409.437,918.123 414.869,915.691 418.716,910.825Z" style="fill-rule:nonzero;"/>

+            <path d="M551.267,847.689L551.267,930.683C551.267,944.034 547.59,954.161 540.236,961.063C532.881,967.965 522.075,971.416 507.819,971.416C494.581,971.416 482.927,968.644 472.856,963.099L476.251,946.976C486.66,952.407 497.013,955.122 507.31,955.122C522.585,955.122 530.222,947.542 530.222,932.38L530.222,915.408C527.62,920.047 523.829,923.809 518.851,926.694C513.872,929.58 508.271,931.022 502.048,931.022C494.581,931.022 487.933,929.24 482.106,925.676C476.279,922.112 471.753,917.077 468.529,910.571C465.304,904.065 463.692,896.625 463.692,888.253C463.692,879.88 465.304,872.44 468.529,865.934C471.753,859.428 476.279,854.393 482.106,850.829C487.933,847.265 494.581,845.483 502.048,845.483C508.385,845.483 514.014,846.812 518.936,849.471C523.858,852.13 527.62,855.836 530.222,860.588L530.222,847.689L551.267,847.689ZM524.197,907.431C528.214,902.792 530.222,896.399 530.222,888.253C530.222,880.106 528.242,873.713 524.282,869.074C520.322,864.435 514.777,862.116 507.649,862.116C500.634,862.116 495.118,864.435 491.101,869.074C487.085,873.713 485.076,880.106 485.076,888.253C485.076,896.399 487.085,902.792 491.101,907.431C495.118,912.07 500.634,914.39 507.649,914.39C514.664,914.39 520.18,912.07 524.197,907.431Z" style="fill-rule:nonzero;"/>

+            <path d="M649.196,891.647L590.133,891.647C590.586,900.812 592.877,907.572 597.007,911.929C601.137,916.285 607.275,918.463 615.422,918.463C624.813,918.463 633.525,915.408 641.559,909.298L647.669,923.894C643.595,927.175 638.589,929.806 632.648,931.786C626.708,933.766 620.683,934.756 614.573,934.756C600.543,934.756 589.511,930.796 581.478,922.876C573.444,914.955 569.428,904.093 569.428,890.289C569.428,881.577 571.181,873.826 574.689,867.037C578.196,860.249 583.118,854.959 589.455,851.169C595.791,847.378 602.976,845.483 611.009,845.483C622.776,845.483 632.083,849.302 638.928,856.939C645.774,864.577 649.196,875.071 649.196,888.422L649.196,891.647ZM597.686,865.765C594.122,869.102 591.831,873.939 590.812,880.276L630.697,880.276C630.018,873.826 628.066,868.961 624.841,865.68C621.617,862.398 617.176,860.758 611.518,860.758C605.861,860.758 601.25,862.427 597.686,865.765Z" style="fill-rule:nonzero;"/>

+        </g>

+    </g>

+    <g transform="matrix(1,0,0,1,28.2875,0)">

+        <path d="M845.696,806.684L1049.45,806.684" style="fill:none;stroke:black;stroke-width:5.5px;"/>

+    </g>

+    <g transform="matrix(1,0,0,1,28.2875,0)">

+        <path d="M1049.45,806.684L1252,806.684" style="fill:none;stroke:black;stroke-width:5.5px;"/>

+    </g>

+    <g transform="matrix(1,0,0,1,28.2875,0)">

+        <path d="M1555.72,806.684L1764.49,803.979L1972.59,806.684" style="fill:none;stroke:black;stroke-width:5.5px;"/>

+    </g>

+    <g transform="matrix(1,0,0,1,28.2875,0)">

+        <path d="M127.118,803.979L335.044,803.979L544.651,806.684" style="fill:none;stroke:black;stroke-width:5.5px;"/>

+    </g>

+</svg>

binary files /dev/null b/static/img/jonbeebe.net-thumbnail.png differ

binary files /dev/null b/static/quickstart/bookshelf-bleak-theme.png differ

binary files /dev/null b/static/quickstart/bookshelf-disqus.png differ

binary files /dev/null b/static/quickstart/bookshelf-new-default-image.png differ

binary files /dev/null b/static/quickstart/bookshelf-only-picture.png differ

binary files /dev/null b/static/quickstart/bookshelf-robust-theme.png differ

binary files /dev/null b/static/quickstart/bookshelf-updated-config.png differ

binary files /dev/null b/static/quickstart/bookshelf.png differ

binary files /dev/null b/static/quickstart/default.jpg differ

binary files /dev/null b/static/quickstart/gh-pages-ui.png differ