Adding unit tests is straightforward in Meteor. Any files in the tests/ folder will be ignored by the Meteor server.
I think it’s safe to say most developers would like to have a successful blog. After all, a blog is great way to develop a personal brand. Personally, I’ve attempted and failed many times over the years. If you’re anything like me, you’ve always felt a bit paralyzed by how much work maintaining a successful online presences is. Meaning I would have to worry about marketing, SEO, social media, readership, engagement, comments, and oh, of course, actually writing quality content. Luckily for us, this book puts together a series of simple, straight forward, and easy steps that will take you from nothing to a well-built blog (like this one, of course!).
This post is part of a series:
One of the missing features in my prototype was handling of permalinks. To make things easy, I originally removed all the routes and added click handlers instead. In retrospect that was a mistake. Instead of having the app logic tangled up with click handlers, it would have been much more straightforward to define routes and use links.
In a previous post, I built an example single page app using Backbone. One thing that bothered me was how similar the views are, yet didn’t share any code. I think part of this was that I originally scaffolded the entire app and worked backwards.
While playing around with Backbone.js, I couldn’t find an easy way to build an app that used the RESTful hierarchy of my models. I think Spine’s implementation is fairly straightforward.
I did find a relevant active project, but for my specific case the added complexity of an additional component and dependency didn’t seem justified. Rails already does the hard part for me, I just need Backbone to call the correct Urls.
I wanted to learn more about Backbone, so I prototyped a very basic project management app using Rails and Backbone called Trackbone that I’ll walk through in this post.