9 |
13 |
14 |
8 |
15 |
13 |
14 | ├── .github └── workflows │ └── main.yml ├── .gitignore ├── LICENSE ├── README-zh.md ├── README.md ├── archetypes └── default.md ├── exampleSite ├── config.toml ├── content │ ├── about │ │ └── index.md │ └── posts │ │ ├── chinese-preview.md │ │ ├── english-preview.md │ │ ├── japanese-preview.md │ │ └── theme-preview.md ├── netlify.toml └── static │ └── 100.jpg ├── i18n ├── en.yaml └── zh-cn.yaml ├── images ├── screenshot.png ├── showcase.png └── tn.png ├── layouts ├── 404.html ├── _default │ ├── list.html │ ├── single.html │ └── terms.html ├── index.html ├── partials │ ├── comments.html │ ├── footer.html │ ├── head.html │ ├── header.html │ ├── js.html │ ├── mathjax.html │ ├── nav.html │ └── post.html └── shortcodes │ └── img.html ├── static ├── css │ ├── animate.min.css │ ├── comments.css │ ├── fancybox.min.css │ ├── highlight.css │ ├── normalize.css │ └── zozo.css ├── images │ └── favicon.ico └── js │ ├── fancybox.min.js │ ├── jquery-3.5.1.min.js │ └── zozo.js └── theme.toml /.github/workflows/main.yml: -------------------------------------------------------------------------------- 1 | name: ci 2 | on: 3 | schedule: 4 | - cron: "*/60 * * * *" 5 | 6 | jobs: 7 | autogreen: 8 | runs-on: ubuntu-latest 9 | steps: 10 | - name: Clone repository 11 | uses: actions/checkout@v3 12 | 13 | - name: Auto green 14 | run: | 15 | git config --local user.email "zk@varkai.com" 16 | git config --local user.name "varkai" 17 | git remote set-url origin https://${{ github.actor }}:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }} 18 | git pull --rebase 19 | git commit --allow-empty -m "a commit a day keeps your girlfriend away" 20 | git push 21 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Hugo default output directory 2 | /public 3 | 4 | ## OS Files 5 | # Windows 6 | Thumbs.db 7 | Desktop.ini 8 | $RECYCLE.BIN/ 9 | 10 | # OSX 11 | .DS_Store 12 | *.map 13 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2019 varkai 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy of 6 | this software and associated documentation files (the "Software"), to deal in 7 | the Software without restriction, including without limitation the rights to 8 | use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of 9 | the Software, and to permit persons to whom the Software is furnished to do so, 10 | subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS 17 | FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR 18 | COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER 19 | IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN 20 | CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 21 | -------------------------------------------------------------------------------- /README-zh.md: -------------------------------------------------------------------------------- 1 | # Hugo Theme Zozo 2 | 3 | [](https://github.com/varkai/hugo-theme-zozo/blob/master/LICENSE) 4 | 5 | > 该主题移植自 [Aragaki](https://github.com/PCDotFan/Aragaki),结构样式参考自 [菩提树下](https://blog.caicai.me/),部分功能参考自 [Even](https://github.com/olOwOlo/hugo-theme-even) 6 | 7 | **在线预览**:[Demo](https://zozo.varkai.com) 8 | 9 | ## 截图 10 | 11 |  12 | 13 | ## 安装 14 | 15 | 首先进入 hugo 的站点目录运行下面的命令: 16 | 17 | ```bash 18 | $ git clone https://github.com/varkai/hugo-theme-zozo themes/zozo 19 | ``` 20 | 21 | 本主题提供了一个示例配置文件是 [`exampleSite`](./exampleSite) 目录里的 [`config.toml`](./exampleSite/config.toml) 文件。 22 | 23 | 配置文件中对大部分配置都有详细的注释说明,复制该文件到站点目录下,根据自己的情况修改即可。 24 | 25 | 更多安装信息查看 Hugo 官方文档 [setup guide](https://gohugo.io/overview/installing/)。 26 | 27 | ## 示例站点 28 | 29 | `exampleSite` 是本主题的一个示例站点,里面有配置文件、关于页面的一些示例。 30 | 31 | ## 关于页面 32 | 33 | 使用关于页面,首先要在你的站点目录的 [`content`](./exampleSite/content/) 目录下创建一个 [`about`](./exampleSite/content/about/) 目录,然后再创建一个 [`index.md`](./exampleSite/content/about/index.md) 文件,最后编写该文件即可。 34 | 35 | ## Shortcodes 36 | 37 | 主题提供了 `img` shortcode. 38 | 39 | ```markdown 40 | {{< img src="path/to/xxx.png" >}} 41 | ``` 42 | 43 | ## Math 公式 44 | 45 | 本主题支持 MathJax 数学公式,默认为关闭状态,如需使用,需要在 [`config.toml`](./exampleSite/config.toml) 中进行设置。 46 | 47 | 设置 `[params]` 下的 `mathjax = true` 来支持数学公式。 48 | 49 | ## Valine 评论 50 | 51 | 本主题提供了 Valine 评论系统,默认为关闭状态,如需使用,需要在 [`config.toml`](./exampleSite/config.toml) 中进行设置。 52 | 53 | 设置 `[params.valine]` 下的 `enable = true` 来开启评论系统,并将 `appId` 和 `appKey` 设置为你自己的。 54 | 55 | 56 | ## 社交链接 57 | 58 | 本主题的社交链接是字体图标的样式,并放置在了页面头部。你可以通过在 [`config.toml`](./exampleSite/config.toml) 的 `[social]` 模块中修改添加你的社交链接。 59 | 60 | ## 部署主题 61 | 62 | 配置完成之后,就可以使用下面的命令来启动 hugo 服务编译 markdown 文件生成静态站点: 63 | 64 | ```bash 65 | $ hugo server 66 | ``` 67 | 68 | 然后在浏览器地址栏输入 [localhost:1313](http://localhost:1313) 来访问站点。 69 | 70 | ## License 71 | 72 | Released under the [MIT](https://github.com/varkai/hugo-theme-zozo/blob/master/LICENSE) License. 73 | 74 | ## 致谢 75 | 76 | - [Aragaki](https://github.com/PCDotFan/Aragaki) 77 | - [菩提树下](https://blog.caicai.me/) 78 | - [olOwOlo](https://olowolo.com/) -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Hugo Theme Zozo 2 | 3 | [](https://github.com/varkai/hugo-theme-zozo/blob/master/LICENSE) 4 | 5 | A simple and beautiful theme for Hugo 6 | 7 | > It's a port of [Aragaki](https://github.com/PCDotFan/Aragaki), The style is reference from [菩提树下](https://blog.caicai.me/), Some functions are referenced from [Even](https://github.com/olOwOlo/hugo-theme-even) 8 | 9 | **Features** 10 | 11 | + **Responsive** 12 | + **Syntax highlighting with highlightjs** 13 | + **Math with mathjax** 14 | + **Social links(Customize)** 15 | + **Tags page** 16 | + **Archive page** 17 | + **Disqus and [Valine](https://valine.js.org/en/index.html) comment-system** 18 | + **Fancybox** 19 | + **GoogleAnalytics** 20 | 21 | [Demo](https://zozo.varkai.com) | [中文说明](./README-zh.md) 22 | 23 | ## Sceenshots 24 | 25 |  26 | 27 | ## Installation 28 | 29 | ```bash 30 | $ git clone https://github.com/varkai/hugo-theme-zozo themes/zozo 31 | ``` 32 | 33 | **Important**: Take a look inside the [`exampleSite`](./exampleSite) folder of this theme. You'll find a file called [`config.toml`](./exampleSite/config.toml). To use it, copy the [`config.toml`](./exampleSite/config.toml) in the root folder of your Hugo site. Feel free to change it. 34 | 35 | ## ExampleSite 36 | 37 | There is an example site with config file and markdown files in `exampleSite` directory. 38 | 39 | ## About Page 40 | 41 | Use the about page to introduce yourself to your visitors. You can customize the content as you like in the `/content/about/index.md`. 42 | 43 | ## Shortcodes 44 | 45 | This theme provides `img` shortcodes. 46 | 47 | ```markdown 48 | {{< img src="path/to/xxx.png" >}} 49 | ``` 50 | 51 | ## MathJax 52 | 53 | This theme supports MathJax, which are turned off by default. If you want to use them, you need to set them in `config.toml`. 54 | 55 | Set `mathjax = true` under the `[params]` to support the MathJax. 56 | 57 | ## Valine Comment System 58 | 59 | This theme provides valine comment system, the default is closed, if you want to use, need to set in `config. toml`. 60 | 61 | Set the `enable = true` under `[params.valine]` to open valine, and will be `appId` and `appKey` set for yourself. 62 | 63 | ## Social Link Icons 64 | 65 | You can add a social link panel in the header by adding entries to the social block in the `config.toml`. 66 | 67 | [Remix icon](https://remixicon.com/) is used in this theme. 68 | 69 | ## Nearly Finished 70 | 71 | In order to see your site in action, run Hugo's built-in local server. 72 | 73 | ```bash 74 | $ hugo server 75 | ``` 76 | 77 | Now enter `localhost:1313` in the address bar of your browser. 78 | 79 | ## License 80 | 81 | Released under the [MIT](https://github.com/varkai/hugo-theme-zozo/blob/master/LICENSE) License. 82 | 83 | ## Acknowledgements 84 | 85 | - [Aragaki](https://github.com/PCDotFan/Aragaki) 86 | - [菩提树下](https://blog.caicai.me/) 87 | - [olOwOlo](https://olowolo.com/) -------------------------------------------------------------------------------- /archetypes/default.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "{{ replace .Name "-" " " | title }}" 3 | date: {{ .Date }} 4 | hidden: false 5 | draft: true 6 | tags: [] 7 | keywords: [] 8 | description: "" 9 | slug: "" 10 | --- 11 | 12 | -------------------------------------------------------------------------------- /exampleSite/config.toml: -------------------------------------------------------------------------------- 1 | baseURL = "http://localhost:1313/" 2 | languageCode = "en" 3 | defaultContentLanguage = "en" 4 | title = "ZO ZO" # site title # 网站标题 5 | theme = "zozo" 6 | hasCJKLanguage = true # has chinese/japanese/korean ? # 自动检测是否包含 中文\日文\韩文 7 | summaryLength = 100 8 | paginate = 4 # shows the number of articles # 首页显示文章数量 9 | enableEmoji = true 10 | googleAnalytics = "" # your google analytics id # Google统计代码 11 | disqusShortname = "" # your discuss shortname # Disqus评论系统代码 12 | 13 | pygmentsUseClasses = true 14 | pygmentCodeFences = true 15 | pygmentscodefencesguesssyntax = true 16 | 17 | [author] # essential # 必需 18 | name = "VarKai" 19 | 20 | [blackfriday] 21 | smartypants = false 22 | 23 | [[menu.main]] # config your menu # 配置菜单 24 | name = "Home" 25 | weight = 10 26 | identifier = "home" 27 | url = "/" 28 | [[menu.main]] 29 | name = "Archive" 30 | weight = 20 31 | identifier = "archive" 32 | url = "/posts/" 33 | [[menu.main]] 34 | name = "Tags" 35 | weight = 30 36 | identifier = "tags" 37 | url = "/tags/" 38 | [[menu.main]] 39 | name = "About" 40 | weight = 40 41 | identifier = "about" 42 | url = "/about/" 43 | 44 | [params] 45 | subTitle = "the site subtitle" # site's subTitle # 网站二级标题 46 | footerSlogan = "My spiritual home" # site's footer slogan # 网站页脚标语 47 | keywords = ["Hugo","theme","zozo"] # site's keywords # 网站关键字 48 | description = "Hugo theme zozo example site." # site's description # 网站描述 49 | enableMathJax = true # enable mathjax # 是否使用mathjax(数学公式) 50 | enableSummary = true # display the article summary # 是否显示文章摘要 51 | mainSections = ["posts","post"] 52 | 53 | # Valine. 54 | # You can get your appid and appkey from https://leancloud.cn 55 | # more info please open https://valine.js.org 56 | [params.valine] 57 | enable = false 58 | appId = "" 59 | appKey = "" 60 | placeholder = " " 61 | visitor = true 62 | 63 | # Your socail's url 64 | # 社交地址配置 65 | [social] 66 | github = " " 67 | twitter = " " 68 | facebook = " " 69 | weibo = " " 70 | instagram = " " 71 | 72 | [markup] 73 | [markup.goldmark] 74 | [markup.goldmark.renderer] 75 | unsafe = true 76 | -------------------------------------------------------------------------------- /exampleSite/content/about/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "关于" 3 | date: 2018-12-29T20:24:28+08:00 4 | hidden: true 5 | draft: false 6 | --- 7 | 8 | Hugo 官方主页: [https://gohugo.io/](https://gohugo.io/) 9 | 10 | Hugo的安装方式有两种,一种是直接下载编译好的Hugo二进制文件。如果只是使用Hugo推荐用这种方式。另一种方式是获取Hugo的源码,自己编译。由于各种不可预料的网络问题,第二种方式不是那么轻易能成功,虽然最后我还是折腾出来了。 11 | 12 | Hugo二进制下载地址: [https://github.com/gohugoio/hugo/releases](https://github.com/gohugoio/hugo/releases) 13 | 14 | -------------------------------------------------------------------------------- /exampleSite/content/posts/chinese-preview.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "药师灌顶真言" 3 | date: 2019-04-11T14:26:00+08:00 4 | draft: false 5 | tags: ["中文", "真言"] 6 | slug: "Chinese-Preview" 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 | -------------------------------------------------------------------------------- /exampleSite/content/posts/english-preview.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Creating a New Theme" 3 | date: 2019-04-01T14:26:00+08:00 4 | draft: false 5 | tags: ["English", "Theme"] 6 | slug: "English Preview" 7 | --- 8 | 9 | ## Introduction 10 | 11 | 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'll explain how Hugo uses templates and how you can organize your templates to create a theme. I won't cover using CSS to style your theme. 12 | 13 | We'll start with creating a new site with a very basic template. Then we'll add in a few pages and posts. With small variations on that, you will be able to create many different types of web sites. 14 | 15 | In this tutorial, commands that you enter will start with the "$" prompt. The output will follow. Lines that start with "#" are comments that I've added to explain a point. When I show updates to a file, the ":wq" on the last line means to save the file. 16 | 17 | Here's an example: 18 | 19 | ``` 20 | ## this is a comment 21 | $ echo this is a command 22 | this is a command 23 | 24 | ## edit the file 25 | $vi foo.md 26 | +++ 27 | date = "2014-09-28" 28 | title = "creating a new theme" 29 | +++ 30 | 31 | bah and humbug 32 | :wq 33 | 34 | ## show it 35 | $ cat foo.md 36 | +++ 37 | date = "2014-09-28" 38 | title = "creating a new theme" 39 | +++ 40 | 41 | bah and humbug 42 | $ 43 | ``` 44 | 45 | 46 | ## Some Definitions 47 | 48 | There are a few concepts that you need to understand before creating a theme. 49 | 50 | ### Skins 51 | 52 | Skins are the files responsible for the look and feel of your site. It’s the CSS that controls colors and fonts, it’s the Javascript that determines actions and reactions. It’s also the rules that Hugo uses to transform your content into the HTML that the site will serve to visitors. 53 | 54 | You have two ways to create a skin. The simplest way is to create it in the ```layouts/``` directory. If you do, then you don’t have to worry about configuring Hugo to recognize it. The first place that Hugo will look for rules and files is in the ```layouts/``` directory so it will always find the skin. 55 | 56 | Your second choice is to create it in a sub-directory of the ```themes/``` directory. If you do, then you must always tell Hugo where to search for the skin. It’s extra work, though, so why bother with it? 57 | 58 | The difference between creating a skin in ```layouts/``` and creating it in ```themes/``` is very subtle. A skin in ```layouts/``` can’t be customized without updating the templates and static files that it is built from. A skin created in ```themes/```, on the other hand, can be and that makes it easier for other people to use it. 59 | 60 | The rest of this tutorial will call a skin created in the ```themes/``` directory a theme. 61 | 62 | Note that you can use this tutorial to create a skin in the ```layouts/``` directory if you wish to. The main difference will be that you won’t need to update the site’s configuration file to use a theme. 63 | 64 | ### The Home Page 65 | 66 | The home page, or landing page, is the first page that many visitors to a site see. It is the index.html file in the root directory of the web site. Since Hugo writes files to the public/ directory, our home page is public/index.html. 67 | 68 | ### Site Configuration File 69 | 70 | When Hugo runs, it looks for a configuration file that contains settings that override default values for the entire site. The file can use TOML, YAML, or JSON. I prefer to use TOML for my configuration files. If you prefer to use JSON or YAML, you’ll need to translate my examples. You’ll also need to change the name of the file since Hugo uses the extension to determine how to process it. 71 | 72 | Hugo translates Markdown files into HTML. By default, Hugo expects to find Markdown files in your ```content/``` directory and template files in your ```themes/``` directory. It will create HTML files in your ```public/``` directory. You can change this by specifying alternate locations in the configuration file. 73 | 74 | ### Content 75 | 76 | Content is stored in text files that contain two sections. The first section is the “front matter,” which is the meta-information on the content. The second section contains Markdown that will be converted to HTML. 77 | 78 | #### Front Matter 79 | 80 | The front matter is information about the content. Like the configuration file, it can be written in TOML, YAML, or JSON. Unlike the configuration file, Hugo doesn’t use the file’s extension to know the format. It looks for markers to signal the type. TOML is surrounded by “`+++`”, YAML by “`---`”, and JSON is enclosed in curly braces. I prefer to use TOML, so you’ll need to translate my examples if you prefer YAML or JSON. 81 | 82 | The information in the front matter is passed into the template before the content is rendered into HTML. 83 | 84 | #### Markdown 85 | 86 | Content is written in Markdown which makes it easier to create the content. Hugo runs the content through a Markdown engine to create the HTML which will be written to the output file. 87 | 88 | ### Template Files 89 | 90 | Hugo uses template files to render content into HTML. Template files are a bridge between the content and presentation. Rules in the template define what content is published, where it's published to, and how it will rendered to the HTML file. The template guides the presentation by specifying the style to use. 91 | 92 | There are three types of templates: single, list, and partial. Each type takes a bit of content as input and transforms it based on the commands in the template. 93 | 94 | Hugo uses its knowledge of the content to find the template file used to render the content. If it can’t find a template that is an exact match for the content, it will shift up a level and search from there. It will continue to do so until it finds a matching template or runs out of templates to try. If it can’t find a template, it will use the default template for the site. 95 | 96 | Please note that you can use the front matter to influence Hugo’s choice of templates. 97 | 98 | #### Single Template 99 | 100 | A single template is used to render a single piece of content. For example, an article or post would be a single piece of content and use a single template. 101 | 102 | #### List Template 103 | 104 | A list template renders a group of related content. That could be a summary of recent postings or all articles in a category. List templates can contain multiple groups. 105 | 106 | The homepage template is a special type of list template. Hugo assumes that the home page of your site will act as the portal for the rest of the content in the site. 107 | 108 | #### Partial Template 109 | 110 | A partial template is a template that can be included in other templates. Partial templates must be called using the “partial” template command. They are very handy for rolling up common behavior. For example, your site may have a banner that all pages use. Instead of copying the text of the banner into every single and list template, you could create a partial with the banner in it. That way if you decide to change the banner, you only have to change the partial template. 111 | 112 | ## Create a New Site 113 | 114 | Let's use Hugo to create a new web site. I'm a Mac user, so I'll create mine in my home directory, in the Sites folder. If you're using Linux, you might have to create the folder first. 115 | 116 | The "new site" command will create a skeleton of a site. It will give you the basic directory structure and a useable configuration file. 117 | 118 | ``` 119 | $ hugo new site ~/Sites/zafta 120 | $ cd ~/Sites/zafta 121 | $ ls -l 122 | total 8 123 | drwxr-xr-x 7 quoha staff 238 Sep 29 16:49 . 124 | drwxr-xr-x 3 quoha staff 102 Sep 29 16:49 .. 125 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 archetypes 126 | -rw-r--r-- 1 quoha staff 82 Sep 29 16:49 config.toml 127 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 content 128 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 layouts 129 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 static 130 | $ 131 | ``` 132 | 133 | Take a look in the content/ directory to confirm that it is empty. 134 | 135 | The other directories (archetypes/, layouts/, and static/) are used when customizing a theme. That's a topic for a different tutorial, so please ignore them for now. 136 | 137 | ### Generate the HTML For the New Site 138 | 139 | Running the `hugo` command with no options will read all the available content and generate the HTML files. It will also copy all static files (that's everything that's not content). Since we have an empty site, it won't do much, but it will do it very quickly. 140 | 141 | ``` 142 | $ hugo --verbose 143 | INFO: 2014/09/29 Using config file: config.toml 144 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/static/ to /Users/quoha/Sites/zafta/public/ 145 | WARN: 2014/09/29 Unable to locate layout: [index.html _default/list.html _default/single.html] 146 | WARN: 2014/09/29 Unable to locate layout: [404.html] 147 | 0 draft content 148 | 0 future content 149 | 0 pages created 150 | 0 tags created 151 | 0 categories created 152 | in 2 ms 153 | $ 154 | ``` 155 | 156 | The "`--verbose`" flag gives extra information that will be helpful when we build the template. Every line of the output that starts with "INFO:" or "WARN:" is present because we used that flag. The lines that start with "WARN:" are warning messages. We'll go over them later. 157 | 158 | We can verify that the command worked by looking at the directory again. 159 | 160 | ``` 161 | $ ls -l 162 | total 8 163 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 archetypes 164 | -rw-r--r-- 1 quoha staff 82 Sep 29 16:49 config.toml 165 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 content 166 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 layouts 167 | drwxr-xr-x 4 quoha staff 136 Sep 29 17:02 public 168 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 static 169 | $ 170 | ``` 171 | 172 | See that new public/ directory? Hugo placed all generated content there. When you're ready to publish your web site, that's the place to start. For now, though, let's just confirm that we have what we'd expect from a site with no content. 173 | 174 | ``` 175 | $ ls -l public 176 | total 16 177 | -rw-r--r-- 1 quoha staff 416 Sep 29 17:02 index.xml 178 | -rw-r--r-- 1 quoha staff 262 Sep 29 17:02 sitemap.xml 179 | $ 180 | ``` 181 | 182 | Hugo created two XML files, which is standard, but there are no HTML files. 183 | 184 | 185 | 186 | ### Test the New Site 187 | 188 | Verify that you can run the built-in web server. It will dramatically shorten your development cycle if you do. Start it by running the "server" command. If it is successful, you will see output similar to the following: 189 | 190 | ``` 191 | $ hugo server --verbose 192 | INFO: 2014/09/29 Using config file: /Users/quoha/Sites/zafta/config.toml 193 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/static/ to /Users/quoha/Sites/zafta/public/ 194 | WARN: 2014/09/29 Unable to locate layout: [index.html _default/list.html _default/single.html] 195 | WARN: 2014/09/29 Unable to locate layout: [404.html] 196 | 0 draft content 197 | 0 future content 198 | 0 pages created 199 | 0 tags created 200 | 0 categories created 201 | in 2 ms 202 | Serving pages from /Users/quoha/Sites/zafta/public 203 | Web Server is available at http://localhost:1313 204 | Press Ctrl+C to stop 205 | ``` 206 | 207 | Connect to the listed URL (it's on the line that starts with "Web Server"). If everything is working correctly, you should get a page that shows the following: 208 | 209 | ``` 210 | index.xml 211 | sitemap.xml 212 | ``` 213 | 214 | That's a listing of your public/ directory. Hugo didn't create a home page because our site has no content. When there's no index.html file in a directory, the server lists the files in the directory, which is what you should see in your browser. 215 | 216 | Let’s go back and look at those warnings again. 217 | 218 | ``` 219 | WARN: 2014/09/29 Unable to locate layout: [index.html _default/list.html _default/single.html] 220 | WARN: 2014/09/29 Unable to locate layout: [404.html] 221 | ``` 222 | 223 | That second warning is easier to explain. We haven’t created a template to be used to generate “page not found errors.” The 404 message is a topic for a separate tutorial. 224 | 225 | Now for the first warning. It is for the home page. You can tell because the first layout that it looked for was “index.html.” That’s only used by the home page. 226 | 227 | I like that the verbose flag causes Hugo to list the files that it's searching for. For the home page, they are index.html, _default/list.html, and _default/single.html. There are some rules that we'll cover later that explain the names and paths. For now, just remember that Hugo couldn't find a template for the home page and it told you so. 228 | 229 | At this point, you've got a working installation and site that we can build upon. All that’s left is to add some content and a theme to display it. 230 | 231 | ## Create a New Theme 232 | 233 | Hugo doesn't ship with a default theme. There are a few available (I counted a dozen when I first installed Hugo) and Hugo comes with a command to create new themes. 234 | 235 | We're going to create a new theme called "zafta." Since the goal of this tutorial is to show you how to fill out the files to pull in your content, the theme will not contain any CSS. In other words, ugly but functional. 236 | 237 | All themes have opinions on content and layout. For example, Zafta uses "post" over "blog". Strong opinions make for simpler templates but differing opinions make it tougher to use themes. When you build a theme, consider using the terms that other themes do. 238 | 239 | 240 | ### Create a Skeleton 241 | 242 | Use the hugo "new" command to create the skeleton of a theme. This creates the directory structure and places empty files for you to fill out. 243 | 244 | ``` 245 | $ hugo new theme zafta 246 | 247 | $ ls -l 248 | total 8 249 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 archetypes 250 | -rw-r--r-- 1 quoha staff 82 Sep 29 16:49 config.toml 251 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 content 252 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 layouts 253 | drwxr-xr-x 4 quoha staff 136 Sep 29 17:02 public 254 | drwxr-xr-x 2 quoha staff 68 Sep 29 16:49 static 255 | drwxr-xr-x 3 quoha staff 102 Sep 29 17:31 themes 256 | 257 | $ find themes -type f | xargs ls -l 258 | -rw-r--r-- 1 quoha staff 1081 Sep 29 17:31 themes/zafta/LICENSE.md 259 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/archetypes/default.md 260 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/_default/list.html 261 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/_default/single.html 262 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/index.html 263 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/partials/footer.html 264 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/partials/header.html 265 | -rw-r--r-- 1 quoha staff 93 Sep 29 17:31 themes/zafta/theme.toml 266 | $ 267 | ``` 268 | 269 | The skeleton includes templates (the files ending in .html), license file, a description of your theme (the theme.toml file), and an empty archetype. 270 | 271 | Please take a minute to fill out the theme.toml and LICENSE.md files. They're optional, but if you're going to be distributing your theme, it tells the world who to praise (or blame). It's also nice to declare the license so that people will know how they can use the theme. 272 | 273 | ``` 274 | $ vi themes/zafta/theme.toml 275 | author = "michael d henderson" 276 | description = "a minimal working template" 277 | license = "MIT" 278 | name = "zafta" 279 | source_repo = "" 280 | tags = ["tags", "categories"] 281 | :wq 282 | 283 | ## also edit themes/zafta/LICENSE.md and change 284 | ## the bit that says "YOUR_NAME_HERE" 285 | ``` 286 | 287 | Note that the the skeleton's template files are empty. Don't worry, we'll be changing that shortly. 288 | 289 | ``` 290 | $ find themes/zafta -name '*.html' | xargs ls -l 291 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/_default/list.html 292 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/_default/single.html 293 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/index.html 294 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/partials/footer.html 295 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 themes/zafta/layouts/partials/header.html 296 | $ 297 | ``` 298 | 299 | 300 | 301 | ### Update the Configuration File to Use the Theme 302 | 303 | Now that we've got a theme to work with, it's a good idea to add the theme name to the configuration file. This is optional, because you can always add "-t zafta" on all your commands. I like to put it the configuration file because I like shorter command lines. If you don't put it in the configuration file or specify it on the command line, you won't use the template that you're expecting to. 304 | 305 | Edit the file to add the theme, add a title for the site, and specify that all of our content will use the TOML format. 306 | 307 | ``` 308 | $ vi config.toml 309 | theme = "zafta" 310 | baseurl = "" 311 | languageCode = "en-us" 312 | title = "zafta - totally refreshing" 313 | MetaDataFormat = "toml" 314 | :wq 315 | 316 | $ 317 | ``` 318 | 319 | ### Generate the Site 320 | 321 | Now that we have an empty theme, let's generate the site again. 322 | 323 | ``` 324 | $ hugo --verbose 325 | INFO: 2014/09/29 Using config file: /Users/quoha/Sites/zafta/config.toml 326 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/themes/zafta/static/ to /Users/quoha/Sites/zafta/public/ 327 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/static/ to /Users/quoha/Sites/zafta/public/ 328 | WARN: 2014/09/29 Unable to locate layout: [404.html theme/404.html] 329 | 0 draft content 330 | 0 future content 331 | 0 pages created 332 | 0 tags created 333 | 0 categories created 334 | in 2 ms 335 | $ 336 | ``` 337 | 338 | Did you notice that the output is different? The warning message for the home page has disappeared and we have an additional information line saying that Hugo is syncing from the theme's directory. 339 | 340 | Let's check the public/ directory to see what Hugo's created. 341 | 342 | ``` 343 | $ ls -l public 344 | total 16 345 | drwxr-xr-x 2 quoha staff 68 Sep 29 17:56 css 346 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:56 index.html 347 | -rw-r--r-- 1 quoha staff 407 Sep 29 17:56 index.xml 348 | drwxr-xr-x 2 quoha staff 68 Sep 29 17:56 js 349 | -rw-r--r-- 1 quoha staff 243 Sep 29 17:56 sitemap.xml 350 | $ 351 | ``` 352 | 353 | Notice four things: 354 | 355 | 1. Hugo created a home page. This is the file public/index.html. 356 | 2. Hugo created a css/ directory. 357 | 3. Hugo created a js/ directory. 358 | 4. Hugo claimed that it created 0 pages. It created a file and copied over static files, but didn't create any pages. That's because it considers a "page" to be a file created directly from a content file. It doesn't count things like the index.html files that it creates automatically. 359 | 360 | #### The Home Page 361 | 362 | Hugo supports many different types of templates. The home page is special because it gets its own type of template and its own template file. The file, layouts/index.html, is used to generate the HTML for the home page. The Hugo documentation says that this is the only required template, but that depends. Hugo's warning message shows that it looks for three different templates: 363 | 364 | ``` 365 | WARN: 2014/09/29 Unable to locate layout: [index.html _default/list.html _default/single.html] 366 | ``` 367 | 368 | If it can't find any of these, it completely skips creating the home page. We noticed that when we built the site without having a theme installed. 369 | 370 | When Hugo created our theme, it created an empty home page template. Now, when we build the site, Hugo finds the template and uses it to generate the HTML for the home page. Since the template file is empty, the HTML file is empty, too. If the template had any rules in it, then Hugo would have used them to generate the home page. 371 | 372 | ``` 373 | $ find . -name index.html | xargs ls -l 374 | -rw-r--r-- 1 quoha staff 0 Sep 29 20:21 ./public/index.html 375 | -rw-r--r-- 1 quoha staff 0 Sep 29 17:31 ./themes/zafta/layouts/index.html 376 | $ 377 | ``` 378 | 379 | #### The Magic of Static 380 | 381 | Hugo does two things when generating the site. It uses templates to transform content into HTML and it copies static files into the site. Unlike content, static files are not transformed. They are copied exactly as they are. 382 | 383 | Hugo assumes that your site will use both CSS and JavaScript, so it creates directories in your theme to hold them. Remember opinions? Well, Hugo's opinion is that you'll store your CSS in a directory named css/ and your JavaScript in a directory named js/. If you don't like that, you can change the directory names in your theme directory or even delete them completely. Hugo's nice enough to offer its opinion, then behave nicely if you disagree. 384 | 385 | ``` 386 | $ find themes/zafta -type d | xargs ls -ld 387 | drwxr-xr-x 7 quoha staff 238 Sep 29 17:38 themes/zafta 388 | drwxr-xr-x 3 quoha staff 102 Sep 29 17:31 themes/zafta/archetypes 389 | drwxr-xr-x 5 quoha staff 170 Sep 29 17:31 themes/zafta/layouts 390 | drwxr-xr-x 4 quoha staff 136 Sep 29 17:31 themes/zafta/layouts/_default 391 | drwxr-xr-x 4 quoha staff 136 Sep 29 17:31 themes/zafta/layouts/partials 392 | drwxr-xr-x 4 quoha staff 136 Sep 29 17:31 themes/zafta/static 393 | drwxr-xr-x 2 quoha staff 68 Sep 29 17:31 themes/zafta/static/css 394 | drwxr-xr-x 2 quoha staff 68 Sep 29 17:31 themes/zafta/static/js 395 | $ 396 | ``` 397 | 398 | ## The Theme Development Cycle 399 | 400 | When you're working on a theme, you will make changes in the theme's directory, rebuild the site, and check your changes in the browser. Hugo makes this very easy: 401 | 402 | 1. Purge the public/ directory. 403 | 2. Run the built in web server in watch mode. 404 | 3. Open your site in a browser. 405 | 4. Update the theme. 406 | 5. Glance at your browser window to see changes. 407 | 6. Return to step 4. 408 | 409 | I’ll throw in one more opinion: never work on a theme on a live site. Always work on a copy of your site. Make changes to your theme, test them, then copy them up to your site. For added safety, use a tool like Git to keep a revision history of your content and your theme. Believe me when I say that it is too easy to lose both your mind and your changes. 410 | 411 | Check the main Hugo site for information on using Git with Hugo. 412 | 413 | ### Purge the public/ Directory 414 | 415 | When generating the site, Hugo will create new files and update existing ones in the ```public/``` directory. It will not delete files that are no longer used. For example, files that were created in the wrong directory or with the wrong title will remain. If you leave them, you might get confused by them later. I recommend cleaning out your site prior to generating it. 416 | 417 | Note: If you're building on an SSD, you should ignore this. Churning on a SSD can be costly. 418 | 419 | ### Hugo's Watch Option 420 | 421 | Hugo's "`--watch`" option will monitor the content/ and your theme directories for changes and rebuild the site automatically. 422 | 423 | ### Live Reload 424 | 425 | Hugo's built in web server supports live reload. As pages are saved on the server, the browser is told to refresh the page. Usually, this happens faster than you can say, "Wow, that's totally amazing." 426 | 427 | ### Development Commands 428 | 429 | Use the following commands as the basis for your workflow. 430 | 431 | ``` 432 | ## purge old files. hugo will recreate the public directory. 433 | ## 434 | $ rm -rf public 435 | ## 436 | ## run hugo in watch mode 437 | ## 438 | $ hugo server --watch --verbose 439 | ``` 440 | 441 | Here's sample output showing Hugo detecting a change to the template for the home page. Once generated, the web browser automatically reloaded the page. I've said this before, it's amazing. 442 | 443 | 444 | ``` 445 | $ rm -rf public 446 | $ hugo server --watch --verbose 447 | INFO: 2014/09/29 Using config file: /Users/quoha/Sites/zafta/config.toml 448 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/themes/zafta/static/ to /Users/quoha/Sites/zafta/public/ 449 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/static/ to /Users/quoha/Sites/zafta/public/ 450 | WARN: 2014/09/29 Unable to locate layout: [404.html theme/404.html] 451 | 0 draft content 452 | 0 future content 453 | 0 pages created 454 | 0 tags created 455 | 0 categories created 456 | in 2 ms 457 | Watching for changes in /Users/quoha/Sites/zafta/content 458 | Serving pages from /Users/quoha/Sites/zafta/public 459 | Web Server is available at http://localhost:1313 460 | Press Ctrl+C to stop 461 | INFO: 2014/09/29 File System Event: ["/Users/quoha/Sites/zafta/themes/zafta/layouts/index.html": MODIFY|ATTRIB] 462 | Change detected, rebuilding site 463 | 464 | WARN: 2014/09/29 Unable to locate layout: [404.html theme/404.html] 465 | 0 draft content 466 | 0 future content 467 | 0 pages created 468 | 0 tags created 469 | 0 categories created 470 | in 1 ms 471 | ``` 472 | 473 | ## Update the Home Page Template 474 | 475 | The home page is one of a few special pages that Hugo creates automatically. As mentioned earlier, it looks for one of three files in the theme's layout/ directory: 476 | 477 | 1. index.html 478 | 2. _default/list.html 479 | 3. _default/single.html 480 | 481 | We could update one of the default templates, but a good design decision is to update the most specific template available. That's not a hard and fast rule (in fact, we'll break it a few times in this tutorial), but it is a good generalization. 482 | 483 | ### Make a Static Home Page 484 | 485 | Right now, that page is empty because we don't have any content and we don't have any logic in the template. Let's change that by adding some text to the template. 486 | 487 | ``` 488 | $ vi themes/zafta/layouts/index.html 489 | 490 | 491 |
492 |hugo says hello!
493 | 494 | 495 | :wq 496 | 497 | $ 498 | ``` 499 | 500 | Build the web site and then verify the results. 501 | 502 | ``` 503 | $ hugo --verbose 504 | INFO: 2014/09/29 Using config file: /Users/quoha/Sites/zafta/config.toml 505 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/themes/zafta/static/ to /Users/quoha/Sites/zafta/public/ 506 | INFO: 2014/09/29 syncing from /Users/quoha/Sites/zafta/static/ to /Users/quoha/Sites/zafta/public/ 507 | WARN: 2014/09/29 Unable to locate layout: [404.html theme/404.html] 508 | 0 draft content 509 | 0 future content 510 | 0 pages created 511 | 0 tags created 512 | 0 categories created 513 | in 2 ms 514 | 515 | $ find public -type f -name '*.html' | xargs ls -l 516 | -rw-r--r-- 1 quoha staff 78 Sep 29 21:26 public/index.html 517 | 518 | $ cat public/index.html 519 | 520 | 521 | 522 |hugo says hello!
523 | 524 | ``` 525 | 526 | #### Live Reload 527 | 528 | Note: If you're running the server with the `--watch` option, you'll see different content in the file: 529 | 530 | ``` 531 | $ cat public/index.html 532 | 533 | 534 | 535 |hugo says hello!
536 | 540 | 541 | ``` 542 | 543 | When you use `--watch`, the Live Reload script is added by Hugo. Look for live reload in the documentation to see what it does and how to disable it. 544 | 545 | ### Build a "Dynamic" Home Page 546 | 547 | "Dynamic home page?" Hugo's a static web site generator, so this seems an odd thing to say. I mean let's have the home page automatically reflect the content in the site every time Hugo builds it. We'll use iteration in the template to do that. 548 | 549 | #### Create New Posts 550 | 551 | Now that we have the home page generating static content, let's add some content to the site. We'll display these posts as a list on the home page and on their own page, too. 552 | 553 | Hugo has a command to generate a skeleton post, just like it does for sites and themes. 554 | 555 | ``` 556 | $ hugo --verbose new post/first.md 557 | INFO: 2014/09/29 Using config file: /Users/quoha/Sites/zafta/config.toml 558 | INFO: 2014/09/29 attempting to create post/first.md of post 559 | INFO: 2014/09/29 curpath: /Users/quoha/Sites/zafta/themes/zafta/archetypes/default.md 560 | ERROR: 2014/09/29 Unable to Castmy first post
808 | 809 | 810 | 811 | 812 | $ cat public/post/second/index.html 813 | 814 | 815 | 816 |my second post
821 | 822 | 823 | 824 | $ 825 | ``` 826 | 827 | Notice that the posts now have content. You can go to localhost:1313/post/first to verify. 828 | 829 | ### Linking to Content 830 | 831 | The posts are on the home page. Let's add a link from there to the post. Since this is the home page, we'll update its template. 832 | 833 | ``` 834 | $ vi themes/zafta/layouts/index.html 835 | 836 | 837 | 838 | {{ range first 10 .Data.Pages }} 839 |