My stab at fixing the Merb wiki

gistfile1.txt

====== Welcome to the Merb Wiki! =======
=====   Homepage and Information Routing =====

Welcome to the Merb Wiki!  This wiki is set up in order to help users of all skill levels.  Herein you should be able to find information about specific subjects, [[merb|learn more about Merb]] and [[development|how to use it]], and find [[further resources]].

  * **__Looking for specific content__**? Or those who like to jump right in, feel free to use the table of contents to the right or [[http://wiki.Merbivore.com/?do=index|the full document index]].
  * **__New user__**?  We have [[articles]] about [[what Merb is]], and what it's [[history]], [[philosophy]] are, and what [[it's future]] will be (and [[the merge with Rails]]).  If you are [[new to Ruby]] as well, we've got [[links for that]] too!
  * **__Rails users__** may be interested in the [[differences between Merb and Rails]], and [[tutorials]] on how to get up and running with Merb.
  * **__Already a Merbist__**?  Looking for more info?  You may be interested in more detailed information about [[development|Merb development]], [[tutorials]] and the [[Merb ecosystem]].
  * If we haven't covered what you're looking for, you can check the [[http://wiki.Merbivore.com/?do==index|index]] just in case.  If you still can't find what you are looking for feel free to let us know how we can improve the wiki through our [[mailing list]], or in our [[irc channel]].

=====   Merb =====
====     What's Merb? ====

Merb is a MVC web development framework written in Ruby.

====     Who's using Merb? ====
====     Why Merb? ====
====     History of Merb ====

Merb began it's life as a pastie.  A tiny proposal on how to handle file uploads better in a Rails application.  But soon it began to rally some developer frustration, and Merb began to bud into a "clean room rewrite" of Ruby on Rails.  Over time Merb blossomed into a substantial web framework in it's own right, boasting a number of features with no analogues in the Rails stack.

====     The Future of Merb ====
=====   Philosophy =====
====     Agnosticism and Componentized Architecture ====
====     Ruby is awesome, use Ruby. ====
====     Principled Development ====
=====   Design Principles =====
====     Public/Private API ====



====     MVC ====
====     Mountable Applications: Slices ====
====     Rack ====
=====   Development =====
====     Setting Up ====
===       Getting Merb ===
==         Would you like that Stacked, or á la carte? ==
==         Stacks ==
==         Á la Carte ==
==         Merb on the Edges ==
===       Getting Merb to work with other stuff (Gem Dependencies) ===
==         To Bundle or Not Bundle ==
====     Building Your App ====
===       Models ===
==         Datamapper ==
==         ActiveRecord ==
==         Sequel ==
===       Views ===
==         View Helpers ==
===       Controllers ===
===       Mailers ===
===       Javascript and AJAX ===
====     Connecting to Your App ====
===       Routing ===
===       Connecting to Slices ===
====     Testing ====
===       Debugging and Hand Testing ===
==         Merb -i ==
===       Testing Libraries ===
==         Rspec ==
==         Test/Unit ==
===       Testing Style ===
=====   The Merb Ecosystem =====
====     Useful Merb Slices ====
====     Getting Help ====
====     Helping Out ====
===	      Helping with the Wiki ===

[[http://twitter.com/knowtheory|Knowtheory]] here!  I would like to try and start a movement to organize the wiki.  Not just this wiki, actually, but a number of related Ruby projects with a certain lack of attention to their crowd-sourced documentation.

I've got a few goals in mind, and would love to hear input and critiques from people who have an interest in the Ruby ecosystem and the state of our community education.  So let's get to the meat of what's important:

  * **__Help get people to their desired destination__**.  If they don't want our help, get out of the way and give them an index/toc.
  * **__Provide clear notifications__**.  Users should know the state of the information they are reading.  E.g. Whether a page has problems/omissions/biases, What versions of software code are applicable, timestamps.
  * **__Provide clear calls to action__**.  If something needs help, or to be improved, point it out.  Keep a list of weaknesses around the site that people can help with.
  * **__Lower barriers to editing & helping__**.  Just because we don't want people to screw up existing pages, shouldn't mean that we prevent other people from trying to help out.  We should encourage people to FORK pages, or create new docs under their own namespace to contribute (like i have done here) or get people to use gist!
  * **__Provide narratives__**.  Different people learn differently.  We can accommodate them!  That is what hypertext is about. :)

=====   Deployment =====
====     Rack, MRI and Mongrel|Thin|Ebb ====
====     Rack and Passenger ====
====     Glassfish & JRuby ====
=====   FAQ =====
====     The Merb2/Rails3 Section ====
===       Why did you sell us out? ===
=====   Tutorials =====