YAML support similar to jekyll (start and end with '---')

docs/content/doc/configuration.md

@@ -1,7 +1,7 @@
 ---
 title: "Configuring Hugo"
 pubdate: "2013-07-01"
-...
+---
 
 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

docs/content/doc/contributing.md

@@ -1,7 +1,7 @@
 ---
 title: "Contributing to Hugo"
 Pubdate: "2013-07-01"
-...
+---
 
 1. Fork it from https://github.com/spf13/hugo
 2. Create your feature branch (`git checkout -b my-new-feature`)

docs/content/doc/contributors.md

@@ -1,7 +1,7 @@
 ---
 title: "Contributors"
 Pubdate: "2013-07-01"
-...
+---
 
 Hugo was built with love and golang by:
 

docs/content/doc/example.md

@@ -1,7 +1,7 @@
 ---
 title: "Example Content File"
 Pubdate: "2013-07-01"
-...
+---
 
 Somethings are better shown than explained. The following is a very basic example of a content file:
 

docs/content/doc/front-matter.md

@@ -1,7 +1,7 @@
 ---
 title: "Front Matter"
 Pubdate: "2013-07-01"
-...
+---
 
 The front matter is one of the features that gives Hugo it's strength. It enables
 you to include the meta data of the content right with it. Hugo supports a few 
@@ -16,7 +16,7 @@ different formats. The main format supported is YAML. Here is an example:
       - "Development"
       - "VIM"
     Slug: "spf13-vim-3-0-release-and-new-website"
-    ...
+    ---
 
 ### Variables
 

docs/content/doc/installing.md

@@ -1,7 +1,7 @@
 ---
 title: "Installing Hugo"
 Pubdate: "2013-07-01"
-...
+---
 
 Hugo is written in GoLang with support for Windows, Linux, FreeBSD and OSX.
 

docs/content/doc/license.md

@@ -1,7 +1,7 @@
 ---
 title: "License"
 Pubdate: "2013-07-01"
-...
+---
 
 Hugo is released under the Simple Public License.
 

docs/content/doc/organization.md

@@ -1,7 +1,7 @@
 ---
 title: "Organization"
 Pubdate: "2013-07-01"
-...
+---
 
 Hugo uses markdown files with headers commonly called the front matter. Hugo respects the organization
 that you provide for your content to minimize any extra configuration, though this can be overridden

docs/content/doc/release-notes.md

@@ -1,7 +1,7 @@
 ---
 title: "Release Notes"
 Pubdate: "2013-07-01"
-...
+---
 
 * **0.7.0** July 4, 2013
   * Hugo now includes a simple server

docs/content/doc/roadmap.md

@@ -1,7 +1,7 @@
 ---
 title: "Roadmap"
 Pubdate: "2013-07-01"
-...
+---
 
 In no particular order, here is what I'm working on:
 

docs/content/doc/shortcodes.md

@@ -1,7 +1,7 @@
 ---
 title: "Shortcodes"
 Pubdate: "2013-07-01"
-...
+---
 
 Because Hugo uses markdown for it's content format, it was clear that there's a lot of things that 
 markdown doesn't support well. This is good, the simple nature of markdown is exactly why we chose it.

docs/content/doc/source-directory.md

@@ -1,7 +1,7 @@
 ---
 title: "Source Directory Organization"
 Pubdate: "2013-07-01"
-...
+---
 
 Hugo takes a single directory and uses it as the input for creating a complete website.
 

docs/content/doc/templates.md

@@ -1,7 +1,7 @@
 ---
 title: "Templates"
 Pubdate: "2013-07-01"
-...
+---
 
 Hugo uses the excellent golang html/template library for it's template engine. It is an extremely
 lightweight engine that provides a very small amount of logic. In our 

docs/content/doc/usage.md

@@ -1,7 +1,7 @@
 ---
 title: "Using Hugo"
 Pubdate: "2013-07-01"
-...
+---
 
 Make sure either hugo is in your path or provide a path to it.
 

docs/content/doc/variables.md

@@ -1,7 +1,7 @@
 ---
 title: "Variables"
 Pubdate: "2013-07-01"
-...
+---
 
 Hugo makes a set of values available to the templates. Go templates are context based. The following
 are available in the context for the templates.