Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Removed some typos / bad writing

  • Loading branch information...
commit cf0acf6da3b8e7e4f8eb502cd56e06fbe2ebe015 1 parent 60a6ef1
@benschwarz authored
Showing with 3 additions and 3 deletions.
  1. +3 −3 content/2.how-it-works/default.yml
View
6 content/2.how-it-works/default.yml
@@ -14,15 +14,15 @@
### Content
All content is stored on the file system in the "content" directory, the folder paths that you use will imply the paths used on the final web site.
- For example, a page that was kept under `content/about-us/services` will have a permalink of "/about-us/services".
+ For example, a page kept under `content/about-us/services` will have a permalink of "/about-us/services".
For a page to be recognised, you'll need a `template-name.yml` file. The "template-name" section of the file name referrers to the template that will be used to render your page.
The yml file holds the textual content for your page, you can create key/value pairs with strings, hashes or arrays. This allows for outputting text or iterating over more complex objects to write them into your template neatly.
- #### Ordering and "Floating" pages
+ #### Page order and "Floating" pages
- Bonsai will order your pages within the "navigation", "children" and "siblings" arrays by the prefix given to its parent folder. `content/1.about-us` will be ordered before `content/2.products` but don't worry - this will be cleaned up and removed from the final permalink
+ Bonsai will order your pages within the "navigation", "children" and "siblings" arrays by the prefix given to its parent folder. `content/1.about-us` will be ordered before `content/2.products` but don't worry - this will be cleaned up and removed from the final permalink.
"Floating" pages are not present in the "navigation", "children" or "siblings" arrays. This can be achieved by _not_ prefixing the containing directory eg `content/about-us/services` with a digit.
Please sign in to comment.
Something went wrong with that request. Please try again.