更换 logo

This commit is contained in:
YDZ
2020-03-28 20:08:07 +08:00
parent ed488266af
commit ae75f59b67
392 changed files with 0 additions and 8373 deletions

View File

@ -0,0 +1,38 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Development on LeetCode Cookbook</title>
<link>https://books.halfrost.com/leetcode/categories/Development/</link>
<description>Recent content in Development on LeetCode Cookbook</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Wed, 02 Apr 2014 00:00:00 +0000</lastBuildDate>
<atom:link href="https://books.halfrost.com/leetcode/categories/Development/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>(Hu)go Template Primer</title>
<link>https://books.halfrost.com/leetcode/posts/goisforlovers/</link>
<pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
<guid>https://books.halfrost.com/leetcode/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://books.halfrost.com/leetcode/posts/hugoisforlovers/</link>
<pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate>
<guid>https://books.halfrost.com/leetcode/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>