Using new parser.
Added safeHtml template function
Normalize paths within hugo

filepath was used inconsistently throughout the hugolib.  With the
introduction of source and target modules, all path are normalized to
"/".  This simplifies the processing of paths.  It does mean that
contributors need to be aware of using path/filepath in any module other
than source or target is not recommended.  The current exception is
hugolib/config.go
Move alias rendering to target
Move alias logic to target module

I want to move all logic to writing aliases to target so I can pave the
way for writing aliases specific to other runtimes (like .htaccess for
apache or a script for updating AWS or symlinking on a filesystem).
Remove RenderedContent from page.

The output is written directly to disk after being written.  Not
entirely sure why it was split into two steps.
Add /index.html to unadorned alias paths

Bring code to be better in line with documentation.
Initialize HTMLRedirectAlias before ShowPlan()

Without it, no alias information is generated when running --check
Fix alias documentation.

Fixes #79
Add a transform step

This allows for the manipulation of the DOM.  This is expected to be
applied after the templates are rendered.
Move AbUrlify to post content transformation

Currently the a@href and script@src elements will have BaseUrl applied
to their elements prior to being written to disk.
Merge remote-tracking branch 'origin/parser' into mrg_praser

Also brought in parse for github.com/noahcampbell/akebia

Conflicts:
	hugolib/page.go
	hugolib/page_test.go
Fix parsing edge case of frontmatter

When the frontmatter contains a - (or other delimiter) close to the
closing frontmatter delimiter, frontmatter detection would fail.
Add IsRenderable to Page

As pages are read from the target, they will be assessed if they should
be rendered or not.  The logic for IsRenderable is in the parser/page.go
and looks for anything exception '<'.
Add renderer information to --check

Now reports if the page will be rendered or not and by which render
engine.
More expressive --check output
Allow non-markdown content in content directory

Allow content that is not markdown and does not need to be rendered to
exists in the content directory.  Currently any valid html or xml
document can exist.  Templates are applied to these documents as well.
If you need to have content that doesn't have templates or AbsUrlify
like operations, then continue to put this content in static and it will
be copied over.
Fix fragments being AbsUrlified in final html

Found that fragments were getting the BaseURL applied creating a proper
anchor url and redirecting off the page.
Section is determined by the source, not the url

This change allows for top level html content to exists.
Create a TargetPath() method that provides OutFile

Moved the generation of the target path to the page breaking all
dependecies on Site.