don't process rakefile, readme
Merge remote-tracking branch 'origin/master'
fix typo
Add new Integration points for themes

The new system will try to namespace all framework integrations with 'JB'. Integration points added in this comment are 'analytics', 'comments', and 'sharing'.
Add JB configuration hash to site config
Update themes to use new integration methods
Themes can define configuration data

Themes can define a 'settings.yml' file which will get injected into the root default.html layout YAML Front Matter which can be accessed through the 'page' variable.
Add ability to dynamically set url paths

This makes GitHub Pages for projects support possible as all urls will need to call on the project's subfolder. The other important piece is that urls should resolve to root locally but be able to change when in production. LLastly this gives themes clear integration points for working with paths. (the jbcache hack just makes it so there is not unnecessary whitespace output in the source.
Provide set_paths to all layouts
Provide path configuration in _config.yml
Need to provide theme name via settings.yml
Update themes and pages to new paths api
Regenerate 'twitter' theme
Rename set_paths to more generic 'setup'

This is because 'setup' will need to be included in every post/page file if we want to have access to BASE_PATH. So I figure 'setup' will be a good access path for any future inclusions we need to make
Include 'JB/setup' in all posts and pages

This is the only way we can have global access to dynamic liquid variables. Using site configuration is too convulated since switching themes and runing in development vs. production relies on being able to dynamically define variables
rename HOME_URL to HOME_PATH
Refactor new post rake task

Rename from 'rake new_post' to 'rake post'. Also use environment variables over rake arguments
Add rake task to create pages

Usage: rake page name='about.md'
Move helpers to namespaced system

Also do away with .html extension
Update helper calls

Use 'JB/[HELPER]' format