You can re-arrange this page, add and subtract titles, and do whatever you need for it to make sense for this project.

Sinatra

Project Details
Title: Sinatra
Language: Ruby
URL: http://www.sinatrarb.com/

Summary: what was read/what it does

Description: more detailed over view

Dependencies: 
Among others, Sinatra uses Rack, a minimal, interface for web apps (see http://en.wikipedia.org/wiki/Rack_(web_server_interface) ) 
and Tilt (a common interface for template engines like ERB, HAML SASS etc.). 

Pseudo code: what does this do, in pseudo code

Comments: Interesting techniques, tricks. Coding style, Things that could have been done better, balance between efficiency and clarity, quality of code-re-use. 

Architecture: Data models, Class hierarchy. Is the architecture clean, intuitive, easy to understand? If not, how would you change it?

How hackable is this code (well documented, easy to find your way around, could create a patch/add a feature without too much pain): Score 1-5


Useful Ressources: 

• http://sinatra-book.gittr.com/

Possible bugs identified, if any



a quick and noobish look at 
Routing

(I'd be grateful for a little help here, the basic idea I got:)

Example: 

get '/' do
  "Hi there!"
end

get '/:name' do
  "Hello #{params[:name]}!"
end

The HTTP-verb methods get, put, post, delete are defined in base.rb, starting at line 837.
so get '/' calls the method route with arguments 'GET' (verb) and '/' (path).
in route() there's a call to compile(path) (see line 887), 
which returns a regular expression 
and keys like our "name" in the second part of the example.

then, the method uses ruby's define_method to define a new method 
with the name "get '/'" and the supplied block (in our case, "Hi there!"; in general everything between do and end).

so for every route there's a method defined. 

the routes go into the hash @route