Marionette has marked `appRegions` as a deprecated feature because it is a
leaky abstraction for the Application to know so much about the DOM and
the structure of your actual page.
Instead of using `appRegions`, Marionette encourages you to setup a
RootLayout whose concern is setting up render targets.

In the near future we are introducing the concept of a "root" to the
application object
https://github.com/marionettejs/backbone.marionette/issues/2279

So that uses will have an idiomatic way of using this pattern. The goal
here is not to conflate the concerns of splitting up render targets
with your application, rather the goal is to give users a pattern to follow when
setting up a single or multiple application objects.

Fixes #1171
Fixes #1184

Closure app upgrade to new UI

Correct spelling/grammar mistake

Checkboxes is plural possessive

Elm Example

fixed youtube urls for "Articles and Guides" section in marionettejs example

Fix the template link in index.html, as it was moved out to a separate repo

Fix the template link

updated sidebar copy for marionettejs example

updated copy for sidebar, removed wiki link and other out dated links, added links to more recent resources and updated description

Fix spec compliance for Marionette.

What:

In issue #789 @ColinEberhardt pointed out that many of the examples do
not respect the rule that when a user hits the esc key on an input that
the input should be cleared and the input state should be left.

Upon investigation I found the Marionette example to have never followed
this directive.

How:

Due the how the escape key works and the keypress event binding from
jQuery one must use the keyup event to register for the escape key
keycode.

Once I intercept the event I instruct the input area to simply rerender.
This has the desired effect in that it clears the transient input state
and also due to it rendering new childnodes clears the focus from the
user.

Update use of initializers

Marionette as of v2.3.0 has marked initializers as a deprecated feature.
https://github.com/marionettejs/backbone.marionette/commit/1717c71af306be28cafebcdafda86ba218df0caa

Why is this?

Back when Marionette was built (late 2011), module patterns were still
emerging, it was the wild west in many ways. @derickbailey came up with
the idea of marionette modules. Modules were built for managing "components" and nested
components. They could be stopped and started at will and were also
started and stopped with their parents (since modules are nestable).

Initializers and Finalizers (pieces of the Marionette.Callbacks helper
class) are a great idea, and are a very powerful one at that, allowing people to specifiy actions to take onStart or
onEnd.

That said, the year is 2015 and much has changed about the landscape of
modules and javascript. Heck @derickbailey even wrote a post about why you
should not use them anymore.
http://derickbailey.com/2014/06/10/browserify-my-new-choice-for-modules-in-a-browser-backbone-app/

Marionette is moving away from modules, and is moving into the land of
applications and sub applications to help people better handle complex
applications.

-------

fixes #1105

Exoskeleton: Switch to the original backbone.localstorage

Close #1162

Bug fix in angular example (issue #1083)