I guess that falls into Ruby dev and less Jekyll stuff?

Ember Data and Ember.js are different projects, although strongly related. Ember Data can be used to render database objects on client side with ease.

OP: Nice post. I've actually spent the last few days on the very same topic. I had the same problem with MongoDB's _id and everything I found on Google seemed to show different approach, from which none worked. Ultimately I changed to Parse and everything worked out of the box.

I would be interested to see how you hooked up Ember Data to Parse.

I used this: https://github.com/clintjhill/ember-parse-adapter

Basically just link the JS and add your API keys.

Correct.

I do this, although I just call it `style.css`

Right,

First of all, thanks for commenting on the thread! Also, I really hope it hasn't come across as though this post was "bandwagoning" on the "struggle with getting started with X.js week". The reason I LOVE Backbone is the fact is the fact that it's not opinionated on application architecture.

However, IMO no one (or not many) people build single page todo apps. People have real, multi-state and multi-screen apps that they're trying to build and I think that Backbone site/docs would really really helps people take their understanding of Backbone and architecture to the next level if an example was provided that went beyond the humble Todo app. DOM structure, Zombie events and View management (subviews, etc) are things that I feel are missing, not from Backbone itself, but that Backbone should/could provide as examples of using Backbone to deal with these real, use-case issues that arise.

I think this lack of documentation/examples acted as a catalyst for things like Marionette (hat tip Derick Bailey), but if patterns were outlined from the get-go on the Backbone site, people would be less inclined/feel the need to throw something like Marionette at it.

Hope this has come off as my humble opinion and not just "grumpy developer snark" - I love Backbone but I'd love to see it have an easier route for learning to build real world apps.

I don't want to waste this opportunity of telling you my thoughts, so I'm gonna let your question settle a litte. Will reply soon :)

Are you thinking of https://svbtle.com/ ? Yeah mine looks similar but I assure you, it wasn't ripped at all!

Sorry Ben, I didn't mean to accuse you of anything. Sorry if it came out that way. And yeah, that's what I was looking for :) thanks!

Truly nitpicking ;), you're probably right, but as a convention it makes sense for me and hopefully others!

Worst. Writing. Style. Ever.

So condescending.

So far, feedback has been:

1. maybe an initial syntax overview: target.addEventListener(type, listener[, useCapture]);

2. I think it’d be worth explaining what capture and bubble are.

I agree!

Another helpful point would be when to use capture, and when to use bubble.

Did like this post though, I've only recently picked up JS and this confused me when I tried implementing listeners a few weeks ago for a project.

I want to take it as a compliment, but I don't feel it was intended like that!

It's not a personal insult if you were taking it like that. I'm pointing out that it's an odd stance you've taken. The audience that recognizes Bootstrap layouts and the audience that recognizes the Svbtle theme (or its variations) are one and the same. More to the point though, if you feel that way about Bootstrap then you should probably feel the same way about the theme you chose.