Expand static dir explanation in dir structure

content/content-management/formats.md

@@ -4,7 +4,7 @@ linktitle: Formats
 description: Markdown is natively supported in Hugo and is parsed by the feature-rich and incredibly speed Blackfriday parse. Hugo also provides support for additional syntaxes (eg, Asciidoc) via external helpers.
 date: 2017-01-10
 publishdate: 2017-01-10
-lastmod: 2017-04-01
+lastmod: 2017-04-02
 categories: [content management]
 tags: [markdown,asciidoc,mmark,content format]
 menu:
@@ -80,7 +80,7 @@ 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 to act as the intermediary between your content and templating. This is one of the most powerful features in Hugo and allows you to essentially create your own markdown extensions very quickly.
+If you write in markdown and find yourself frequently embedding your content with raw HTML, Hugo provides built-in shortcode functionality to act as the intermediary between your content and templating. This is one of the most powerful features in Hugo in that is allows you to extend markdown arbitrarily and 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.
 

content/getting-started/directory-structure.md

@@ -58,7 +58,11 @@ used by Hugo when generating your website. You can write these files in YAML, JS
 : 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. Note that when Hugo build your site, all assets inside your static directory are copied over as-is.
+: 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/spf13/hugo/issues/3207)). You can solicit support from the community in the [Hugo forums](https://discuss.gohugo.io) or check out a few of the [Hugo starter kits](/tools/starter-kits/) for examples of how Hugo developers are managing these assets.
+{{% /note %}}
 
 
 [archetypes]: /content-management/archetypes/
@@ -72,7 +76,9 @@ used by Hugo when generating your website. You can write these files in YAML, JS
 [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/

content/templates/internal.md

@@ -17,7 +17,8 @@ aliases: []
 toc: true
 wip: true
 ---
-<!-- reference: https://discuss.gohugo.io/t/lookup-order-for-partials/5705/6 -->
+<!-- reference: https://discuss.gohugo.io/t/lookup-order-for-partials/5705/6
+code: https://github.com/spf13/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.