diff --git a/exampleSite/public/.gitignore b/exampleSite/public/.gitignore deleted file mode 100755 index e69de29..0000000 diff --git a/exampleSite/public/404/index.html b/exampleSite/public/404/index.html deleted file mode 100644 index e69de29..0000000 diff --git a/exampleSite/public/about-hugo/index.html b/exampleSite/public/about-hugo/index.html deleted file mode 100644 index 852bc31..0000000 --- a/exampleSite/public/about-hugo/index.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - - - - - - - - - - - - About Hugo · Hugo Themes - - - - - - - - - - - - - - - - - - - -
-
-
- -
map[]
 -
-
-
- -
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
- -
-
-
-
- - About Hugo - -
- - -
- - -

Hugo is a static site engine written in Go.

- -

It makes use of a variety of open source projects including:

- - - -

Learn more and contribute on GitHub.

- -

Setup

- -

Some fun facts about Hugo:

- -
    -
  • Built in Go
    • -
  • Loosely inspired by Jekyll
    • -
  • Primarily developed by spf13 on the train while commuting to and from Manhattan.
    • -
  • Coded in Vim using spf13-vim
    • -
- -

Have questions or suggestions? Feel free to open an issue on GitHub or ask me on Twitter.

- -

Thanks for reading!

- -
-
-
-
- - - - - - - - - - diff --git a/exampleSite/public/about-this-site/index.html b/exampleSite/public/about-this-site/index.html deleted file mode 100644 index a68e05c..0000000 --- a/exampleSite/public/about-this-site/index.html +++ /dev/null @@ -1,8 +0,0 @@ - - - - - - - - diff --git a/exampleSite/public/about/index.html b/exampleSite/public/about/index.html deleted file mode 100644 index e69de29..0000000 diff --git a/exampleSite/public/blog/index.html b/exampleSite/public/blog/index.html deleted file mode 100644 index 2669858..0000000 --- a/exampleSite/public/blog/index.html +++ /dev/null @@ -1,8 +0,0 @@ - - - - - - - - diff --git a/exampleSite/public/categories/development/index.html b/exampleSite/public/categories/development/index.html deleted file mode 100644 index 6e6ac18..0000000 --- a/exampleSite/public/categories/development/index.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - - Development · Hugo Themes - - - - - - - - - - - - - - - - - - - -
-
-
- -
map[]
 -
