Adds Events part 1.

This is the first part of a 2-part post to respond to [this blog post](http://naturaily.com/blog/post/marionette-plain-object-over-reqres-commands-above-all)
So great posts with lots of good tips!  I'm just gonna throw this idea out there. But I think it'd be great if the content is restructured to not be a direct response to Maciej but a post _inspired_ by his post.

So some thoughts on how this might look....all the content is there but just have to re-ordered

**Title:**
Best Practices in Using Events in Your App

   *or*

Best Practices for Apps Using Evented Architecture 


* Inspired by a blog post by Maciej Kucharski

**Section: How to Think About Events**

* Analogy
* HTTP get & post analogy
* decoupling the client and server


**Section: Use Channels Instead of the Global Event Bus**

**Sub-Section: How People Typically Use Events**

* The typical way that one introduces namespacing on the global message bus is using period or colon-separated strings

   // Namespace this as a notifications event
   app.vent.trigger('notifications:show');

   // And namespace this as a profile event
   app.vent.trigger('profile:show');


**Sub-Section: 3 Problems with Global Event Bus Pattern**

**Sub-Section: How to Use Channels**

 * 3 ways to get a channel with examples


**Section: If you find the Wrequr syntax unwiedly and convoluted... Radio**

**Sub-Section: Debug mode?**

**Sub-Section: Synchronous vs other async libs?**