Headings with paragraphs

h1. Heading

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.

h2. Heading

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.

h3. Heading

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.

h4. Heading

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.

h5. Heading

The information in the front matter is passed into the template before the content is rendered into HTML.

h6. Heading

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.

Headings

h1. Heading

h2. Heading

h3. Heading

h4. Heading

h5. Heading

h6. Heading

Multi-line Headings

h1. When the Pawn Hits the Conflicts He Thinks like a

h2. King What He Knows Throws the Blows When He Goes to the Fight and He’ll Win

h3. The Whole Thing He Enters the Ring There’s No Body to Batter

h4. When Your Mind Is Your Might so When You Go Solo You Hold Your Own Hand and

h5. Remember That Depth Is the Greatest of Heights and If You Know Where You Stand, Then You Know Where

h6. To Land and If You Fall It Won’t Matter, Cuz You’ll Know That You’re Right Fiona Apple

Paragraph

Lorem ipsum dolor sit amet, test link adipiscing elit. Nullam dignissim convallis est. Quisque aliquam. Donec faucibus. Nunc iaculis suscipit dui. Nam sit amet sem. Aliquam libero nisi, imperdiet at, tincidunt nec, gravida vehicula, nisl. Praesent mattis, massa quis luctus fermentum, turpis mi volutpat justo, eu volutpat enim diam eget metus. Maecenas ornare tortor. Donec sed tellus eget sapien fringilla nonummy. Mauris a ante. Suspendisse quam sem, consequat at, commodo vitae, feugiat in, nunc. Morbi imperdiet augue quis tellus.

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.

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.

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?

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.

The rest of this tutorial will call a skin created in the themes/ directory a theme.

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.

List Types

Definition List

Definition List Title

This is a definition list division.

Ordered List

1. List Item 1
2. List Item 2
3. List Item 3

Unordered List

• List Item 1
• List Item 2
• List Item 3

%default-ol Ordered List

1. List Item 1
2. List Item 2
3. List Item 3

%default-ul Unordered List

• List Item 1
• List Item 2
• List Item 3

Code

## this is a comment
$ echo this is a command
this is a command

## edit the file
$vi foo.md

+++
date = "2014-09-28"
title = "creating a new theme"
+++

bah and humbug
:wq

<h1>Hello World</h1>

func main() {
  fmt.Println('hello world');
}

## show it
$ cat foo.md
+++
date = "2014-09-28"
title = "creating a new theme"
+++

bah and humbug

Fieldsets and Form Elements

TODO: Add fieldsets here

Tables