This is anything else, css files, images, fixed pages, layouts. This content lives in the `source` directory.
If you added `source/images/horse.png` is would be available at the url `/images/horse.png` after publishing it.
Content processing is applied to normal content if it has the correct header as described below.
## Content processing
Three types of content can have special processing done.
-`.html` liquid/HTML files
-`.md` markdown files
-`.textile` textile files
All files to be processed should also have a special header at the top too:
---
layout: default
title: Some Very Wordy and Expressive Title
menu_title: Some Title
---
<p>My Actual Content</p>
The `title` field will end up as an `h1` in the right panel. The `menu_title` is what is used in the menu tree on the left (if not preset it will default to using `title`).
### `.html` files
These are almost normal html, but extended with [Liquid templates](http://liquidmarkup.org/). There are a couple of special tags created for this project.
-`{% tree %}` is what shows the manual structure in the left column
-`{% children %}` shows the immediate list of children for a page
Much of the functionality comes from `_plugins/manual.rb` - it takes the _manual format_ (contained in `_manual/`) and mushes it around a bit into a tmp directory.
This is to enable the directory tree to be understood, child page lists to be constructed, clean URLs, and the correct ordering of pages maintained.
### Clean URLs
To allow the clean URLs (no `.html` extension) _and_ to support simple hosting (no `.htaccess` or apache configuration required) each page ends up in it's own directory with an `index.html` page for the content.
E.g. `02_main/05_more/02_blah.html` after all processing is complete would end up in `_site/main/more/blah/index.html`.
The page format contained in the `_manual/` directory is different to the final rendered output (see special `_manual` content above) to make it simple to create content (you don't need to think about the `index.html` files).