Start new callout styles

2026-08-24 15:28:54 +00:00 · 2017-02-15 10:09:30 -08:00
parent 16b16216e9
commit 5851f4b6a1
117 changed files with 838 additions and 230 deletions
@@ -78,7 +78,8 @@ watch = true
  ## Gh repo for site footer
  ghrepo = "https://github.com/spf13/hugo/"
  ## GitHub Docs Repository Base URL (include trailing slash)
-  ghdocsrepo = "https://github.com/rdwatters/hugo-docs-concept/"
+  # ghdocsrepo = "https://github.com/rdwatters/hugo-docs-concept/"
+  ghdocsrepo = ""
  ## Github Wiki for Documentation
  ghdocswiki = ""
  ## Github Wiki for Development
@@ -15,22 +15,11 @@ notes:

 ## What is Hugo?

-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
-your content. Since websites are viewed far more often than they are
-edited, Hugo is optimized for website viewing for the end users of your site and an ideal writing experience for authors.
+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 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 authors.

-Sites built with Hugo are extremely fast and secure. Hugo sites can
-be hosted anywhere, including [Heroku][], [GoDaddy][], [DreamHost][],
-[GitHub Pages][], [Surge][], [Aerobatic][], [Firebase Hosting][],
-[Google Cloud Storage][], [Amazon S3][], 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.
+Websites built with Hugo are extremely fast and secure. Hugo sites can be hosted anywhere, including [Heroku][], [GoDaddy][], [DreamHost][], [GitHub Pages][], [Surge][], [Aerobatic][], [Firebase][], [Google Cloud Storage][], [Amazon S3][], 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 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.
+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, which is essential when you are designing websites and creating content.

 ## How Fast is Hugo?

@@ -39,38 +28,26 @@ designing websites, but also very useful when creating content.

 ## 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.
+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 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 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 website, or a website with thousands of
-pages.
-
-## See Also
-
-* [Hugo Performance Benchmark(@bep)]
+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.

 [Aerobatic]: https://www.aerobatic.com/
 [Amazon S3]: http://aws.amazon.com/s3/
 [CloudFront]: http://aws.amazon.com/cloudfront/ "Amazon CloudFront"
 [DreamHost]: http://www.dreamhost.com/
-[Firebase Hosting]: https://firebase.google.com/docs/hosting/
+[Firebase]: https://firebase.google.com/docs/hosting/ "Firebase static hosting"
 [GitHub Pages]: https://pages.github.com/
 [GitLab]: https://about.gitlab.com
-[Go language]: http://golang.org/ "The Go Programming Language"
-[GoDaddy]: https://www.godaddy.com/
+[GoDaddy]: https://www.godaddy.com/ "Godaddy.com Hosting"
 [Google Cloud Storage]: http://cloud.google.com/storage/
 [Heroku]: https://www.heroku.com/
-[Hugo Performance Benchmark(@bep)]: https://github.com/bep/hugo-benchmark
 [Jekyll]: http://jekyllrb.com/
 [Middleman]: https://middlemanapp.com/
 [Nanoc]: http://nanoc.ws/
@@ -14,7 +14,7 @@ notes:

 ## General

-* Extremely fast build times (&lt; .7 ms per page)
+* [Extremely fast][] build times (&lt; .7 ms per page)
 * Completely cross platform, with easy installation on [Mac OSX][], [Linux][], [Windows][], and more
 * Renders changes on the fly with [LiveReload][] as you develop
 * [Powerful theming][]
@@ -55,12 +55,13 @@ See what's coming next in the [Hugo roadmap][].

 ["Minutes to Read"]: /variables-and-params/
 ["Wordcount"]: /variables-and-params/
-[Ace]: https://github.com/yosssi/ace
+[Ace]: /templates/ace-templating/
 [aliases]: /content-management/url-management/#aliases
 [Amber]: https://github.com/eknkc/amber
 [content summaries]: /content-management/content-summaries/
 [content types]: /content-management/content-types/
 [Disqus]: https://disqus.com/
+[Extremely fast]: https://github.com/bep/hugo-benchmark
 [front matter]: /content-management/front-matter/
 [functions]: /functions/
 [Golang]: http://golang.org/pkg/html/template/
@@ -1,6 +1,6 @@
 ---
-title: "Introduction: Content Organization"
-linktitle: "Introduction"
+title: "Overview"
+linktitle: "Overview"
 description: Content organization, summaries, archetypes, front matter, and supported formats.
 date: 2017-02-01
 publishdate: 2017-02-01
