building solution first

Author: dfenjves

.learn

@@ -1,5 +1,7 @@
 tags:
-  - tag1
+  - sinatra
+  - forms
+  - html
 languages:
-  - language1
-resources: 0
+  - ruby
+  - html

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing to Learn.co Curriculum
+
+We're really exited that you're about to contribute to the [open curriculum](https://learn.co/content-license) on [Learn.co](https://learn.co). If this is your first time contributing, please continue reading to learn how to make the most meaningful and useful impact possible.
+
+## Raising an Issue to Encourage a Contribution
+
+If you notice a problem with the curriculum that you believe needs improvement
+but you're unable to make the change yourself, you should raise a Github issue
+containing a clear description of the problem. Include relevant snippets of
+the content and/or screenshots if applicable. Curriculum owners regularly review
+issue lists and your issue will be prioritized and addressed as appropriate.
+
+## Submitting a Pull Request to Suggest an Improvement
+
+If you see an opportunity for improvement and can make the change yourself go
+ahead and use a typical git workflow to make it happen:
+
+* Fork this curriculum repository
+* Make the change on your fork, with descriptive commits in the standard format
+* Open a Pull Request against this repo
+
+A curriculum owner will review your change and approve or comment on it in due
+course.
+
+# Why Contribute?
+
+Curriculum on Learn is publicly and freely available under Learn's
+[Educational Content License](https://learn.co/content-license). By
+embracing an open-source contribution model, our goal is for the curriculum
+on Learn to become, in time, the best educational content the world has
+ever seen.
+
+We need help from the community of Learners to maintain and improve the
+educational content. Everything from fixing typos, to correcting
+out-dated information, to improving exposition, to adding better examples,
+to fixing tests—all contributions to making the curriculum more effective are
+welcome.

Gemfile

@@ -4,14 +4,14 @@ source "https://rubygems.org"
 # gem "rails"
 
 gem 'sinatra'
-    gem 'rake'
-    gem 'thin'
-    gem 'shotgun'
-    gem 'pry'
-    gem 'require_all'
-    
+gem 'rake'
+gem 'thin'
+gem 'shotgun'
+gem 'pry'
+gem 'require_all'
+
 group :test do
-      gem 'rspec'
-      gem 'capybara'
-      gem 'rack-test'
-    end
+  gem 'rspec'
+  gem 'capybara'
+  gem 'rack-test'
+end

Gemfile.lock

@@ -0,0 +1,20 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    rack (1.5.2)
+    rack-protection (1.5.0)
+      rack
+    shotgun (0.9)
+      rack (>= 1.0)
+    sinatra (1.4.3)
+      rack (~> 1.4)
+      rack-protection (~> 1.4)
+      tilt (~> 1.3, >= 1.3.4)
+    tilt (1.4.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  shotgun
+  sinatra

README.md

@@ -1,8 +1,50 @@
-# Basic Sinatra Forms Lab
-
-## Teacher outline
-The lab should consist of:
-+ Students creating html forms on multiple get routes
-+ Creating 'Post' routes for each form in the controller
-+ Manipulating the data in params and seting to instance variables
-+ Render the data in the instance variables in new .erb files
+# Superheroes!
+
+## Description
+
+In this lab, you'll practice building nested forms in Sinatra for creating teams of superheros. No database is required, but feel free to add persistence *after* you have successfully completed the instructions below.
+
+## Instructions
+
+1. `bundle install`
+2. `bundle exec shotgun`
+
+### Make a form
+
+1. Create a route that responds to a GET request at `/`.
+2. Create a view with a form and render it in the GET `/` route.
+3. The form should have fields for the `name` of a superhero team and their `motto`.
+4. There should be form inputs for each of the three superhero member's `name`, `power`, and `bio`.
+
+It should look something like this:
+
+![Imgur](http://i.imgur.com/zrbFWNE.png?1)
+
+### Handle form submission
+
+1. Create a route that responds to a POST request at `/teams`
+2. Have the form send a POST request to this route.
+2. Upon submission, render a template that displays the submitted team data and each member's data.
+
+## Final Output
+
+Your params should be nested. For example, you would access the first super-hero's name as:
+
+```ruby
+params["team"]["members"][0][name]
+```
+
+When you post to this form you should render a page that displays the name of the team and each member of the team, along with their name, super power and bio.
+
+Your view should display something like this:
+
+![Imgur](http://i.imgur.com/SzO0phP.png?1)
+
+## Deliverables
+
+Pass the tests!
+
+## Resources
+* [Ashley William's GitHub](https://github.com/ashleygwilliams/) - [Sinatra Form Party](https://github.com/ashleygwilliams/sinatra-form-party)
+
+* [Ashley William's GitHub](https://github.com/ashleygwilliams/) - [Citibike Sinatra](https://github.com/ashleygwilliams/citibike-sinatra)

Rakefile

@@ -1,4 +1,5 @@
-require_relative 'config/environment'
+require 'sinatra/base'
 
 class App < Sinatra::Base
-end
+
+end

app.rb

@@ -3,5 +3,4 @@
 require 'bundler/setup'
 Bundler.require(:default, ENV['SINATRA_ENV'])
 
-require './app'
-require_all 'models'
+require './app'