diff --git a/public/posts/drafts/_data.json b/public/posts/drafts/_data.json
new file mode 100644
index 0000000..92e9d9c
--- /dev/null
+++ b/public/posts/drafts/_data.json
@@ -0,0 +1,17 @@
+{
+  "the-case-for-native": {
+    "title": "The Case for Native",
+    "timestamp": 1307084400,
+    "tags": [
+      "titanium", "native", "mobile", "apps", "platforms", "android", "ios"
+    ],
+    "author": "Sami Samhuri"
+  },
+  "mach-o-symbol-and-relocation-tables": {
+    "title": "Mach-O Symbol and Relocation Tables",
+    "timestamp": 1296547200,
+    "tags": [
+    ],
+    "author": "Sami Samhuri"
+  }
+}
diff --git a/public/posts/drafts/mach-o-symbol-and-relocation-tables.html b/public/posts/drafts/mach-o-symbol-and-relocation-tables.md
similarity index 81%
rename from public/posts/drafts/mach-o-symbol-and-relocation-tables.html
rename to public/posts/drafts/mach-o-symbol-and-relocation-tables.md
index 06bf83c..dc89618 100644
--- a/public/posts/drafts/mach-o-symbol-and-relocation-tables.html
+++ b/public/posts/drafts/mach-o-symbol-and-relocation-tables.md
@@ -3,27 +3,27 @@ with Ruby. The first post](/posts/2010/01/working-with-c-style-structs-in-ruby)
 a Ruby class used to serialize simple struct-like objects, while the second describes
 [the structure of a simple Mach-O file](/posts/2010/01/basics-of-the-mach-o-file-format).*
 
-<h2>Symbol Tables</h2>
+## Symbol Tables
 
 TODO
 
 
-<h3>N-List structures</h3>
+### N-List structures
 
 TODO
 
 
-<h3>Load Command</h3>
+### Load Command
 
 TODO
 
 
-<h2>Relocation Tables</h2>
+## Relocation Tables
 
 TODO
 
 
-<h2>Putting it all together</h2>
+## Putting it all together
 
 As promised I'll show you how to create a very basic Mach-O binary
 that you can execute on a machine running OS X (well, any x86 machine
diff --git a/public/posts/drafts/2011.06.03-the-case-for-native.md b/public/posts/drafts/the-case-for-native.md
similarity index 97%
rename from public/posts/drafts/2011.06.03-the-case-for-native.md
rename to public/posts/drafts/the-case-for-native.md
index 84da393..3a29616 100644
--- a/public/posts/drafts/2011.06.03-the-case-for-native.md
+++ b/public/posts/drafts/the-case-for-native.md
@@ -1,9 +1,3 @@
-Title: The Case For Native
-Date: June 3, 2011
-Author: sjs
-Tags: titanium, native, mobile, apps, platforms, android, ios
-----
-
 For the past month I've been using [Appcelerator Titanium](http://www.appcelerator.com/products/) on a two man team. We made a simple iPhone app with a tab bar with embedded nav controllers, just 10 screens or so total. We started porting it to the iPad and Android so have some experience there. It's been a pretty frustrating exercise most days. I had a lot of little complaints but didn't take the time to step back and look at the bigger picture. I love JavaScript and in theory Titanium is awesome and a huge win. I wanted it to be a win but in reality it just hasn't been.
 
 Here are 9 reasons why native is better in the short and long run.
@@ -23,7 +17,7 @@ They're better. For these reasons:
  - Debuggers. Yup, they're useful.
 
  - Xcode / Interface Builder for iOS, Faster prototyping by using a GUI to build your GUIs.
- 
+
    *[One more level, we can go deeper.... BRRRAAAAAAUUUUUM](http://youtu.be/d2yD4yDsiP4)*
 
  - Android has XML layout which is somewhat better than code. Not as a big a win but still a win. Declarative is better than imperative.