@@ -14,7 +14,7 @@ aliases: []
 notes:
 ---

-**Archetypes** are content files in the [archetypes directory][] of your project that contain pre-configured [front matter][] for your site's [content types][]. Archetypes facilitate consistent metadata in your website's content and allow content authors to quickly generate instances of a content type via the `hugo new` command.
+**Archetypes** are content files in the [archetypes directory][] of your project that contain pre-configured [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.

 Hugo's generator 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:

@@ -31,10 +31,10 @@ hugo new posts/my-first-post.md
 {{% /input %}}

 {{% note "Override Content Type in a New File" %}}
-To override the content type Hugo infers from `[content-section]`, you can include the `--kind` flag at the end of the `hugo new` command.
+To override the content type Hugo infers from `[content-section]`, add the `--kind` flag to the end of the `hugo new` command.
 {{% /note %}}

-If you were to run this command in a new site that does not contain any default or custom archetypes, Hugo will create the following file.
+Running this command in a new site that does not have default or custom archetypes will create the following file:

 {{% output "content/posts/my-first-post.md" %}}
 ```toml
@@ -45,15 +45,15 @@ title: my first post
 ```
 {{% /output %}}

-Note that if you do not already have a `posts` directory in `content`, Hugo will create both `content/posts/` and `content/posts/my-first-post.md`.
+Note that if you do not already have a `posts` directory, Hugo will create both `content/posts/` and `content/posts/my-first-post.md`.

-`date` and `title` are the key-values that ship with Hugo and are therefore included in *all* content files created with the Hugo CLI. `title` is generated from the new content's filename. `date` is generated in [RFC 3339 format][] by way of Golang's [`now()`][] function, which returns the current time.
+`date` and `title` are the variables that ship with Hugo and are therefore included in *all* content files created with the Hugo CLI. `title` is generated from the new content's filename. `date` is generated in [RFC 3339 format][] by way of Golang's [`now()`][] function, which returns the current time.

-Two key-values are often not enough for effective content management of larger websites. As such, Hugo provides a simple mechanism for extending these key-values through default and custom archetypes.
+Two 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 default and custom archetypes.

 ## Lookup Order for Archetypes

-Similar to the lookup order for [templates in the layouts folder][], Hugo looks for a default file before falling back on the base/internal archetype. For the `my-first-post.md` example, Hugo looks for the new content's archetype file in the following order:
+Similar to the lookup order for [templates in the `layouts` directory][], Hugo looks for a default file before falling back on the base/internal archetype. For the `my-first-post.md` example, Hugo looks for the new content's archetype file in the following order:

 1. `archetypes/posts.md`
 2. `archetypes/default.md`
@@ -172,5 +172,5 @@ title = post from custom
 [front matter]: /content-management/front-matter/
 [RFC 3339 format]: https://www.ietf.org/rfc/rfc3339.txt
 [taxonomies]: /content-management/taxonomies/
-[templates in the layouts folder]: /templates/base-templates-and-blocks/
+[templates in the `layouts` directory]: /templates/base-templates-and-blocks/
 [templates]: /templates/
@@ -5,7 +5,7 @@ description:
 date: 2017-02-01
 publishdate: 2017-02-01
 lastmod: 2017-02-01
-tags: []
+tags: [lists,sections,content,types,organization]
 weight: 30
 draft: false
 slug:
@@ -13,4 +13,50 @@ aliases: [/content-management/sections,/content/sections/]
 notes:
 ---

+## Content Organization
+
+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 [example site][] used throughout the Hugo docs includes three sections: "authors," "events," and "posts":
+
+```bash
+./content
+    |—–authors
+        |––_index.md
+        |––jon-doe.md
+        |––jane-doe.md
+    |––events
+        |––_index.md
+        |––event-1.md
+        |––event-2.md
+        |––event-3.md
+    |––posts
+        |--_index.md
+        |––post-1.md
+        |––post-2.md
+        |––post-3.md
+        |––post-4.md
+        |––post-5.md
+```
+
+## Content Section Lists
+
+Hugo will automatically create pages for each section root that list all of the content in that section. See [List and Section Page 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` in a content section as a workaround to emulate the behavior of `_index.md`. The workaround works...*sometimes*. The order of page rendering can be unpredictable in Hugo. What works now may fail to render appropriately once you begin adding more content to your site. It is *strongly advised* to use the *preferred* content section organization and `_index.md`.
+{{% /warning %}}
+
+## Content Section and Content Types
+
+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 and if using an [archetype][] will generate front matter according to `archetypes/posts.md`.
+
+[archetype]: /content-management/archetypes/
+[example site]: /getting-started/
+[directory structure]: /project-organization/directory-structure/
+

@@ -5,11 +5,22 @@ description:
 date: 2017-02-01
 publishdate: 2017-02-01
 lastmod: 2017-02-01
-tags: []
+tags: [lists,sections,content,types,organization]
 categories: []
 weight: 40
 draft: false
 slug:
 aliases: [/content/types]
 notes:
---
+---
+
+Hugo provides full support for content types. 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 content [archetypes][].
+
+
+
+
+
+
+[archetypes]: /content-management/archetypes/
+[front matter]: /content-management/front-matter/
+[template]: /templates/
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -1,10 +1,10 @@
 ---
-title: Quick Reference
-linktitle: Quick Reference
+title: Overview
+linktitle: Overview
 description: Comprehensive list of Hugo templating functions, including basic and advanced usage examples.
-date: 2017-01-09
-publishdate: 2017-01-09
-lastmod: 2017-01-09
+date: 2017-02-01
+publishdate: 2017-02-01
+lastmod: 2017-02-01
 tags: [functions,templating]
 weight: 01
 draft: false
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -14,4 +14,8 @@ layout:
 slug:
 aliases: []
 notes:
---
+---
+
+## Example
+
+## Advanced Example
@@ -14,3 +14,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -13,3 +13,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -16,4 +16,6 @@ aliases: []
 notes:
 ---

-Here is some content for the `index` function.
+## Example
+
+## Advanced Example
@@ -16,3 +16,8 @@ aliases: []
 tags: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -8,12 +8,15 @@ date: 2017-02-01
 publishdate: 2017-02-01
 lastmod: 2017-02-01
 categories: [fundamentals]
-tags: []
+tags: [iteration]
 weight:
 draft: false
-type:
-layout:
 slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -13,3 +13,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -13,3 +13,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -13,3 +13,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -13,3 +13,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,7 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -15,3 +15,8 @@ slug:
 aliases: []
 notes:
 ---
+
+## Example
+
+## Advanced Example
+
@@ -16,4 +16,9 @@ aliases: []
 notes:
 ---

+## Example
+
+## Advanced Example
+
+
 Here is just some content testing for the where function.
@@ -1,6 +1,6 @@
 ---
-title: How to Use the Hugo Docs
-linktitle: How to Use the Hugo Docs
+title: Using the Docs
+linktitle: Using the Docs
 description: Quick start and guides for installing Hugo on your preferred operating system.
 date: 2017-02-01
 publishdate: 2017-02-01
@@ -1,5 +1,5 @@
 ---
-title: Building Your Static Site
+title: Overview
 linktitle:
 description: Site builds, automated deployments, and popular hosting solutions.
 date: 2016-11-01
@@ -1,18 +0,0 @@
---
-title: Migrating to Hugo
-linktitle:
-description: Tools and tutorials for migrating to Hugo from other platforms or generators (eg, Wordpress, Jekyll).
-date: 2017-02-01
-publishdate: 2017-02-01
-lastmod: 2017-02-01
-tags: []
-categories: []
-weight: 01
-draft: false
-slug:
-aliases: []
-notes:
---
-
-
-
@@ -1,5 +1,5 @@
 ---
-title: News and Articles
+title: Overview
 linktitle:
 description: Articles where Hugo is featured, as well as news and updates on the project itself.
 date: 2017-02-01
@@ -1,5 +1,5 @@
 ---
-title: New Website Scaffolding
+title: Overview
 linktitle:
 description: Scaffolding new projects, configuration, and source organization.
 date: 2016-11-01
@@ -5,6 +5,8 @@ description: Explanation of the directory structure in a typical Hugo project an
 date: 2017-01-02
 publishdate: 2017-01-02
 lastmod: 2017-01-02
+categories: [project organization]
+tags: [source, organization, directories]
 weight: 10
 draft: false
 slug:
@@ -1,6 +1,6 @@
 ---
-title: Introduction to Hugo Templating
-linktitle:
+title: Overview
+linktitle: Overview
 description: Golang templating, template types and lookup order, shortcodes, and data.
 date: 2017-02-01
 publishdate: 2017-02-01
@@ -0,0 +1,16 @@
+---
+title: List and Section Page Templates
+linktitle: List and Section Page Templates
+description:
+date: 2017-02-01
+publishdate: 2017-02-01
+lastmod: 2017-02-01
+weight:
+tags: [lists,sections]
+draft: false
+slug:
+aliases:[/templates/list/]
+notes:
+---
+
+## Lookup Order for List and Section Page Templates
@@ -1,16 +0,0 @@
---
-title: List Page Templates
-linktitle:
-description:
-date: 2017-02-01
-publishdate: 2017-02-01
-lastmod: 2017-02-01
-weight:
-tags: []
-draft: false
-slug:
-aliases:
-notes:
---
-
-## Lookup Order for List and Section Pages
@@ -2,10 +2,8 @@
 {{$title := .Title}}
 <main class="main">
 	<header class="content-header">
-		<h1 class="page-title">{{with .LinkTitle}}{{ . |markdownify}}{{else}}{{ .Title | markdownify }}{{end}}</h1>
-		<div class="content-header-links">
-			<a target="_blank" class="edit-link" href="{{.Site.Params.ghdocsrepo}}edit/master/content/{{.File.Path}}"><i class="icon-pencil" aria-hidden="true"></i></a>
-		</div>
+		<h1 class="page-title"><img src="{{.Site.BaseURL}}images/{{.Section}}.svg" alt="Icon for the {{.Section}} section.">{{with .LinkTitle}}{{ . |markdownify}}{{else}}{{ .Title | markdownify }}{{end}}</h1>
+		{{partial "content-header-links.html" . }}
 		{{with .Params.tags}}
 		<ul class="tags">
 			<li><i class="icon-tags"></i></li>
@@ -3,15 +3,14 @@
 <span id="page-top"></span>
 <main class="main">
 	<header class="content-header">
-		<h1 class="page-title {{.Section}}">{{ .Title | markdownify }}</h1>
-		<div class="content-header-links">
-		<a target="_blank" title="Edit {{.Title}} on GitHub" class="edit-link" href="{{.Site.Params.ghdocsrepo}}edit/master/content/{{.File.Path}}"><i class="icon-pencil" aria-hidden="true"></i></a>
-		{{- if .Params.godocref -}}
-		<a target="_blank" class="godoc-link" href="{{.Params.godocref}}" title="See the corresponding Golang Documentation for {{$title}}."><span class="godocs">GoDocs</span>
-			{{ partial "svg-icons/godoc-icon.html" .}}
-		</a>
-		{{- end -}}
+		<div class="content-section-image-wrapper">
+			<a href="{{.Site.BaseURL}}{{.Section | urlize}}">
+			<img src="{{.Site.BaseURL}}images/{{.Section | urlize}}.svg" alt="">
+			<span>{{replace (replace .Section "-" " " | title) "And" "and"}}</span>
+			</a>
 		</div>
+		<h1 class="page-title {{.Section}}">{{ .Title | markdownify }}</h1>
+		{{partial "content-header-links.html" . }}
 		{{with .Params.tags}}
 		<ul class="tags">
 			<li><i class="icon-tags"></i></li>
@@ -0,0 +1,8 @@
+<div class="content-header-links">
+	{{- if .Params.godocref -}}
+	<a target="_blank" class="tooltip godoc-link" data-tooltip="Golang Ref" href="{{.Params.godocref}}" >
+		{{ partial "svg-icons/godoc-icon.html" .}}
+	</a>
+	{{- end -}}
+	<a target="_blank" class="tooltip edit-link" data-tooltip="Edit on GitHub" href="{{.Site.Params.ghdocsrepo}}edit/master/content/{{.File.Path}}"><i class="icon-pencil" aria-hidden="true"></i></a>
+</div>
@@ -1,7 +1,7 @@
 {{ if .NextInSection }}
 <a role="button" href="{{.NextInSection.Permalink}}" class="prev-and-next-link prev-page">
 	<div>
-		<span>Prev</span>
+		<span>Previous</span>
 		<h4 class="{{.Section}}">{{.NextInSection.Title}}</h4>
 	</div>
 </a>
@@ -9,7 +9,7 @@
 	{{ with .Site.GetPage "section" .Section }}
 	<a role="button" href="{{.Permalink}}" class="prev-and-next-link prev-page">
 		<div>
-			<span>Prev</span>
+			<span>Previous</span>
 			<h4>{{ .Title }}</h4>
 		</div>
 	</a>
--- a/Show More
+++ b/Show More