Wiki Update (part 1 of ...)

@jasonLaster @cmaher @thejameskyle @jmeas @samccone

hola,

I wanna help out with cleaning up the github wiki. here's the total list of internal pages with notes next to them. let me know about agreements, disagreements, etc. it'll give me/others a better opportunity to aid in removal, re-writing, etc.

Adding support for sorted collections
proposition: content is fine, possibly prepend the title with something to organize these types of entries.

AMD Modules vs Marionette's Modules
proposition: content could be richer, possibly prepend the title with something to organize these types of entries.

Available packages
proposition: needs a better title. it's extremely ambiguous.

Books, Articles, Screencasts, and Presentations
proposition: title is way too busy. can instead turn this into a Resources section or less specificity in the title.

Developing for Marionette
proposition: this is nice to have, but i think it's unnecessary to dedicate a wiki page to it. it's pretty clear on what to do in the README. could be removed.

Displaying A "loading ..." Message For A Collection Or Composite View
proposition: nice to have, but I'd more so leave this as a link in some sort of resources area and not it's own individual wiki entry.

Integrate backbone boilerplate and backbone.marionette
proposition: deprecate this.

Introduction to composite javascript apps
proposition: last edited in 2012 by derick, could probably use an update.

Loading Views and Indicators
proposition: shouldn't have its own wiki entry, could be put elsewhere or deprecated.

Meeting Notes April 15th, 2014
proposition: deprecate this. meeting notes are now added to the blog.

Meeting Notes April 29th, 2014
proposition: deprecate this. meeting notes are now added to the blog.

Packages, plugins and snippets for ides and editors
proposition: remove this

Passing custom options to itemview from collectionview or compositeview
proposition: content seems fine. could prepend the title to organize with the other helpful wiki entries.

Projects and websites using marionette
proposition: cute/nice to have, but i don't think it necessarily needs a wiki entry. could be an extended part of the website.

Showing a View in a Dialog Modal
proposition: deprecate this. doesn't need its own wiki page.

Swapping page content with regions
proposition: written by derick in 2012, needs review and possible update

The relationship between regions and layouts
proposition: written in 2012, needs review and possible update. could prepend the title to organize with the other helpful articles.

Use cases for the different views
proposition: great

Using a controller to change content in a marionette.layout
proposition: helpful, but honestly not really meant for a wiki page, could be great for a blog post. i'm 50/50 on this.

Using dustjs templates with marionette
proposition: condense to 1 page. possibly Templating in Marionette

Using handlebars templates with marionette
proposition: see above

Using jst templates with marionette
proposition: see above

Using Marionette With Browserify and Grunt
proposition: written in 2013, could use review; possibly prepend title to organize with the other helpful articles.

Using marionette with rails asset pipeline
proposition: written in 2012, could use update or deprecation.

Using marionette with requirejs
proposition: needs to be updated as the latest of each libraries now have UMD wrappers.

Using pre compiled templates
proposition: see propositions on templating page or deprecated. written in 2012.

View helpers for underscore templates
proposition: written in 2012, could be deprecated or re-written, or condensed in possibly new Templating in Marionette page.

marionettejs / backbone.marionette

Wiki Update (part 1 of ...) #1743