mirror of
https://github.com/gohugoio/hugoDocs.git
synced 2025-09-11 15:16:45 -04:00
sanity: move from json to yaml
This commit is contained in:
parent
fade418bc3
commit
0dce06a04d
@ -1,4 +0,0 @@
|
|||||||
{
|
|
||||||
"Indexes" : {"tag": "tags"},
|
|
||||||
"BaseUrl" : "http://localhost"
|
|
||||||
}
|
|
4
config.yaml
Normal file
4
config.yaml
Normal file
@ -0,0 +1,4 @@
|
|||||||
|
Indexes:
|
||||||
|
tag: 'tags'
|
||||||
|
BaseUrl: 'http://localhost'
|
||||||
|
...
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Configuring Hugo",
|
title: "Configuring Hugo"
|
||||||
"Pubdate": "2013-07-01"
|
pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
The directory structure and templates provide the majority of the
|
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
|
configuration for a site. In fact a config file isn't even needed for many websites
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Contributing to Hugo",
|
title: "Contributing to Hugo"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
1. Fork it from https://github.com/spf13/hugo
|
1. Fork it from https://github.com/spf13/hugo
|
||||||
2. Create your feature branch (`git checkout -b my-new-feature`)
|
2. Create your feature branch (`git checkout -b my-new-feature`)
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Contributors",
|
title: "Contributors"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Hugo was built with love and golang by:
|
Hugo was built with love and golang by:
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Example Content File",
|
title: "Example Content File"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Somethings are better shown than explained. The following is a very basic example of a content file:
|
Somethings are better shown than explained. The following is a very basic example of a content file:
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Front Matter",
|
title: "Front Matter"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
The front matter is one of the features that gives Hugo it's strength. It enables
|
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
|
you to include the meta data of the content right with it. Hugo supports a few
|
||||||
|
@ -1,7 +1,8 @@
|
|||||||
{
|
---
|
||||||
"title": "Installing Hugo",
|
title: "Installing Hugo"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Hugo is written in GoLang with support for Windows, Linux, FreeBSD and OSX.
|
Hugo is written in GoLang with support for Windows, Linux, FreeBSD and OSX.
|
||||||
|
|
||||||
The latest release can be found at [hugo releases](https://github.com/spf13/hugo/releases).
|
The latest release can be found at [hugo releases](https://github.com/spf13/hugo/releases).
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "License",
|
title: "License"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Hugo is released under the Simple Public License.
|
Hugo is released under the Simple Public License.
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Organization",
|
title: "Organization"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Hugo uses markdown files with headers commonly called the front matter. Hugo respects the organization
|
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
|
that you provide for your content to minimize any extra configuration, though this can be overridden
|
||||||
|
@ -1,8 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Release Notes",
|
title: "Release Notes"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
|
...
|
||||||
}
|
|
||||||
|
|
||||||
* **0.7.0** July 4, 2013
|
* **0.7.0** July 4, 2013
|
||||||
* Hugo now includes a simple server
|
* Hugo now includes a simple server
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Roadmap",
|
title: "Roadmap"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
In no particular order, here is what I'm working on:
|
In no particular order, here is what I'm working on:
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Shortcodes",
|
title: "Shortcodes"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Because Hugo uses markdown for it's content format, it was clear that there's a lot of things that
|
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.
|
markdown doesn't support well. This is good, the simple nature of markdown is exactly why we chose it.
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Source Directory Organization",
|
title: "Source Directory Organization"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Hugo takes a single directory and uses it as the input for creating a complete website.
|
Hugo takes a single directory and uses it as the input for creating a complete website.
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Templates",
|
title: "Templates"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Hugo uses the excellent golang html/template library for it's template engine. It is an extremely
|
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
|
lightweight engine that provides a very small amount of logic. In our
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Using Hugo",
|
title: "Using Hugo"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Make sure either hugo is in your path or provide a path to it.
|
Make sure either hugo is in your path or provide a path to it.
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
{
|
---
|
||||||
"title": "Variables",
|
title: "Variables"
|
||||||
"Pubdate": "2013-07-01"
|
Pubdate: "2013-07-01"
|
||||||
}
|
...
|
||||||
|
|
||||||
Hugo makes a set of values available to the templates. Go templates are context based. The following
|
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.
|
are available in the context for the templates.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user