Upgrade boostrap-sass to 2.1.0.0
Add support for Atom categories

category to map tags is as good as any solution
and complies with the atom validators
http://edward.oconnor.cx/2007/02/representing-tags-in-atom
Fix display of author in feed

In ruby 1.9.3 on Mac, defined? does not seem to work. I tested with
and without the presence of the said values in a blog entry to make
sure it does not fail if the data is not defined.
Trivial change (to get build working).
Use proper variable name in transformers loop

Use the variable name t instead of e when looping over transformers.
Move :html, :js and :css compression from using cmd to ruby gems

The minfiy extension rely on calling yuicompressor and htmlcompressor on
the command line with no control if they are installed or not. Change Minify
to use the htmlcompressor and yui-compressor ruby gems to control the
dependencies.

pngcrush is untouched and still rely on calling the cmd.

Includes :html, :css and :js compression spec tests.
issue 186: fix assignment of post archives on site
add support for handling less stylesheets
Merge pull request #175 from rhauch/upgrade-boostrap

Upgrade boostrap-sass to 2.1.0.0
Merge pull request #177 from emmanuelbernard/atom_category

Add support for Atom categories. The buildhive failure was a problem with the build, not this change.
Merge pull request #178 from emmanuelbernard/feed_author_fix

Fix display of author in feed
Merge pull request #181 from mojavelinux/master

Use proper variable name in transformers loop
Merge pull request #182 from aslakknutsen/minify_convert

Move :html, :js and :css compression from using cmd to ruby gems

Thanks for adding a spec!
Merge pull request #187 from mojavelinux/issue-186

issue 186: fix assignment of post archives on site
Merge pull request #188 from mojavelinux/less-handler

add support for handling less stylesheets
Fix for issue #183
Add spec for handling an empty .awestruct_ignore file
Be explicit about libv8 requirements
Adding 'selected_tag' as an argument to the paginator

This 'selected_tag' variable becomes available in the page context if
the page is generated by the tagger. This enables the generated page
to display the current tag in the page body.

For example, if /news/tags/awestruct/index.html is generated, the page
can display somewhere in its body that theselected tag is: "awestruct"