Comments

Card: https://trello.com/c/DOb3MOBk/10-comments-on-a-card-last-comment-at-the-top-initially-just-record-who-commented-and-what-did-they-say-that-s-all

Realtime and e-mail were too large for a single iteration, thus let’s keep them separate (as they are in cards, after all).

Please, @exalted give this a look :smile: 
> What about https://github.com/task-planner/task-planner-web/pull/15/files#diff-21497849d8f00507c9c8dcaf6288b136R3?

Do you mean putting it under the first `resources :cards` declaration? 

If yes, please, read [this nice article](http://weblog.jamisbuck.org/2007/2/5/nesting-resources) by Jamis Buck (ex Basecamp employee) which explains the issue of having deeply nested route. I wanted to follow the advice, since it makes sense (generated helpers are awful, and remembering a URL is pretty difficult). He uses a technique which has been integrated in Rails (e.g. `shallow routes`), but it has a weird behavior and thus I avoided it altogether, sticking with a plain ol’ custom route.

That said, I think I can put it right under the first declaration creating a “deeply nested route”, but I believe we can stick with what we have right now as well.