GitXplorerGitXplorer
s

metadown

public
69 stars
6 forks
2 issues

Commits

List of commits on branch master.
Unverified
972c908cfbbe750a73a108467d432d41879c859f

Remove ruby-head

ssteveklabnik committed 12 years ago
Unverified
67622c062f2bdf5b08f2bbc3b7529b62cbffe7d1

Merge pull request #2 from miloshadzic/master

ssteveklabnik committed 12 years ago
Unverified
4b62eb30c08b35097b027da9baa012c1044bd333

Make it easier to inject your own Markdown renderer.

mmiloshadzic committed 12 years ago
Unverified
84f4bb751cf7fd3284d1e0eeb8871da4fda53fe7

Allow you to inject your own parser.

ssteveklabnik committed 13 years ago
Unverified
56aa762eb5268840737e0af111cb820ff913f69a

bumping to 1.0.1

ssteveklabnik committed 13 years ago
Unverified
ea6e6c75030db4cc13130423f4337e0fd3f53fc7

Fixing homepage in the gemspec

ssteveklabnik committed 13 years ago

README

The README file for this repository.

Metadown

Build Status

tl;dr... This gem gives you a custom markdown parser that allows you to prefix the markdown itself with YAML metadata.

Sometimes, just having plain markdown isn't good enough. Say you're writing a blog post, and you want to include some information about the post itself, such as the date and time it was posted. Keeping it in a separate file seems like a bad idea, but Markdown doesn't have any good way of doing this.

Enter Jekyll. It lets you put some YAML at the head of your file:

---
layout: post
title: An Awesome Blog Post
---

Four score and seven years ago,

Woudn't that be neat to use on other projects? I thought so too! Hence, metadown.

Furthermore, you don't have to have just markdown. Inject any kind of parser you'd like!

Installation

Add this line to your application's Gemfile:

gem 'metadown'

And then execute:

$ bundle

Or install it yourself as:

$ gem install metadown

Usage

Metadown might have the simplest API I've ever written: one method! Just send the string with the metadown you want rendered, and boom! You get an object back with two attributes: output and metadata.

require 'metadown'

data = Metadown.render("hello world")
data.output #=> "<p>hello, world</p>"
data.metadata #=> "{}"

text = <<-MARKDOWN
---
key: "value"
---
hello world
MARKDOWN

data = Metadown.render(text)
data.output #=> "<p>hello, world</p>\n"
data.metadata #=> {"key" => "value"}

The default Markdown parser Metadown uses is pretty simple. If you'd like to change it, you can inject your own in the standard Redcarpet fashion. Here's an example with code highlighting using Pygments.

class HTMLwithPygments < Metadown::Renderer
  def block_code(code, language)
    Pygments.highlight(code, :lexer => language)
  end
end

Then use it with Metadown like this:

require 'metadown'
require 'html_with_pygments'

renderer = Redcarpet::Markdown.new(HTMLwithPygments, :fenced_code_blocks => true)
data = Metadown.render("```ruby\nself\n```", renderer)
data.output   #=> "<div class=\"highlight\"><pre><span class=\"nb\">self</span>\n</pre>\n</div>\n"
data.metadata #=> "{}"

The Redcarpet README has more examples on how to customize your Markdown rendering.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request