56 lines
3.7 KiB
XML
56 lines
3.7 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
|
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
|
<channel>
|
|
<title>Blog on Epic 免费人</title>
|
|
<link>https://blog.echosec.top/epic-awesome-gamer/posts/</link>
|
|
<description>Recent content in Blog on Epic 免费人</description>
|
|
<generator>Hugo -- gohugo.io</generator>
|
|
<language>en-us</language>
|
|
<lastBuildDate>Sun, 28 Sep 2014 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.echosec.top/epic-awesome-gamer/posts/index.xml" rel="self" type="application/rss+xml" />
|
|
<item>
|
|
<title>Creating a New Theme</title>
|
|
<link>https://blog.echosec.top/epic-awesome-gamer/posts/creating-a-new-theme/</link>
|
|
<pubDate>Sun, 28 Sep 2014 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://blog.echosec.top/epic-awesome-gamer/posts/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>Migrate to Hugo from Jekyll</title>
|
|
<link>https://blog.echosec.top/epic-awesome-gamer/posts/migrate-from-jekyll/</link>
|
|
<pubDate>Mon, 10 Mar 2014 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://blog.echosec.top/epic-awesome-gamer/posts/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
|
|
▾ &lt;root&gt;/
|
|
▾ images/
|
|
logo.png
|
|
should become
|
|
▾ &lt;root&gt;/
|
|
▾ static/
|
|
▾ images/
|
|
logo.png
|
|
Additionally, you&rsquo;ll want any files that should reside at the root (such as CNAME) to be moved to static.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>(Hu)go Template Primer</title>
|
|
<link>https://blog.echosec.top/epic-awesome-gamer/posts/goisforlovers/</link>
|
|
<pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://blog.echosec.top/epic-awesome-gamer/posts/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://blog.echosec.top/epic-awesome-gamer/posts/hugoisforlovers/</link>
|
|
<pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://blog.echosec.top/epic-awesome-gamer/posts/hugoisforlovers/</guid>
|
|
<description>Step 1. Install Hugo
|
|
#
|
|
|
|
Go to 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 Install 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:</description>
|
|
</item>
|
|
|
|
</channel>
|
|
</rss>
|