-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.xml
104 lines (80 loc) · 4.3 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Hugo Future Imperfect</title>
<link>/</link>
<description>Recent content on Hugo Future Imperfect</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Thu, 22 Jun 2017 00:00:00 +0000</lastBuildDate>
<atom:link href="/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Fancy App 1</title>
<link>/itemized/item1/</link>
<pubDate>Thu, 22 Jun 2017 00:00:00 +0000</pubDate>
<guid>/itemized/item1/</guid>
<description> App 1 </description>
</item>
<item>
<title>Fancy App 2</title>
<link>/itemized/item2/</link>
<pubDate>Thu, 22 Jun 2017 00:00:00 +0000</pubDate>
<guid>/itemized/item2/</guid>
<description> App 2 </description>
</item>
<item>
<title>Fancy App 3</title>
<link>/itemized/item3/</link>
<pubDate>Thu, 22 Jun 2017 00:00:00 +0000</pubDate>
<guid>/itemized/item3/</guid>
<description> App 3 </description>
</item>
<item>
<title>Fancy App 4</title>
<link>/itemized/item4/</link>
<pubDate>Thu, 22 Jun 2017 00:00:00 +0000</pubDate>
<guid>/itemized/item4/</guid>
<description> App 4 </description>
</item>
<item>
<title>Creating a New Theme</title>
<link>/blog/creating-a-new-theme/</link>
<pubDate>Sun, 28 Sep 2014 00:00:00 +0000</pubDate>
<guid>/blog/creating-a-new-theme/</guid>
<description>Introduction This tutorial will show you how to create a simple theme in Hugo. I assume that you are familiar with HTML, the bash command line, and that you are comfortable using Markdown to format content. I&rsquo;ll explain how Hugo uses templates and how you can organize your templates to create a theme. I won&rsquo;t cover using CSS to style your theme.
We&rsquo;ll start with creating a new site with a very basic template.</description>
</item>
<item>
<title>(Hu)go Template Primer</title>
<link>/blog/goisforlovers/</link>
<pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
<guid>/blog/goisforlovers/</guid>
<description>Hugo uses the excellent go html/template library for its template engine. It is an extremely lightweight engine that provides a very small amount of logic. In our experience 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.
This document is a brief primer on using go templates.</description>
</item>
<item>
<title>Getting Started with Hugo</title>
<link>/blog/hugoisforlovers/</link>
<pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
<guid>/blog/hugoisforlovers/</guid>
<description><h2 id="step-1-install-hugo">Step 1. Install Hugo</h2>
<p>Go to <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="/overview/installing/">installing hugo</a></p></description>
</item>
<item>
<title>Migrate to Hugo from Jekyll</title>
<link>/blog/migrate-from-jekyll/</link>
<pubDate>Mon, 10 Mar 2014 00:00:00 +0000</pubDate>
<guid>/blog/migrate-from-jekyll/</guid>
<description><h2 id="move-static-content-to-static">Move static content to <code>static</code></h2>
<p>Jekyll has a rule that any directory not starting with <code>_</code> will be copied as-is to the <code>_site</code> output. Hugo keeps all static content under <code>static</code>. You should therefore move it all there.
With Jekyll, something that looked like</p>
<pre><code>▾ &lt;root&gt;/
▾ images/
logo.png
</code></pre></description>
</item>
</channel>
</rss>