README.md in slodown-0.3.0 vs README.md in slodown-0.4.0
- old
+ new
@@ -6,11 +6,11 @@
**I love Markdown. I love syntax highlighting. I love oEmbed. And last but not least, I love whitelist-based HTML sanitizing. Slodown rolls all of these into one, and then some.**
Here's what Slodown does by default:
-- **render extended Markdown into HTML**. It uses the [kramdown](http://kramdown.rubyforge.org/) library, so yes, footnotes are supported!
+- **render extended Markdown into HTML**. It uses the [kramdown](http://kramdown.gettalong.org/) library, so yes, footnotes are supported!
- **add syntax highlighting to Markdown code blocks** through [CodeRay](http://coderay.rubychan.de/), [Rouge](http://rouge.jneen.net/), or any other highlighter supported by kramdown.
- **support super-easy rich media embeds**. Just point the Markdown image syntax at, say, a Youtube video, and Slodown will fetch the complete embed code through the magic of [ruby-oembed](https://github.com/judofyr/ruby-oembed).
- **auto-link contained URLs** using [Rinku](https://github.com/vmg/rinku), which is smart enough to not auto-link URLs contained in, say, code blocks.
- **sanitize the generated HTML** using the white-list based [sanitize](https://github.com/rgrove/sanitize) gem, with some really good default configuration.
@@ -23,11 +23,11 @@
- Convert all Markdown to HTML.
- Don't strip HTML the user added themselves.
- Auto-link contained URLs and email addresses.
- Finally, and most importantly, run the entire HTML through a really, really good whitelist-based sanitizer.
-This allows users to still add their own HTML, if required. In fact, I typically encourage users to make use of [kramdown's inline attributes], leaving it up the sanitizer to make sure they don't go crazy.
+This allows users to still add their own HTML, if required. In fact, I typically encourage users to make use of [kramdown's inline attributes](http://kramdown.gettalong.org/syntax.html#inline-attribute-lists), leaving it up the sanitizer to make sure they don't go crazy.
If this is not what you want, you will most likely be able to bend Slodown to your will -- it's pretty flexible.
## Usage
@@ -146,9 +146,15 @@
2. The pull request must only contain changes _related to the feature_.
3. Please include specs where it makes sense.
4. Absolutely _no_ version bumps or similar.
## Version History
+
+### 0.4.0 (2017-01-13)
+
+- Feature: Block-level images are now rendered as a complete `<figure>` structure (with optional `<figcaption>`.)
+- Change: The Slodown sanitizer now allows `<figure>`, `<figcaption>`, `<cite>`, `<mark>`, `<del>` and `<ins>` tags by default.
+- Change: The Slodown sanitizer was stripping HTML of table tags. Tables are harmless, so they're not being stripped any longer.
### 0.3.0 (2016-02-22)
- Removed the dependency on CodeRay. If you want syntax highlighting in your Markdown parsing, simply add CodeRay (or Rouge, or any other highlighter supported by kramdown) to your project.