Skip to content

Latest commit

 

History

History
61 lines (50 loc) · 1.77 KB

defaults.markdown

File metadata and controls

61 lines (50 loc) · 1.77 KB
Raw
title date position
Default fields
2016-05-25 22:00:00 -0400
6

Instead of defining fields each time you create a page, post, or document, you can set defaults in your _config.yml theme file. In most cases, it'll be handy to set at least the default layout.

The defaults key in your _config.yml file is a list of different defaults. Each list item has two objects: scope and values.

  • scope is how you choose which collection and files you're defining defaults on.
  • values is where you define your default fields as key/value pairs. Keys can be nested and their values are optional.

For example:

{% highlight yaml %} defaults:

scope:
  path: ""
  type: "posts"
values:
  layout: "default"
  author: "Ethan"
  • scope: path: "" type: "pages" values: layout: "page"
  • scope: path: "projects" type: "pages" values: colors: ["red", "green", "blue"] layout: "project"
  • scope: path: "" type: "locations" values: map: latitude: longitude: {% endhighlight %}

In this case, we're:

  • Setting the default layout and author for all posts.
  • Setting the default layout for all pages.
  • Overriding the previous default layout for all pages in the projects/ path, and setting a default colors List field with the values red, green, blue.
  • Defining fields for map.latitude and map.longitude for all documents in the locations collection. Using blank values, these fields will show up to content editors but remain optional.

Note that type can be posts, pages or any other collection name (e.g. people).

Further Reading: