diff --git a/app.js b/app.js
index b8663819c9..bf87e283f5 100644
--- a/app.js
+++ b/app.js
@@ -1,25 +1,28 @@
 // # Ghost main app file
 
-/*global require */
+/*global require, __dirname */
 (function () {
     "use strict";
 
     // Module dependencies.
     var express = require('express'),
-        fs = require('fs'),
         admin = require('./core/admin/controllers'),
         frontend = require('./core/frontend/controllers'),
+        api = require('./core/shared/api'),
         flash = require('connect-flash'),
         Ghost = require('./core/ghost'),
         I18n = require('./core/lang/i18n'),
-        helpers = require('./core/frontend/helpers'),
-        auth,
+        helpers = require('./core/frontend/helpers');
+
+
+
+    var auth,
 
     // ## Variables
-    /**
-     * Create new Ghost object
-     * @type {Ghost}
-     */
+        /**
+         * Create new Ghost object
+         * @type {Ghost}
+         */
         ghost = new Ghost();
 
     ghost.app().configure('development', function () {
@@ -46,11 +49,13 @@
 
     /**
      * API routes..
-     * @todo convert these into a RESTful, public, authenticated API!
+     * @todo auth should be public auth not user auth
      */
-    ghost.app().post('/api/v0.1/posts/create', auth, admin.posts.create);
-    ghost.app().post('/api/v0.1/posts/edit', auth, admin.posts.edit);
-    ghost.app().get('/api/v0.1/posts', auth, admin.posts.index);
+    ghost.app().get('/api/v0.1/posts', auth, api.requestHandler(api.posts.browse));
+    ghost.app().get('/api/v0.1/posts/:id', auth, api.requestHandler(api.posts.read));
+    ghost.app().post('/api/v0.1/posts/create', auth, api.requestHandler(api.posts.add));
+    ghost.app().put('/api/v0.1/posts/edit', auth, api.requestHandler(api.posts.edit));
+    ghost.app()['delete']('/api/v0.1/posts/:id', auth, api.requestHandler(api.posts.destroy));
 
     /**
      * Admin routes..
@@ -75,6 +80,10 @@
 
     ghost.app().listen(3333, function () {
         console.log("Express server listening on port " + 3333);
-        console.log('process: ', process.env);
     });
+//    }, function (e) {
+//        console.log(e.toString());
+//    }).then(null, function (e) {
+//        console.log(e.stack);
+//    });
 }());
\ No newline at end of file
diff --git a/config.js b/config.js
index 28875e22f6..1362072b76 100644
--- a/config.js
+++ b/config.js
@@ -55,6 +55,19 @@
      */
     config.homepage.posts = 4;
 
+    config.database = {
+        development: {
+            client: 'sqlite3',
+            connection: {
+                filename: './core/shared/data/testdb.db'
+            }
+        },
+
+        staging: {},
+
+        production: {}
+    };
+
     /**
      * @property {Object} exports
      */
diff --git a/core/admin/assets/js/editor.js b/core/admin/assets/js/editor.js
index 1a56d386e4..31b1ab13e0 100644
--- a/core/admin/assets/js/editor.js
+++ b/core/admin/assets/js/editor.js
@@ -56,7 +56,7 @@
     function save() {
         var entry = {
                 title: document.getElementById('entry-title').value,
-                markdown: editor.getValue()
+                content: editor.getValue()
             },
             urlSegments = window.location.pathname.split('/');
 
@@ -64,7 +64,7 @@
             entry.id = urlSegments[3];
             $.ajax({
                 url: '/api/v0.1/posts/edit',
-                method: 'POST',
+                method: 'PUT',
                 data: entry,
                 success: function (data) {
                     console.log('response', data);
diff --git a/core/admin/controllers/index.js b/core/admin/controllers/index.js
index c5ad0705c7..c8b9decd43 100644
--- a/core/admin/controllers/index.js
+++ b/core/admin/controllers/index.js
@@ -1,11 +1,12 @@
+/*global require, module */
 (function () {
     "use strict";
 
     var Ghost = require('../../ghost'),
         _ = require('underscore'),
         fs = require('fs'),
-        Showdown = require('showdown'),
-        converter = new Showdown.converter(),
+        when = require('when/node/function'),
+        api = require('../../shared/api'),
 
         ghost = new Ghost(),
         adminNavbar,
@@ -60,14 +61,15 @@
         },
         'editor': function (req, res) {
             if (req.params.id !== undefined) {
-                ghost.dataProvider().posts.findOne({'id': parseInt(req.params.id, 10)}, function (error, post) {
-                    res.render('editor', {
-                        bodyClass: 'editor',
-                        adminNav: setSelected(adminNavbar, 'blog'),
-                        title: post.title,
-                        content: post.content
+                api.posts.read({id: parseInt(req.params.id, 10)})
+                    .then(function (post) {
+                        res.render('editor', {
+                            bodyClass: 'editor',
+                            adminNav: setSelected(adminNavbar, 'blog'),
+                            title: post.get('title'),
+                            content: post.get('content')
+                        });
                     });
-                });
             } else {
                 res.render('editor', {
                     bodyClass: 'editor',
@@ -76,13 +78,14 @@
             }
         },
         'blog': function (req, res) {
-            ghost.dataProvider().posts.findAll(function (error, posts) {
-                res.render('blog', {
-                    bodyClass: 'manage',
-                    adminNav: setSelected(adminNavbar, 'blog'),
-                    posts: posts
+            api.posts.browse()
+                .then(function (posts) {
+                    res.render('blog', {
+                        bodyClass: 'manage',
+                        adminNav: setSelected(adminNavbar, 'blog'),
+                        posts: posts.toJSON()
+                    });
                 });
-            });
         },
         'settings': function (req, res) {
             res.render('settings', {
@@ -119,47 +122,6 @@
                     res.redirect('/ghost/debug');
                 });
             }
-        },
-        'posts': {
-            'index': function (req, res) {
-
-            },
-            'create': function (req, res) {
-                var entry = {
-                    title: req.body.title,
-                    content: req.body.markdown,
-                    contentHtml: '',
-                    language: ghost.config().defaultLang,
-                    status: ghost.statuses().draft,
-                    featured: false
-                };
-
-                entry.contentHtml = converter.makeHtml(entry.content);
-
-                ghost.dataProvider().posts.add(entry, function (error, post) {
-                    if (!error) {
-                        console.log('added', post);
-                        res.json({id: post.id});
-                    } else {
-                        res.json(400, {error: post.errors});
-                    }
-                });
-            },
-            'edit': function (req, res) {
-                var entry = {
-                    id: parseInt(req.body.id, 10),
-                    title: req.body.title,
-                    content: req.body.markdown,
-                    contentHtml: ''
-                };
-
-                entry.contentHtml = converter.makeHtml(entry.content);
-
-                ghost.dataProvider().posts.edit(entry, function (error, post) {
-                    console.log('edited', post);
-                    res.json({id: parseInt(post.id, 10)});
-                });
-            }
         }
     };
 
diff --git a/core/admin/views/blog.hbs b/core/admin/views/blog.hbs
index 39c36da632..f0aa9bbe0e 100644
--- a/core/admin/views/blog.hbs
+++ b/core/admin/views/blog.hbs
@@ -18,7 +18,7 @@
       <ol>
         {{#each posts}}
             {{! #if featured class="featured"{{/if}}
-        <li data-id="{{id}}" data-content="{{contentHtml}}">
+        <li data-id="{{id}}" data-content="{{content_html}}">
           <a class="permalink" href="#">
             <h3 class="entry-title">{{title}}</h3>
             <section class="entry-meta">
diff --git a/core/frontend/controllers/index.js b/core/frontend/controllers/index.js
index cbe4581e42..cf42783778 100644
--- a/core/frontend/controllers/index.js
+++ b/core/frontend/controllers/index.js
@@ -7,45 +7,27 @@
     'use strict';
 
     var Ghost = require('../../ghost'),
-        _ = require('underscore'),
+        api = require('../../shared/api'),
 
         ghost = new Ghost(),
         frontendControllers;
 
     frontendControllers = {
         'homepage': function (req, res) {
-            var featureCount = 0,
-                postCount = 0,
-                data;
-
-            ghost.dataProvider().posts.findAll(function (error, posts) {
-                data = _.groupBy(posts, function (post) {
-                    var group = null;
-                    if (post.featured === true && featureCount < ghost.config().homepage.features) {
-                        featureCount += 1;
-                        group = 'features';
-                    } else if (postCount < ghost.config().homepage.posts) {
-                        postCount += 1;
-                        group = 'posts';
-                    }
-
-                    return group;
-                });
-
-                ghost.doFilter('prepostsRender', data.posts, function (posts) {
-                    res.render('index', {features: data.features, posts: posts, ghostGlobals: ghost.globals()});
+            api.posts.browse().then(function (posts) {
+                ghost.doFilter('prePostsRender', posts.toJSON(), function (posts) {
+                    res.render('index', {posts: posts, ghostGlobals: ghost.globals()});
                 });
             });
         },
         'single': function (req, res) {
-            ghost.dataProvider().posts.findOne({'slug': req.params.slug}, function (error, post) {
-                ghost.doFilter('prePostsRender', post, function (post) {
+            api.posts.read({'slug': req.params.slug}).then(function (post) {
+                ghost.doFilter('prePostsRender', post.toJSON(), function (post) {
                     res.render('single', {post: post, ghostGlobals: ghost.globals()});
                 });
             });
         }
     };
 
-
     module.exports = frontendControllers;
 }());
\ No newline at end of file
diff --git a/core/ghost.js b/core/ghost.js
index d227f84a0d..b239b4960e 100644
--- a/core/ghost.js
+++ b/core/ghost.js
@@ -1,11 +1,7 @@
 // # Ghost Module
 // Defines core methods required to build the frontend
 
-/**
- * global module,
- *        require,
- *        __dirname
- **/
+/*global module, require, __dirname */
 (function () {
     "use strict";
 
@@ -16,10 +12,13 @@
         hbs = require('express-hbs'),
         _ = require('underscore'),
         Polyglot = require('node-polyglot'),
+
         JsonDataProvider = require('./shared/models/dataProvider.json'),
         jsonDataProvider = new JsonDataProvider(),
-        JugglingDataProvider = require('./shared/models/dataProvider.juggling'),
-        jugglingDataProvider = new JugglingDataProvider(),
+//        JugglingDataProvider = require('./shared/models/dataProvider.juggling'),
+//        jugglingDataProvider = new JugglingDataProvider(),
+        BookshelfDataProvider = require('./shared/models/dataProvider.bookshelf'),
+        bookshelfDataProvider = new BookshelfDataProvider(),
         Ghost,
         instance,
         filterCallbacks = {},
@@ -70,7 +69,7 @@
                 app: function () { return app; },
                 config: function () { return config; },
                 globals: function () { return globals; }, // there's no management here to be sure this has loaded
-                dataProvider: function () { return jugglingDataProvider; },
+                dataProvider: function () { return bookshelfDataProvider; },
                 statuses: function () { return statuses; },
                 polyglot: function () { return polyglot; },
                 paths: function () {
diff --git a/core/shared/api.js b/core/shared/api.js
new file mode 100644
index 0000000000..1a5073c757
--- /dev/null
+++ b/core/shared/api.js
@@ -0,0 +1,75 @@
+// # Ghost Data API
+// Provides access to the data model
+
+/**
+ * This is intended to replace the old dataProvider files and should access & manipulate the models directly
+ */
+
+/*global module, require */
+(function () {
+    "use strict";
+
+    var Ghost = require('../ghost'),
+        when = require('when/node/function'),
+        _ = require('underscore'),
+
+        ghost = new Ghost(),
+        posts,
+        users,
+        requestHandler;
+
+    // # Posts
+    posts = {
+        // takes filter / pagination parameters
+        // returns a list of posts in a json response
+        browse: function (options) {
+            return when.call(ghost.dataProvider().posts.findAll, options);
+        },
+        // takes an identifier (id or slug?)
+        // returns a single post in a json response
+        read: function (args) {
+            return when.call(ghost.dataProvider().posts.findOne, args);
+        },
+        // takes a json object with all the properties which should be updated
+        // returns the resulting post in a json response
+        edit: function (postData) {
+            return when.call(ghost.dataProvider().posts.edit, postData);
+        },
+        // takes a json object representing a post,
+        // returns the resulting post in a json response
+        add: function (postData) {
+            return when.call(ghost.dataProvider().posts.add, postData);
+        },
+        // takes an identifier (id or slug?)
+        // returns a json response with the id of the deleted post
+        destroy: function (id) {
+            return when.call(ghost.dataProvider().posts.destroy, id);
+        }
+    };
+
+    // # Users
+    users = {};
+//        settings: {},
+//        categories: {},
+//        post_categories: {}
+
+
+    // requestHandler
+    // decorator for api functions which are called via an HTTP request
+    // takes the API method and wraps it so that it gets data from the request and returns a sensible JSON response
+    requestHandler = function (apiMethod) {
+        return function (req, res) {
+            var options = _.extend(req.body, req.params);
+            return apiMethod(options).then(function (result) {
+                res.json(result);
+            }, function (error) {
+                res.json(400, {error: error});
+            });
+        };
+    };
+
+
+    module.exports.posts = posts;
+    module.exports.users = users;
+    module.exports.requestHandler = requestHandler;
+}());
\ No newline at end of file
diff --git a/core/shared/data/fixtures/001.js b/core/shared/data/fixtures/001.js
new file mode 100644
index 0000000000..e8aae20bf9
--- /dev/null
+++ b/core/shared/data/fixtures/001.js
@@ -0,0 +1,67 @@
+/*global module */
+module.exports = {
+    posts: [
+        {
+            "title": "Ghost: from fiction to function",
+            "slug": "ghost-from-fiction-to-function",
+            "content": "Three days ago I released a <a title=\"Ghost\" href=\"http:\/\/john.onolan.org\/ghost\/\">concept page<\/a> for a lite version of WordPress that I've been thinking about for a long time, called Ghost. I think it's fair to say that I didn't quite anticipate how strong the reaction would be - and I've hardly had time to catch my breath in the last 72 hours.\n\nThe response was overwhelming, and overwhelmingly positive. In the first 6 hours my site got 35,000 page views after hitting the number 1 slot on <a href=\"http:\/\/news.ycombinator.com\/item?id=4743245\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/news.ycombinator.com']);\">Hacker News<\/a>.&nbsp;As of right now, the traffic count is just over <a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/Screen-Shot-2012-11-09-at-17.51.21.png\" rel=\"lightbox\" class=\"cboxElement\">91,000 page views<\/a>&nbsp;- and Ghost has been featured all over the place. Notable mentions so far include Christina Warren from Mashable, who <a href=\"http:\/\/christina.is\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/christina.is']);\">wrote about it<\/a>. Michael Carney from PandoDaily <a href=\"http:\/\/pandodaily.com\/2012\/11\/07\/wordpress-guru-designs-a-concept-blogging-platform-that-doesnt-suck-gets-rave-reviews\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/pandodaily.com']);\">interviewed me about it<\/a>. Someone even <a href=\"http:\/\/www.voicens.com\/web\/?p=4425\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/www.voicens.com']);\">wrote about it in Chinese<\/a>. That's pretty cool.\n\n\nThe feedback has been amazing, and while it's impossible to reply to all of the messages individually, I'm getting to as many of them as I can and I want to thank each and every one of you who took the time to send me a message or share the concept because you liked it. Now that the initial storm has died down a bit, I wanted to take some time to answer some of the more common questions and talk about what's next.\n<h2>FAQ - Continued...<\/h2>\n\nThe most common question, bizarrely:\n<h5><em><strong>Oh my god, why is that whole page made of images? What's wrong with you? \/\/ I can't take you seriously \/\/ Don't you know anything about the web? \/\/ You are literally Satan re-incarnate.<\/strong><\/em><\/h5>\n\nThis was really the only negativity I got in response to the post, and it surprised me. I put together the concept page as... just that... a concept. It was a way for me to get the ideas out of my head and \"down on paper\" - or so to speak. I used photoshop as a <em>tool<\/em> to write down my idea with text and images. If I used a sketchbook as a <em>tool&nbsp;<\/em>to create images and handwritten notes, then uploaded scans of it, I doubt anyone would complain. The concept page was never supposed to be a finished product because I had no idea if there would be any interest in it. I had no motivation to waste hours coding a custom layout for something might only ever be read by a few people and then forgotten.\n\nHardware manufacturers make hundreds of foam cutout prototypes of products before they build one with working buttons and screens. I'm aware of all the usability problems with a web page made of images, and equally, foam cutouts without buttons or screens aren't particularly user friendly either. They're not supposed to be.\n\nLet's move on.\n<h5><em><strong>What? Why no comments? I need comments.<\/strong><\/em><\/h5>\n\nBecause comments add a layer of complexity that is beyond the core focus of this platform, which is publishing. Again, that's not to say you couldn't have any comments. This could easily be added with a dedicated plugin where you own the data or (as mentioned) there are third party providers such as Disqus, IntenseDebate, Livefyre and Facebook who all have great platforms. The point of this isn't to say \"you can't have comments\" - it's to say \"comments aren't on by default\". It's about simplicity, more than anything else.\n<h5><em><strong>Yeah, but WordPress are already going to revise their dashboard, WordPress.com is experimenting with a potential simplified version... so why bother with this?<\/strong><\/em><\/h5>\n\n<a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp.png\" rel=\"lightbox[2102]\" title=\"newwp\" class=\"cboxElement\"><img class=\"alignnone size-large wp-image-2117\" title=\"newwp\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp-550x210.png\" alt=\"\" width=\"550\" height=\"210\"><\/a>\n\nSorry, but Tumblr already did this - it's not the future of blogging, it's the past.\n\nGhost isn't about sharing \"Fuck Yeah [<a href=\"http:\/\/fuckyeahdogs.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahdogs.tumblr.com']);\">Dogs<\/a>\/<a href=\"http:\/\/fuckyeahsharks.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahsharks.tumblr.com']);\" rel=\"lightbox\" class=\"cboxElement\">Sharks<\/a>\/<a href=\"http:\/\/fuckyeahgirlswithtattoos.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahgirlswithtattoos.tumblr.com']);\">Girls with Tattoos<\/a>]\" - it's about publishing - which means writing - rather than mashing a few buttons to make sure that everyone can see and appreciate your latest funny picture\/status, which is surely the most funny picture\/status you've ever posted.\n\nTumblr, Pinterest and Facebook already have this locked down.&nbsp;It's not the future.\n<h5><em><strong>So... are you actually going to build this thing?<\/strong><\/em><\/h5>\n\nThe concept page was a way for me to test demand and interest. To see if anyone actually agreed with my frustrations and, more importantly, my solutions. I plucked a random figure of \"10,000 pageviews\" out of the air before I hit the publish button. If it got less than 10,000 pageviews, I would surrender to the fact that it would only ever be an idea. I've now exceeded that goal 9 times over, so yes, I'm looking at how Ghost can now be made into a reality.\n<h5><em><strong>How can I find out when it's done? \/\/ SHUT UP AND TAKE MY MONEY<\/strong><\/em><\/h5>\n\nOk, ok - there's a holding page up on <a href=\"http:\/\/tryghost.org\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/tryghost.org']);\">http:\/\/TryGhost.org<\/a> - put your email address in.\n<hr>\n<h3>How are you going to do this?<\/h3>\n\nThere's three main ways of going about this, each has merits as well as drawbacks.\n\n<em><strong>1.) Build it from scratch<\/strong><\/em> - Many people (particularly the Hacker News crowd) expressed the sentiment that there was little point in forking WordPress. When you're going to strip out so much, you get to a point where you might as well start from scratch anyway. Take away the crutches of being stuck with older technologies and put together something which is as sophisticated in code as it is in UI\/UX.\n<ul>\n<li><em>Pros:<\/em> The idea of something completely new is exciting, opportunity to build something very sophisticated, complete control over everything.<\/li>\n<li><em>Cons:<\/em> Lose the &nbsp;WordPress ecosystem which includes millions of users and thousands of developers, potentially spend the next 6 months fighting over whether to use PHP\/RoR\/Django\/Python\/Node\/Whateverthefuck because everyone loves to evangelise the technology they know best.<\/li>\n<\/ul>\n\n<em><strong>2.) Fork WordPress<\/strong><\/em> - This was the original idea I put out. Take the WordPress codebase, as is, and modify it to turn it into something new. Initially the codebase is practically the same, which means developers already know it. Then it can change over time and evolve into its own thing.\n<ul>\n<li><em>Pros:<\/em> Easy start with existing codebase, potential to evolve, doesn't lose WordPress ecosystem initially.<\/li>\n<li><em>Cons:<\/em> Stuck with existing codebase - the good as well as the bad, &nbsp;eventually needs to be rewritten completely, less control, loses the WordPress ecosystem after a while anyway, makes it complicated to transition from legacy code to new code.<\/li>\n<\/ul>\n\n<em><strong>3.) Make it a plugin\/extension<\/strong><\/em> - Lots of people asked why Ghost couldn't just be a WordPress plugin. It would certainly be the easiest route of the 3, it's possible to completely remove \/wp-admin\/ and replace with with \/ghost\/ ... but I feel like it kind of misses the point. This route bolts Ghost on, but it's still WordPress under the hood. From a UI\/UX standpoint it would function - but it wouldn't revolutionise anything else. It makes WordPress itself about blogging again, rather than creating something new.\n<ul>\n<li><em>Pros:<\/em> Very easy development, very easy deployment, keeps WordPress ecosystem forever, doesn't force anyone to change.<\/li>\n<li><em>Cons:<\/em> The least exciting (for me, personally), much less control, it would be much harder to maintain something like this on a non-profit basis - which loses a piece of what Ghost is about.<\/li>\n<\/ul>\n<h3>What's the answer?<\/h3>\n\nI've spoken to a lot of smart people over the last few days. The one thing that everyone seems to agree on is that a fork is the worst of both worlds. So the one thing that I suggested as a way of making this happen, is the least likely to work in reality. Remember the foam prototype metaphor earlier? Learning and iterating - that's what happening now.\n\nThat leaves a choice between WordPress plugin or fresh build. The answer? Both.\n\nA WordPress plugin will act as a proof of concept and a working prototype, initially, because it's easier to leverage the existing WordPress ecosystem to create it than to go into a cave for 6 months trying to build this amazing thing that everyone will have forgotten about.\n\nThe plugin will not be perfect. It will add the Ghost UI\/UX and as much functionality as we can cram into it. It will completely remove \/wp-admin\/ and replace it with \/ghost\/ - effectively using WordPress core as a basic foundation to build on top of. It will give people who don't want to switch away from WordPress access to the Ghost UX which they want to have, and it will give people who want the full Ghost platform a taste of what's to come.\n\nIt will allow us to develop and learn and iterate on the concept pretty rapidly, which has a great deal of value.\n\nThis is step one. Assuming the plugin is actually used by people - it would then justify exploring building the standalone version of Ghost from the ground up. The plugin would subsequently serve as a great marketing tool for the platform. Think of it as an upgrade path. But that's a long way away. Having the idea is the easy part. Making it happen is what counts.\n\nHappily - amongst the thousands of people talking about Ghost for the last few days - several have been talking about how they've already built some working prototypes of my mockups and turned them into WordPress plugins or just local development sites. These will likely go on to be the starting point of the first Ghost plugin.<\/p>\n\nThere's a lot to do, and I'm amazed by the number of people who have offered their help with this. In the next few days I'll be kicking off work on the plugin properly and start putting together a more organised structure which explains how you can get involved and contribute to the project if you're interested. So... watch this space - and thanks for all your support so far.\n\n<a href=\"http:\/\/twitter.com\/TryGhost\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/twitter.com']);\" class=\"twitter-follow-button\">Follow @TryGhost<\/a>",
+            "content_html": "<p>Three days ago I released a <a title=\"Ghost\" href=\"http:\/\/john.onolan.org\/ghost\/\">concept page<\/a> for a lite version of WordPress that I've been thinking about for a long time, called Ghost. I think it's fair to say that I didn't quite anticipate how strong the reaction would be - and I've hardly had time to catch my breath in the last 72 hours.<\/p>\n<p>The response was overwhelming, and overwhelmingly positive. In the first 6 hours my site got 35,000 page views after hitting the number 1 slot on <a href=\"http:\/\/news.ycombinator.com\/item?id=4743245\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/news.ycombinator.com']);\">Hacker News<\/a>.&nbsp;As of right now, the traffic count is just over <a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/Screen-Shot-2012-11-09-at-17.51.21.png\" rel=\"lightbox\" class=\"cboxElement\">91,000 page views<\/a>&nbsp;- and Ghost has been featured all over the place. Notable mentions so far include Christina Warren from Mashable, who <a href=\"http:\/\/christina.is\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/christina.is']);\">wrote about it<\/a>. Michael Carney from PandoDaily <a href=\"http:\/\/pandodaily.com\/2012\/11\/07\/wordpress-guru-designs-a-concept-blogging-platform-that-doesnt-suck-gets-rave-reviews\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/pandodaily.com']);\">interviewed me about it<\/a>. Someone even <a href=\"http:\/\/www.voicens.com\/web\/?p=4425\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/www.voicens.com']);\">wrote about it in Chinese<\/a>. That's pretty cool.\\n<p>The feedback has been amazing, and while it's impossible to reply to all of the messages individually, I'm getting to as many of them as I can and I want to thank each and every one of you who took the time to send me a message or share the concept because you liked it. Now that the initial storm has died down a bit, I wanted to take some time to answer some of the more common questions and talk about what's next.<\/p>\n<h2>FAQ - Continued...<\/h2>\n<p>The most common question, bizarrely:<\/p>\n<h5><em><strong>Oh my god, why is that whole page made of images? What's wrong with you? \/\/ I can't take you seriously \/\/ Don't you know anything about the web? \/\/ You are literally Satan re-incarnate.<\/strong><\/em><\/h5>\n<p>This was really the only negativity I got in response to the post, and it surprised me. I put together the concept page as... just that... a concept. It was a way for me to get the ideas out of my head and \"down on paper\" - or so to speak. I used photoshop as a <em>tool<\/em> to write down my idea with text and images. If I used a sketchbook as a <em>tool&nbsp;<\/em>to create images and handwritten notes, then uploaded scans of it, I doubt anyone would complain. The concept page was never supposed to be a finished product because I had no idea if there would be any interest in it. I had no motivation to waste hours coding a custom layout for something might only ever be read by a few people and then forgotten.<\/p>\n<p>Hardware manufacturers make hundreds of foam cutout prototypes of products before they build one with working buttons and screens. I'm aware of all the usability problems with a web page made of images, and equally, foam cutouts without buttons or screens aren't particularly user friendly either. They're not supposed to be.<\/p>\n<p>Let's move on.<\/p>\n<h5><em><strong>What? Why no comments? I need comments.<\/strong><\/em><\/h5>\n<p>Because comments add a layer of complexity that is beyond the core focus of this platform, which is publishing. Again, that's not to say you couldn't have any comments. This could easily be added with a dedicated plugin where you own the data or (as mentioned) there are third party providers such as Disqus, IntenseDebate, Livefyre and Facebook who all have great platforms. The point of this isn't to say \"you can't have comments\" - it's to say \"comments aren't on by default\". It's about simplicity, more than anything else.<\/p>\n<h5><em><strong>Yeah, but WordPress are already going to revise their dashboard, WordPress.com is experimenting with a potential simplified version... so why bother with this?<\/strong><\/em><\/h5>\n<p><a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp.png\" rel=\"lightbox[2102]\" title=\"newwp\" class=\"cboxElement\"><img class=\"alignnone size-large wp-image-2117\" title=\"newwp\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp-550x210.png\" alt=\"\" width=\"550\" height=\"210\"><\/a><\/p>\n<p>Sorry, but Tumblr already did this - it's not the future of blogging, it's the past.<\/p>\n<p>Ghost isn't about sharing \"Fuck Yeah [<a href=\"http:\/\/fuckyeahdogs.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahdogs.tumblr.com']);\">Dogs<\/a>\/<a href=\"http:\/\/fuckyeahsharks.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahsharks.tumblr.com']);\" rel=\"lightbox\" class=\"cboxElement\">Sharks<\/a>\/<a href=\"http:\/\/fuckyeahgirlswithtattoos.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahgirlswithtattoos.tumblr.com']);\">Girls with Tattoos<\/a>]\" - it's about publishing - which means writing - rather than mashing a few buttons to make sure that everyone can see and appreciate your latest funny picture\/status, which is surely the most funny picture\/status you've ever posted.<\/p>\n<p>Tumblr, Pinterest and Facebook already have this locked down.&nbsp;It's not the future.<\/p>\n<h5><em><strong>So... are you actually going to build this thing?<\/strong><\/em><\/h5>\n<p>The concept page was a way for me to test demand and interest. To see if anyone actually agreed with my frustrations and, more importantly, my solutions. I plucked a random figure of \"10,000 pageviews\" out of the air before I hit the publish button. If it got less than 10,000 pageviews, I would surrender to the fact that it would only ever be an idea. I've now exceeded that goal 9 times over, so yes, I'm looking at how Ghost can now be made into a reality.<\/p>\n<h5><em><strong>How can I find out when it's done? \/\/ SHUT UP AND TAKE MY MONEY<\/strong><\/em><\/h5>\n<p>Ok, ok - there's a holding page up on <a href=\"http:\/\/tryghost.org\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/tryghost.org']);\">http:\/\/TryGhost.org<\/a> - put your email address in.<\/p>\n<hr>\n<h3>How are you going to do this?<\/h3>\n<p>There's three main ways of going about this, each has merits as well as drawbacks.<\/p>\n<p><em><strong>1.) Build it from scratch<\/strong><\/em> - Many people (particularly the Hacker News crowd) expressed the sentiment that there was little point in forking WordPress. When you're going to strip out so much, you get to a point where you might as well start from scratch anyway. Take away the crutches of being stuck with older technologies and put together something which is as sophisticated in code as it is in UI\/UX.<\/p>\n<ul>\n<li><em>Pros:<\/em> The idea of something completely new is exciting, opportunity to build something very sophisticated, complete control over everything.<\/li>\n<li><em>Cons:<\/em> Lose the &nbsp;WordPress ecosystem which includes millions of users and thousands of developers, potentially spend the next 6 months fighting over whether to use PHP\/RoR\/Django\/Python\/Node\/Whateverthefuck because everyone loves to evangelise the technology they know best.<\/li>\n<\/ul>\n<p><em><strong>2.) Fork WordPress<\/strong><\/em> - This was the original idea I put out. Take the WordPress codebase, as is, and modify it to turn it into something new. Initially the codebase is practically the same, which means developers already know it. Then it can change over time and evolve into its own thing.<\/p>\n<ul>\n<li><em>Pros:<\/em> Easy start with existing codebase, potential to evolve, doesn't lose WordPress ecosystem initially.<\/li>\n<li><em>Cons:<\/em> Stuck with existing codebase - the good as well as the bad, &nbsp;eventually needs to be rewritten completely, less control, loses the WordPress ecosystem after a while anyway, makes it complicated to transition from legacy code to new code.<\/li>\n<\/ul>\n<p><em><strong>3.) Make it a plugin\/extension<\/strong><\/em> - Lots of people asked why Ghost couldn't just be a WordPress plugin. It would certainly be the easiest route of the 3, it's possible to completely remove \/wp-admin\/ and replace with with \/ghost\/ ... but I feel like it kind of misses the point. This route bolts Ghost on, but it's still WordPress under the hood. From a UI\/UX standpoint it would function - but it wouldn't revolutionise anything else. It makes WordPress itself about blogging again, rather than creating something new.<\/p>\n<ul>\n<li><em>Pros:<\/em> Very easy development, very easy deployment, keeps WordPress ecosystem forever, doesn't force anyone to change.<\/li>\n<li><em>Cons:<\/em> The least exciting (for me, personally), much less control, it would be much harder to maintain something like this on a non-profit basis - which loses a piece of what Ghost is about.<\/li>\n<\/ul>\n<h3>What's the answer?<\/h3>\n<p>I've spoken to a lot of smart people over the last few days. The one thing that everyone seems to agree on is that a fork is the worst of both worlds. So the one thing that I suggested as a way of making this happen, is the least likely to work in reality. Remember the foam prototype metaphor earlier? Learning and iterating - that's what happening now.<\/p>\n<p>That leaves a choice between WordPress plugin or fresh build. The answer? Both.<\/p>\n<p>A WordPress plugin will act as a proof of concept and a working prototype, initially, because it's easier to leverage the existing WordPress ecosystem to create it than to go into a cave for 6 months trying to build this amazing thing that everyone will have forgotten about.<\/p>\n<p>The plugin will not be perfect. It will add the Ghost UI\/UX and as much functionality as we can cram into it. It will completely remove \/wp-admin\/ and replace it with \/ghost\/ - effectively using WordPress core as a basic foundation to build on top of. It will give people who don't want to switch away from WordPress access to the Ghost UX which they want to have, and it will give people who want the full Ghost platform a taste of what's to come.<\/p>\n<p>It will allow us to develop and learn and iterate on the concept pretty rapidly, which has a great deal of value.<\/p>\n<p>This is step one. Assuming the plugin is actually used by people - it would then justify exploring building the standalone version of Ghost from the ground up. The plugin would subsequently serve as a great marketing tool for the platform. Think of it as an upgrade path. But that's a long way away. Having the idea is the easy part. Making it happen is what counts.<\/p>\n<p>Happily - amongst the thousands of people talking about Ghost for the last few days - several have been talking about how they've already built some working prototypes of my mockups and turned them into WordPress plugins or just local development sites. These will likely go on to be the starting point of the first Ghost plugin.<\/p>\n<p>There's a lot to do, and I'm amazed by the number of people who have offered their help with this. In the next few days I'll be kicking off work on the plugin properly and start putting together a more organised structure which explains how you can get involved and contribute to the project if you're interested. So... watch this space - and thanks for all your support so far.<\/p>\n<p><a href=\"http:\/\/twitter.com\/TryGhost\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/twitter.com']);\" class=\"twitter-follow-button\">Follow @TryGhost<\/a><\/p>",
+            "image": "ghostpost.jpg",
+            "language": "en",
+            "status": "published",
+            "featured": true,
+            "created_at": 1352475600601,
+            "created_by": 1
+        },
+        {
+            "title": "Designing emotion",
+            "slug": "designing-emotion",
+            "content": "A terminal plague on the soul:&nbsp;Six words to accurately describe the process of writing a book. I've often read articles by authors (particularly non-fiction authors) about how writing a book was one of the most difficult, frustrating, mind-numbingly hell-ridden surefire path to insanity that they'd ever experienced. Many noted that they'd never do it again. I didn't listen, obviously. It can't be that hard, I thought, there are plenty of books out there and each one of them had an author who managed to pull it off. And if they can do it, so can I.\n\n\nThat was just over two years ago.\n\n<h2>The Back Story<\/h2>\n\nA little more than two&nbsp;<strong>years<\/strong> ago, I wrote a blog post that was the beginning of Designing Emotion and @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/Adii\">Adii<\/a> and I decided to write it up into a short eBook. It was going to be pretty straightforward, to begin with. We'd come across this new concept that explored the psychology behind design and marketing, and we were going to put together maybe 10,000 words on why we thought it was a big deal. As we started writing, I submitted an article to Web Designer Depot (who I was writing for a lot at the time) on this subject - to&nbsp;gauge&nbsp;interest, and to promote a little bit of what we were doing.\n\n\nI didn't know, at the time, that Wiley &amp; Sons (the publishing house) scour places like Web Designer Depot looking for potential <span style=\"text-decoration: line-through;\">suckers<\/span>, <span style=\"text-decoration: line-through;\">victims<\/span>, new authors. Within a couple of weeks of the article being published - we'd been approached and offered a contract to write and publish a&nbsp;<em>real<\/em> book on the subject.\n\n\nI've held off for a long time on telling the next part of this story because, frankly, it's embarrassing and depressing.\n\n\nDesigning Emotion back then was, at best, a half-baked seed that had the potential to one day be an idea, that had the potential to one day be a real concept, that had the potential to one day be a book. Suddenly we were taken from \"Let's write this thing for fun in our free time and put it out ourselves\" to \"Write a 345 part outline for a 200 page book to be written in the next 2 months and published worldwide. Oh, and we'll need to review this 1,245 page contract about royalty terms, advances, and [other shit that sounds important].\"\n\n\nGulp.\n\n\nTo cut a long story short: We tried, and it didn't work. There were two main reasons for this:\n\n\nFirst - Adii and I already worked the equivalent of 4 full time jobs. Writing a book for a publisher is the equivalent of about 3 more full time jobs that neither of us had time for. We would have struggled to keep up with the writing schedule if the idea was fully formed. The reality was, we were researching, documenting, and writing at the same time as we were&nbsp;<em>learning<\/em> what the hell we were even talking about. In short: we weren't ready to write a book.\n\n\nSecond - Wiley &amp; Sons are best known for publishing the \"For Dummies\" series and, unfortunately, they take a \"For Dummies\" approach to publishing. Our book was going to be about grand ideas, about concepts and new ways of thinking, about exploring subjects that hadn't been explored before. Our commissioning editor (the guy who signed us) seemed to get this, but every other editor we had (and there were several) couldn't wrap their head around it. They wanted us to write a book with numbered bullet points, quick tips, pictures, chapter summaries about what the reader has learned, and a whole host of other things that would make us fit perfectly into the \"For Dummies\" cookie cutter template. We didn't like it, and we fought for over a year to work with the publisher and the editors to try and let us write the book we'd wanted to all along.\n\n<h2>Game Over<\/h2>\n\nAbout a year ago, we drew a line in the sand and Wiley released us from our contract.\n\n\nWe were frustrated, angry, and thoroughly worn out. Adii bowed out completely at this point, he'd had enough. I don't blame him whatsoever - with a company as large and as profitable as WooThemes - it wasn't really surprising that he wanted to focus his efforts on things that&nbsp;<em>were<\/em> working instead of those that weren't. I had a slightly different perspective, however. Once the manuscript had gotten to about 70% complete, I'd put together a presentation and started giving it at large design, development and marketing conferences all over the world. I still give this presentation now, talking about the building blocks of Designing Emotion - the foundations of the book... and you know what? The feedback, every time, was (and is) unreal. People get it - and they're interested by it. I've had more positive feedback from giving keynotes on this subject than any other - I know that this is something worth talking about.\n\n\nFor that reason - this semi-complete manuscript has haunted my dreams. It started out as a simple idea, progressed into a big idea, transformed into a big book, was utterly destroyed by incompetant editors and reduced to rubble. At one point, our lead editor added the bolded words to the following passage because she believed our readers wold be unclear on what we were talking about: YouTube is the second most popular&nbsp;<strong>digital<\/strong> site in the&nbsp;<strong>virtual<\/strong> world. - you know, just in case you thought that \"YouTube\" was a physical location somewhere on planet Earth.\n\n\nOur Amazon pre-order page went from \"delayed\" to \"delayed further\" to \"delayed until further notice\" to \"removed\". People asked, and still do ask, \"What's going on with the book? When can I get it?\"\n\n\nI haven't even wanted to look at the damn thing for the best part of a year now. It really did kill me.&nbsp;While I was busy failing to complete Designing Emotion, my friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RobHawkes\">RobHawkes<\/a> got his own book deal, wrote the book, published the book, sold out of the book and had it go for a second print run. Epic levels of depressing on my part.\n\n\nSo that's the back-story. Sorry, I rambled a bit. Anyway, here's what's happening next:\n\n<h2>Releasing Designing Emotion<\/h2>\n\nI'm publishing book myself, one blog-post-length section at a time, on <a href=\"http:\/\/emotion.onolan.org\/\">emotion.onolan.org<\/a>. I'm doing it like this for a couple of reasons. First, I've written a proverbial fuck-ton of this thing already, and it seems like a shame not to share it. There's lots of content that I think people who enjoyed my keynote on the subject would find interesting and benefit from in some way. Second, I'm trying to remove all the dreadfully heavy feelings of responsibility that come with the sentence \"I'm writing a book\" so that I can actually finish writing&nbsp;<strong>it<\/strong>. Where&nbsp;<strong>it<\/strong>&nbsp;is the original idea that Adii and I had years ago to just write something, slightly longer than a blog post, and share it with people.\n\n\nSo, there it is. That's how it's going to go. Once it's finished, I'll look at how to make the entire thing available as one complete piece. For now, I invite you to think of it as a large, interesting, and regularly published blog series. <a href=\"http:\/\/emotion.onolan.org\/\">Follow along<\/a>, and tell me what you think.\n\n\nOh, and here's the cover - My friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RickNunn\">RickNunn<\/a> photographed it - I designed it. It's been under wraps for too long - I hope you like it.\n\n\n<img class=\"alignnone size-full wp-image-2016\" title=\"decoverbig\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/06\/decoverbig.jpg\" alt=\"\" width=\"550\" height=\"815\">\n",
+            "content_html": "<p>A terminal plague on the soul:&nbsp;Six words to accurately describe the process of writing a book. I've often read articles by authors (particularly non-fiction authors) about how writing a book was one of the most difficult, frustrating, mind-numbingly hell-ridden surefire path to insanity that they'd ever experienced. Many noted that they'd never do it again. I didn't listen, obviously. It can't be that hard, I thought, there are plenty of books out there and each one of them had an author who managed to pull it off. And if they can do it, so can I.<\/p>\n<p>That was just over two years ago.<\/p>\n<h2>The Back Story<\/h2>\n<p>A little more than two&nbsp;<strong>years<\/strong> ago, I wrote a blog post that was the beginning of Designing Emotion and @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/Adii\">Adii<\/a> and I decided to write it up into a short eBook. It was going to be pretty straightforward, to begin with. We'd come across this new concept that explored the psychology behind design and marketing, and we were going to put together maybe 10,000 words on why we thought it was a big deal. As we started writing, I submitted an article to Web Designer Depot (who I was writing for a lot at the time) on this subject - to&nbsp;gauge&nbsp;interest, and to promote a little bit of what we were doing.<\/p>\n<p>I didn't know, at the time, that Wiley &amp; Sons (the publishing house) scour places like Web Designer Depot looking for potential <span style=\"text-decoration: line-through;\">suckers<\/span>, <span style=\"text-decoration: line-through;\">victims<\/span>, new authors. Within a couple of weeks of the article being published - we'd been approached and offered a contract to write and publish a&nbsp;<em>real<\/em> book on the subject.<\/p>\n<p>I've held off for a long time on telling the next part of this story because, frankly, it's embarrassing and depressing.<\/p>\n<p>Designing Emotion back then was, at best, a half-baked seed that had the potential to one day be an idea, that had the potential to one day be a real concept, that had the potential to one day be a book. Suddenly we were taken from \"Let's write this thing for fun in our free time and put it out ourselves\" to \"Write a 345 part outline for a 200 page book to be written in the next 2 months and published worldwide. Oh, and we'll need to review this 1,245 page contract about royalty terms, advances, and [other shit that sounds important].\"<\/p>\n<p>Gulp.<\/p>\n<p>To cut a long story short: We tried, and it didn't work. There were two main reasons for this:<\/p>\n<p>First - Adii and I already worked the equivalent of 4 full time jobs. Writing a book for a publisher is the equivalent of about 3 more full time jobs that neither of us had time for. We would have struggled to keep up with the writing schedule if the idea was fully formed. The reality was, we were researching, documenting, and writing at the same time as we were&nbsp;<em>learning<\/em> what the hell we were even talking about. In short: we weren't ready to write a book.<\/p>\n<p>Second - Wiley &amp; Sons are best known for publishing the \"For Dummies\" series and, unfortunately, they take a \"For Dummies\" approach to publishing. Our book was going to be about grand ideas, about concepts and new ways of thinking, about exploring subjects that hadn't been explored before. Our commissioning editor (the guy who signed us) seemed to get this, but every other editor we had (and there were several) couldn't wrap their head around it. They wanted us to write a book with numbered bullet points, quick tips, pictures, chapter summaries about what the reader has learned, and a whole host of other things that would make us fit perfectly into the \"For Dummies\" cookie cutter template. We didn't like it, and we fought for over a year to work with the publisher and the editors to try and let us write the book we'd wanted to all along.<\/p>\n<h2>Game Over<\/h2>\n<p>About a year ago, we drew a line in the sand and Wiley released us from our contract.<\/p>\n<p>We were frustrated, angry, and thoroughly worn out. Adii bowed out completely at this point, he'd had enough. I don't blame him whatsoever - with a company as large and as profitable as WooThemes - it wasn't really surprising that he wanted to focus his efforts on things that&nbsp;<em>were<\/em> working instead of those that weren't. I had a slightly different perspective, however. Once the manuscript had gotten to about 70% complete, I'd put together a presentation and started giving it at large design, development and marketing conferences all over the world. I still give this presentation now, talking about the building blocks of Designing Emotion - the foundations of the book... and you know what? The feedback, every time, was (and is) unreal. People get it - and they're interested by it. I've had more positive feedback from giving keynotes on this subject than any other - I know that this is something worth talking about.<\/p>\n<p>For that reason - this semi-complete manuscript has haunted my dreams. It started out as a simple idea, progressed into a big idea, transformed into a big book, was utterly destroyed by incompetant editors and reduced to rubble. At one point, our lead editor added the bolded words to the following passage because she believed our readers wold be unclear on what we were talking about: YouTube is the second most popular&nbsp;<strong>digital<\/strong> site in the&nbsp;<strong>virtual<\/strong> world. - you know, just in case you thought that \"YouTube\" was a physical location somewhere on planet Earth.<\/p>\n<p>Our Amazon pre-order page went from \"delayed\" to \"delayed further\" to \"delayed until further notice\" to \"removed\". People asked, and still do ask, \"What's going on with the book? When can I get it?\"<\/p>\n<p>I haven't even wanted to look at the damn thing for the best part of a year now. It really did kill me.&nbsp;While I was busy failing to complete Designing Emotion, my friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RobHawkes\">RobHawkes<\/a> got his own book deal, wrote the book, published the book, sold out of the book and had it go for a second print run. Epic levels of depressing on my part.<\/p>\n<p>So that's the back-story. Sorry, I rambled a bit. Anyway, here's what's happening next:<\/p>\n<h2>Releasing Designing Emotion<\/h2>\n<p>I'm publishing book myself, one blog-post-length section at a time, on <a href=\"http:\/\/emotion.onolan.org\/\">emotion.onolan.org<\/a>. I'm doing it like this for a couple of reasons. First, I've written a proverbial fuck-ton of this thing already, and it seems like a shame not to share it. There's lots of content that I think people who enjoyed my keynote on the subject would find interesting and benefit from in some way. Second, I'm trying to remove all the dreadfully heavy feelings of responsibility that come with the sentence \"I'm writing a book\" so that I can actually finish writing&nbsp;<strong>it<\/strong>. Where&nbsp;<strong>it<\/strong>&nbsp;is the original idea that Adii and I had years ago to just write something, slightly longer than a blog post, and share it with people.<\/p>\n<p>So, there it is. That's how it's going to go. Once it's finished, I'll look at how to make the entire thing available as one complete piece. For now, I invite you to think of it as a large, interesting, and regularly published blog series. <a href=\"http:\/\/emotion.onolan.org\/\">Follow along<\/a>, and tell me what you think.<\/p>\n<p>Oh, and here's the cover - My friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RickNunn\">RickNunn<\/a> photographed it - I designed it. It's been under wraps for too long - I hope you like it.<\/p>\n<p><img class=\"alignnone size-full wp-image-2016\" title=\"decoverbig\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/06\/decoverbig.jpg\" alt=\"\" width=\"550\" height=\"815\"><\/p>",
+            "image": "depostimg.jpg",
+            "language": "en",
+            "status": "published",
+            "featured": true,
+            "created_at": 1340582400102,
+            "created_by": 1
+        }
+    ],
+
+    settings: [
+        {
+            "key":          "url",
+            "value":        "http://localhost:3333",
+            "created_by":    1,
+            "updated_by":    1
+        },
+        {
+            "key":          "title",
+            "value":        "John O'Nolan",
+            "created_by":    1,
+            "updated_by":    1
+        },
+        {
+            "key":          "description",
+            "value":        "Interactive designer, public speaker, startup advisor and writer. Living in Austria, attempting world domination via keyboard.",
+            "created_by":    1,
+            "updated_by":    1
+        }
+    ],
+
+    users: [
+        {
+            "id":               "1",
+            "username":         "johnonolan",
+            "first_name":        "John",
+            "last_name":         "O'Nolan",
+            "email_address":     "john@onolan.org",
+            "profile_picture":   "logo.png",
+            "cover_picture":     "",
+            "bio":              "Interactive designer, public speaker, startup advisor and writer. Living in Austria, attempting world domination via keyboard.",
+            "url":              "john.onolan.org",
+            "created_by":        1,
+            "updated_by":        1
+        }
+    ]
+
+};
diff --git a/core/shared/data/fixtures/posts.json b/core/shared/data/fixtures/posts.json
deleted file mode 100644
index 14b15644fe..0000000000
--- a/core/shared/data/fixtures/posts.json
+++ /dev/null
@@ -1,24 +0,0 @@
-[
-    {
-        "title": "Ghost: from fiction to function",
-        "content": "Three days ago I released a <a title=\"Ghost\" href=\"http:\/\/john.onolan.org\/ghost\/\">concept page<\/a> for a lite version of WordPress that I've been thinking about for a long time, called Ghost. I think it's fair to say that I didn't quite anticipate how strong the reaction would be - and I've hardly had time to catch my breath in the last 72 hours.\n\nThe response was overwhelming, and overwhelmingly positive. In the first 6 hours my site got 35,000 page views after hitting the number 1 slot on <a href=\"http:\/\/news.ycombinator.com\/item?id=4743245\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/news.ycombinator.com']);\">Hacker News<\/a>.&nbsp;As of right now, the traffic count is just over <a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/Screen-Shot-2012-11-09-at-17.51.21.png\" rel=\"lightbox\" class=\"cboxElement\">91,000 page views<\/a>&nbsp;- and Ghost has been featured all over the place. Notable mentions so far include Christina Warren from Mashable, who <a href=\"http:\/\/christina.is\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/christina.is']);\">wrote about it<\/a>. Michael Carney from PandoDaily <a href=\"http:\/\/pandodaily.com\/2012\/11\/07\/wordpress-guru-designs-a-concept-blogging-platform-that-doesnt-suck-gets-rave-reviews\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/pandodaily.com']);\">interviewed me about it<\/a>. Someone even <a href=\"http:\/\/www.voicens.com\/web\/?p=4425\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/www.voicens.com']);\">wrote about it in Chinese<\/a>. That's pretty cool.\n\n\nThe feedback has been amazing, and while it's impossible to reply to all of the messages individually, I'm getting to as many of them as I can and I want to thank each and every one of you who took the time to send me a message or share the concept because you liked it. Now that the initial storm has died down a bit, I wanted to take some time to answer some of the more common questions and talk about what's next.\n<h2>FAQ - Continued...<\/h2>\n\nThe most common question, bizarrely:\n<h5><em><strong>Oh my god, why is that whole page made of images? What's wrong with you? \/\/ I can't take you seriously \/\/ Don't you know anything about the web? \/\/ You are literally Satan re-incarnate.<\/strong><\/em><\/h5>\n\nThis was really the only negativity I got in response to the post, and it surprised me. I put together the concept page as... just that... a concept. It was a way for me to get the ideas out of my head and \"down on paper\" - or so to speak. I used photoshop as a <em>tool<\/em> to write down my idea with text and images. If I used a sketchbook as a <em>tool&nbsp;<\/em>to create images and handwritten notes, then uploaded scans of it, I doubt anyone would complain. The concept page was never supposed to be a finished product because I had no idea if there would be any interest in it. I had no motivation to waste hours coding a custom layout for something might only ever be read by a few people and then forgotten.\n\nHardware manufacturers make hundreds of foam cutout prototypes of products before they build one with working buttons and screens. I'm aware of all the usability problems with a web page made of images, and equally, foam cutouts without buttons or screens aren't particularly user friendly either. They're not supposed to be.\n\nLet's move on.\n<h5><em><strong>What? Why no comments? I need comments.<\/strong><\/em><\/h5>\n\nBecause comments add a layer of complexity that is beyond the core focus of this platform, which is publishing. Again, that's not to say you couldn't have any comments. This could easily be added with a dedicated plugin where you own the data or (as mentioned) there are third party providers such as Disqus, IntenseDebate, Livefyre and Facebook who all have great platforms. The point of this isn't to say \"you can't have comments\" - it's to say \"comments aren't on by default\". It's about simplicity, more than anything else.\n<h5><em><strong>Yeah, but WordPress are already going to revise their dashboard, WordPress.com is experimenting with a potential simplified version... so why bother with this?<\/strong><\/em><\/h5>\n\n<a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp.png\" rel=\"lightbox[2102]\" title=\"newwp\" class=\"cboxElement\"><img class=\"alignnone size-large wp-image-2117\" title=\"newwp\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp-550x210.png\" alt=\"\" width=\"550\" height=\"210\"><\/a>\n\nSorry, but Tumblr already did this - it's not the future of blogging, it's the past.\n\nGhost isn't about sharing \"Fuck Yeah [<a href=\"http:\/\/fuckyeahdogs.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahdogs.tumblr.com']);\">Dogs<\/a>\/<a href=\"http:\/\/fuckyeahsharks.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahsharks.tumblr.com']);\" rel=\"lightbox\" class=\"cboxElement\">Sharks<\/a>\/<a href=\"http:\/\/fuckyeahgirlswithtattoos.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahgirlswithtattoos.tumblr.com']);\">Girls with Tattoos<\/a>]\" - it's about publishing - which means writing - rather than mashing a few buttons to make sure that everyone can see and appreciate your latest funny picture\/status, which is surely the most funny picture\/status you've ever posted.\n\nTumblr, Pinterest and Facebook already have this locked down.&nbsp;It's not the future.\n<h5><em><strong>So... are you actually going to build this thing?<\/strong><\/em><\/h5>\n\nThe concept page was a way for me to test demand and interest. To see if anyone actually agreed with my frustrations and, more importantly, my solutions. I plucked a random figure of \"10,000 pageviews\" out of the air before I hit the publish button. If it got less than 10,000 pageviews, I would surrender to the fact that it would only ever be an idea. I've now exceeded that goal 9 times over, so yes, I'm looking at how Ghost can now be made into a reality.\n<h5><em><strong>How can I find out when it's done? \/\/ SHUT UP AND TAKE MY MONEY<\/strong><\/em><\/h5>\n\nOk, ok - there's a holding page up on <a href=\"http:\/\/tryghost.org\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/tryghost.org']);\">http:\/\/TryGhost.org<\/a> - put your email address in.\n<hr>\n<h3>How are you going to do this?<\/h3>\n\nThere's three main ways of going about this, each has merits as well as drawbacks.\n\n<em><strong>1.) Build it from scratch<\/strong><\/em> - Many people (particularly the Hacker News crowd) expressed the sentiment that there was little point in forking WordPress. When you're going to strip out so much, you get to a point where you might as well start from scratch anyway. Take away the crutches of being stuck with older technologies and put together something which is as sophisticated in code as it is in UI\/UX.\n<ul>\n<li><em>Pros:<\/em> The idea of something completely new is exciting, opportunity to build something very sophisticated, complete control over everything.<\/li>\n<li><em>Cons:<\/em> Lose the &nbsp;WordPress ecosystem which includes millions of users and thousands of developers, potentially spend the next 6 months fighting over whether to use PHP\/RoR\/Django\/Python\/Node\/Whateverthefuck because everyone loves to evangelise the technology they know best.<\/li>\n<\/ul>\n\n<em><strong>2.) Fork WordPress<\/strong><\/em> - This was the original idea I put out. Take the WordPress codebase, as is, and modify it to turn it into something new. Initially the codebase is practically the same, which means developers already know it. Then it can change over time and evolve into its own thing.\n<ul>\n<li><em>Pros:<\/em> Easy start with existing codebase, potential to evolve, doesn't lose WordPress ecosystem initially.<\/li>\n<li><em>Cons:<\/em> Stuck with existing codebase - the good as well as the bad, &nbsp;eventually needs to be rewritten completely, less control, loses the WordPress ecosystem after a while anyway, makes it complicated to transition from legacy code to new code.<\/li>\n<\/ul>\n\n<em><strong>3.) Make it a plugin\/extension<\/strong><\/em> - Lots of people asked why Ghost couldn't just be a WordPress plugin. It would certainly be the easiest route of the 3, it's possible to completely remove \/wp-admin\/ and replace with with \/ghost\/ ... but I feel like it kind of misses the point. This route bolts Ghost on, but it's still WordPress under the hood. From a UI\/UX standpoint it would function - but it wouldn't revolutionise anything else. It makes WordPress itself about blogging again, rather than creating something new.\n<ul>\n<li><em>Pros:<\/em> Very easy development, very easy deployment, keeps WordPress ecosystem forever, doesn't force anyone to change.<\/li>\n<li><em>Cons:<\/em> The least exciting (for me, personally), much less control, it would be much harder to maintain something like this on a non-profit basis - which loses a piece of what Ghost is about.<\/li>\n<\/ul>\n<h3>What's the answer?<\/h3>\n\nI've spoken to a lot of smart people over the last few days. The one thing that everyone seems to agree on is that a fork is the worst of both worlds. So the one thing that I suggested as a way of making this happen, is the least likely to work in reality. Remember the foam prototype metaphor earlier? Learning and iterating - that's what happening now.\n\nThat leaves a choice between WordPress plugin or fresh build. The answer? Both.\n\nA WordPress plugin will act as a proof of concept and a working prototype, initially, because it's easier to leverage the existing WordPress ecosystem to create it than to go into a cave for 6 months trying to build this amazing thing that everyone will have forgotten about.\n\nThe plugin will not be perfect. It will add the Ghost UI\/UX and as much functionality as we can cram into it. It will completely remove \/wp-admin\/ and replace it with \/ghost\/ - effectively using WordPress core as a basic foundation to build on top of. It will give people who don't want to switch away from WordPress access to the Ghost UX which they want to have, and it will give people who want the full Ghost platform a taste of what's to come.\n\nIt will allow us to develop and learn and iterate on the concept pretty rapidly, which has a great deal of value.\n\nThis is step one. Assuming the plugin is actually used by people - it would then justify exploring building the standalone version of Ghost from the ground up. The plugin would subsequently serve as a great marketing tool for the platform. Think of it as an upgrade path. But that's a long way away. Having the idea is the easy part. Making it happen is what counts.\n\nHappily - amongst the thousands of people talking about Ghost for the last few days - several have been talking about how they've already built some working prototypes of my mockups and turned them into WordPress plugins or just local development sites. These will likely go on to be the starting point of the first Ghost plugin.<\/p>\n\nThere's a lot to do, and I'm amazed by the number of people who have offered their help with this. In the next few days I'll be kicking off work on the plugin properly and start putting together a more organised structure which explains how you can get involved and contribute to the project if you're interested. So... watch this space - and thanks for all your support so far.\n\n<a href=\"http:\/\/twitter.com\/TryGhost\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/twitter.com']);\" class=\"twitter-follow-button\">Follow @TryGhost<\/a>",
-        "contentHTML": "<p>Three days ago I released a <a title=\"Ghost\" href=\"http:\/\/john.onolan.org\/ghost\/\">concept page<\/a> for a lite version of WordPress that I've been thinking about for a long time, called Ghost. I think it's fair to say that I didn't quite anticipate how strong the reaction would be - and I've hardly had time to catch my breath in the last 72 hours.<\/p>\n<p>The response was overwhelming, and overwhelmingly positive. In the first 6 hours my site got 35,000 page views after hitting the number 1 slot on <a href=\"http:\/\/news.ycombinator.com\/item?id=4743245\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/news.ycombinator.com']);\">Hacker News<\/a>.&nbsp;As of right now, the traffic count is just over <a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/Screen-Shot-2012-11-09-at-17.51.21.png\" rel=\"lightbox\" class=\"cboxElement\">91,000 page views<\/a>&nbsp;- and Ghost has been featured all over the place. Notable mentions so far include Christina Warren from Mashable, who <a href=\"http:\/\/christina.is\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/christina.is']);\">wrote about it<\/a>. Michael Carney from PandoDaily <a href=\"http:\/\/pandodaily.com\/2012\/11\/07\/wordpress-guru-designs-a-concept-blogging-platform-that-doesnt-suck-gets-rave-reviews\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/pandodaily.com']);\">interviewed me about it<\/a>. Someone even <a href=\"http:\/\/www.voicens.com\/web\/?p=4425\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/www.voicens.com']);\">wrote about it in Chinese<\/a>. That's pretty cool.\\n<p>The feedback has been amazing, and while it's impossible to reply to all of the messages individually, I'm getting to as many of them as I can and I want to thank each and every one of you who took the time to send me a message or share the concept because you liked it. Now that the initial storm has died down a bit, I wanted to take some time to answer some of the more common questions and talk about what's next.<\/p>\n<h2>FAQ - Continued...<\/h2>\n<p>The most common question, bizarrely:<\/p>\n<h5><em><strong>Oh my god, why is that whole page made of images? What's wrong with you? \/\/ I can't take you seriously \/\/ Don't you know anything about the web? \/\/ You are literally Satan re-incarnate.<\/strong><\/em><\/h5>\n<p>This was really the only negativity I got in response to the post, and it surprised me. I put together the concept page as... just that... a concept. It was a way for me to get the ideas out of my head and \"down on paper\" - or so to speak. I used photoshop as a <em>tool<\/em> to write down my idea with text and images. If I used a sketchbook as a <em>tool&nbsp;<\/em>to create images and handwritten notes, then uploaded scans of it, I doubt anyone would complain. The concept page was never supposed to be a finished product because I had no idea if there would be any interest in it. I had no motivation to waste hours coding a custom layout for something might only ever be read by a few people and then forgotten.<\/p>\n<p>Hardware manufacturers make hundreds of foam cutout prototypes of products before they build one with working buttons and screens. I'm aware of all the usability problems with a web page made of images, and equally, foam cutouts without buttons or screens aren't particularly user friendly either. They're not supposed to be.<\/p>\n<p>Let's move on.<\/p>\n<h5><em><strong>What? Why no comments? I need comments.<\/strong><\/em><\/h5>\n<p>Because comments add a layer of complexity that is beyond the core focus of this platform, which is publishing. Again, that's not to say you couldn't have any comments. This could easily be added with a dedicated plugin where you own the data or (as mentioned) there are third party providers such as Disqus, IntenseDebate, Livefyre and Facebook who all have great platforms. The point of this isn't to say \"you can't have comments\" - it's to say \"comments aren't on by default\". It's about simplicity, more than anything else.<\/p>\n<h5><em><strong>Yeah, but WordPress are already going to revise their dashboard, WordPress.com is experimenting with a potential simplified version... so why bother with this?<\/strong><\/em><\/h5>\n<p><a href=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp.png\" rel=\"lightbox[2102]\" title=\"newwp\" class=\"cboxElement\"><img class=\"alignnone size-large wp-image-2117\" title=\"newwp\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/11\/newwp-550x210.png\" alt=\"\" width=\"550\" height=\"210\"><\/a><\/p>\n<p>Sorry, but Tumblr already did this - it's not the future of blogging, it's the past.<\/p>\n<p>Ghost isn't about sharing \"Fuck Yeah [<a href=\"http:\/\/fuckyeahdogs.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahdogs.tumblr.com']);\">Dogs<\/a>\/<a href=\"http:\/\/fuckyeahsharks.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahsharks.tumblr.com']);\" rel=\"lightbox\" class=\"cboxElement\">Sharks<\/a>\/<a href=\"http:\/\/fuckyeahgirlswithtattoos.tumblr.com\/\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/fuckyeahgirlswithtattoos.tumblr.com']);\">Girls with Tattoos<\/a>]\" - it's about publishing - which means writing - rather than mashing a few buttons to make sure that everyone can see and appreciate your latest funny picture\/status, which is surely the most funny picture\/status you've ever posted.<\/p>\n<p>Tumblr, Pinterest and Facebook already have this locked down.&nbsp;It's not the future.<\/p>\n<h5><em><strong>So... are you actually going to build this thing?<\/strong><\/em><\/h5>\n<p>The concept page was a way for me to test demand and interest. To see if anyone actually agreed with my frustrations and, more importantly, my solutions. I plucked a random figure of \"10,000 pageviews\" out of the air before I hit the publish button. If it got less than 10,000 pageviews, I would surrender to the fact that it would only ever be an idea. I've now exceeded that goal 9 times over, so yes, I'm looking at how Ghost can now be made into a reality.<\/p>\n<h5><em><strong>How can I find out when it's done? \/\/ SHUT UP AND TAKE MY MONEY<\/strong><\/em><\/h5>\n<p>Ok, ok - there's a holding page up on <a href=\"http:\/\/tryghost.org\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/tryghost.org']);\">http:\/\/TryGhost.org<\/a> - put your email address in.<\/p>\n<hr>\n<h3>How are you going to do this?<\/h3>\n<p>There's three main ways of going about this, each has merits as well as drawbacks.<\/p>\n<p><em><strong>1.) Build it from scratch<\/strong><\/em> - Many people (particularly the Hacker News crowd) expressed the sentiment that there was little point in forking WordPress. When you're going to strip out so much, you get to a point where you might as well start from scratch anyway. Take away the crutches of being stuck with older technologies and put together something which is as sophisticated in code as it is in UI\/UX.<\/p>\n<ul>\n<li><em>Pros:<\/em> The idea of something completely new is exciting, opportunity to build something very sophisticated, complete control over everything.<\/li>\n<li><em>Cons:<\/em> Lose the &nbsp;WordPress ecosystem which includes millions of users and thousands of developers, potentially spend the next 6 months fighting over whether to use PHP\/RoR\/Django\/Python\/Node\/Whateverthefuck because everyone loves to evangelise the technology they know best.<\/li>\n<\/ul>\n<p><em><strong>2.) Fork WordPress<\/strong><\/em> - This was the original idea I put out. Take the WordPress codebase, as is, and modify it to turn it into something new. Initially the codebase is practically the same, which means developers already know it. Then it can change over time and evolve into its own thing.<\/p>\n<ul>\n<li><em>Pros:<\/em> Easy start with existing codebase, potential to evolve, doesn't lose WordPress ecosystem initially.<\/li>\n<li><em>Cons:<\/em> Stuck with existing codebase - the good as well as the bad, &nbsp;eventually needs to be rewritten completely, less control, loses the WordPress ecosystem after a while anyway, makes it complicated to transition from legacy code to new code.<\/li>\n<\/ul>\n<p><em><strong>3.) Make it a plugin\/extension<\/strong><\/em> - Lots of people asked why Ghost couldn't just be a WordPress plugin. It would certainly be the easiest route of the 3, it's possible to completely remove \/wp-admin\/ and replace with with \/ghost\/ ... but I feel like it kind of misses the point. This route bolts Ghost on, but it's still WordPress under the hood. From a UI\/UX standpoint it would function - but it wouldn't revolutionise anything else. It makes WordPress itself about blogging again, rather than creating something new.<\/p>\n<ul>\n<li><em>Pros:<\/em> Very easy development, very easy deployment, keeps WordPress ecosystem forever, doesn't force anyone to change.<\/li>\n<li><em>Cons:<\/em> The least exciting (for me, personally), much less control, it would be much harder to maintain something like this on a non-profit basis - which loses a piece of what Ghost is about.<\/li>\n<\/ul>\n<h3>What's the answer?<\/h3>\n<p>I've spoken to a lot of smart people over the last few days. The one thing that everyone seems to agree on is that a fork is the worst of both worlds. So the one thing that I suggested as a way of making this happen, is the least likely to work in reality. Remember the foam prototype metaphor earlier? Learning and iterating - that's what happening now.<\/p>\n<p>That leaves a choice between WordPress plugin or fresh build. The answer? Both.<\/p>\n<p>A WordPress plugin will act as a proof of concept and a working prototype, initially, because it's easier to leverage the existing WordPress ecosystem to create it than to go into a cave for 6 months trying to build this amazing thing that everyone will have forgotten about.<\/p>\n<p>The plugin will not be perfect. It will add the Ghost UI\/UX and as much functionality as we can cram into it. It will completely remove \/wp-admin\/ and replace it with \/ghost\/ - effectively using WordPress core as a basic foundation to build on top of. It will give people who don't want to switch away from WordPress access to the Ghost UX which they want to have, and it will give people who want the full Ghost platform a taste of what's to come.<\/p>\n<p>It will allow us to develop and learn and iterate on the concept pretty rapidly, which has a great deal of value.<\/p>\n<p>This is step one. Assuming the plugin is actually used by people - it would then justify exploring building the standalone version of Ghost from the ground up. The plugin would subsequently serve as a great marketing tool for the platform. Think of it as an upgrade path. But that's a long way away. Having the idea is the easy part. Making it happen is what counts.<\/p>\n<p>Happily - amongst the thousands of people talking about Ghost for the last few days - several have been talking about how they've already built some working prototypes of my mockups and turned them into WordPress plugins or just local development sites. These will likely go on to be the starting point of the first Ghost plugin.<\/p>\n<p>There's a lot to do, and I'm amazed by the number of people who have offered their help with this. In the next few days I'll be kicking off work on the plugin properly and start putting together a more organised structure which explains how you can get involved and contribute to the project if you're interested. So... watch this space - and thanks for all your support so far.<\/p>\n<p><a href=\"http:\/\/twitter.com\/TryGhost\" onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/twitter.com']);\" class=\"twitter-follow-button\">Follow @TryGhost<\/a><\/p>",
-        "image": "ghostpost.jpg",
-        "language": "en",
-        "status": "published",
-        "featured": true,
-        "createdAt": 1352475600601,
-        "createdBy": 1
-    },
-    {
-        "title": "Designing emotion",
-        "content": "A terminal plague on the soul:&nbsp;Six words to accurately describe the process of writing a book. I've often read articles by authors (particularly non-fiction authors) about how writing a book was one of the most difficult, frustrating, mind-numbingly hell-ridden surefire path to insanity that they'd ever experienced. Many noted that they'd never do it again. I didn't listen, obviously. It can't be that hard, I thought, there are plenty of books out there and each one of them had an author who managed to pull it off. And if they can do it, so can I.\n\n\nThat was just over two years ago.\n\n<h2>The Back Story<\/h2>\n\nA little more than two&nbsp;<strong>years<\/strong> ago, I wrote a blog post that was the beginning of Designing Emotion and @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/Adii\">Adii<\/a> and I decided to write it up into a short eBook. It was going to be pretty straightforward, to begin with. We'd come across this new concept that explored the psychology behind design and marketing, and we were going to put together maybe 10,000 words on why we thought it was a big deal. As we started writing, I submitted an article to Web Designer Depot (who I was writing for a lot at the time) on this subject - to&nbsp;gauge&nbsp;interest, and to promote a little bit of what we were doing.\n\n\nI didn't know, at the time, that Wiley &amp; Sons (the publishing house) scour places like Web Designer Depot looking for potential <span style=\"text-decoration: line-through;\">suckers<\/span>, <span style=\"text-decoration: line-through;\">victims<\/span>, new authors. Within a couple of weeks of the article being published - we'd been approached and offered a contract to write and publish a&nbsp;<em>real<\/em> book on the subject.\n\n\nI've held off for a long time on telling the next part of this story because, frankly, it's embarrassing and depressing.\n\n\nDesigning Emotion back then was, at best, a half-baked seed that had the potential to one day be an idea, that had the potential to one day be a real concept, that had the potential to one day be a book. Suddenly we were taken from \"Let's write this thing for fun in our free time and put it out ourselves\" to \"Write a 345 part outline for a 200 page book to be written in the next 2 months and published worldwide. Oh, and we'll need to review this 1,245 page contract about royalty terms, advances, and [other shit that sounds important].\"\n\n\nGulp.\n\n\nTo cut a long story short: We tried, and it didn't work. There were two main reasons for this:\n\n\nFirst - Adii and I already worked the equivalent of 4 full time jobs. Writing a book for a publisher is the equivalent of about 3 more full time jobs that neither of us had time for. We would have struggled to keep up with the writing schedule if the idea was fully formed. The reality was, we were researching, documenting, and writing at the same time as we were&nbsp;<em>learning<\/em> what the hell we were even talking about. In short: we weren't ready to write a book.\n\n\nSecond - Wiley &amp; Sons are best known for publishing the \"For Dummies\" series and, unfortunately, they take a \"For Dummies\" approach to publishing. Our book was going to be about grand ideas, about concepts and new ways of thinking, about exploring subjects that hadn't been explored before. Our commissioning editor (the guy who signed us) seemed to get this, but every other editor we had (and there were several) couldn't wrap their head around it. They wanted us to write a book with numbered bullet points, quick tips, pictures, chapter summaries about what the reader has learned, and a whole host of other things that would make us fit perfectly into the \"For Dummies\" cookie cutter template. We didn't like it, and we fought for over a year to work with the publisher and the editors to try and let us write the book we'd wanted to all along.\n\n<h2>Game Over<\/h2>\n\nAbout a year ago, we drew a line in the sand and Wiley released us from our contract.\n\n\nWe were frustrated, angry, and thoroughly worn out. Adii bowed out completely at this point, he'd had enough. I don't blame him whatsoever - with a company as large and as profitable as WooThemes - it wasn't really surprising that he wanted to focus his efforts on things that&nbsp;<em>were<\/em> working instead of those that weren't. I had a slightly different perspective, however. Once the manuscript had gotten to about 70% complete, I'd put together a presentation and started giving it at large design, development and marketing conferences all over the world. I still give this presentation now, talking about the building blocks of Designing Emotion - the foundations of the book... and you know what? The feedback, every time, was (and is) unreal. People get it - and they're interested by it. I've had more positive feedback from giving keynotes on this subject than any other - I know that this is something worth talking about.\n\n\nFor that reason - this semi-complete manuscript has haunted my dreams. It started out as a simple idea, progressed into a big idea, transformed into a big book, was utterly destroyed by incompetant editors and reduced to rubble. At one point, our lead editor added the bolded words to the following passage because she believed our readers wold be unclear on what we were talking about: YouTube is the second most popular&nbsp;<strong>digital<\/strong> site in the&nbsp;<strong>virtual<\/strong> world. - you know, just in case you thought that \"YouTube\" was a physical location somewhere on planet Earth.\n\n\nOur Amazon pre-order page went from \"delayed\" to \"delayed further\" to \"delayed until further notice\" to \"removed\". People asked, and still do ask, \"What's going on with the book? When can I get it?\"\n\n\nI haven't even wanted to look at the damn thing for the best part of a year now. It really did kill me.&nbsp;While I was busy failing to complete Designing Emotion, my friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RobHawkes\">RobHawkes<\/a> got his own book deal, wrote the book, published the book, sold out of the book and had it go for a second print run. Epic levels of depressing on my part.\n\n\nSo that's the back-story. Sorry, I rambled a bit. Anyway, here's what's happening next:\n\n<h2>Releasing Designing Emotion<\/h2>\n\nI'm publishing book myself, one blog-post-length section at a time, on <a href=\"http:\/\/emotion.onolan.org\/\">emotion.onolan.org<\/a>. I'm doing it like this for a couple of reasons. First, I've written a proverbial fuck-ton of this thing already, and it seems like a shame not to share it. There's lots of content that I think people who enjoyed my keynote on the subject would find interesting and benefit from in some way. Second, I'm trying to remove all the dreadfully heavy feelings of responsibility that come with the sentence \"I'm writing a book\" so that I can actually finish writing&nbsp;<strong>it<\/strong>. Where&nbsp;<strong>it<\/strong>&nbsp;is the original idea that Adii and I had years ago to just write something, slightly longer than a blog post, and share it with people.\n\n\nSo, there it is. That's how it's going to go. Once it's finished, I'll look at how to make the entire thing available as one complete piece. For now, I invite you to think of it as a large, interesting, and regularly published blog series. <a href=\"http:\/\/emotion.onolan.org\/\">Follow along<\/a>, and tell me what you think.\n\n\nOh, and here's the cover - My friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RickNunn\">RickNunn<\/a> photographed it - I designed it. It's been under wraps for too long - I hope you like it.\n\n\n<img class=\"alignnone size-full wp-image-2016\" title=\"decoverbig\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/06\/decoverbig.jpg\" alt=\"\" width=\"550\" height=\"815\">\n",
-        "contentHtml": "<p>A terminal plague on the soul:&nbsp;Six words to accurately describe the process of writing a book. I've often read articles by authors (particularly non-fiction authors) about how writing a book was one of the most difficult, frustrating, mind-numbingly hell-ridden surefire path to insanity that they'd ever experienced. Many noted that they'd never do it again. I didn't listen, obviously. It can't be that hard, I thought, there are plenty of books out there and each one of them had an author who managed to pull it off. And if they can do it, so can I.<\/p>\n<p>That was just over two years ago.<\/p>\n<h2>The Back Story<\/h2>\n<p>A little more than two&nbsp;<strong>years<\/strong> ago, I wrote a blog post that was the beginning of Designing Emotion and @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/Adii\">Adii<\/a> and I decided to write it up into a short eBook. It was going to be pretty straightforward, to begin with. We'd come across this new concept that explored the psychology behind design and marketing, and we were going to put together maybe 10,000 words on why we thought it was a big deal. As we started writing, I submitted an article to Web Designer Depot (who I was writing for a lot at the time) on this subject - to&nbsp;gauge&nbsp;interest, and to promote a little bit of what we were doing.<\/p>\n<p>I didn't know, at the time, that Wiley &amp; Sons (the publishing house) scour places like Web Designer Depot looking for potential <span style=\"text-decoration: line-through;\">suckers<\/span>, <span style=\"text-decoration: line-through;\">victims<\/span>, new authors. Within a couple of weeks of the article being published - we'd been approached and offered a contract to write and publish a&nbsp;<em>real<\/em> book on the subject.<\/p>\n<p>I've held off for a long time on telling the next part of this story because, frankly, it's embarrassing and depressing.<\/p>\n<p>Designing Emotion back then was, at best, a half-baked seed that had the potential to one day be an idea, that had the potential to one day be a real concept, that had the potential to one day be a book. Suddenly we were taken from \"Let's write this thing for fun in our free time and put it out ourselves\" to \"Write a 345 part outline for a 200 page book to be written in the next 2 months and published worldwide. Oh, and we'll need to review this 1,245 page contract about royalty terms, advances, and [other shit that sounds important].\"<\/p>\n<p>Gulp.<\/p>\n<p>To cut a long story short: We tried, and it didn't work. There were two main reasons for this:<\/p>\n<p>First - Adii and I already worked the equivalent of 4 full time jobs. Writing a book for a publisher is the equivalent of about 3 more full time jobs that neither of us had time for. We would have struggled to keep up with the writing schedule if the idea was fully formed. The reality was, we were researching, documenting, and writing at the same time as we were&nbsp;<em>learning<\/em> what the hell we were even talking about. In short: we weren't ready to write a book.<\/p>\n<p>Second - Wiley &amp; Sons are best known for publishing the \"For Dummies\" series and, unfortunately, they take a \"For Dummies\" approach to publishing. Our book was going to be about grand ideas, about concepts and new ways of thinking, about exploring subjects that hadn't been explored before. Our commissioning editor (the guy who signed us) seemed to get this, but every other editor we had (and there were several) couldn't wrap their head around it. They wanted us to write a book with numbered bullet points, quick tips, pictures, chapter summaries about what the reader has learned, and a whole host of other things that would make us fit perfectly into the \"For Dummies\" cookie cutter template. We didn't like it, and we fought for over a year to work with the publisher and the editors to try and let us write the book we'd wanted to all along.<\/p>\n<h2>Game Over<\/h2>\n<p>About a year ago, we drew a line in the sand and Wiley released us from our contract.<\/p>\n<p>We were frustrated, angry, and thoroughly worn out. Adii bowed out completely at this point, he'd had enough. I don't blame him whatsoever - with a company as large and as profitable as WooThemes - it wasn't really surprising that he wanted to focus his efforts on things that&nbsp;<em>were<\/em> working instead of those that weren't. I had a slightly different perspective, however. Once the manuscript had gotten to about 70% complete, I'd put together a presentation and started giving it at large design, development and marketing conferences all over the world. I still give this presentation now, talking about the building blocks of Designing Emotion - the foundations of the book... and you know what? The feedback, every time, was (and is) unreal. People get it - and they're interested by it. I've had more positive feedback from giving keynotes on this subject than any other - I know that this is something worth talking about.<\/p>\n<p>For that reason - this semi-complete manuscript has haunted my dreams. It started out as a simple idea, progressed into a big idea, transformed into a big book, was utterly destroyed by incompetant editors and reduced to rubble. At one point, our lead editor added the bolded words to the following passage because she believed our readers wold be unclear on what we were talking about: YouTube is the second most popular&nbsp;<strong>digital<\/strong> site in the&nbsp;<strong>virtual<\/strong> world. - you know, just in case you thought that \"YouTube\" was a physical location somewhere on planet Earth.<\/p>\n<p>Our Amazon pre-order page went from \"delayed\" to \"delayed further\" to \"delayed until further notice\" to \"removed\". People asked, and still do ask, \"What's going on with the book? When can I get it?\"<\/p>\n<p>I haven't even wanted to look at the damn thing for the best part of a year now. It really did kill me.&nbsp;While I was busy failing to complete Designing Emotion, my friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RobHawkes\">RobHawkes<\/a> got his own book deal, wrote the book, published the book, sold out of the book and had it go for a second print run. Epic levels of depressing on my part.<\/p>\n<p>So that's the back-story. Sorry, I rambled a bit. Anyway, here's what's happening next:<\/p>\n<h2>Releasing Designing Emotion<\/h2>\n<p>I'm publishing book myself, one blog-post-length section at a time, on <a href=\"http:\/\/emotion.onolan.org\/\">emotion.onolan.org<\/a>. I'm doing it like this for a couple of reasons. First, I've written a proverbial fuck-ton of this thing already, and it seems like a shame not to share it. There's lots of content that I think people who enjoyed my keynote on the subject would find interesting and benefit from in some way. Second, I'm trying to remove all the dreadfully heavy feelings of responsibility that come with the sentence \"I'm writing a book\" so that I can actually finish writing&nbsp;<strong>it<\/strong>. Where&nbsp;<strong>it<\/strong>&nbsp;is the original idea that Adii and I had years ago to just write something, slightly longer than a blog post, and share it with people.<\/p>\n<p>So, there it is. That's how it's going to go. Once it's finished, I'll look at how to make the entire thing available as one complete piece. For now, I invite you to think of it as a large, interesting, and regularly published blog series. <a href=\"http:\/\/emotion.onolan.org\/\">Follow along<\/a>, and tell me what you think.<\/p>\n<p>Oh, and here's the cover - My friend @<a class=\"twitter-anywhere-user\" href=\"http:\/\/twitter.com\/RickNunn\">RickNunn<\/a> photographed it - I designed it. It's been under wraps for too long - I hope you like it.<\/p>\n<p><img class=\"alignnone size-full wp-image-2016\" title=\"decoverbig\" src=\"http:\/\/john.onolan.org\/wp-content\/uploads\/2012\/06\/decoverbig.jpg\" alt=\"\" width=\"550\" height=\"815\"><\/p>",
-        "image": "depostimg.jpg",
-        "language": "en",
-        "status": "published",
-        "featured": true,
-        "createdAt": 1340582400102,
-        "createdBy": 1
-    }
-]
\ No newline at end of file
diff --git a/core/shared/data/fixtures/settings.json b/core/shared/data/fixtures/settings.json
deleted file mode 100644
index 2e4e8ea1b5..0000000000
--- a/core/shared/data/fixtures/settings.json
+++ /dev/null
@@ -1,20 +0,0 @@
-[
-    {
-        "key":          "url",
-        "value":        "http://localhost:3333",
-        "createdBy":    1,
-        "updatedBy":    1
-    },
-    {
-        "key":          "title",
-        "value":        "John O'Nolan",
-        "createdBy":    1,
-        "updatedBy":    1
-    },
-    {
-        "key":          "description",
-        "value":        "Interactive designer, public speaker, startup advisor and writer. Living in Austria, attempting world domination via keyboard.",
-        "createdBy":    1,
-        "updatedBy":    1
-    }
-]
\ No newline at end of file
diff --git a/core/shared/data/fixtures/users.json b/core/shared/data/fixtures/users.json
deleted file mode 100644
index b6db5c477d..0000000000
--- a/core/shared/data/fixtures/users.json
+++ /dev/null
@@ -1,15 +0,0 @@
-[
-    {
-        "id":               "1",
-        "username":         "johnonolan",
-        "firstName":        "John",
-        "lastName":         "O'Nolan",
-        "emailAddress":     "john@onolan.org",
-        "profilePicture":   "logo.png",
-        "coverPicture":     "",
-        "bio":              "Interactive designer, public speaker, startup advisor and writer. Living in Austria, attempting world domination via keyboard.",
-        "url":              "john.onolan.org",
-        "createdBy":        1,
-        "updatedBy":        1
-    }
-]
\ No newline at end of file
diff --git a/core/shared/data/migration/001.js b/core/shared/data/migration/001.js
new file mode 100644
index 0000000000..29dccf23a6
--- /dev/null
+++ b/core/shared/data/migration/001.js
@@ -0,0 +1,75 @@
+/*global require, exports */
+
+(function () {
+    "use strict";
+
+
+    var when    = require('when'),
+        knex    = require('./knex_init'),
+        fixtures = require('../fixtures/001'),
+        up,
+        down;
+
+    up = function () {
+
+        return when.all([
+
+            knex.Schema.createTable('posts', function (t) {
+                t.increments().primary();
+                t.string('title');
+                t.string('slug');
+                t.text('content');
+                t.text('content_html');
+                t.bool('featured');
+                t.string('image');
+                t.string('status');
+                t.string('language');
+                t.date('created_at');
+                t.integer('created_by');
+                t.date('updated_at');
+                t.integer('updated_by');
+            }),
+
+            knex.Schema.createTable('users', function (t) {
+                t.increments().primary();
+                t.string('username');
+                t.string('first_name');
+                t.string('last_name');
+                t.string('email_address');
+                t.string('profile_picture');
+                t.string('cover_picture');
+                t.text('bio');
+                t.string('url');
+                t.date('created_at');
+                t.integer('created_by');
+                t.date('updated_at');
+                t.integer('updated_by');
+            }),
+
+            knex.Schema.createTable('settings', function (t) {
+                t.increments().primary();
+                t.string('key');
+                t.text('value');
+                t.date('created_at');
+                t.integer('created_by');
+                t.date('updated_at');
+                t.integer('updated_by');
+            })
+
+        // Once we create all of the initial tables, bootstrap any of the data
+        ]).then(function () {
+
+            return when.all([
+                knex('posts').insert(fixtures.posts),
+                knex('users').insert(fixtures.users),
+                knex('settings').insert(fixtures.settings)
+            ]);
+
+        });
+    };
+
+    down = function () {};
+
+    exports.up = up;
+    exports.down = down;
+}());
\ No newline at end of file
diff --git a/core/shared/models/dataProvider.bookshelf.js b/core/shared/models/dataProvider.bookshelf.js
new file mode 100644
index 0000000000..d56188262a
--- /dev/null
+++ b/core/shared/models/dataProvider.bookshelf.js
@@ -0,0 +1,86 @@
+/**
+ * Provides access to data via the Bookshelf ORM
+ */
+
+/*globals module, require, process */
+(function () {
+    "use strict";
+
+    var knex  = require('knex'),
+        models = require('./models'),
+        DataProvider,
+        instance;
+
+    knex.Initialize(require('../../../config').database[process.env.NODE_ENV || 'development']);
+
+    DataProvider = function () {
+        if (!instance) {
+            instance = this;
+            knex.Schema.hasTable('posts').then(null, function () {
+                // Simple boostraping of the data model for now.
+                require('./../data/migration/001').up().then(function () {
+                    console.log('all done....');
+                });
+            });
+        }
+
+        return instance;
+    };
+
+    DataProvider.prototype.posts = function () { };
+
+    /**
+     * Naive find all
+     * @param args
+     * @param callback
+     */
+    DataProvider.prototype.posts.findAll = function (args, callback) {
+        models.Posts.forge().fetch().then(function (posts) {
+            callback(null, posts);
+        }, callback);
+    };
+
+    /**
+     * Naive find one where args match
+     * @param args
+     * @param callback
+     */
+    DataProvider.prototype.posts.findOne = function (args, callback) {
+        models.Post.forge(args).fetch().then(function (post) {
+            callback(null, post);
+        }, callback);
+    };
+
+    /**
+     * Naive add
+     * @param _post
+     * @param callback
+     */
+    DataProvider.prototype.posts.add = function (_post, callback) {
+        models.Post.forge(_post).save().then(function (post) {
+            callback(null, post);
+        }, callback);
+    };
+
+    /**
+     * Naive edit
+     * @param _post
+     * @param callback
+     */
+    DataProvider.prototype.posts.edit = function (_post, callback) {
+        models.Post.forge({id: _post.id}).fetch().then(function (post) {
+            post.set(_post).save().then(function (post) {
+                callback(null, post);
+            }, callback);
+        });
+    };
+
+
+    DataProvider.prototype.posts.destroy = function (_identifier, callback) {
+        models.Post.forge({id: _identifier}).destroy().then(function () {
+            callback(null);
+        });
+    };
+
+    module.exports = DataProvider;
+}());
\ No newline at end of file
diff --git a/core/shared/models/dataProvider.juggling.js b/core/shared/models/dataProvider.juggling.js
deleted file mode 100644
index e5a147c5da..0000000000
--- a/core/shared/models/dataProvider.juggling.js
+++ /dev/null
@@ -1,139 +0,0 @@
-/**
- * Provides access to data via the JugglingDb ORM
- */
-
-/*globals module, require */
-(function () {
-    "use strict";
-
-    var schema = require('./schema').schema,
-        fs = require('fs'),
-        _ =  require('underscore'),
-        DataProvider,
-        instance;
-
-
-    function populateData(callback) {
-        // TODO: convert to promises
-        schema.models.Setting.findOne({}, function (error, data) {
-            if (data === null) {
-                // we haven't loaded any data yet
-                fs.readFile(__dirname + '/data/fixtures/users.json', function (error, data) {
-                    if (error) {
-                        throw error;
-                    }
-
-                    var users = JSON.parse(data);
-
-                    _.each(users, function (post) {
-                        schema.models.User.create(post, function (error, data) {
-                            console.log('User created error', error);
-                            console.log('User created data', data);
-                        });
-                    });
-
-                    fs.readFile(__dirname + '/data/fixtures/posts.json', function (error, data) {
-                        if (error) {
-                            throw error;
-                        }
-
-                        var posts = JSON.parse(data),
-                            post;
-
-                        _.each(posts, function (_post) {
-                            post = new schema.models.Post(_post);
-
-                            post.preCreate(function () {
-                                post.save(function (error, data) {
-                                    console.log('Post created error', error);
-                                    console.log('Post created data', data);
-                                });
-                            });
-                        });
-
-                        fs.readFile(__dirname + '/data/fixtures/settings.json', function (error, data) {
-                            if (error) {
-                                throw error;
-                            }
-
-                            var posts = JSON.parse(data);
-
-                            _.each(posts, function (post) {
-                                schema.models.Setting.create(post, function (error, data) {
-                                    console.log('Setting created error', error);
-                                    console.log('Setting created data', data);
-                                });
-                            });
-
-                            callback();
-                        });
-                    });
-
-
-                });
-            } else {
-                callback();
-            }
-        });
-    }
-
-    DataProvider = function () {
-        if (!instance) {
-            instance = this;
-
-            if (process.env.forcePopulate) {
-                populateData();
-            }
-        }
-
-        return instance;
-    };
-
-    DataProvider.prototype.posts = function () {};
-
-    /**
-     * Naive find all
-     * @param callback
-     */
-    DataProvider.prototype.posts.findAll = function (callback) {
-        schema.models.Post.all(callback);
-    };
-
-    /**
-     * Naive find one where args match
-     * @param callback
-     */
-    DataProvider.prototype.posts.findOne = function (args, callback) {
-        schema.models.Post.findOne({where: args}, callback);
-    };
-
-    /**
-     * Naive add
-     * @param post
-     * @param callback
-     */
-    DataProvider.prototype.posts.add = function (_post, callback) {
-        var post = new schema.models.Post(_post);
-
-        post.preCreate(function () {
-            post.save(callback);
-        });
-    };
-
-    /**
-     * Naive edit
-     * @param post
-     * @param callback
-     */
-    DataProvider.prototype.posts.edit = function (_post, callback) {
-        schema.models.Post.findOne({where: {id: _post.id}}, function (error, post) {
-            post = _.extend(post, _post);
-
-            schema.models.Post.updateOrCreate(post, callback);
-        });
-    };
-
-    DataProvider.prototype.populateData = populateData;
-
-    module.exports = DataProvider;
-}());
\ No newline at end of file
diff --git a/core/shared/models/models.js b/core/shared/models/models.js
new file mode 100644
index 0000000000..0dd61a7f1a
--- /dev/null
+++ b/core/shared/models/models.js
@@ -0,0 +1,86 @@
+/*global require, module */
+
+(function () {
+    "use strict";
+
+    // We should just be able to require bookshelf and have it reference
+    // the `Knex` instance bootstraped at the app initialization.
+    var Bookshelf = require('bookshelf'),
+        Showdown = require('showdown'),
+        converter = new Showdown.converter(),
+
+        Post,
+        Posts,
+        User,
+        Setting;
+
+    Post = Bookshelf.Model.extend({
+
+        tableName: 'posts',
+
+        hasTimestamps: true,
+
+        initialize: function () {
+            this.on('creating', this.creating, this);
+            this.on('saving', this.saving, this);
+        },
+
+        saving: function () {
+            if (!this.get('title')) {
+                throw new Error('Post title cannot be blank');
+            }
+            this.set('content_html', converter.makeHtml(this.get('content')));
+
+            // refactoring of ghost required in order to make these details available here
+            // this.set('language', this.get('language') || ghost.config().defaultLang);
+            // this.set('status', this.get('status') || ghost.statuses().draft);
+
+        },
+
+        creating: function () {
+            if (!this.get('slug')) {
+                this.generateSlug();
+            }
+        },
+
+        generateSlug: function () {
+            return this.set('slug', this.get('title').replace(/\:/g, '').replace(/\s/g, '-').toLowerCase());
+        },
+
+        user: function () {
+            return this.belongsTo(User, 'created_by');
+        }
+
+    });
+
+    Posts = Bookshelf.Collection.extend({
+
+        model: Post
+
+    });
+
+    User = Bookshelf.Model.extend({
+
+        tableName: 'users',
+
+        hasTimestamps: true,
+
+        posts: function () {
+            return this.hasMany(Posts, 'created_by');
+        }
+
+    });
+
+    Setting = Bookshelf.Model.extend({
+
+        tableName: 'settings'
+
+    });
+
+    module.exports = {
+        Post: Post,
+        Posts: Posts,
+        User: User,
+        Setting: Setting
+    };
+}());
\ No newline at end of file
diff --git a/core/shared/models/schema.js b/core/shared/models/schema.js
deleted file mode 100644
index 4fe9b49b46..0000000000
--- a/core/shared/models/schema.js
+++ /dev/null
@@ -1,111 +0,0 @@
-/**
- * Database Schema, created with JugglingDB
- *
- * Vastly incomplete!
- */
-
-/*globals module, require */
-(function () {
-    "use strict";
-
-    var Schema = require('jugglingdb').Schema,
-        schema = new Schema('sqlite3', {
-            database: __dirname + '/../data/datastore.db'
-        }),
-        Post,
-        User,
-        Setting;
-
-    /*------------------------------------------------------------------------------------
-     POST / Post / Posts
-     ------------------------------------------------------------------------------------*/
-    Post = schema.define('Post', {
-        title:          String,
-        slug:           String,
-        content:        Schema.Text,
-        contentHtml:    Schema.Text,
-        featured:       Boolean,
-        image:          String,
-        status:         String,
-        language:       String,
-        createdAt:      Date,
-        createdBy:      Number,
-        updatedAt:      Date,
-        updatedBy:      Number
-    });
-
-    Post.prototype.generateSlug = function () {
-        return this.title.replace(/\:/g, '').replace(/\s/g, '-').toLowerCase();
-    };
-
-    Post.prototype.preCreate = function (next) {
-        console.log('pre create 1', this);
-
-        if (this.createdAt === undefined) {
-            this.createdAt = new Date();
-        }
-        if (this.slug === undefined) {
-            this.slug = this.generateSlug();
-        }
-
-        console.log('pre create 2', this);
-        next();
-    };
-
-    // Validations
-    Post.validatesPresenceOf('title', {message: 'Post title cannot be blank'});
-    //Post.validatesPresenceOf('slug');
-    //Post.validatesPresenceOf('language', {message: 'Language cannot be blank'});
-    //Post.validatesUniquenessOf('slug');
-    //Post.validatesLengthOf('language', {min: 2, max: 5}, "The language code should be between 2 and 5 chars long, E.g. 'en' or 'en_GB' ");
-
-
-    Post.beforeSave = function (next, data) {
-        console.log('before s1', data);
-        // set updated
-        data.updatedAt = new Date();
-        next();
-    };
-
-    /*------------------------------------------------------------------------------------
-     USER / User / Users
-     ------------------------------------------------------------------------------------*/
-    User = schema.define('User', {
-        username: String,
-        firstName: String,
-        lastName: String,
-        emailAddress: String,
-        profilePicture: String,
-        coverPicture: String,
-        bio: Schema.Text,
-        url: String,
-        createdAt:      Date,
-        createdBy:      Number,
-        updatedAt:      Date,
-        updatedBy:      Number
-    });
-
-
-    /*------------------------------------------------------------------------------------
-     SETTING / Setting / Settings
-     ------------------------------------------------------------------------------------*/
-    Setting = schema.define('Setting', {
-        key: String,
-        value: Schema.Text,
-        createdAt:      Date,
-        createdBy:      Number,
-        updatedAt:      Date,
-        updatedBy:      Number
-    });
-
-
-    /*------------------------------------------------------------------------------------
-     RELATIONSHIPS
-     ------------------------------------------------------------------------------------*/
-    User.hasMany(Post,   {as: 'posts',  foreignKey: 'createdBy'});
-    Post.belongsTo(User, {as: 'author', foreignKey: 'createdBy'});
-
-    schema.autoupdate();
-
-    exports.schema = schema;
-}());
\ No newline at end of file
diff --git a/package.json b/package.json
index b456e1b6b3..187a5c8f9a 100644
--- a/package.json
+++ b/package.json
@@ -16,7 +16,10 @@
     "underscore": "*",
     "showdown": "*",
     "sqlite3": "2.1.7",
-    "jugglingdb": "0.2.x",
+    "bookshelf": "0.1.x",
+    "knex": "0.1.x",
+    "when": "~2.1.0",
+    "jugglingdb": "0.2.0-29",
     "jugglingdb-sqlite3": "git+https://github.com/jugglingdb/sqlite3-adapter.git#master"
   },
   "devDependencies": {