-
-
- -
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
- -
-
-
-
- - Development - -
- - - -
  • -
    Apr 2, 2014
    -
    (Hu)go Template Primer
     -
    • - - -
  • -
    Apr 2, 2014
    -
    Getting Started with Hugo
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/categories/development/index.xml b/exampleSite/public/categories/development/index.xml deleted file mode 100644 index de94dcd..0000000 --- a/exampleSite/public/categories/development/index.xml +++ /dev/null @@ -1,446 +0,0 @@ - - - - Development on Hugo Themes - http://localhost:1313/categories/development/ - Recent content in Development on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - (Hu)go Template Primer - http://localhost:1313/post/goisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/goisforlovers/ - - -<p>Hugo uses the excellent <a href="http://golang.org/&gt;">go</a> <a href="http://golang.org/pkg/html/template/&gt;">html/template</a> library for -its template engine. It is an extremely lightweight engine that provides a very -small amount of logic. In our experience that 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.</p> - -<p>This document is a brief primer on using go templates. The <a href="http://golang.org/pkg/html/template/&gt;">go docs</a> -provide more details.</p> - -<h2 id="introduction-to-go-templates:4d30d99f79bd431d57546bbed04b7347">Introduction to Go Templates</h2> - -<p>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.</p> - -<p>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 <a href="http://golang.org/pkg/html/template/&gt;">go docs</a>.</p> - -<h2 id="basic-syntax:4d30d99f79bd431d57546bbed04b7347">Basic Syntax</h2> - -<p>Go lang templates are html files with the addition of variables and -functions.</p> - -<p><strong>Go variables and functions are accessible within {{ }}</strong></p> - -<p>Accessing a predefined variable &ldquo;foo&rdquo;:</p> - -<pre><code>{{ foo }} -</code></pre> - -<p><strong>Parameters are separated using spaces</strong></p> - -<p>Calling the add function with input of 1, 2:</p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<p><strong>Methods and fields are accessed via dot notation</strong></p> - -<p>Accessing the Page Parameter &ldquo;bar&rdquo;</p> - -<pre><code>{{ .Params.bar }} -</code></pre> - -<p><strong>Parentheses can be used to group items together</strong></p> - -<pre><code>{{ if or (isset .Params &quot;alt&quot;) (isset .Params &quot;caption&quot;) }} Caption {{ end }} -</code></pre> - -<h2 id="variables:4d30d99f79bd431d57546bbed04b7347">Variables</h2> - -<p>Each go template has a struct (object) made available to it. In hugo each -template is passed either a page or a node struct depending on which type of -page you are rendering. More details are available on the -<a href="http://localhost:1313/layout/variables">variables</a> page.</p> - -<p>A variable is accessed by referencing the variable name.</p> - -<pre><code>&lt;title&gt;{{ .Title }}&lt;/title&gt; -</code></pre> - -<p>Variables can also be defined and referenced.</p> - -<pre><code>{{ $address := &quot;123 Main St.&quot;}} -{{ $address }} -</code></pre> - -<h2 id="functions:4d30d99f79bd431d57546bbed04b7347">Functions</h2> - -<p>Go template ship 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. <a href="http://localhost:1313/layout/functions">Hugo template -functions</a> 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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<h2 id="includes:4d30d99f79bd431d57546bbed04b7347">Includes</h2> - -<p>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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ template &quot;chrome/header.html&quot; . }} -</code></pre> - -<h2 id="logic:4d30d99f79bd431d57546bbed04b7347">Logic</h2> - -<p>Go templates provide the most basic iteration and conditional logic.</p> - -<h3 id="iteration:4d30d99f79bd431d57546bbed04b7347">Iteration</h3> - -<p>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.</p> - -<p><strong>Example 1: Using Context</strong></p> - -<pre><code>{{ range array }} - {{ . }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring value variable name</strong></p> - -<pre><code>{{range $element := array}} - {{ $element }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring key and value variable name</strong></p> - -<pre><code>{{range $index, $element := array}} - {{ $index }} - {{ $element }} -{{ end }} -</code></pre> - -<h3 id="conditionals:4d30d99f79bd431d57546bbed04b7347">Conditionals</h3> - -<p>If, else, with, or, &amp; and provide the framework for handling conditional -logic in Go Templates. Like range, each statement is closed with <code>end</code>.</p> - -<p>Go Templates treat the following values as false:</p> - -<ul> -<li>false</li> -<li>0</li> -<li>any array, slice, map, or string of length zero</li> -</ul> - -<p><strong>Example 1: If</strong></p> - -<pre><code>{{ if isset .Params &quot;title&quot; }}&lt;h4&gt;{{ index .Params &quot;title&quot; }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 2: If -&gt; Else</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{else}} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<p><strong>Example 3: And &amp; Or</strong></p> - -<pre><code>{{ if and (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -</code></pre> - -<p><strong>Example 4: With</strong></p> - -<p>An alternative way of writing &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent.</p> - -<p>The first example above could be simplified as:</p> - -<pre><code>{{ with .Params.title }}&lt;h4&gt;{{ . }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 5: If -&gt; Else If</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{ else if isset .Params &quot;caption&quot; }} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<h2 id="pipes:4d30d99f79bd431d57546bbed04b7347">Pipes</h2> - -<p>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&rsquo;s output becomes the -input of the following pipe.</p> - -<p>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.</p> - -<p>A few simple examples should help convey how to use the pipe.</p> - -<p><strong>Example 1 :</strong></p> - -<pre><code>{{ if eq 1 1 }} Same {{ end }} -</code></pre> - -<p>is the same as</p> - -<pre><code>{{ eq 1 1 | if }} Same {{ end }} -</code></pre> - -<p>It does look odd to place the if at the end, but it does provide a good -illustration of how to use the pipes.</p> - -<p><strong>Example 2 :</strong></p> - -<pre><code>{{ index .Params &quot;disqus_url&quot; | html }} -</code></pre> - -<p>Access the page parameter called &ldquo;disqus_url&rdquo; and escape the HTML.</p> - -<p><strong>Example 3 :</strong></p> - -<pre><code>{{ if or (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -Stuff Here -{{ end }} -</code></pre> - -<p>Could be rewritten as</p> - -<pre><code>{{ isset .Params &quot;caption&quot; | or isset .Params &quot;title&quot; | or isset .Params &quot;attr&quot; | if }} -Stuff Here -{{ end }} -</code></pre> - -<h2 id="context-aka-the-dot:4d30d99f79bd431d57546bbed04b7347">Context (aka. the dot)</h2> - -<p>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 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 set it to a variable -instead of depending on the context.</p> - -<p><strong>Example:</strong></p> - -<pre><code> {{ $title := .Site.Title }} - {{ range .Params.tags }} - &lt;li&gt; &lt;a href=&quot;{{ $baseurl }}/tags/{{ . | urlize }}&quot;&gt;{{ . }}&lt;/a&gt; - {{ $title }} &lt;/li&gt; - {{ end }} -</code></pre> - -<p>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.</p> - -<h1 id="hugo-parameters:4d30d99f79bd431d57546bbed04b7347">Hugo Parameters</h1> - -<p>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.</p> - -<h2 id="using-content-page-parameters:4d30d99f79bd431d57546bbed04b7347">Using Content (page) Parameters</h2> - -<p>In each piece of content you can provide variables to be used by the -templates. This happens in the <a href="http://localhost:1313/content/front-matter">front matter</a>.</p> - -<p>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&rsquo;t make a lot of sense. We&rsquo;ve defined a variable in our front matter -of some pages to turn off the TOC from being displayed.</p> - -<p>Here is the example front matter:</p> - -<pre><code>--- -title: &quot;Permalinks&quot; -date: &quot;2013-11-18&quot; -aliases: - - &quot;/doc/permalinks/&quot; -groups: [&quot;extras&quot;] -groups_weight: 30 -notoc: true ---- -</code></pre> - -<p>Here is the corresponding code inside of the template:</p> - -<pre><code> {{ if not .Params.notoc }} - &lt;div id=&quot;toc&quot; class=&quot;well col-md-4 col-sm-6&quot;&gt; - {{ .TableOfContents }} - &lt;/div&gt; - {{ end }} -</code></pre> - -<h2 id="using-site-config-parameters:4d30d99f79bd431d57546bbed04b7347">Using Site (config) Parameters</h2> - -<p>In your top-level configuration file (eg, <code>config.yaml</code>) you can define site -parameters, which are values which will be available to you in chrome.</p> - -<p>For instance, you might declare:</p> - -<pre><code class="language-yaml">params: - CopyrightHTML: &quot;Copyright &amp;#xA9; 2013 John Doe. All Rights Reserved.&quot; - TwitterUser: &quot;spf13&quot; - SidebarRecentLimit: 5 -</code></pre> - -<p>Within a footer layout, you might then declare a <code>&lt;footer&gt;</code> which is only -provided if the <code>CopyrightHTML</code> 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.</p> - -<pre><code>{{if .Site.Params.CopyrightHTML}}&lt;footer&gt; -&lt;div class=&quot;text-center&quot;&gt;{{.Site.Params.CopyrightHTML | safeHtml}}&lt;/div&gt; -&lt;/footer&gt;{{end}} -</code></pre> - -<p>An alternative way of writing the &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent:</p> - -<pre><code>{{with .Site.Params.TwitterUser}}&lt;span class=&quot;twitter&quot;&gt; -&lt;a href=&quot;https://twitter.com/{{.}}&quot; rel=&quot;author&quot;&gt; -&lt;img src=&quot;/images/twitter.png&quot; width=&quot;48&quot; height=&quot;48&quot; title=&quot;Twitter: {{.}}&quot; - alt=&quot;Twitter&quot;&gt;&lt;/a&gt; -&lt;/span&gt;{{end}} -</code></pre> - -<p>Finally, if you want to pull &ldquo;magic constants&rdquo; out of your layouts, you can do -so, such as in this example:</p> - -<pre><code>&lt;nav class=&quot;recent&quot;&gt; - &lt;h1&gt;Recent Posts&lt;/h1&gt; - &lt;ul&gt;{{range first .Site.Params.SidebarRecentLimit .Site.Recent}} - &lt;li&gt;&lt;a href=&quot;{{.RelPermalink}}&quot;&gt;{{.Title}}&lt;/a&gt;&lt;/li&gt; - {{end}}&lt;/ul&gt; -&lt;/nav&gt; -</code></pre> - - - - - Getting Started with Hugo - http://localhost:1313/post/hugoisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/hugoisforlovers/ - - -<h2 id="step-1-install-hugo:c57cc0038c788519b441e0331c8bebc7">Step 1. Install Hugo</h2> - -<p>Goto <a href="https://github.com/spf13/hugo/releases">hugo releases</a> and download the -appropriate version for your os and architecture.</p> - -<p>Save it somewhere specific as we will be using it in the next step.</p> - -<p>More complete instructions are available at <a href="http://localhost:1313/overview/installing/">installing hugo</a></p> - -<h2 id="step-2-build-the-docs:c57cc0038c788519b441e0331c8bebc7">Step 2. Build the Docs</h2> - -<p>Hugo has its own example site which happens to also be the documentation site -you are reading right now.</p> - -<p>Follow the following steps:</p> - -<ol> -<li>Clone the <a href="http://github.com/spf13/hugo">hugo repository</a></li> -<li>Go into the repo</li> -<li>Run hugo in server mode and build the docs</li> -<li>Open your browser to <a href="http://localhost:1313">http://localhost:1313</a></li> -</ol> - -<p>Corresponding pseudo commands:</p> - -<pre><code>git clone https://github.com/spf13/hugo -cd hugo -/path/to/where/you/installed/hugo server --source=./docs -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Press ctrl+c to stop -</code></pre> - -<p>Once you&rsquo;ve gotten here, follow along the rest of this page on your local build.</p> - -<h2 id="step-3-change-the-docs-site:c57cc0038c788519b441e0331c8bebc7">Step 3. Change the docs site</h2> - -<p>Stop the Hugo process by hitting ctrl+c.</p> - -<p>Now we are going to run hugo again, but this time with hugo in watch mode.</p> - -<pre><code>/path/to/hugo/from/step/1/hugo server --source=./docs --watch -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Watching for changes in /Users/spf13/Code/hugo/docs/content -&gt; Press ctrl+c to stop -</code></pre> - -<p>Open your <a href="http://vim.spf13.com">favorite editor</a> and change one of the source -content pages. How about changing this very file to <em>fix the typo</em>. How about changing this very file to <em>fix the typo</em>.</p> - -<p>Content files are found in <code>docs/content/</code>. Unless otherwise specified, files -are located at the same relative location as the url, in our case -<code>docs/content/overview/quickstart.md</code>.</p> - -<p>Change and save this file.. Notice what happened in your terminal.</p> - -<pre><code>&gt; Change detected, rebuilding site - -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 26 ms -</code></pre> - -<p>Refresh the browser and observe that the typo is now fixed.</p> - -<p>Notice how quick that was. Try to refresh the site before it&rsquo;s finished building.. I double dare you. -Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.</p> - -<h2 id="step-4-have-fun:c57cc0038c788519b441e0331c8bebc7">Step 4. Have fun</h2> - -<p>The best way to learn something is to play with it.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/categories/golang/index.html b/exampleSite/public/categories/golang/index.html deleted file mode 100644 index a0ba331..0000000 --- a/exampleSite/public/categories/golang/index.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - - Golang · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - Golang - -
    - - - -
  • -
    Apr 2, 2014
    -
    (Hu)go Template Primer
     -
    • - - -
  • -
    Apr 2, 2014
    -
    Getting Started with Hugo
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/categories/golang/index.xml b/exampleSite/public/categories/golang/index.xml deleted file mode 100644 index dcc3c7c..0000000 --- a/exampleSite/public/categories/golang/index.xml +++ /dev/null @@ -1,446 +0,0 @@ - - - - Golang on Hugo Themes - http://localhost:1313/categories/golang/ - Recent content in Golang on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - (Hu)go Template Primer - http://localhost:1313/post/goisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/goisforlovers/ - - -<p>Hugo uses the excellent <a href="http://golang.org/&gt;">go</a> <a href="http://golang.org/pkg/html/template/&gt;">html/template</a> library for -its template engine. It is an extremely lightweight engine that provides a very -small amount of logic. In our experience that 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.</p> - -<p>This document is a brief primer on using go templates. The <a href="http://golang.org/pkg/html/template/&gt;">go docs</a> -provide more details.</p> - -<h2 id="introduction-to-go-templates:4d30d99f79bd431d57546bbed04b7347">Introduction to Go Templates</h2> - -<p>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.</p> - -<p>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 <a href="http://golang.org/pkg/html/template/&gt;">go docs</a>.</p> - -<h2 id="basic-syntax:4d30d99f79bd431d57546bbed04b7347">Basic Syntax</h2> - -<p>Go lang templates are html files with the addition of variables and -functions.</p> - -<p><strong>Go variables and functions are accessible within {{ }}</strong></p> - -<p>Accessing a predefined variable &ldquo;foo&rdquo;:</p> - -<pre><code>{{ foo }} -</code></pre> - -<p><strong>Parameters are separated using spaces</strong></p> - -<p>Calling the add function with input of 1, 2:</p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<p><strong>Methods and fields are accessed via dot notation</strong></p> - -<p>Accessing the Page Parameter &ldquo;bar&rdquo;</p> - -<pre><code>{{ .Params.bar }} -</code></pre> - -<p><strong>Parentheses can be used to group items together</strong></p> - -<pre><code>{{ if or (isset .Params &quot;alt&quot;) (isset .Params &quot;caption&quot;) }} Caption {{ end }} -</code></pre> - -<h2 id="variables:4d30d99f79bd431d57546bbed04b7347">Variables</h2> - -<p>Each go template has a struct (object) made available to it. In hugo each -template is passed either a page or a node struct depending on which type of -page you are rendering. More details are available on the -<a href="http://localhost:1313/layout/variables">variables</a> page.</p> - -<p>A variable is accessed by referencing the variable name.</p> - -<pre><code>&lt;title&gt;{{ .Title }}&lt;/title&gt; -</code></pre> - -<p>Variables can also be defined and referenced.</p> - -<pre><code>{{ $address := &quot;123 Main St.&quot;}} -{{ $address }} -</code></pre> - -<h2 id="functions:4d30d99f79bd431d57546bbed04b7347">Functions</h2> - -<p>Go template ship 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. <a href="http://localhost:1313/layout/functions">Hugo template -functions</a> 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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<h2 id="includes:4d30d99f79bd431d57546bbed04b7347">Includes</h2> - -<p>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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ template &quot;chrome/header.html&quot; . }} -</code></pre> - -<h2 id="logic:4d30d99f79bd431d57546bbed04b7347">Logic</h2> - -<p>Go templates provide the most basic iteration and conditional logic.</p> - -<h3 id="iteration:4d30d99f79bd431d57546bbed04b7347">Iteration</h3> - -<p>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.</p> - -<p><strong>Example 1: Using Context</strong></p> - -<pre><code>{{ range array }} - {{ . }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring value variable name</strong></p> - -<pre><code>{{range $element := array}} - {{ $element }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring key and value variable name</strong></p> - -<pre><code>{{range $index, $element := array}} - {{ $index }} - {{ $element }} -{{ end }} -</code></pre> - -<h3 id="conditionals:4d30d99f79bd431d57546bbed04b7347">Conditionals</h3> - -<p>If, else, with, or, &amp; and provide the framework for handling conditional -logic in Go Templates. Like range, each statement is closed with <code>end</code>.</p> - -<p>Go Templates treat the following values as false:</p> - -<ul> -<li>false</li> -<li>0</li> -<li>any array, slice, map, or string of length zero</li> -</ul> - -<p><strong>Example 1: If</strong></p> - -<pre><code>{{ if isset .Params &quot;title&quot; }}&lt;h4&gt;{{ index .Params &quot;title&quot; }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 2: If -&gt; Else</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{else}} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<p><strong>Example 3: And &amp; Or</strong></p> - -<pre><code>{{ if and (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -</code></pre> - -<p><strong>Example 4: With</strong></p> - -<p>An alternative way of writing &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent.</p> - -<p>The first example above could be simplified as:</p> - -<pre><code>{{ with .Params.title }}&lt;h4&gt;{{ . }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 5: If -&gt; Else If</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{ else if isset .Params &quot;caption&quot; }} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<h2 id="pipes:4d30d99f79bd431d57546bbed04b7347">Pipes</h2> - -<p>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&rsquo;s output becomes the -input of the following pipe.</p> - -<p>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.</p> - -<p>A few simple examples should help convey how to use the pipe.</p> - -<p><strong>Example 1 :</strong></p> - -<pre><code>{{ if eq 1 1 }} Same {{ end }} -</code></pre> - -<p>is the same as</p> - -<pre><code>{{ eq 1 1 | if }} Same {{ end }} -</code></pre> - -<p>It does look odd to place the if at the end, but it does provide a good -illustration of how to use the pipes.</p> - -<p><strong>Example 2 :</strong></p> - -<pre><code>{{ index .Params &quot;disqus_url&quot; | html }} -</code></pre> - -<p>Access the page parameter called &ldquo;disqus_url&rdquo; and escape the HTML.</p> - -<p><strong>Example 3 :</strong></p> - -<pre><code>{{ if or (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -Stuff Here -{{ end }} -</code></pre> - -<p>Could be rewritten as</p> - -<pre><code>{{ isset .Params &quot;caption&quot; | or isset .Params &quot;title&quot; | or isset .Params &quot;attr&quot; | if }} -Stuff Here -{{ end }} -</code></pre> - -<h2 id="context-aka-the-dot:4d30d99f79bd431d57546bbed04b7347">Context (aka. the dot)</h2> - -<p>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 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 set it to a variable -instead of depending on the context.</p> - -<p><strong>Example:</strong></p> - -<pre><code> {{ $title := .Site.Title }} - {{ range .Params.tags }} - &lt;li&gt; &lt;a href=&quot;{{ $baseurl }}/tags/{{ . | urlize }}&quot;&gt;{{ . }}&lt;/a&gt; - {{ $title }} &lt;/li&gt; - {{ end }} -</code></pre> - -<p>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.</p> - -<h1 id="hugo-parameters:4d30d99f79bd431d57546bbed04b7347">Hugo Parameters</h1> - -<p>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.</p> - -<h2 id="using-content-page-parameters:4d30d99f79bd431d57546bbed04b7347">Using Content (page) Parameters</h2> - -<p>In each piece of content you can provide variables to be used by the -templates. This happens in the <a href="http://localhost:1313/content/front-matter">front matter</a>.</p> - -<p>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&rsquo;t make a lot of sense. We&rsquo;ve defined a variable in our front matter -of some pages to turn off the TOC from being displayed.</p> - -<p>Here is the example front matter:</p> - -<pre><code>--- -title: &quot;Permalinks&quot; -date: &quot;2013-11-18&quot; -aliases: - - &quot;/doc/permalinks/&quot; -groups: [&quot;extras&quot;] -groups_weight: 30 -notoc: true ---- -</code></pre> - -<p>Here is the corresponding code inside of the template:</p> - -<pre><code> {{ if not .Params.notoc }} - &lt;div id=&quot;toc&quot; class=&quot;well col-md-4 col-sm-6&quot;&gt; - {{ .TableOfContents }} - &lt;/div&gt; - {{ end }} -</code></pre> - -<h2 id="using-site-config-parameters:4d30d99f79bd431d57546bbed04b7347">Using Site (config) Parameters</h2> - -<p>In your top-level configuration file (eg, <code>config.yaml</code>) you can define site -parameters, which are values which will be available to you in chrome.</p> - -<p>For instance, you might declare:</p> - -<pre><code class="language-yaml">params: - CopyrightHTML: &quot;Copyright &amp;#xA9; 2013 John Doe. All Rights Reserved.&quot; - TwitterUser: &quot;spf13&quot; - SidebarRecentLimit: 5 -</code></pre> - -<p>Within a footer layout, you might then declare a <code>&lt;footer&gt;</code> which is only -provided if the <code>CopyrightHTML</code> 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.</p> - -<pre><code>{{if .Site.Params.CopyrightHTML}}&lt;footer&gt; -&lt;div class=&quot;text-center&quot;&gt;{{.Site.Params.CopyrightHTML | safeHtml}}&lt;/div&gt; -&lt;/footer&gt;{{end}} -</code></pre> - -<p>An alternative way of writing the &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent:</p> - -<pre><code>{{with .Site.Params.TwitterUser}}&lt;span class=&quot;twitter&quot;&gt; -&lt;a href=&quot;https://twitter.com/{{.}}&quot; rel=&quot;author&quot;&gt; -&lt;img src=&quot;/images/twitter.png&quot; width=&quot;48&quot; height=&quot;48&quot; title=&quot;Twitter: {{.}}&quot; - alt=&quot;Twitter&quot;&gt;&lt;/a&gt; -&lt;/span&gt;{{end}} -</code></pre> - -<p>Finally, if you want to pull &ldquo;magic constants&rdquo; out of your layouts, you can do -so, such as in this example:</p> - -<pre><code>&lt;nav class=&quot;recent&quot;&gt; - &lt;h1&gt;Recent Posts&lt;/h1&gt; - &lt;ul&gt;{{range first .Site.Params.SidebarRecentLimit .Site.Recent}} - &lt;li&gt;&lt;a href=&quot;{{.RelPermalink}}&quot;&gt;{{.Title}}&lt;/a&gt;&lt;/li&gt; - {{end}}&lt;/ul&gt; -&lt;/nav&gt; -</code></pre> - - - - - Getting Started with Hugo - http://localhost:1313/post/hugoisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/hugoisforlovers/ - - -<h2 id="step-1-install-hugo:c57cc0038c788519b441e0331c8bebc7">Step 1. Install Hugo</h2> - -<p>Goto <a href="https://github.com/spf13/hugo/releases">hugo releases</a> and download the -appropriate version for your os and architecture.</p> - -<p>Save it somewhere specific as we will be using it in the next step.</p> - -<p>More complete instructions are available at <a href="http://localhost:1313/overview/installing/">installing hugo</a></p> - -<h2 id="step-2-build-the-docs:c57cc0038c788519b441e0331c8bebc7">Step 2. Build the Docs</h2> - -<p>Hugo has its own example site which happens to also be the documentation site -you are reading right now.</p> - -<p>Follow the following steps:</p> - -<ol> -<li>Clone the <a href="http://github.com/spf13/hugo">hugo repository</a></li> -<li>Go into the repo</li> -<li>Run hugo in server mode and build the docs</li> -<li>Open your browser to <a href="http://localhost:1313">http://localhost:1313</a></li> -</ol> - -<p>Corresponding pseudo commands:</p> - -<pre><code>git clone https://github.com/spf13/hugo -cd hugo -/path/to/where/you/installed/hugo server --source=./docs -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Press ctrl+c to stop -</code></pre> - -<p>Once you&rsquo;ve gotten here, follow along the rest of this page on your local build.</p> - -<h2 id="step-3-change-the-docs-site:c57cc0038c788519b441e0331c8bebc7">Step 3. Change the docs site</h2> - -<p>Stop the Hugo process by hitting ctrl+c.</p> - -<p>Now we are going to run hugo again, but this time with hugo in watch mode.</p> - -<pre><code>/path/to/hugo/from/step/1/hugo server --source=./docs --watch -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Watching for changes in /Users/spf13/Code/hugo/docs/content -&gt; Press ctrl+c to stop -</code></pre> - -<p>Open your <a href="http://vim.spf13.com">favorite editor</a> and change one of the source -content pages. How about changing this very file to <em>fix the typo</em>. How about changing this very file to <em>fix the typo</em>.</p> - -<p>Content files are found in <code>docs/content/</code>. Unless otherwise specified, files -are located at the same relative location as the url, in our case -<code>docs/content/overview/quickstart.md</code>.</p> - -<p>Change and save this file.. Notice what happened in your terminal.</p> - -<pre><code>&gt; Change detected, rebuilding site - -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 26 ms -</code></pre> - -<p>Refresh the browser and observe that the typo is now fixed.</p> - -<p>Notice how quick that was. Try to refresh the site before it&rsquo;s finished building.. I double dare you. -Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.</p> - -<h2 id="step-4-have-fun:c57cc0038c788519b441e0331c8bebc7">Step 4. Have fun</h2> - -<p>The best way to learn something is to play with it.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/code/index.html b/exampleSite/public/code/index.html deleted file mode 100644 index e69de29..0000000 diff --git a/exampleSite/public/colophon/index.html b/exampleSite/public/colophon/index.html deleted file mode 100644 index 26ae284..0000000 --- a/exampleSite/public/colophon/index.html +++ /dev/null @@ -1,137 +0,0 @@ - - - - - - - - - - - - - - - - colophon · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - about this site - -
    - - -
    -

    This website is the place where I write about JavaScript, git, and tech. It is also a personal homepage.

    - -

    The site is built with Hugo—a static site generator made with Go and is hosted on GitHub Pages. The website source code is available on GitHub. It uses the cocoa theme. The posts are written in Markdown.

    - -

    The primary font face is Proxima Nova and the monospace font face is Ubuntu Mono. The social icons are from the Ionicons font set. CSS classes for code syntax highlighting are inserted during compile-time by Hugo using Pygments.

    - -

    If you find errors, please let me know.

    - -
    -
    -
    -
    - - - - - - - - - - diff --git a/exampleSite/public/css/main.css b/exampleSite/public/css/main.css deleted file mode 100644 index 6188a7d..0000000 --- a/exampleSite/public/css/main.css +++ /dev/null @@ -1,599 +0,0 @@ -@import url(https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700); -@import url(http://fonts.googleapis.com/css?family=Ubuntu+Mono:400,400italic,700,700italic); -@import url(http://code.ionicframework.com/ionicons/2.0.1/css/ionicons.min.css); -@import url(http://fonts.googleapis.com/css?family=Raleway:200); -.dark { - color: #333333 !important; -} -.light { - color: #b7b7b7 !important; -} -.accent { - color: #21bb5b !important; -} -*, -*:before, -*:after { - box-sizing: border-box; -} -a, -a:visited, -a:focus, -a:active { - text-decoration: none; -} -html { - height: 100%; - font-size: 16px; -} -body { - display: -webkit-flex; - display: -moz-flex; - display: -ms-flexbox; - display: -ms-flex; - display: flex; - -webkit-flex-direction: column; - -moz-flex-direction: column; - -ms-flex-direction: column; - flex-direction: column; - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; - -webkit-justify-content: flex-start; - -moz-justify-content: flex-start; - -ms-justify-content: flex-start; - justify-content: flex-start; - width: 100%; - min-height: 100%; - font-weight: 400; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial' sans-serif; - color: #333333; - line-height: 1.6; - text-rendering: optimizeLegibility !important; - -webkit-font-smoothing: subpixel-antialiased; - font-smoothing: subpixel-antialiased; -} -@media (min-width: 550px) { - body { - -webkit-justify-content: center; - -moz-justify-content: center; - -ms-justify-content: center; - justify-content: center; - } -} -.icon { - text-rendering: geometricPrecision !important; -} -.section { - display: -webkit-flex; - display: -moz-flex; - display: -ms-flexbox; - display: -ms-flex; - display: flex; - -webkit-justify-content: center; - -moz-justify-content: center; - -ms-justify-content: center; - justify-content: center; - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; - width: 100%; -} -.container { - display: -webkit-flex; - display: -moz-flex; - display: -ms-flexbox; - display: -ms-flex; - display: flex; - width: 100%; -} -@media (min-width: 550px) { - .section { - padding: 0 20px; - margin-left: 100px; - margin-right: 100px; - max-width: 900px; - } -} -.section.header { - -webkit-order: 0; - -moz-order: 0; - -ms-order: 0; - order: 0; -} -.section.icons { - -webkit-order: 1; - -moz-order: 1; - -ms-order: 1; - order: 1; -} -.section.main { - -webkit-order: 2; - -moz-order: 2; - -ms-order: 2; - order: 2; -} -@media (min-width: 550px) { - .section.header { - -webkit-order: 0; - -moz-order: 0; - -ms-order: 0; - order: 0; - } - .section.icons { - -webkit-order: 2; - -moz-order: 2; - -ms-order: 2; - order: 2; - } - .section.main { - -webkit-order: 1; - -moz-order: 1; - -ms-order: 1; - order: 1; - } -} -.section.header { - background-color: #21bb5b; -} -.section.header .container { - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; - -webkit-justify-content: center; - -moz-justify-content: center; - -ms-justify-content: center; - justify-content: center; -} -.section.header .content { - display: -webkit-flex; - display: -moz-flex; - display: -ms-flexbox; - display: -ms-flex; - display: flex; - -webkit-flex-direction: column; - -moz-flex-direction: column; - -ms-flex-direction: column; - flex-direction: column; - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; -} -.section.header .name { - font-size: 18px; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial' sans-serif; - letter-spacing: -0.005rem; - text-transform: uppercase; - font-weight: 700; - -moz-osx-font-smoothing: grayscale; - -webkit-font-smoothing: antialiased; - font-smoothing: antialiased; - color: #333333; - color: #fefefe; -} -.section.header nav { - font-size: 14px; - margin-bottom: 16px; -} -.section.header nav ul { - list-style: none; - text-align: center; - display: -webkit-inline-flex; - display: -moz-inline-flex; - display: -ms-inline-flexbox; - display: -ms-inline-flex; - display: inline-flex; -} -.section.header nav ul a { - margin-right: 12px; -} -.section.header nav ul a:last-child { - margin-right: 0; -} -.section.header nav ul li { - color: #fefefe; - -webkit-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); - -moz-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); - -ms-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); - -o-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); -} -.section.header nav ul li:hover { - color: #fefefe; -} -@media (min-width: 550px) { - .section.header { - background-color: transparent; - } - .section.header .container { - -webkit-justify-content: flex-start; - -moz-justify-content: flex-start; - -ms-justify-content: flex-start; - justify-content: flex-start; - } - .section.header .content { - -webkit-align-items: flex-start; - -moz-align-items: flex-start; - -ms-align-items: flex-start; - align-items: flex-start; - } - .section.header .name { - color: #333333; - } - .section.header nav { - margin-bottom: 0; - } - .section.header nav ul { - text-align: left; - } - .section.header nav ul li { - color: #b7b7b7; - } - .section.header nav ul li:hover { - color: #333333; - } -} -.section.icons { - background-color: #21bb5b; -} -.section.icons .container { - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; - -webkit-justify-content: center; - -moz-justify-content: center; - -ms-justify-content: center; - justify-content: center; -} -.section.icons .content a { - margin-right: 4px; - color: #fefefe; - -webkit-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); - -moz-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); - -ms-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); - -o-transition: color 0.1s cubic-bezier(0.47, 0, 0.75, 0.72); -} -.section.icons .content a:last-child { - margin-right: 0; -} -.section.icons .content a:hover { - color: #fefefe; -} -.section.icons .content a .icon { - font-size: 16px; -} -.section.icons .content a .icon.larger { - font-size: 18px; -} -@media (min-width: 550px) { - .section.icons { - background-color: transparent; - } - .section.icons .container { - -webkit-justify-content: flex-start; - -moz-justify-content: flex-start; - -ms-justify-content: flex-start; - justify-content: flex-start; - } - .section.icons .content a { - color: #b7b7b7; - } - .section.icons .content a:hover { - color: #333333; - } -} -.section.main .container { - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; - -webkit-justify-content: flex-start; - -moz-justify-content: flex-start; - -ms-justify-content: flex-start; - justify-content: flex-start; -} -.section.main .content { - color: #333333; - font-size: 16px; -} -.section.main .content .page-heading { - font-size: 18px; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial' sans-serif; - letter-spacing: -0.005rem; - text-transform: uppercase; - font-weight: 700; - -moz-osx-font-smoothing: grayscale; - -webkit-font-smoothing: antialiased; - font-smoothing: antialiased; - color: #333333; - margin-bottom: 16px; -} -.section.main .content .front-matter .page-heading { - margin-bottom: 0; -} -.section.main .content .front-matter .meta { - font-size: 14px; - color: #b7b7b7; - display: -webkit-flex; - display: -moz-flex; - display: -ms-flexbox; - display: -ms-flex; - display: flex; - margin-bottom: 32px; -} -.section.main .content .front-matter .date, -.section.main .content .front-matter .word-count, -.section.main .content .front-matter .reading-time .middot { - display: none; -} -.section.main .content .front-matter .middot { - font-size: 6px; - margin: 0 6px; - display: inline; - vertical-align: middle; -} -.section.main .content .front-matter .middot:before { - content: "•"; -} -@media (min-width: 550px) { - .section.main .content .front-matter .date, - .section.main .content .front-matter .word-count, - .section.main .content .front-matter .reading-time .middot { - display: initial; - } -} -.section.main .container.f04 { - -webkit-justify-content: center; - -moz-justify-content: center; - -ms-justify-content: center; - justify-content: center; -} -.section.main .container.f04 .content { - display: -webkit-flex; - display: -moz-flex; - display: -ms-flexbox; - display: -ms-flex; - display: flex; - -webkit-flex-direction: column; - -moz-flex-direction: column; - -ms-flex-direction: column; - flex-direction: column; - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; -} -.section.main .container.f04 .content .num { - margin: 30px 0px 30px 0; - font-weight: 200; - font-family: 'Raleway', 'Helvetica Neue', 'Arial', sans-serif; - font-size: 50px; -} -.section.main .container.f04 .content .detail { - margin-bottom: 40px; -} -@media (min-width: 550px) { - .section.main .container.f04 { - -webkit-justify-content: flex-start; - -moz-justify-content: flex-start; - -ms-justify-content: flex-start; - justify-content: flex-start; - } - .section.main .container.f04 .content { - -webkit-align-items: flex-start; - -moz-align-items: flex-start; - -ms-align-items: flex-start; - align-items: flex-start; - } - .section.main .container.f04 .content .num { - margin: 0 0 10px 0; - font-size: 32px; - } - .section.main .container.f04 .content .detail { - margin-bottom: 30px; - } -} -.section.main .container .content .post-item { - display: -webkit-flex; - display: -moz-flex; - display: -ms-flexbox; - display: -ms-flex; - display: flex; - -webkit-align-items: center; - -moz-align-items: center; - -ms-align-items: center; - align-items: center; - list-style: none; -} -.section.main .container .content .post-item .meta { - font-size: 14px; - color: #b7b7b7; - min-width: 100px; - text-align: right; - margin-right: 20px; -} -.section { - padding: 0 20px; -} -.section.header { - padding-top: 32px; - padding-bottom: 16px; -} -.section.icons { - padding-top: 0; - padding-bottom: 32px; -} -.section.main { - padding-top: 32px; - padding-bottom: 32px; -} -@media (min-width: 550px) { - .container { - margin: 0 20px; - } - .section.header { - padding-top: 60px; - padding-bottom: 60px; - } - .section.icons { - padding-top: 60px; - padding-bottom: 60px; - } - .section.main { - padding-top: 0; - padding-bottom: 0; - } - .section.main.post { - padding-top: 60px; - padding-bottom: 60px; - } -} -a { - color: #21bb5b; -} -.section.main .content .markdown h1, -.section.main .content .markdown h2, -.section.main .content .markdown h3, -.section.main .content .markdown h4, -.section.main .content .markdown h5, -.section.main .content .markdown h6 { - font-size: 18px; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial' sans-serif; - letter-spacing: -0.005rem; - text-transform: uppercase; - font-weight: 700; - -moz-osx-font-smoothing: grayscale; - -webkit-font-smoothing: antialiased; - font-smoothing: antialiased; - color: #333333; -} -.section.main .content .markdown h1 { - font-size: 1.75rem; - margin-bottom: 2rem; -} -.section.main .content .markdown h2 { - font-size: 1.5rem; - margin-bottom: 1.5rem; -} -.section.main .content .markdown h3 { - font-size: 1em; - margin-bottom: 1rem; -} -.section.main .content .markdown h4, -.section.main .content .markdown h5, -.section.main .content .markdown h6 { - font-size: 1rem; - margin-bottom: 1rem; - letter-spacing: none; - text-transform: none; -} -.section.main .content .markdown code, -.section.main .content .markdown pre { - font-family: 'Ubuntu Mono', 'Menlo', monospace; - font-size: 15px; - background-color: #f9f9f9; -} -.section.main .content .markdown code { - /* enclosed by single backtick (`) */ - padding: .15em .5em; - color: #a10c31; - border-radius: 2px; -} -.section.main .content .markdown pre { - /* Hugo specific: consider using the 'highlight' shortcode */ - display: block; - margin-top: 1rem; - margin-bottom: 2rem; - padding: 1rem; - line-height: 1.5em; - white-space: pre; - white-space: pre-wrap; - word-break: break-all; - word-wrap: break-word; -} -.section.main .content .markdown pre code { - /* enclosed by 4 backticks (````) */ - padding: 0; - font-size: 15px; -} -.section.main .content .markdown p { - /* Invoked by line break */ - font-size: 1rem; - margin-top: 0; - margin-bottom: 1em; -} -.section.main .content .markdown ul, -.section.main .content .markdown ol, -.section.main .content .markdown dl { - margin-top: 1rem; - margin-bottom: 2rem; -} -.section.main .content .markdown dt { - font-weight: bold; -} -.section.main .content .markdown dd { - margin-bottom: .5rem; -} -.section.main .content .markdown ul { - margin-bottom: 1.25rem; -} -.section.main .content .markdown li { - list-style-type: disc; - list-style-position: inside; -} -.section.main .content .markdown hr { - position: relative; - margin: 1.75rem 0; - border: 0; - border-top: 1px solid #d1d1d1; - border-top: 1px solid #eaeaea; -} -.section.main .content .markdown abbr { - font-size: 0.85rem; - font-weight: bold; - color: #666666; - text-transform: uppercase; -} -.section.main .content .markdown abbr[title] { - cursor: help; - border-bottom: 1px dotted #d1d1d1; -} -.section.main .content .markdown blockquote { - padding: .5rem 1rem; - margin: .8rem 0; - color: #7a7a7a; - border-left: .25rem solid #e5e5e5; -} -.section.main .content .markdown blockquote p:last-child { - margin-bottom: 0; -} -@media (min-width: 550px) { - .section.main .content .markdown blockquote { - padding-right: 5rem; - padding-left: 1.25rem; - } -} -.section.main .content .markdown img { - display: block; - margin: 0 0 1rem; - max-width: 100%; -} -.section.main .content .markdown table { - margin-bottom: 1rem; - width: 100%; - border: 1px solid #e5e5e5; - border-collapse: collapse; -} -.section.main .content .markdown td, -.section.main .content .markdown th { - padding: .25rem .5rem; - border: 1px solid #e5e5e5; -} -.section.main .content .markdown tbody tr:nth-child(odd) td, -.section.main .content .markdown tbody tr:nth-child(odd) th { - background-color: #f9f9f9; -} diff --git a/exampleSite/public/css/pygments.css b/exampleSite/public/css/pygments.css deleted file mode 100644 index dc60655..0000000 --- a/exampleSite/public/css/pygments.css +++ /dev/null @@ -1,61 +0,0 @@ -.hll { background-color: #ffffcc } -.c { color: #999988; font-style: italic } /* Comment */ -.err { color: #a61717; background-color: #e3d2d2 } /* Error */ -.k { color: #000000; font-weight: bold } /* Keyword */ -.o { color: #000000; font-weight: bold } /* Operator */ -.cm { color: #999988; font-style: italic } /* Comment.Multiline */ -.cp { color: #999999; font-weight: bold; font-style: italic } /* Comment.Preproc */ -.c1 { color: #999988; font-style: italic } /* Comment.Single */ -.cs { color: #999999; font-weight: bold; font-style: italic } /* Comment.Special */ -.gd { color: #000000; background-color: #ffdddd } /* Generic.Deleted */ -.ge { color: #000000; font-style: italic } /* Generic.Emph */ -.gr { color: #aa0000 } /* Generic.Error */ -.gh { color: #999999 } /* Generic.Heading */ -.gi { color: #000000; background-color: #ddffdd } /* Generic.Inserted */ -.go { color: #888888 } /* Generic.Output */ -.gp { color: #555555 } /* Generic.Prompt */ -.gs { font-weight: bold } /* Generic.Strong */ -.gu { color: #aaaaaa } /* Generic.Subheading */ -.gt { color: #aa0000 } /* Generic.Traceback */ -.kc { color: #000000; font-weight: bold } /* Keyword.Constant */ -.kd { color: #000000; font-weight: bold } /* Keyword.Declaration */ -.kn { color: #000000; font-weight: bold } /* Keyword.Namespace */ -.kp { color: #000000; font-weight: bold } /* Keyword.Pseudo */ -.kr { color: #000000; font-weight: bold } /* Keyword.Reserved */ -.kt { color: #445588; font-weight: bold } /* Keyword.Type */ -.m { color: #009999 } /* Literal.Number */ -.s { color: #d01040 } /* Literal.String */ -.na { color: #008080 } /* Name.Attribute */ -.nb { color: #0086B3 } /* Name.Builtin */ -.nc { color: #445588; font-weight: bold } /* Name.Class */ -.no { color: #008080 } /* Name.Constant */ -.nd { color: #3c5d5d; font-weight: bold } /* Name.Decorator */ -.ni { color: #800080 } /* Name.Entity */ -.ne { color: #990000; font-weight: bold } /* Name.Exception */ -.nf { color: #990000; font-weight: bold } /* Name.Function */ -.nl { color: #990000; font-weight: bold } /* Name.Label */ -.nn { color: #555555 } /* Name.Namespace */ -.nt { color: #000080 } /* Name.Tag */ -.nv { color: #008080 } /* Name.Variable */ -.ow { color: #000000; font-weight: bold } /* Operator.Word */ -.w { color: #bbbbbb } /* Text.Whitespace */ -.mf { color: #009999 } /* Literal.Number.Float */ -.mh { color: #009999 } /* Literal.Number.Hex */ -.mi { color: #009999 } /* Literal.Number.Integer */ -.mo { color: #009999 } /* Literal.Number.Oct */ -.sb { color: #d01040 } /* Literal.String.Backtick */ -.sc { color: #d01040 } /* Literal.String.Char */ -.sd { color: #d01040 } /* Literal.String.Doc */ -.s2 { color: #d01040 } /* Literal.String.Double */ -.se { color: #d01040 } /* Literal.String.Escape */ -.sh { color: #d01040 } /* Literal.String.Heredoc */ -.si { color: #d01040 } /* Literal.String.Interpol */ -.sx { color: #d01040 } /* Literal.String.Other */ -.sr { color: #009926 } /* Literal.String.Regex */ -.s1 { color: #d01040 } /* Literal.String.Single */ -.ss { color: #990073 } /* Literal.String.Symbol */ -.bp { color: #999999 } /* Name.Builtin.Pseudo */ -.vc { color: #008080 } /* Name.Variable.Class */ -.vg { color: #008080 } /* Name.Variable.Global */ -.vi { color: #008080 } /* Name.Variable.Instance */ -.il { color: #009999 } /* Literal.Number.Integer.Long */ diff --git a/exampleSite/public/css/reset.css b/exampleSite/public/css/reset.css deleted file mode 100644 index 87df836..0000000 --- a/exampleSite/public/css/reset.css +++ /dev/null @@ -1,48 +0,0 @@ -/* http://meyerweb.com/eric/tools/css/reset/ - v2.0 | 20110126 - License: none (public domain) -*/ - -html, body, div, span, applet, object, iframe, -h1, h2, h3, h4, h5, h6, p, blockquote, pre, -a, abbr, acronym, address, big, cite, code, -del, dfn, em, img, ins, kbd, q, s, samp, -small, strike, strong, sub, sup, tt, var, -b, u, i, center, -dl, dt, dd, ol, ul, li, -fieldset, form, label, legend, -table, caption, tbody, tfoot, thead, tr, th, td, -article, aside, canvas, details, embed, -figure, figcaption, footer, header, hgroup, -menu, nav, output, ruby, section, summary, -time, mark, audio, video { - margin: 0; - padding: 0; - border: 0; - font-size: 100%; - font: inherit; - vertical-align: baseline; -} -/* HTML5 display-role reset for older browsers */ -article, aside, details, figcaption, figure, -footer, header, hgroup, menu, nav, section { - display: block; -} -body { - line-height: 1; -} -ol, ul { - list-style: none; -} -blockquote, q { - quotes: none; -} -blockquote:before, blockquote:after, -q:before, q:after { - content: ''; - content: none; -} -table { - border-collapse: collapse; - border-spacing: 0; -} diff --git a/exampleSite/public/fixed/index.html b/exampleSite/public/fixed/index.html deleted file mode 100644 index e69de29..0000000 diff --git a/exampleSite/public/fixed/index.xml b/exampleSite/public/fixed/index.xml deleted file mode 100644 index 5c7755f..0000000 --- a/exampleSite/public/fixed/index.xml +++ /dev/null @@ -1,49 +0,0 @@ - - - - Fixeds on Hugo Themes - http://hugo.spf13.com/fixed/ - Recent content in Fixeds on Hugo Themes - Hugo -- gohugo.io - en-US - Sat, 22 Aug 2015 06:42:21 -0700 - - - - About - http://hugo.spf13.com/about/ - Sat, 22 Aug 2015 06:42:21 -0700 - - http://hugo.spf13.com/about/ - <p>TODO: Page not complete yet.</p> - -<p>Information about you.</p> - -<p>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod -tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, -quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo -consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse -cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non -proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p> - - - - - Code - http://hugo.spf13.com/code/ - Wed, 19 Aug 2015 20:29:37 -0700 - - http://hugo.spf13.com/code/ - <p>TODO: Page not complete yet.</p> - -<p>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod -tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, -quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo -consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse -cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non -proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/img/favicon.ico b/exampleSite/public/img/favicon.ico deleted file mode 100644 index 63d51a5..0000000 Binary files a/exampleSite/public/img/favicon.ico and /dev/null differ diff --git a/exampleSite/public/index.html b/exampleSite/public/index.html deleted file mode 100644 index e69de29..0000000 diff --git a/exampleSite/public/index.xml b/exampleSite/public/index.xml deleted file mode 100644 index 29dc018..0000000 --- a/exampleSite/public/index.xml +++ /dev/null @@ -1,74 +0,0 @@ - - - - Hugo Themes - http://hugo.spf13.com/ - Recent content on Hugo Themes - Hugo -- gohugo.io - en-US - Sat, 22 Aug 2015 15:45:30 -0700 - - - - Redirect webpages using HTML - http://hugo.spf13.com/posts/redirect-webpages-html/ - Sat, 22 Aug 2015 15:45:30 -0700 - - http://hugo.spf13.com/posts/redirect-webpages-html/ - - -<p>Webpage redirection is great for automatically redirecting people visiting an old URL to a new URL where the content has moved to. It can be done using JavaScript, but there is also a convenient HTML-only solution.</p> - -<p>To redirect visitors reaching <code>yourwebsite.com/blog</code> to <code>yourwebsite.com/posts</code>, add this to the <code>&lt;head&gt;</code> section of the HTML at <code>yourwebsite.com/blog</code>:</p> - -<p><div class="highlight"><pre><span class="nt">&lt;meta</span> <span class="na">http-equiv=</span><span class="s">&quot;refresh&quot;</span> <span class="na">content=</span><span class="s">&quot;0;url=&#39;/posts&#39;&quot;</span> <span class="nt">/&gt;</span> -<span class="nt">&lt;link</span> <span class="na">rel=</span><span class="s">&quot;canonical&quot;</span> <span class="na">href=</span><span class="s">&quot;/posts&quot;</span> <span class="nt">/&gt;</span> -</pre></div> -</p> - -<h3 id="walkthrough:afdc852818bb97af4efb4d34b2fcce3b">walkthrough</h3> - -<p>Setting <code>http-equiv=&quot;refresh&quot;</code> in the first line performs the actual redirect. The number in the <code>content</code> attribute specified in seconds tells the browser how long to wait before redirecting. In this example, <code>0</code> redirects immediately. Increasing the wait may be useful for briefly displaying a 404 page before automatically switching to the home page. The <code>url</code> specfies the destination for the redirect. In this example, we wanted to switch to <code>/posts</code>.</p> - -<p>The second line is optional; it helps search engines know which the preferred version of the page is. Usually, this is the redirect destination.</p> - - - - - About - http://hugo.spf13.com/about/ - Sat, 22 Aug 2015 06:42:21 -0700 - - http://hugo.spf13.com/about/ - <p>TODO: Page not complete yet.</p> - -<p>Information about you.</p> - -<p>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod -tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, -quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo -consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse -cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non -proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p> - - - - - Code - http://hugo.spf13.com/code/ - Wed, 19 Aug 2015 20:29:37 -0700 - - http://hugo.spf13.com/code/ - <p>TODO: Page not complete yet.</p> - -<p>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod -tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, -quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo -consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse -cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non -proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/posts/index.html b/exampleSite/public/posts/index.html deleted file mode 100644 index e69de29..0000000 diff --git a/exampleSite/public/posts/index.xml b/exampleSite/public/posts/index.xml deleted file mode 100644 index c64e608..0000000 --- a/exampleSite/public/posts/index.xml +++ /dev/null @@ -1,38 +0,0 @@ - - - - Posts on Hugo Themes - http://hugo.spf13.com/posts/ - Recent content in Posts on Hugo Themes - Hugo -- gohugo.io - en-US - Sat, 22 Aug 2015 15:45:30 -0700 - - - - Redirect webpages using HTML - http://hugo.spf13.com/posts/redirect-webpages-html/ - Sat, 22 Aug 2015 15:45:30 -0700 - - http://hugo.spf13.com/posts/redirect-webpages-html/ - - -<p>Webpage redirection is great for automatically redirecting people visiting an old URL to a new URL where the content has moved to. It can be done using JavaScript, but there is also a convenient HTML-only solution.</p> - -<p>To redirect visitors reaching <code>yourwebsite.com/blog</code> to <code>yourwebsite.com/posts</code>, add this to the <code>&lt;head&gt;</code> section of the HTML at <code>yourwebsite.com/blog</code>:</p> - -<p><div class="highlight"><pre><span class="nt">&lt;meta</span> <span class="na">http-equiv=</span><span class="s">&quot;refresh&quot;</span> <span class="na">content=</span><span class="s">&quot;0;url=&#39;/posts&#39;&quot;</span> <span class="nt">/&gt;</span> -<span class="nt">&lt;link</span> <span class="na">rel=</span><span class="s">&quot;canonical&quot;</span> <span class="na">href=</span><span class="s">&quot;/posts&quot;</span> <span class="nt">/&gt;</span> -</pre></div> -</p> - -<h3 id="walkthrough:afdc852818bb97af4efb4d34b2fcce3b">walkthrough</h3> - -<p>Setting <code>http-equiv=&quot;refresh&quot;</code> in the first line performs the actual redirect. The number in the <code>content</code> attribute specified in seconds tells the browser how long to wait before redirecting. In this example, <code>0</code> redirects immediately. Increasing the wait may be useful for briefly displaying a 404 page before automatically switching to the home page. The <code>url</code> specfies the destination for the redirect. In this example, we wanted to switch to <code>/posts</code>.</p> - -<p>The second line is optional; it helps search engines know which the preferred version of the page is. Usually, this is the redirect destination.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/posts/redirect-webpages-html/index.html b/exampleSite/public/posts/redirect-webpages-html/index.html deleted file mode 100644 index e69de29..0000000 diff --git a/exampleSite/public/projects/index.html b/exampleSite/public/projects/index.html deleted file mode 100644 index 57ed6e7..0000000 --- a/exampleSite/public/projects/index.html +++ /dev/null @@ -1,8 +0,0 @@ - - - - - - - - diff --git a/exampleSite/public/sitemap.xml b/exampleSite/public/sitemap.xml deleted file mode 100644 index d2b3480..0000000 --- a/exampleSite/public/sitemap.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - - - http://hugo.spf13.com/ - 2015-08-22T15:45:30-07:00 - 0 - - - - http://hugo.spf13.com/posts/redirect-webpages-html/ - 2015-08-22T15:45:30-07:00 - - - - http://hugo.spf13.com/about/ - 2015-08-22T06:42:21-07:00 - - - - http://hugo.spf13.com/code/ - 2015-08-19T20:29:37-07:00 - - - \ No newline at end of file diff --git a/exampleSite/public/tags/development/index.html b/exampleSite/public/tags/development/index.html deleted file mode 100644 index 32db006..0000000 --- a/exampleSite/public/tags/development/index.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - - Development · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - Development - -
    - - - -
  • -
    Apr 2, 2014
    -
    (Hu)go Template Primer
     -
    • - - -
  • -
    Apr 2, 2014
    -
    Getting Started with Hugo
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/tags/development/index.xml b/exampleSite/public/tags/development/index.xml deleted file mode 100644 index 99420d3..0000000 --- a/exampleSite/public/tags/development/index.xml +++ /dev/null @@ -1,446 +0,0 @@ - - - - Development on Hugo Themes - http://localhost:1313/tags/development/ - Recent content in Development on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - (Hu)go Template Primer - http://localhost:1313/post/goisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/goisforlovers/ - - -<p>Hugo uses the excellent <a href="http://golang.org/&gt;">go</a> <a href="http://golang.org/pkg/html/template/&gt;">html/template</a> library for -its template engine. It is an extremely lightweight engine that provides a very -small amount of logic. In our experience that 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.</p> - -<p>This document is a brief primer on using go templates. The <a href="http://golang.org/pkg/html/template/&gt;">go docs</a> -provide more details.</p> - -<h2 id="introduction-to-go-templates:4d30d99f79bd431d57546bbed04b7347">Introduction to Go Templates</h2> - -<p>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.</p> - -<p>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 <a href="http://golang.org/pkg/html/template/&gt;">go docs</a>.</p> - -<h2 id="basic-syntax:4d30d99f79bd431d57546bbed04b7347">Basic Syntax</h2> - -<p>Go lang templates are html files with the addition of variables and -functions.</p> - -<p><strong>Go variables and functions are accessible within {{ }}</strong></p> - -<p>Accessing a predefined variable &ldquo;foo&rdquo;:</p> - -<pre><code>{{ foo }} -</code></pre> - -<p><strong>Parameters are separated using spaces</strong></p> - -<p>Calling the add function with input of 1, 2:</p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<p><strong>Methods and fields are accessed via dot notation</strong></p> - -<p>Accessing the Page Parameter &ldquo;bar&rdquo;</p> - -<pre><code>{{ .Params.bar }} -</code></pre> - -<p><strong>Parentheses can be used to group items together</strong></p> - -<pre><code>{{ if or (isset .Params &quot;alt&quot;) (isset .Params &quot;caption&quot;) }} Caption {{ end }} -</code></pre> - -<h2 id="variables:4d30d99f79bd431d57546bbed04b7347">Variables</h2> - -<p>Each go template has a struct (object) made available to it. In hugo each -template is passed either a page or a node struct depending on which type of -page you are rendering. More details are available on the -<a href="http://localhost:1313/layout/variables">variables</a> page.</p> - -<p>A variable is accessed by referencing the variable name.</p> - -<pre><code>&lt;title&gt;{{ .Title }}&lt;/title&gt; -</code></pre> - -<p>Variables can also be defined and referenced.</p> - -<pre><code>{{ $address := &quot;123 Main St.&quot;}} -{{ $address }} -</code></pre> - -<h2 id="functions:4d30d99f79bd431d57546bbed04b7347">Functions</h2> - -<p>Go template ship 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. <a href="http://localhost:1313/layout/functions">Hugo template -functions</a> 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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<h2 id="includes:4d30d99f79bd431d57546bbed04b7347">Includes</h2> - -<p>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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ template &quot;chrome/header.html&quot; . }} -</code></pre> - -<h2 id="logic:4d30d99f79bd431d57546bbed04b7347">Logic</h2> - -<p>Go templates provide the most basic iteration and conditional logic.</p> - -<h3 id="iteration:4d30d99f79bd431d57546bbed04b7347">Iteration</h3> - -<p>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.</p> - -<p><strong>Example 1: Using Context</strong></p> - -<pre><code>{{ range array }} - {{ . }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring value variable name</strong></p> - -<pre><code>{{range $element := array}} - {{ $element }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring key and value variable name</strong></p> - -<pre><code>{{range $index, $element := array}} - {{ $index }} - {{ $element }} -{{ end }} -</code></pre> - -<h3 id="conditionals:4d30d99f79bd431d57546bbed04b7347">Conditionals</h3> - -<p>If, else, with, or, &amp; and provide the framework for handling conditional -logic in Go Templates. Like range, each statement is closed with <code>end</code>.</p> - -<p>Go Templates treat the following values as false:</p> - -<ul> -<li>false</li> -<li>0</li> -<li>any array, slice, map, or string of length zero</li> -</ul> - -<p><strong>Example 1: If</strong></p> - -<pre><code>{{ if isset .Params &quot;title&quot; }}&lt;h4&gt;{{ index .Params &quot;title&quot; }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 2: If -&gt; Else</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{else}} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<p><strong>Example 3: And &amp; Or</strong></p> - -<pre><code>{{ if and (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -</code></pre> - -<p><strong>Example 4: With</strong></p> - -<p>An alternative way of writing &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent.</p> - -<p>The first example above could be simplified as:</p> - -<pre><code>{{ with .Params.title }}&lt;h4&gt;{{ . }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 5: If -&gt; Else If</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{ else if isset .Params &quot;caption&quot; }} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<h2 id="pipes:4d30d99f79bd431d57546bbed04b7347">Pipes</h2> - -<p>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&rsquo;s output becomes the -input of the following pipe.</p> - -<p>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.</p> - -<p>A few simple examples should help convey how to use the pipe.</p> - -<p><strong>Example 1 :</strong></p> - -<pre><code>{{ if eq 1 1 }} Same {{ end }} -</code></pre> - -<p>is the same as</p> - -<pre><code>{{ eq 1 1 | if }} Same {{ end }} -</code></pre> - -<p>It does look odd to place the if at the end, but it does provide a good -illustration of how to use the pipes.</p> - -<p><strong>Example 2 :</strong></p> - -<pre><code>{{ index .Params &quot;disqus_url&quot; | html }} -</code></pre> - -<p>Access the page parameter called &ldquo;disqus_url&rdquo; and escape the HTML.</p> - -<p><strong>Example 3 :</strong></p> - -<pre><code>{{ if or (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -Stuff Here -{{ end }} -</code></pre> - -<p>Could be rewritten as</p> - -<pre><code>{{ isset .Params &quot;caption&quot; | or isset .Params &quot;title&quot; | or isset .Params &quot;attr&quot; | if }} -Stuff Here -{{ end }} -</code></pre> - -<h2 id="context-aka-the-dot:4d30d99f79bd431d57546bbed04b7347">Context (aka. the dot)</h2> - -<p>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 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 set it to a variable -instead of depending on the context.</p> - -<p><strong>Example:</strong></p> - -<pre><code> {{ $title := .Site.Title }} - {{ range .Params.tags }} - &lt;li&gt; &lt;a href=&quot;{{ $baseurl }}/tags/{{ . | urlize }}&quot;&gt;{{ . }}&lt;/a&gt; - {{ $title }} &lt;/li&gt; - {{ end }} -</code></pre> - -<p>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.</p> - -<h1 id="hugo-parameters:4d30d99f79bd431d57546bbed04b7347">Hugo Parameters</h1> - -<p>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.</p> - -<h2 id="using-content-page-parameters:4d30d99f79bd431d57546bbed04b7347">Using Content (page) Parameters</h2> - -<p>In each piece of content you can provide variables to be used by the -templates. This happens in the <a href="http://localhost:1313/content/front-matter">front matter</a>.</p> - -<p>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&rsquo;t make a lot of sense. We&rsquo;ve defined a variable in our front matter -of some pages to turn off the TOC from being displayed.</p> - -<p>Here is the example front matter:</p> - -<pre><code>--- -title: &quot;Permalinks&quot; -date: &quot;2013-11-18&quot; -aliases: - - &quot;/doc/permalinks/&quot; -groups: [&quot;extras&quot;] -groups_weight: 30 -notoc: true ---- -</code></pre> - -<p>Here is the corresponding code inside of the template:</p> - -<pre><code> {{ if not .Params.notoc }} - &lt;div id=&quot;toc&quot; class=&quot;well col-md-4 col-sm-6&quot;&gt; - {{ .TableOfContents }} - &lt;/div&gt; - {{ end }} -</code></pre> - -<h2 id="using-site-config-parameters:4d30d99f79bd431d57546bbed04b7347">Using Site (config) Parameters</h2> - -<p>In your top-level configuration file (eg, <code>config.yaml</code>) you can define site -parameters, which are values which will be available to you in chrome.</p> - -<p>For instance, you might declare:</p> - -<pre><code class="language-yaml">params: - CopyrightHTML: &quot;Copyright &amp;#xA9; 2013 John Doe. All Rights Reserved.&quot; - TwitterUser: &quot;spf13&quot; - SidebarRecentLimit: 5 -</code></pre> - -<p>Within a footer layout, you might then declare a <code>&lt;footer&gt;</code> which is only -provided if the <code>CopyrightHTML</code> 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.</p> - -<pre><code>{{if .Site.Params.CopyrightHTML}}&lt;footer&gt; -&lt;div class=&quot;text-center&quot;&gt;{{.Site.Params.CopyrightHTML | safeHtml}}&lt;/div&gt; -&lt;/footer&gt;{{end}} -</code></pre> - -<p>An alternative way of writing the &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent:</p> - -<pre><code>{{with .Site.Params.TwitterUser}}&lt;span class=&quot;twitter&quot;&gt; -&lt;a href=&quot;https://twitter.com/{{.}}&quot; rel=&quot;author&quot;&gt; -&lt;img src=&quot;/images/twitter.png&quot; width=&quot;48&quot; height=&quot;48&quot; title=&quot;Twitter: {{.}}&quot; - alt=&quot;Twitter&quot;&gt;&lt;/a&gt; -&lt;/span&gt;{{end}} -</code></pre> - -<p>Finally, if you want to pull &ldquo;magic constants&rdquo; out of your layouts, you can do -so, such as in this example:</p> - -<pre><code>&lt;nav class=&quot;recent&quot;&gt; - &lt;h1&gt;Recent Posts&lt;/h1&gt; - &lt;ul&gt;{{range first .Site.Params.SidebarRecentLimit .Site.Recent}} - &lt;li&gt;&lt;a href=&quot;{{.RelPermalink}}&quot;&gt;{{.Title}}&lt;/a&gt;&lt;/li&gt; - {{end}}&lt;/ul&gt; -&lt;/nav&gt; -</code></pre> - - - - - Getting Started with Hugo - http://localhost:1313/post/hugoisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/hugoisforlovers/ - - -<h2 id="step-1-install-hugo:c57cc0038c788519b441e0331c8bebc7">Step 1. Install Hugo</h2> - -<p>Goto <a href="https://github.com/spf13/hugo/releases">hugo releases</a> and download the -appropriate version for your os and architecture.</p> - -<p>Save it somewhere specific as we will be using it in the next step.</p> - -<p>More complete instructions are available at <a href="http://localhost:1313/overview/installing/">installing hugo</a></p> - -<h2 id="step-2-build-the-docs:c57cc0038c788519b441e0331c8bebc7">Step 2. Build the Docs</h2> - -<p>Hugo has its own example site which happens to also be the documentation site -you are reading right now.</p> - -<p>Follow the following steps:</p> - -<ol> -<li>Clone the <a href="http://github.com/spf13/hugo">hugo repository</a></li> -<li>Go into the repo</li> -<li>Run hugo in server mode and build the docs</li> -<li>Open your browser to <a href="http://localhost:1313">http://localhost:1313</a></li> -</ol> - -<p>Corresponding pseudo commands:</p> - -<pre><code>git clone https://github.com/spf13/hugo -cd hugo -/path/to/where/you/installed/hugo server --source=./docs -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Press ctrl+c to stop -</code></pre> - -<p>Once you&rsquo;ve gotten here, follow along the rest of this page on your local build.</p> - -<h2 id="step-3-change-the-docs-site:c57cc0038c788519b441e0331c8bebc7">Step 3. Change the docs site</h2> - -<p>Stop the Hugo process by hitting ctrl+c.</p> - -<p>Now we are going to run hugo again, but this time with hugo in watch mode.</p> - -<pre><code>/path/to/hugo/from/step/1/hugo server --source=./docs --watch -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Watching for changes in /Users/spf13/Code/hugo/docs/content -&gt; Press ctrl+c to stop -</code></pre> - -<p>Open your <a href="http://vim.spf13.com">favorite editor</a> and change one of the source -content pages. How about changing this very file to <em>fix the typo</em>. How about changing this very file to <em>fix the typo</em>.</p> - -<p>Content files are found in <code>docs/content/</code>. Unless otherwise specified, files -are located at the same relative location as the url, in our case -<code>docs/content/overview/quickstart.md</code>.</p> - -<p>Change and save this file.. Notice what happened in your terminal.</p> - -<pre><code>&gt; Change detected, rebuilding site - -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 26 ms -</code></pre> - -<p>Refresh the browser and observe that the typo is now fixed.</p> - -<p>Notice how quick that was. Try to refresh the site before it&rsquo;s finished building.. I double dare you. -Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.</p> - -<h2 id="step-4-have-fun:c57cc0038c788519b441e0331c8bebc7">Step 4. Have fun</h2> - -<p>The best way to learn something is to play with it.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/tags/go/index.html b/exampleSite/public/tags/go/index.html deleted file mode 100644 index 994250d..0000000 --- a/exampleSite/public/tags/go/index.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - - Go · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - Go - -
    - - - -
  • -
    Apr 2, 2014
    -
    (Hu)go Template Primer
     -
    • - - -
  • -
    Apr 2, 2014
    -
    Getting Started with Hugo
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/tags/go/index.xml b/exampleSite/public/tags/go/index.xml deleted file mode 100644 index 5c52f74..0000000 --- a/exampleSite/public/tags/go/index.xml +++ /dev/null @@ -1,446 +0,0 @@ - - - - Go on Hugo Themes - http://localhost:1313/tags/go/ - Recent content in Go on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - (Hu)go Template Primer - http://localhost:1313/post/goisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/goisforlovers/ - - -<p>Hugo uses the excellent <a href="http://golang.org/&gt;">go</a> <a href="http://golang.org/pkg/html/template/&gt;">html/template</a> library for -its template engine. It is an extremely lightweight engine that provides a very -small amount of logic. In our experience that 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.</p> - -<p>This document is a brief primer on using go templates. The <a href="http://golang.org/pkg/html/template/&gt;">go docs</a> -provide more details.</p> - -<h2 id="introduction-to-go-templates:4d30d99f79bd431d57546bbed04b7347">Introduction to Go Templates</h2> - -<p>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.</p> - -<p>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 <a href="http://golang.org/pkg/html/template/&gt;">go docs</a>.</p> - -<h2 id="basic-syntax:4d30d99f79bd431d57546bbed04b7347">Basic Syntax</h2> - -<p>Go lang templates are html files with the addition of variables and -functions.</p> - -<p><strong>Go variables and functions are accessible within {{ }}</strong></p> - -<p>Accessing a predefined variable &ldquo;foo&rdquo;:</p> - -<pre><code>{{ foo }} -</code></pre> - -<p><strong>Parameters are separated using spaces</strong></p> - -<p>Calling the add function with input of 1, 2:</p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<p><strong>Methods and fields are accessed via dot notation</strong></p> - -<p>Accessing the Page Parameter &ldquo;bar&rdquo;</p> - -<pre><code>{{ .Params.bar }} -</code></pre> - -<p><strong>Parentheses can be used to group items together</strong></p> - -<pre><code>{{ if or (isset .Params &quot;alt&quot;) (isset .Params &quot;caption&quot;) }} Caption {{ end }} -</code></pre> - -<h2 id="variables:4d30d99f79bd431d57546bbed04b7347">Variables</h2> - -<p>Each go template has a struct (object) made available to it. In hugo each -template is passed either a page or a node struct depending on which type of -page you are rendering. More details are available on the -<a href="http://localhost:1313/layout/variables">variables</a> page.</p> - -<p>A variable is accessed by referencing the variable name.</p> - -<pre><code>&lt;title&gt;{{ .Title }}&lt;/title&gt; -</code></pre> - -<p>Variables can also be defined and referenced.</p> - -<pre><code>{{ $address := &quot;123 Main St.&quot;}} -{{ $address }} -</code></pre> - -<h2 id="functions:4d30d99f79bd431d57546bbed04b7347">Functions</h2> - -<p>Go template ship 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. <a href="http://localhost:1313/layout/functions">Hugo template -functions</a> 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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<h2 id="includes:4d30d99f79bd431d57546bbed04b7347">Includes</h2> - -<p>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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ template &quot;chrome/header.html&quot; . }} -</code></pre> - -<h2 id="logic:4d30d99f79bd431d57546bbed04b7347">Logic</h2> - -<p>Go templates provide the most basic iteration and conditional logic.</p> - -<h3 id="iteration:4d30d99f79bd431d57546bbed04b7347">Iteration</h3> - -<p>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.</p> - -<p><strong>Example 1: Using Context</strong></p> - -<pre><code>{{ range array }} - {{ . }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring value variable name</strong></p> - -<pre><code>{{range $element := array}} - {{ $element }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring key and value variable name</strong></p> - -<pre><code>{{range $index, $element := array}} - {{ $index }} - {{ $element }} -{{ end }} -</code></pre> - -<h3 id="conditionals:4d30d99f79bd431d57546bbed04b7347">Conditionals</h3> - -<p>If, else, with, or, &amp; and provide the framework for handling conditional -logic in Go Templates. Like range, each statement is closed with <code>end</code>.</p> - -<p>Go Templates treat the following values as false:</p> - -<ul> -<li>false</li> -<li>0</li> -<li>any array, slice, map, or string of length zero</li> -</ul> - -<p><strong>Example 1: If</strong></p> - -<pre><code>{{ if isset .Params &quot;title&quot; }}&lt;h4&gt;{{ index .Params &quot;title&quot; }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 2: If -&gt; Else</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{else}} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<p><strong>Example 3: And &amp; Or</strong></p> - -<pre><code>{{ if and (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -</code></pre> - -<p><strong>Example 4: With</strong></p> - -<p>An alternative way of writing &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent.</p> - -<p>The first example above could be simplified as:</p> - -<pre><code>{{ with .Params.title }}&lt;h4&gt;{{ . }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 5: If -&gt; Else If</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{ else if isset .Params &quot;caption&quot; }} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<h2 id="pipes:4d30d99f79bd431d57546bbed04b7347">Pipes</h2> - -<p>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&rsquo;s output becomes the -input of the following pipe.</p> - -<p>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.</p> - -<p>A few simple examples should help convey how to use the pipe.</p> - -<p><strong>Example 1 :</strong></p> - -<pre><code>{{ if eq 1 1 }} Same {{ end }} -</code></pre> - -<p>is the same as</p> - -<pre><code>{{ eq 1 1 | if }} Same {{ end }} -</code></pre> - -<p>It does look odd to place the if at the end, but it does provide a good -illustration of how to use the pipes.</p> - -<p><strong>Example 2 :</strong></p> - -<pre><code>{{ index .Params &quot;disqus_url&quot; | html }} -</code></pre> - -<p>Access the page parameter called &ldquo;disqus_url&rdquo; and escape the HTML.</p> - -<p><strong>Example 3 :</strong></p> - -<pre><code>{{ if or (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -Stuff Here -{{ end }} -</code></pre> - -<p>Could be rewritten as</p> - -<pre><code>{{ isset .Params &quot;caption&quot; | or isset .Params &quot;title&quot; | or isset .Params &quot;attr&quot; | if }} -Stuff Here -{{ end }} -</code></pre> - -<h2 id="context-aka-the-dot:4d30d99f79bd431d57546bbed04b7347">Context (aka. the dot)</h2> - -<p>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 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 set it to a variable -instead of depending on the context.</p> - -<p><strong>Example:</strong></p> - -<pre><code> {{ $title := .Site.Title }} - {{ range .Params.tags }} - &lt;li&gt; &lt;a href=&quot;{{ $baseurl }}/tags/{{ . | urlize }}&quot;&gt;{{ . }}&lt;/a&gt; - {{ $title }} &lt;/li&gt; - {{ end }} -</code></pre> - -<p>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.</p> - -<h1 id="hugo-parameters:4d30d99f79bd431d57546bbed04b7347">Hugo Parameters</h1> - -<p>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.</p> - -<h2 id="using-content-page-parameters:4d30d99f79bd431d57546bbed04b7347">Using Content (page) Parameters</h2> - -<p>In each piece of content you can provide variables to be used by the -templates. This happens in the <a href="http://localhost:1313/content/front-matter">front matter</a>.</p> - -<p>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&rsquo;t make a lot of sense. We&rsquo;ve defined a variable in our front matter -of some pages to turn off the TOC from being displayed.</p> - -<p>Here is the example front matter:</p> - -<pre><code>--- -title: &quot;Permalinks&quot; -date: &quot;2013-11-18&quot; -aliases: - - &quot;/doc/permalinks/&quot; -groups: [&quot;extras&quot;] -groups_weight: 30 -notoc: true ---- -</code></pre> - -<p>Here is the corresponding code inside of the template:</p> - -<pre><code> {{ if not .Params.notoc }} - &lt;div id=&quot;toc&quot; class=&quot;well col-md-4 col-sm-6&quot;&gt; - {{ .TableOfContents }} - &lt;/div&gt; - {{ end }} -</code></pre> - -<h2 id="using-site-config-parameters:4d30d99f79bd431d57546bbed04b7347">Using Site (config) Parameters</h2> - -<p>In your top-level configuration file (eg, <code>config.yaml</code>) you can define site -parameters, which are values which will be available to you in chrome.</p> - -<p>For instance, you might declare:</p> - -<pre><code class="language-yaml">params: - CopyrightHTML: &quot;Copyright &amp;#xA9; 2013 John Doe. All Rights Reserved.&quot; - TwitterUser: &quot;spf13&quot; - SidebarRecentLimit: 5 -</code></pre> - -<p>Within a footer layout, you might then declare a <code>&lt;footer&gt;</code> which is only -provided if the <code>CopyrightHTML</code> 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.</p> - -<pre><code>{{if .Site.Params.CopyrightHTML}}&lt;footer&gt; -&lt;div class=&quot;text-center&quot;&gt;{{.Site.Params.CopyrightHTML | safeHtml}}&lt;/div&gt; -&lt;/footer&gt;{{end}} -</code></pre> - -<p>An alternative way of writing the &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent:</p> - -<pre><code>{{with .Site.Params.TwitterUser}}&lt;span class=&quot;twitter&quot;&gt; -&lt;a href=&quot;https://twitter.com/{{.}}&quot; rel=&quot;author&quot;&gt; -&lt;img src=&quot;/images/twitter.png&quot; width=&quot;48&quot; height=&quot;48&quot; title=&quot;Twitter: {{.}}&quot; - alt=&quot;Twitter&quot;&gt;&lt;/a&gt; -&lt;/span&gt;{{end}} -</code></pre> - -<p>Finally, if you want to pull &ldquo;magic constants&rdquo; out of your layouts, you can do -so, such as in this example:</p> - -<pre><code>&lt;nav class=&quot;recent&quot;&gt; - &lt;h1&gt;Recent Posts&lt;/h1&gt; - &lt;ul&gt;{{range first .Site.Params.SidebarRecentLimit .Site.Recent}} - &lt;li&gt;&lt;a href=&quot;{{.RelPermalink}}&quot;&gt;{{.Title}}&lt;/a&gt;&lt;/li&gt; - {{end}}&lt;/ul&gt; -&lt;/nav&gt; -</code></pre> - - - - - Getting Started with Hugo - http://localhost:1313/post/hugoisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/hugoisforlovers/ - - -<h2 id="step-1-install-hugo:c57cc0038c788519b441e0331c8bebc7">Step 1. Install Hugo</h2> - -<p>Goto <a href="https://github.com/spf13/hugo/releases">hugo releases</a> and download the -appropriate version for your os and architecture.</p> - -<p>Save it somewhere specific as we will be using it in the next step.</p> - -<p>More complete instructions are available at <a href="http://localhost:1313/overview/installing/">installing hugo</a></p> - -<h2 id="step-2-build-the-docs:c57cc0038c788519b441e0331c8bebc7">Step 2. Build the Docs</h2> - -<p>Hugo has its own example site which happens to also be the documentation site -you are reading right now.</p> - -<p>Follow the following steps:</p> - -<ol> -<li>Clone the <a href="http://github.com/spf13/hugo">hugo repository</a></li> -<li>Go into the repo</li> -<li>Run hugo in server mode and build the docs</li> -<li>Open your browser to <a href="http://localhost:1313">http://localhost:1313</a></li> -</ol> - -<p>Corresponding pseudo commands:</p> - -<pre><code>git clone https://github.com/spf13/hugo -cd hugo -/path/to/where/you/installed/hugo server --source=./docs -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Press ctrl+c to stop -</code></pre> - -<p>Once you&rsquo;ve gotten here, follow along the rest of this page on your local build.</p> - -<h2 id="step-3-change-the-docs-site:c57cc0038c788519b441e0331c8bebc7">Step 3. Change the docs site</h2> - -<p>Stop the Hugo process by hitting ctrl+c.</p> - -<p>Now we are going to run hugo again, but this time with hugo in watch mode.</p> - -<pre><code>/path/to/hugo/from/step/1/hugo server --source=./docs --watch -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Watching for changes in /Users/spf13/Code/hugo/docs/content -&gt; Press ctrl+c to stop -</code></pre> - -<p>Open your <a href="http://vim.spf13.com">favorite editor</a> and change one of the source -content pages. How about changing this very file to <em>fix the typo</em>. How about changing this very file to <em>fix the typo</em>.</p> - -<p>Content files are found in <code>docs/content/</code>. Unless otherwise specified, files -are located at the same relative location as the url, in our case -<code>docs/content/overview/quickstart.md</code>.</p> - -<p>Change and save this file.. Notice what happened in your terminal.</p> - -<pre><code>&gt; Change detected, rebuilding site - -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 26 ms -</code></pre> - -<p>Refresh the browser and observe that the typo is now fixed.</p> - -<p>Notice how quick that was. Try to refresh the site before it&rsquo;s finished building.. I double dare you. -Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.</p> - -<h2 id="step-4-have-fun:c57cc0038c788519b441e0331c8bebc7">Step 4. Have fun</h2> - -<p>The best way to learn something is to play with it.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/tags/golang/index.html b/exampleSite/public/tags/golang/index.html deleted file mode 100644 index dab6cf9..0000000 --- a/exampleSite/public/tags/golang/index.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - - - - - - - - Golang · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - Golang - -
    - - - -
  • -
    Apr 2, 2014
    -
    (Hu)go Template Primer
     -
    • - - -
  • -
    Apr 2, 2014
    -
    Getting Started with Hugo
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/tags/golang/index.xml b/exampleSite/public/tags/golang/index.xml deleted file mode 100644 index 4d3c51e..0000000 --- a/exampleSite/public/tags/golang/index.xml +++ /dev/null @@ -1,446 +0,0 @@ - - - - Golang on Hugo Themes - http://localhost:1313/tags/golang/ - Recent content in Golang on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - (Hu)go Template Primer - http://localhost:1313/post/goisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/goisforlovers/ - - -<p>Hugo uses the excellent <a href="http://golang.org/&gt;">go</a> <a href="http://golang.org/pkg/html/template/&gt;">html/template</a> library for -its template engine. It is an extremely lightweight engine that provides a very -small amount of logic. In our experience that 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.</p> - -<p>This document is a brief primer on using go templates. The <a href="http://golang.org/pkg/html/template/&gt;">go docs</a> -provide more details.</p> - -<h2 id="introduction-to-go-templates:4d30d99f79bd431d57546bbed04b7347">Introduction to Go Templates</h2> - -<p>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.</p> - -<p>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 <a href="http://golang.org/pkg/html/template/&gt;">go docs</a>.</p> - -<h2 id="basic-syntax:4d30d99f79bd431d57546bbed04b7347">Basic Syntax</h2> - -<p>Go lang templates are html files with the addition of variables and -functions.</p> - -<p><strong>Go variables and functions are accessible within {{ }}</strong></p> - -<p>Accessing a predefined variable &ldquo;foo&rdquo;:</p> - -<pre><code>{{ foo }} -</code></pre> - -<p><strong>Parameters are separated using spaces</strong></p> - -<p>Calling the add function with input of 1, 2:</p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<p><strong>Methods and fields are accessed via dot notation</strong></p> - -<p>Accessing the Page Parameter &ldquo;bar&rdquo;</p> - -<pre><code>{{ .Params.bar }} -</code></pre> - -<p><strong>Parentheses can be used to group items together</strong></p> - -<pre><code>{{ if or (isset .Params &quot;alt&quot;) (isset .Params &quot;caption&quot;) }} Caption {{ end }} -</code></pre> - -<h2 id="variables:4d30d99f79bd431d57546bbed04b7347">Variables</h2> - -<p>Each go template has a struct (object) made available to it. In hugo each -template is passed either a page or a node struct depending on which type of -page you are rendering. More details are available on the -<a href="http://localhost:1313/layout/variables">variables</a> page.</p> - -<p>A variable is accessed by referencing the variable name.</p> - -<pre><code>&lt;title&gt;{{ .Title }}&lt;/title&gt; -</code></pre> - -<p>Variables can also be defined and referenced.</p> - -<pre><code>{{ $address := &quot;123 Main St.&quot;}} -{{ $address }} -</code></pre> - -<h2 id="functions:4d30d99f79bd431d57546bbed04b7347">Functions</h2> - -<p>Go template ship 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. <a href="http://localhost:1313/layout/functions">Hugo template -functions</a> 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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<h2 id="includes:4d30d99f79bd431d57546bbed04b7347">Includes</h2> - -<p>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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ template &quot;chrome/header.html&quot; . }} -</code></pre> - -<h2 id="logic:4d30d99f79bd431d57546bbed04b7347">Logic</h2> - -<p>Go templates provide the most basic iteration and conditional logic.</p> - -<h3 id="iteration:4d30d99f79bd431d57546bbed04b7347">Iteration</h3> - -<p>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.</p> - -<p><strong>Example 1: Using Context</strong></p> - -<pre><code>{{ range array }} - {{ . }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring value variable name</strong></p> - -<pre><code>{{range $element := array}} - {{ $element }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring key and value variable name</strong></p> - -<pre><code>{{range $index, $element := array}} - {{ $index }} - {{ $element }} -{{ end }} -</code></pre> - -<h3 id="conditionals:4d30d99f79bd431d57546bbed04b7347">Conditionals</h3> - -<p>If, else, with, or, &amp; and provide the framework for handling conditional -logic in Go Templates. Like range, each statement is closed with <code>end</code>.</p> - -<p>Go Templates treat the following values as false:</p> - -<ul> -<li>false</li> -<li>0</li> -<li>any array, slice, map, or string of length zero</li> -</ul> - -<p><strong>Example 1: If</strong></p> - -<pre><code>{{ if isset .Params &quot;title&quot; }}&lt;h4&gt;{{ index .Params &quot;title&quot; }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 2: If -&gt; Else</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{else}} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<p><strong>Example 3: And &amp; Or</strong></p> - -<pre><code>{{ if and (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -</code></pre> - -<p><strong>Example 4: With</strong></p> - -<p>An alternative way of writing &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent.</p> - -<p>The first example above could be simplified as:</p> - -<pre><code>{{ with .Params.title }}&lt;h4&gt;{{ . }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 5: If -&gt; Else If</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{ else if isset .Params &quot;caption&quot; }} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<h2 id="pipes:4d30d99f79bd431d57546bbed04b7347">Pipes</h2> - -<p>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&rsquo;s output becomes the -input of the following pipe.</p> - -<p>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.</p> - -<p>A few simple examples should help convey how to use the pipe.</p> - -<p><strong>Example 1 :</strong></p> - -<pre><code>{{ if eq 1 1 }} Same {{ end }} -</code></pre> - -<p>is the same as</p> - -<pre><code>{{ eq 1 1 | if }} Same {{ end }} -</code></pre> - -<p>It does look odd to place the if at the end, but it does provide a good -illustration of how to use the pipes.</p> - -<p><strong>Example 2 :</strong></p> - -<pre><code>{{ index .Params &quot;disqus_url&quot; | html }} -</code></pre> - -<p>Access the page parameter called &ldquo;disqus_url&rdquo; and escape the HTML.</p> - -<p><strong>Example 3 :</strong></p> - -<pre><code>{{ if or (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -Stuff Here -{{ end }} -</code></pre> - -<p>Could be rewritten as</p> - -<pre><code>{{ isset .Params &quot;caption&quot; | or isset .Params &quot;title&quot; | or isset .Params &quot;attr&quot; | if }} -Stuff Here -{{ end }} -</code></pre> - -<h2 id="context-aka-the-dot:4d30d99f79bd431d57546bbed04b7347">Context (aka. the dot)</h2> - -<p>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 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 set it to a variable -instead of depending on the context.</p> - -<p><strong>Example:</strong></p> - -<pre><code> {{ $title := .Site.Title }} - {{ range .Params.tags }} - &lt;li&gt; &lt;a href=&quot;{{ $baseurl }}/tags/{{ . | urlize }}&quot;&gt;{{ . }}&lt;/a&gt; - {{ $title }} &lt;/li&gt; - {{ end }} -</code></pre> - -<p>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.</p> - -<h1 id="hugo-parameters:4d30d99f79bd431d57546bbed04b7347">Hugo Parameters</h1> - -<p>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.</p> - -<h2 id="using-content-page-parameters:4d30d99f79bd431d57546bbed04b7347">Using Content (page) Parameters</h2> - -<p>In each piece of content you can provide variables to be used by the -templates. This happens in the <a href="http://localhost:1313/content/front-matter">front matter</a>.</p> - -<p>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&rsquo;t make a lot of sense. We&rsquo;ve defined a variable in our front matter -of some pages to turn off the TOC from being displayed.</p> - -<p>Here is the example front matter:</p> - -<pre><code>--- -title: &quot;Permalinks&quot; -date: &quot;2013-11-18&quot; -aliases: - - &quot;/doc/permalinks/&quot; -groups: [&quot;extras&quot;] -groups_weight: 30 -notoc: true ---- -</code></pre> - -<p>Here is the corresponding code inside of the template:</p> - -<pre><code> {{ if not .Params.notoc }} - &lt;div id=&quot;toc&quot; class=&quot;well col-md-4 col-sm-6&quot;&gt; - {{ .TableOfContents }} - &lt;/div&gt; - {{ end }} -</code></pre> - -<h2 id="using-site-config-parameters:4d30d99f79bd431d57546bbed04b7347">Using Site (config) Parameters</h2> - -<p>In your top-level configuration file (eg, <code>config.yaml</code>) you can define site -parameters, which are values which will be available to you in chrome.</p> - -<p>For instance, you might declare:</p> - -<pre><code class="language-yaml">params: - CopyrightHTML: &quot;Copyright &amp;#xA9; 2013 John Doe. All Rights Reserved.&quot; - TwitterUser: &quot;spf13&quot; - SidebarRecentLimit: 5 -</code></pre> - -<p>Within a footer layout, you might then declare a <code>&lt;footer&gt;</code> which is only -provided if the <code>CopyrightHTML</code> 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.</p> - -<pre><code>{{if .Site.Params.CopyrightHTML}}&lt;footer&gt; -&lt;div class=&quot;text-center&quot;&gt;{{.Site.Params.CopyrightHTML | safeHtml}}&lt;/div&gt; -&lt;/footer&gt;{{end}} -</code></pre> - -<p>An alternative way of writing the &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent:</p> - -<pre><code>{{with .Site.Params.TwitterUser}}&lt;span class=&quot;twitter&quot;&gt; -&lt;a href=&quot;https://twitter.com/{{.}}&quot; rel=&quot;author&quot;&gt; -&lt;img src=&quot;/images/twitter.png&quot; width=&quot;48&quot; height=&quot;48&quot; title=&quot;Twitter: {{.}}&quot; - alt=&quot;Twitter&quot;&gt;&lt;/a&gt; -&lt;/span&gt;{{end}} -</code></pre> - -<p>Finally, if you want to pull &ldquo;magic constants&rdquo; out of your layouts, you can do -so, such as in this example:</p> - -<pre><code>&lt;nav class=&quot;recent&quot;&gt; - &lt;h1&gt;Recent Posts&lt;/h1&gt; - &lt;ul&gt;{{range first .Site.Params.SidebarRecentLimit .Site.Recent}} - &lt;li&gt;&lt;a href=&quot;{{.RelPermalink}}&quot;&gt;{{.Title}}&lt;/a&gt;&lt;/li&gt; - {{end}}&lt;/ul&gt; -&lt;/nav&gt; -</code></pre> - - - - - Getting Started with Hugo - http://localhost:1313/post/hugoisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/hugoisforlovers/ - - -<h2 id="step-1-install-hugo:c57cc0038c788519b441e0331c8bebc7">Step 1. Install Hugo</h2> - -<p>Goto <a href="https://github.com/spf13/hugo/releases">hugo releases</a> and download the -appropriate version for your os and architecture.</p> - -<p>Save it somewhere specific as we will be using it in the next step.</p> - -<p>More complete instructions are available at <a href="http://localhost:1313/overview/installing/">installing hugo</a></p> - -<h2 id="step-2-build-the-docs:c57cc0038c788519b441e0331c8bebc7">Step 2. Build the Docs</h2> - -<p>Hugo has its own example site which happens to also be the documentation site -you are reading right now.</p> - -<p>Follow the following steps:</p> - -<ol> -<li>Clone the <a href="http://github.com/spf13/hugo">hugo repository</a></li> -<li>Go into the repo</li> -<li>Run hugo in server mode and build the docs</li> -<li>Open your browser to <a href="http://localhost:1313">http://localhost:1313</a></li> -</ol> - -<p>Corresponding pseudo commands:</p> - -<pre><code>git clone https://github.com/spf13/hugo -cd hugo -/path/to/where/you/installed/hugo server --source=./docs -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Press ctrl+c to stop -</code></pre> - -<p>Once you&rsquo;ve gotten here, follow along the rest of this page on your local build.</p> - -<h2 id="step-3-change-the-docs-site:c57cc0038c788519b441e0331c8bebc7">Step 3. Change the docs site</h2> - -<p>Stop the Hugo process by hitting ctrl+c.</p> - -<p>Now we are going to run hugo again, but this time with hugo in watch mode.</p> - -<pre><code>/path/to/hugo/from/step/1/hugo server --source=./docs --watch -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Watching for changes in /Users/spf13/Code/hugo/docs/content -&gt; Press ctrl+c to stop -</code></pre> - -<p>Open your <a href="http://vim.spf13.com">favorite editor</a> and change one of the source -content pages. How about changing this very file to <em>fix the typo</em>. How about changing this very file to <em>fix the typo</em>.</p> - -<p>Content files are found in <code>docs/content/</code>. Unless otherwise specified, files -are located at the same relative location as the url, in our case -<code>docs/content/overview/quickstart.md</code>.</p> - -<p>Change and save this file.. Notice what happened in your terminal.</p> - -<pre><code>&gt; Change detected, rebuilding site - -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 26 ms -</code></pre> - -<p>Refresh the browser and observe that the typo is now fixed.</p> - -<p>Notice how quick that was. Try to refresh the site before it&rsquo;s finished building.. I double dare you. -Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.</p> - -<h2 id="step-4-have-fun:c57cc0038c788519b441e0331c8bebc7">Step 4. Have fun</h2> - -<p>The best way to learn something is to play with it.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/tags/hugo/index.html b/exampleSite/public/tags/hugo/index.html deleted file mode 100644 index 5eadc84..0000000 --- a/exampleSite/public/tags/hugo/index.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - - - - - - - - - - - Hugo · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - Hugo - -
    - - - -
  • -
    Apr 2, 2014
    -
    Getting Started with Hugo
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/tags/hugo/index.xml b/exampleSite/public/tags/hugo/index.xml deleted file mode 100644 index ad23bb4..0000000 --- a/exampleSite/public/tags/hugo/index.xml +++ /dev/null @@ -1,100 +0,0 @@ - - - - Hugo on Hugo Themes - http://localhost:1313/tags/hugo/ - Recent content in Hugo on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - Getting Started with Hugo - http://localhost:1313/post/hugoisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/hugoisforlovers/ - - -<h2 id="step-1-install-hugo:c57cc0038c788519b441e0331c8bebc7">Step 1. Install Hugo</h2> - -<p>Goto <a href="https://github.com/spf13/hugo/releases">hugo releases</a> and download the -appropriate version for your os and architecture.</p> - -<p>Save it somewhere specific as we will be using it in the next step.</p> - -<p>More complete instructions are available at <a href="http://localhost:1313/overview/installing/">installing hugo</a></p> - -<h2 id="step-2-build-the-docs:c57cc0038c788519b441e0331c8bebc7">Step 2. Build the Docs</h2> - -<p>Hugo has its own example site which happens to also be the documentation site -you are reading right now.</p> - -<p>Follow the following steps:</p> - -<ol> -<li>Clone the <a href="http://github.com/spf13/hugo">hugo repository</a></li> -<li>Go into the repo</li> -<li>Run hugo in server mode and build the docs</li> -<li>Open your browser to <a href="http://localhost:1313">http://localhost:1313</a></li> -</ol> - -<p>Corresponding pseudo commands:</p> - -<pre><code>git clone https://github.com/spf13/hugo -cd hugo -/path/to/where/you/installed/hugo server --source=./docs -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Press ctrl+c to stop -</code></pre> - -<p>Once you&rsquo;ve gotten here, follow along the rest of this page on your local build.</p> - -<h2 id="step-3-change-the-docs-site:c57cc0038c788519b441e0331c8bebc7">Step 3. Change the docs site</h2> - -<p>Stop the Hugo process by hitting ctrl+c.</p> - -<p>Now we are going to run hugo again, but this time with hugo in watch mode.</p> - -<pre><code>/path/to/hugo/from/step/1/hugo server --source=./docs --watch -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 27 ms -&gt; Web Server is available at http://localhost:1313 -&gt; Watching for changes in /Users/spf13/Code/hugo/docs/content -&gt; Press ctrl+c to stop -</code></pre> - -<p>Open your <a href="http://vim.spf13.com">favorite editor</a> and change one of the source -content pages. How about changing this very file to <em>fix the typo</em>. How about changing this very file to <em>fix the typo</em>.</p> - -<p>Content files are found in <code>docs/content/</code>. Unless otherwise specified, files -are located at the same relative location as the url, in our case -<code>docs/content/overview/quickstart.md</code>.</p> - -<p>Change and save this file.. Notice what happened in your terminal.</p> - -<pre><code>&gt; Change detected, rebuilding site - -&gt; 29 pages created -&gt; 0 tags index created -&gt; in 26 ms -</code></pre> - -<p>Refresh the browser and observe that the typo is now fixed.</p> - -<p>Notice how quick that was. Try to refresh the site before it&rsquo;s finished building.. I double dare you. -Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.</p> - -<h2 id="step-4-have-fun:c57cc0038c788519b441e0331c8bebc7">Step 4. Have fun</h2> - -<p>The best way to learn something is to play with it.</p> - - - - - \ No newline at end of file diff --git a/exampleSite/public/tags/templates/index.html b/exampleSite/public/tags/templates/index.html deleted file mode 100644 index 67df313..0000000 --- a/exampleSite/public/tags/templates/index.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - - - - - - - - - - - Templates · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - Templates - -
    - - - -
  • -
    Apr 2, 2014
    -
    (Hu)go Template Primer
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/tags/templates/index.xml b/exampleSite/public/tags/templates/index.xml deleted file mode 100644 index dd3c5bd..0000000 --- a/exampleSite/public/tags/templates/index.xml +++ /dev/null @@ -1,359 +0,0 @@ - - - - Templates on Hugo Themes - http://localhost:1313/tags/templates/ - Recent content in Templates on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - (Hu)go Template Primer - http://localhost:1313/post/goisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/goisforlovers/ - - -<p>Hugo uses the excellent <a href="http://golang.org/&gt;">go</a> <a href="http://golang.org/pkg/html/template/&gt;">html/template</a> library for -its template engine. It is an extremely lightweight engine that provides a very -small amount of logic. In our experience that 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.</p> - -<p>This document is a brief primer on using go templates. The <a href="http://golang.org/pkg/html/template/&gt;">go docs</a> -provide more details.</p> - -<h2 id="introduction-to-go-templates:4d30d99f79bd431d57546bbed04b7347">Introduction to Go Templates</h2> - -<p>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.</p> - -<p>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 <a href="http://golang.org/pkg/html/template/&gt;">go docs</a>.</p> - -<h2 id="basic-syntax:4d30d99f79bd431d57546bbed04b7347">Basic Syntax</h2> - -<p>Go lang templates are html files with the addition of variables and -functions.</p> - -<p><strong>Go variables and functions are accessible within {{ }}</strong></p> - -<p>Accessing a predefined variable &ldquo;foo&rdquo;:</p> - -<pre><code>{{ foo }} -</code></pre> - -<p><strong>Parameters are separated using spaces</strong></p> - -<p>Calling the add function with input of 1, 2:</p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<p><strong>Methods and fields are accessed via dot notation</strong></p> - -<p>Accessing the Page Parameter &ldquo;bar&rdquo;</p> - -<pre><code>{{ .Params.bar }} -</code></pre> - -<p><strong>Parentheses can be used to group items together</strong></p> - -<pre><code>{{ if or (isset .Params &quot;alt&quot;) (isset .Params &quot;caption&quot;) }} Caption {{ end }} -</code></pre> - -<h2 id="variables:4d30d99f79bd431d57546bbed04b7347">Variables</h2> - -<p>Each go template has a struct (object) made available to it. In hugo each -template is passed either a page or a node struct depending on which type of -page you are rendering. More details are available on the -<a href="http://localhost:1313/layout/variables">variables</a> page.</p> - -<p>A variable is accessed by referencing the variable name.</p> - -<pre><code>&lt;title&gt;{{ .Title }}&lt;/title&gt; -</code></pre> - -<p>Variables can also be defined and referenced.</p> - -<pre><code>{{ $address := &quot;123 Main St.&quot;}} -{{ $address }} -</code></pre> - -<h2 id="functions:4d30d99f79bd431d57546bbed04b7347">Functions</h2> - -<p>Go template ship 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. <a href="http://localhost:1313/layout/functions">Hugo template -functions</a> 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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<h2 id="includes:4d30d99f79bd431d57546bbed04b7347">Includes</h2> - -<p>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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ template &quot;chrome/header.html&quot; . }} -</code></pre> - -<h2 id="logic:4d30d99f79bd431d57546bbed04b7347">Logic</h2> - -<p>Go templates provide the most basic iteration and conditional logic.</p> - -<h3 id="iteration:4d30d99f79bd431d57546bbed04b7347">Iteration</h3> - -<p>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.</p> - -<p><strong>Example 1: Using Context</strong></p> - -<pre><code>{{ range array }} - {{ . }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring value variable name</strong></p> - -<pre><code>{{range $element := array}} - {{ $element }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring key and value variable name</strong></p> - -<pre><code>{{range $index, $element := array}} - {{ $index }} - {{ $element }} -{{ end }} -</code></pre> - -<h3 id="conditionals:4d30d99f79bd431d57546bbed04b7347">Conditionals</h3> - -<p>If, else, with, or, &amp; and provide the framework for handling conditional -logic in Go Templates. Like range, each statement is closed with <code>end</code>.</p> - -<p>Go Templates treat the following values as false:</p> - -<ul> -<li>false</li> -<li>0</li> -<li>any array, slice, map, or string of length zero</li> -</ul> - -<p><strong>Example 1: If</strong></p> - -<pre><code>{{ if isset .Params &quot;title&quot; }}&lt;h4&gt;{{ index .Params &quot;title&quot; }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 2: If -&gt; Else</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{else}} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<p><strong>Example 3: And &amp; Or</strong></p> - -<pre><code>{{ if and (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -</code></pre> - -<p><strong>Example 4: With</strong></p> - -<p>An alternative way of writing &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent.</p> - -<p>The first example above could be simplified as:</p> - -<pre><code>{{ with .Params.title }}&lt;h4&gt;{{ . }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 5: If -&gt; Else If</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{ else if isset .Params &quot;caption&quot; }} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<h2 id="pipes:4d30d99f79bd431d57546bbed04b7347">Pipes</h2> - -<p>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&rsquo;s output becomes the -input of the following pipe.</p> - -<p>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.</p> - -<p>A few simple examples should help convey how to use the pipe.</p> - -<p><strong>Example 1 :</strong></p> - -<pre><code>{{ if eq 1 1 }} Same {{ end }} -</code></pre> - -<p>is the same as</p> - -<pre><code>{{ eq 1 1 | if }} Same {{ end }} -</code></pre> - -<p>It does look odd to place the if at the end, but it does provide a good -illustration of how to use the pipes.</p> - -<p><strong>Example 2 :</strong></p> - -<pre><code>{{ index .Params &quot;disqus_url&quot; | html }} -</code></pre> - -<p>Access the page parameter called &ldquo;disqus_url&rdquo; and escape the HTML.</p> - -<p><strong>Example 3 :</strong></p> - -<pre><code>{{ if or (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -Stuff Here -{{ end }} -</code></pre> - -<p>Could be rewritten as</p> - -<pre><code>{{ isset .Params &quot;caption&quot; | or isset .Params &quot;title&quot; | or isset .Params &quot;attr&quot; | if }} -Stuff Here -{{ end }} -</code></pre> - -<h2 id="context-aka-the-dot:4d30d99f79bd431d57546bbed04b7347">Context (aka. the dot)</h2> - -<p>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 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 set it to a variable -instead of depending on the context.</p> - -<p><strong>Example:</strong></p> - -<pre><code> {{ $title := .Site.Title }} - {{ range .Params.tags }} - &lt;li&gt; &lt;a href=&quot;{{ $baseurl }}/tags/{{ . | urlize }}&quot;&gt;{{ . }}&lt;/a&gt; - {{ $title }} &lt;/li&gt; - {{ end }} -</code></pre> - -<p>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.</p> - -<h1 id="hugo-parameters:4d30d99f79bd431d57546bbed04b7347">Hugo Parameters</h1> - -<p>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.</p> - -<h2 id="using-content-page-parameters:4d30d99f79bd431d57546bbed04b7347">Using Content (page) Parameters</h2> - -<p>In each piece of content you can provide variables to be used by the -templates. This happens in the <a href="http://localhost:1313/content/front-matter">front matter</a>.</p> - -<p>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&rsquo;t make a lot of sense. We&rsquo;ve defined a variable in our front matter -of some pages to turn off the TOC from being displayed.</p> - -<p>Here is the example front matter:</p> - -<pre><code>--- -title: &quot;Permalinks&quot; -date: &quot;2013-11-18&quot; -aliases: - - &quot;/doc/permalinks/&quot; -groups: [&quot;extras&quot;] -groups_weight: 30 -notoc: true ---- -</code></pre> - -<p>Here is the corresponding code inside of the template:</p> - -<pre><code> {{ if not .Params.notoc }} - &lt;div id=&quot;toc&quot; class=&quot;well col-md-4 col-sm-6&quot;&gt; - {{ .TableOfContents }} - &lt;/div&gt; - {{ end }} -</code></pre> - -<h2 id="using-site-config-parameters:4d30d99f79bd431d57546bbed04b7347">Using Site (config) Parameters</h2> - -<p>In your top-level configuration file (eg, <code>config.yaml</code>) you can define site -parameters, which are values which will be available to you in chrome.</p> - -<p>For instance, you might declare:</p> - -<pre><code class="language-yaml">params: - CopyrightHTML: &quot;Copyright &amp;#xA9; 2013 John Doe. All Rights Reserved.&quot; - TwitterUser: &quot;spf13&quot; - SidebarRecentLimit: 5 -</code></pre> - -<p>Within a footer layout, you might then declare a <code>&lt;footer&gt;</code> which is only -provided if the <code>CopyrightHTML</code> 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.</p> - -<pre><code>{{if .Site.Params.CopyrightHTML}}&lt;footer&gt; -&lt;div class=&quot;text-center&quot;&gt;{{.Site.Params.CopyrightHTML | safeHtml}}&lt;/div&gt; -&lt;/footer&gt;{{end}} -</code></pre> - -<p>An alternative way of writing the &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent:</p> - -<pre><code>{{with .Site.Params.TwitterUser}}&lt;span class=&quot;twitter&quot;&gt; -&lt;a href=&quot;https://twitter.com/{{.}}&quot; rel=&quot;author&quot;&gt; -&lt;img src=&quot;/images/twitter.png&quot; width=&quot;48&quot; height=&quot;48&quot; title=&quot;Twitter: {{.}}&quot; - alt=&quot;Twitter&quot;&gt;&lt;/a&gt; -&lt;/span&gt;{{end}} -</code></pre> - -<p>Finally, if you want to pull &ldquo;magic constants&rdquo; out of your layouts, you can do -so, such as in this example:</p> - -<pre><code>&lt;nav class=&quot;recent&quot;&gt; - &lt;h1&gt;Recent Posts&lt;/h1&gt; - &lt;ul&gt;{{range first .Site.Params.SidebarRecentLimit .Site.Recent}} - &lt;li&gt;&lt;a href=&quot;{{.RelPermalink}}&quot;&gt;{{.Title}}&lt;/a&gt;&lt;/li&gt; - {{end}}&lt;/ul&gt; -&lt;/nav&gt; -</code></pre> - - - - - \ No newline at end of file diff --git a/exampleSite/public/tags/themes/index.html b/exampleSite/public/tags/themes/index.html deleted file mode 100644 index 7957978..0000000 --- a/exampleSite/public/tags/themes/index.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - - - - - - - - - - - Themes · Hugo Themes - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    map[]
     -
    -
    -
    - -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -
    -
    - -
    -
    -
    -
    - - Themes - -
    - - - -
  • -
    Apr 2, 2014
    -
    (Hu)go Template Primer
     -
    • - - -
    -
    -
    - - - - - - - - - - - diff --git a/exampleSite/public/tags/themes/index.xml b/exampleSite/public/tags/themes/index.xml deleted file mode 100644 index 8976262..0000000 --- a/exampleSite/public/tags/themes/index.xml +++ /dev/null @@ -1,359 +0,0 @@ - - - - Themes on Hugo Themes - http://localhost:1313/tags/themes/ - Recent content in Themes on Hugo Themes - Hugo -- gohugo.io - en-US - Wed, 02 Apr 2014 00:00:00 +0000 - - - - (Hu)go Template Primer - http://localhost:1313/post/goisforlovers/ - Wed, 02 Apr 2014 00:00:00 +0000 - - http://localhost:1313/post/goisforlovers/ - - -<p>Hugo uses the excellent <a href="http://golang.org/&gt;">go</a> <a href="http://golang.org/pkg/html/template/&gt;">html/template</a> library for -its template engine. It is an extremely lightweight engine that provides a very -small amount of logic. In our experience that 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.</p> - -<p>This document is a brief primer on using go templates. The <a href="http://golang.org/pkg/html/template/&gt;">go docs</a> -provide more details.</p> - -<h2 id="introduction-to-go-templates:4d30d99f79bd431d57546bbed04b7347">Introduction to Go Templates</h2> - -<p>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.</p> - -<p>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 <a href="http://golang.org/pkg/html/template/&gt;">go docs</a>.</p> - -<h2 id="basic-syntax:4d30d99f79bd431d57546bbed04b7347">Basic Syntax</h2> - -<p>Go lang templates are html files with the addition of variables and -functions.</p> - -<p><strong>Go variables and functions are accessible within {{ }}</strong></p> - -<p>Accessing a predefined variable &ldquo;foo&rdquo;:</p> - -<pre><code>{{ foo }} -</code></pre> - -<p><strong>Parameters are separated using spaces</strong></p> - -<p>Calling the add function with input of 1, 2:</p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<p><strong>Methods and fields are accessed via dot notation</strong></p> - -<p>Accessing the Page Parameter &ldquo;bar&rdquo;</p> - -<pre><code>{{ .Params.bar }} -</code></pre> - -<p><strong>Parentheses can be used to group items together</strong></p> - -<pre><code>{{ if or (isset .Params &quot;alt&quot;) (isset .Params &quot;caption&quot;) }} Caption {{ end }} -</code></pre> - -<h2 id="variables:4d30d99f79bd431d57546bbed04b7347">Variables</h2> - -<p>Each go template has a struct (object) made available to it. In hugo each -template is passed either a page or a node struct depending on which type of -page you are rendering. More details are available on the -<a href="http://localhost:1313/layout/variables">variables</a> page.</p> - -<p>A variable is accessed by referencing the variable name.</p> - -<pre><code>&lt;title&gt;{{ .Title }}&lt;/title&gt; -</code></pre> - -<p>Variables can also be defined and referenced.</p> - -<pre><code>{{ $address := &quot;123 Main St.&quot;}} -{{ $address }} -</code></pre> - -<h2 id="functions:4d30d99f79bd431d57546bbed04b7347">Functions</h2> - -<p>Go template ship 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. <a href="http://localhost:1313/layout/functions">Hugo template -functions</a> 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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ add 1 2 }} -</code></pre> - -<h2 id="includes:4d30d99f79bd431d57546bbed04b7347">Includes</h2> - -<p>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.</p> - -<p><strong>Example:</strong></p> - -<pre><code>{{ template &quot;chrome/header.html&quot; . }} -</code></pre> - -<h2 id="logic:4d30d99f79bd431d57546bbed04b7347">Logic</h2> - -<p>Go templates provide the most basic iteration and conditional logic.</p> - -<h3 id="iteration:4d30d99f79bd431d57546bbed04b7347">Iteration</h3> - -<p>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.</p> - -<p><strong>Example 1: Using Context</strong></p> - -<pre><code>{{ range array }} - {{ . }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring value variable name</strong></p> - -<pre><code>{{range $element := array}} - {{ $element }} -{{ end }} -</code></pre> - -<p><strong>Example 2: Declaring key and value variable name</strong></p> - -<pre><code>{{range $index, $element := array}} - {{ $index }} - {{ $element }} -{{ end }} -</code></pre> - -<h3 id="conditionals:4d30d99f79bd431d57546bbed04b7347">Conditionals</h3> - -<p>If, else, with, or, &amp; and provide the framework for handling conditional -logic in Go Templates. Like range, each statement is closed with <code>end</code>.</p> - -<p>Go Templates treat the following values as false:</p> - -<ul> -<li>false</li> -<li>0</li> -<li>any array, slice, map, or string of length zero</li> -</ul> - -<p><strong>Example 1: If</strong></p> - -<pre><code>{{ if isset .Params &quot;title&quot; }}&lt;h4&gt;{{ index .Params &quot;title&quot; }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 2: If -&gt; Else</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{else}} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<p><strong>Example 3: And &amp; Or</strong></p> - -<pre><code>{{ if and (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -</code></pre> - -<p><strong>Example 4: With</strong></p> - -<p>An alternative way of writing &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent.</p> - -<p>The first example above could be simplified as:</p> - -<pre><code>{{ with .Params.title }}&lt;h4&gt;{{ . }}&lt;/h4&gt;{{ end }} -</code></pre> - -<p><strong>Example 5: If -&gt; Else If</strong></p> - -<pre><code>{{ if isset .Params &quot;alt&quot; }} - {{ index .Params &quot;alt&quot; }} -{{ else if isset .Params &quot;caption&quot; }} - {{ index .Params &quot;caption&quot; }} -{{ end }} -</code></pre> - -<h2 id="pipes:4d30d99f79bd431d57546bbed04b7347">Pipes</h2> - -<p>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&rsquo;s output becomes the -input of the following pipe.</p> - -<p>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.</p> - -<p>A few simple examples should help convey how to use the pipe.</p> - -<p><strong>Example 1 :</strong></p> - -<pre><code>{{ if eq 1 1 }} Same {{ end }} -</code></pre> - -<p>is the same as</p> - -<pre><code>{{ eq 1 1 | if }} Same {{ end }} -</code></pre> - -<p>It does look odd to place the if at the end, but it does provide a good -illustration of how to use the pipes.</p> - -<p><strong>Example 2 :</strong></p> - -<pre><code>{{ index .Params &quot;disqus_url&quot; | html }} -</code></pre> - -<p>Access the page parameter called &ldquo;disqus_url&rdquo; and escape the HTML.</p> - -<p><strong>Example 3 :</strong></p> - -<pre><code>{{ if or (or (isset .Params &quot;title&quot;) (isset .Params &quot;caption&quot;)) (isset .Params &quot;attr&quot;)}} -Stuff Here -{{ end }} -</code></pre> - -<p>Could be rewritten as</p> - -<pre><code>{{ isset .Params &quot;caption&quot; | or isset .Params &quot;title&quot; | or isset .Params &quot;attr&quot; | if }} -Stuff Here -{{ end }} -</code></pre> - -<h2 id="context-aka-the-dot:4d30d99f79bd431d57546bbed04b7347">Context (aka. the dot)</h2> - -<p>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 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 set it to a variable -instead of depending on the context.</p> - -<p><strong>Example:</strong></p> - -<pre><code> {{ $title := .Site.Title }} - {{ range .Params.tags }} - &lt;li&gt; &lt;a href=&quot;{{ $baseurl }}/tags/{{ . | urlize }}&quot;&gt;{{ . }}&lt;/a&gt; - {{ $title }} &lt;/li&gt; - {{ end }} -</code></pre> - -<p>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.</p> - -<h1 id="hugo-parameters:4d30d99f79bd431d57546bbed04b7347">Hugo Parameters</h1> - -<p>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.</p> - -<h2 id="using-content-page-parameters:4d30d99f79bd431d57546bbed04b7347">Using Content (page) Parameters</h2> - -<p>In each piece of content you can provide variables to be used by the -templates. This happens in the <a href="http://localhost:1313/content/front-matter">front matter</a>.</p> - -<p>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&rsquo;t make a lot of sense. We&rsquo;ve defined a variable in our front matter -of some pages to turn off the TOC from being displayed.</p> - -<p>Here is the example front matter:</p> - -<pre><code>--- -title: &quot;Permalinks&quot; -date: &quot;2013-11-18&quot; -aliases: - - &quot;/doc/permalinks/&quot; -groups: [&quot;extras&quot;] -groups_weight: 30 -notoc: true ---- -</code></pre> - -<p>Here is the corresponding code inside of the template:</p> - -<pre><code> {{ if not .Params.notoc }} - &lt;div id=&quot;toc&quot; class=&quot;well col-md-4 col-sm-6&quot;&gt; - {{ .TableOfContents }} - &lt;/div&gt; - {{ end }} -</code></pre> - -<h2 id="using-site-config-parameters:4d30d99f79bd431d57546bbed04b7347">Using Site (config) Parameters</h2> - -<p>In your top-level configuration file (eg, <code>config.yaml</code>) you can define site -parameters, which are values which will be available to you in chrome.</p> - -<p>For instance, you might declare:</p> - -<pre><code class="language-yaml">params: - CopyrightHTML: &quot;Copyright &amp;#xA9; 2013 John Doe. All Rights Reserved.&quot; - TwitterUser: &quot;spf13&quot; - SidebarRecentLimit: 5 -</code></pre> - -<p>Within a footer layout, you might then declare a <code>&lt;footer&gt;</code> which is only -provided if the <code>CopyrightHTML</code> 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.</p> - -<pre><code>{{if .Site.Params.CopyrightHTML}}&lt;footer&gt; -&lt;div class=&quot;text-center&quot;&gt;{{.Site.Params.CopyrightHTML | safeHtml}}&lt;/div&gt; -&lt;/footer&gt;{{end}} -</code></pre> - -<p>An alternative way of writing the &ldquo;if&rdquo; and then referencing the same value -is to use &ldquo;with&rdquo; instead. With rebinds the context <code>.</code> within its scope, -and skips the block if the variable is absent:</p> - -<pre><code>{{with .Site.Params.TwitterUser}}&lt;span class=&quot;twitter&quot;&gt; -&lt;a href=&quot;https://twitter.com/{{.}}&quot; rel=&quot;author&quot;&gt; -&lt;img src=&quot;/images/twitter.png&quot; width=&quot;48&quot; height=&quot;48&quot; title=&quot;Twitter: {{.}}&quot; - alt=&quot;Twitter&quot;&gt;&lt;/a&gt; -&lt;/span&gt;{{end}} -</code></pre> - -<p>Finally, if you want to pull &ldquo;magic constants&rdquo; out of your layouts, you can do -so, such as in this example:</p> - -<pre><code>&lt;nav class=&quot;recent&quot;&gt; - &lt;h1&gt;Recent Posts&lt;/h1&gt; - &lt;ul&gt;{{range first .Site.Params.SidebarRecentLimit .Site.Recent}} - &lt;li&gt;&lt;a href=&quot;{{.RelPermalink}}&quot;&gt;{{.Title}}&lt;/a&gt;&lt;/li&gt; - {{end}}&lt;/ul&gt; -&lt;/nav&gt; -</code></pre> - - - - - \ No newline at end of file diff --git a/exampleSite/public/writing/index.html b/exampleSite/public/writing/index.html deleted file mode 100644 index 2669858..0000000 --- a/exampleSite/public/writing/index.html +++ /dev/null @@ -1,8 +0,0 @@ - - - - - - - - diff --git a/main.less b/main.less index f71c8ec..fe30c99 100644 --- a/main.less +++ b/main.less @@ -1,18 +1,17 @@ // Font imports: +// Less variables @import url(https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700); @import url(http://fonts.googleapis.com/css?family=Ubuntu+Mono:400,400italic,700,700italic); @import url(http://code.ionicframework.com/ionicons/2.0.1/css/ionicons.min.css); @import url(http://fonts.googleapis.com/css?family=Raleway:200); -// Less variables - -@base-font-size: 18px; +@base-font-size: 16px; @vspacing: @base-font-size*2; @monospace-font-stack: ~"'Ubuntu Mono', 'Menlo', monospace"; -@body-font-stack: ~"'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial', sans-serif"; -@heading-font-stack: ~"'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial', sans-serif"; +@body-font-stack: ~"'ProximaNova', 'Helvetica Neue', 'Arial', sans-serif"; +@heading-font-stack: ~"'ProximaNova', 'Helvetica Neue', 'Arial', sans-serif"; @special-font-stack-1: ~"'Raleway', 'Helvetica Neue', 'Arial', sans-serif"; @black: #333; @@ -98,7 +97,7 @@ body { .justify-content(flex-start); // start sections at the top width: 100%; min-height: 100%; - font-weight: 400; + font-weight: 300; font-family: @body-font-stack; color: @black; line-height: 1.6; @@ -285,10 +284,10 @@ body { } .icon { - font-size: 1rem; + font-size: 16px; &.larger { - font-size: 1.2rem; + font-size: 18px; } } } diff --git a/markdown.less b/markdown.less index 89224b0..5279029 100644 --- a/markdown.less +++ b/markdown.less @@ -39,7 +39,7 @@ h4, h5, h6 { code, pre { font-family: @monospace-font-stack; - font-size: 0.9rem; + font-size: 0.95rem; background-color: @background-gray; } @@ -66,7 +66,7 @@ pre { pre code { /* enclosed by 4 backticks (````) */ padding: 0; - font-size: 15px; + font-size: 0.9rem; } // diff --git a/static/css/main.css b/static/css/main.css index 54e1eba..214c4b4 100644 --- a/static/css/main.css +++ b/static/css/main.css @@ -24,7 +24,7 @@ a:active { } html { height: 100%; - font-size: 18px; + font-size: 16px; } body { display: -webkit-flex; @@ -46,8 +46,8 @@ body { justify-content: flex-start; width: 100%; min-height: 100%; - font-weight: 400; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial', sans-serif; + font-weight: 300; + font-family: 'ProximaNova', 'Helvetica Neue', 'Arial', sans-serif; color: #333333; line-height: 1.6; text-rendering: optimizeLegibility !important; @@ -91,7 +91,7 @@ body { } @media (min-width: 550px) { .section { - padding: 0 18px; + padding: 0 16px; margin-left: 100px; margin-right: 100px; max-width: 900px; @@ -165,7 +165,7 @@ body { } .section.header .name { font-size: 18px; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial', sans-serif; + font-family: 'ProximaNova', 'Helvetica Neue', 'Arial', sans-serif; letter-spacing: -0.005rem; text-transform: uppercase; font-weight: 700; @@ -177,7 +177,7 @@ body { } .section.header nav { font-size: 14px; - margin-bottom: 18px; + margin-bottom: 16px; } .section.header nav ul { list-style: none; @@ -264,10 +264,10 @@ body { color: #fefefe; } .section.icons .content a .icon { - font-size: 1rem; + font-size: 16px; } .section.icons .content a .icon.larger { - font-size: 1.2rem; + font-size: 18px; } @media (min-width: 550px) { .section.icons { @@ -287,7 +287,7 @@ body { color: #333333; } .section.icons .content a .icon { - font-size: 18px; + font-size: 16px; } .section.icons .content a .icon.larger { font-size: 18px; @@ -305,11 +305,11 @@ body { } .section.main .content { color: #333333; - font-size: 18px; + font-size: 16px; } .section.main .content .page-heading { font-size: 18px; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial', sans-serif; + font-family: 'ProximaNova', 'Helvetica Neue', 'Arial', sans-serif; letter-spacing: -0.005rem; text-transform: uppercase; font-weight: 700; @@ -317,7 +317,7 @@ body { -webkit-font-smoothing: antialiased; font-smoothing: antialiased; color: #333333; - margin-bottom: 18px; + margin-bottom: 16px; } .section.main .content .front-matter .page-heading { margin-bottom: 0; @@ -330,7 +330,7 @@ body { display: -ms-flexbox; display: -ms-flex; display: flex; - margin-bottom: 36px; + margin-bottom: 32px; } .section.main .content .front-matter .date, .section.main .content .front-matter .word-count, @@ -421,22 +421,22 @@ body { color: #b7b7b7; min-width: 100px; text-align: right; - margin-right: 18px; + margin-right: 16px; } .section { - padding: 0 18px; + padding: 0 16px; } .section.header { - padding-top: 36px; - padding-bottom: 18px; + padding-top: 32px; + padding-bottom: 16px; } .section.icons { padding-top: 0; - padding-bottom: 36px; + padding-bottom: 32px; } .section.main { - padding-top: 36px; - padding-bottom: 36px; + padding-top: 32px; + padding-bottom: 32px; } @media (min-width: 550px) { .container { @@ -469,7 +469,7 @@ a { .section.main .content .markdown h5, .section.main .content .markdown h6 { font-size: 18px; - font-family: 'ProximaNova', 'Source Sans Pro', 'Helvetica Neue', 'Arial', sans-serif; + font-family: 'ProximaNova', 'Helvetica Neue', 'Arial', sans-serif; letter-spacing: -0.005rem; text-transform: uppercase; font-weight: 700; @@ -501,7 +501,7 @@ a { .section.main .content .markdown code, .section.main .content .markdown pre { font-family: 'Ubuntu Mono', 'Menlo', monospace; - font-size: 0.9rem; + font-size: 0.95rem; background-color: #f9f9f9; } .section.main .content .markdown code { @@ -525,7 +525,7 @@ a { .section.main .content .markdown pre code { /* enclosed by 4 backticks (````) */ padding: 0; - font-size: 15px; + font-size: 0.9rem; } .section.main .content .markdown p { /* Invoked by line break */