hugo/docs/content/overview/configuration.md
Anthony Fok d397bc4f43 [Docs] Complete the transition from "indexes" to "taxonomies" (almost)
Also mention `.Site.Indexes` → `.Site.Taxonomies` as well as
the upcoming `.Site.Recent` → `.Site.Pages` transitions.
2015-01-29 12:48:14 -07:00

5.1 KiB
Raw Blame History

aliases date linktitle menu next notoc prev title weight
/doc/configuration/
2013-07-01 Configuration
main
parent
getting started
/overview/source-directory true /overview/usage Configuring Hugo 40

The directory structure and templates provide the majority of the configuration for a site. In fact, a config file isn't even needed for many websites since the defaults follow commonly used patterns.

Hugo expects to find the config file in the root of the source directory and will look there first for a config.toml file. If none is present, it will then look for a config.yaml file, followed by a config.json file.

The config file is a site-wide config. The config file provides directions to hugo on how to build the site as well as site-wide parameters and menus.

Examples

The following is an example of a typical yaml config file:

---
baseurl: "http://yoursite.example.com/"
...

The following is an example of a toml config file with some of the default values. Values under [params] will populate the .Site.Params variable for use in templates:

contentdir = "content"
layoutdir = "layouts"
publishdir = "public"
builddrafts = false
baseurl = "http://yoursite.example.com/"
canonifyurls = true

[taxonomies]
  category = "categories"
  tag = "tags"
   
[params]
  description = "Tesla's Awesome Hugo Site"
  author = "Nikola Tesla"

Here is a yaml configuration file which sets a few more options

---
baseurl: "http://yoursite.example.com/"
title: "Yoyodyne Widget Blogging"
footnotereturnlinkcontents: "↩"
permalinks:
  post: /:year/:month/:title/
params:
  Subtitle: "Spinning the cogs in the widgets"
  AuthorName: "John Doe"
  GitHubUser: "spf13"
  ListOfFoo:
    - "foo1"
    - "foo2"
  SidebarRecentLimit: 5
...

Configure Blackfriday rendering

Blackfriday is the Markdown rendering engine used in Hugo. The Blackfriday configuration in Hugo is mostly a set of sane defaults that should fit most use cases.

But Hugo does expose some options---as listed in the table below, matched with the corresponding flag in the Blackfriday source (html.go and markdown.go):

FlagDefaultBlackfriday flag
angledQuotes false HTML_SMARTYPANTS_ANGLED_QUOTES
Purpose: Enable smart angled double quotes (e.g. "Hugo" renders to «Hugo» instead of “Hugo”)
fractions true HTML_SMARTYPANTS_FRACTIONS
Purpose: Enable smart fractions (e.g. 5/12 renders to 512 (<sup>5</sup>&frasl;<sub>12</sub>)) Caveat: Even with fractions = false, Blackfriday would still convert 1/2, 1/4 and 3/4 to ½ (&frac12;), ¼ (&frac14;) and ¾ (&frac34;) respectively, but only these three.
plainIdAnchors false FootnoteAnchorPrefix and HeaderIDSuffix
Purpose: If true, then header and footnote IDs are generated without the document ID (e.g. #my-header instead of #my-header:bec3ed8ba720b9073ab75abcf3ba5d97)
extensions [] EXTENSION_*
Purpose: Use non-default additional extensions (e.g. Add "hardLineBreak" to use EXTENSION_HARD_LINE_BREAK)

Note that these flags must be grouped under the blackfriday key and can be set on both site and page level. If set on page, it will override the site setting. Example:

TOMLYAML
[blackfriday]
  angledQuotes = true
  fractions = false
  plainIdAnchors = true
  extensions = ["hardLineBreak"]
blackfriday:
  angledQuotes: true
  fractions: false
  plainIdAnchors: true
  extensions:
    - hardLineBreak

Notes

Config changes are not reflected with LiveReload.

Please restart hugo server --watch whenever you make a config change.