title |
---|
The config file |
Config files should be YAML.
Prefer multi-line arrays for readability and version control purposes.
Good:
numbers:
- one
- two
- three
Bad:
numbers: [one, two, three]
Use the following site-wide variables, where appropriate:
title
- the name of the site. Usetitle
and not name to match document and page meta.description
- the site's tagline or subtitle
The site's base URL is only to be used when the resulting site lives at a subpath of the domain. Otherwise, the subpath should be nil, not /
.
- Example 1: If your site lives at
example.com/blog
, you should have abaseurl
of/blog
. - Example 2: If your site lives at
example.com
, you should not set abaseurl
. Not even/
.
When your site is intended to be hosted on GitHub Pages, prefer values in the site.github
namespace to manually specified values. In additional to reducing configuration noise, this will save headache if your repository is renamed, you add a CNAME, the project is forked, or if you preview the site locally.
Prefer site.github.url
when using GitHub Pages. To ensure your site renders properly locally, add the following to your site's config (which will be overridden by GitHub Pages):
github:
url: http://localhost:4000