aboutsummaryrefslogtreecommitdiffstats
path: root/post/index.xml
diff options
context:
space:
mode:
authorNathan2017-07-22 10:57:44 -0400
committerNathan2017-07-22 10:57:44 -0400
commitabd86fd571b3c0e161a818047dfebbbd893a6714 (patch)
tree17c1fcaf3a2500e226a0a09986b9d38800e8536d /post/index.xml
parente208d1977ccac68ccc01c356a4d485924022572e (diff)
downloadpodcast-abd86fd571b3c0e161a818047dfebbbd893a6714.tar.bz2
New websitegh-pages
Diffstat (limited to 'post/index.xml')
-rw-r--r--post/index.xml60
1 files changed, 60 insertions, 0 deletions
diff --git a/post/index.xml b/post/index.xml
new file mode 100644
index 0000000..e97d272
--- /dev/null
+++ b/post/index.xml
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+ <channel>
+ <title>Posts on podcast</title>
+ <link>https://nathanjaremko.com/podcast/post/</link>
+ <description>Recent content in Posts on podcast</description>
+ <generator>Hugo -- gohugo.io</generator>
+ <language>en-us</language>
+ <lastBuildDate>Sun, 28 Sep 2014 00:00:00 +0000</lastBuildDate>
+
+ <atom:link href="https://nathanjaremko.com/podcast/post/index.xml" rel="self" type="application/rss+xml" />
+
+
+ <item>
+ <title>Creating a New Theme</title>
+ <link>https://nathanjaremko.com/podcast/post/creating-a-new-theme/</link>
+ <pubDate>Sun, 28 Sep 2014 00:00:00 +0000</pubDate>
+
+ <guid>https://nathanjaremko.com/podcast/post/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&amp;rsquo;ll explain how Hugo uses templates and how you can organize your templates to create a theme. I won&amp;rsquo;t cover using CSS to style your theme.
+We&amp;rsquo;ll start with creating a new site with a very basic template.</description>
+ </item>
+
+ <item>
+ <title>(Hu)go Template Primer</title>
+ <link>https://nathanjaremko.com/podcast/post/goisforlovers/</link>
+ <pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
+
+ <guid>https://nathanjaremko.com/podcast/post/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>https://nathanjaremko.com/podcast/post/hugoisforlovers/</link>
+ <pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
+
+ <guid>https://nathanjaremko.com/podcast/post/hugoisforlovers/</guid>
+ <description>Step 1. Install Hugo Goto hugo releases and download the appropriate version for your os and architecture.
+Save it somewhere specific as we will be using it in the next step.
+More complete instructions are available at installing hugo
+Step 2. Build the Docs Hugo has its own example site which happens to also be the documentation site you are reading right now.
+Follow the following steps:
+ Clone the hugo repository Go into the repo Run hugo in server mode and build the docs Open your browser to http://localhost:1313 Corresponding pseudo commands:</description>
+ </item>
+
+ <item>
+ <title>Migrate from Jekyll</title>
+ <link>https://nathanjaremko.com/podcast/post/migrate-from-jekyll/</link>
+ <pubDate>Mon, 10 Mar 2014 00:00:00 +0000</pubDate>
+
+ <guid>https://nathanjaremko.com/podcast/post/migrate-from-jekyll/</guid>
+ <description>Move static content to static Jekyll has a rule that any directory not starting with _ will be copied as-is to the _site output. Hugo keeps all static content under static. You should therefore move it all there. With Jekyll, something that looked like
+▾ &amp;lt;root&amp;gt;/ ▾ images/ logo.png should become
+▾ &amp;lt;root&amp;gt;/ ▾ static/ ▾ images/ logo.png Additionally, you&amp;rsquo;ll want any files that should reside at the root (such as CNAME) to be moved to static.</description>
+ </item>
+
+ </channel>
+</rss> \ No newline at end of file