middleman/middleman-blog — pull request #129 by rmm5t (2013-05-27 04:27:51+00:00)
Title: Kramdown is krammed down our throats

(sorry, couldn't help the pun)

[This change](https://github.com/middleman/middleman-blog/commit/03d2db9b2adf3680ce3a03beace333892d8c5586#L1L40) sets kramdown as the markdown engine when a blog is activated.

This change does not allow for the markdown engine to be specified (as something other than kramdown) before the blog is activated in config.rb. Instead, for example, if you want to use redcarpet or maruku, you must now set the markdown engine _after_ activating the blog.

Even though I understand that the default markdown engine is changing from maruku to kramdown, I don't understand the necessity of this forced setting to kramdown since a default markdown engine is already specified in middleman-more.

My suggestion is to remove this forced markdown engine behavior from middleman-blog. If the middleman-blog test suite needs kramdown, then I would suggest that it only be hard set in the test suite, not for all blogs.

I'm willing to work on cleaning this up, but I first wanted to open the discussion in case I'm missing something very important.