bump tilt requirement, unregister plaintext template. fixes #824
prep
changelog
Remove Rainpress pure ruby CSS compressor and simply use SCSS :)
Document livereload usage in config file
Suggest adding middleman-livereload to bundle
Fix several issues around i18n and resource metadata.

There are a few things changing here. One is that we always dup metadata before using it - this prevents a class of nasty bugs where after the first resource list build, blocks had been deleted from metadata hashes, meaning they would no longer be applied. Now they will always stick around. Then, I made sure that whenever we render a file, we save the previous I18n.locale and restore it afterwards, in case people change locale from blocks. This should help in some weird cases where files are rendered recursively. Finally, I've added a :lang option that can be used from "page" or "proxy" to allow people to specify the language for one or more files without having to pass a block that sets I18n.locale directly, which should make that pattern much cleaner. This fixes #809 and may also fix middleman/middleman-blog#106.
Added .idea dir to .gitignore

… just in case if somebody uses RubyMine to dev it.
Merge pull request #845 from bhollis/i18n

Fix several issues around i18n and resource metadata.
Merge pull request #846 from argent-smith/master

Added .idea to .gitignore
add feature tests for markdown support in haml
Merge pull request #849 from stevenosloan/markdown_filter_in_haml

Markdown filter support for Haml 4
More agressively set the context for our custom Markdown renderer, and fall back if we still don't manage to get it right. Fixes #662.
Handle empty frontmatter without logging an exception
Undo my previous change, apparently it is no good
Fixes for alpha Sass versions
Minor performance fix to not double-compute metadata in directory_indexes.
Simplify frontmatter by removing its resource_list_manipulator
Fix a bunch of Ruby warnings, including a bug in the not_found method
Overhaul content-type handling, making it configurable via page/proxy commands as well as frontmatter with the 'content_type' parameter.

Now, users can set content type explicitly for their files in a number of ways, or rely on automatic file-extension content types. Proxied files default to automatic file-extension content types, but then fall back to the content type of the resource they proxy to. There is also a bug fixed around correctly setting content type inside send_file. Fixes #821.