updated packages, readme

.gitignore

@@ -1,15 +1,33 @@
-# See http://help.github.com/ignore-files/ for more about ignoring files.
+# Created by https://www.gitignore.io/api/node
 
-# dependencies
+.DS_Store
+
+### Node ###
+# Logs
+logs
+*.log
+npm-debug.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Compiled binary addons (http://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
 node_modules
+jspm_packages
 
-# testing
-coverage
+# Optional npm cache directory
+.npm
 
-# production
-build
+# Optional REPL history
+.node_repl_history
 
-# misc
-.DS_Store
-.env
-npm-debug.log
+# Learn-specific .results.json
+.results.json

.learn

@@ -0,0 +1,5 @@
+tags:
+  - undefined
+languages:
+  - undefined
+resources: 0

CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing to Learn.co Curriculum
+
+We're really excited 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.

LICENSE.md

@@ -0,0 +1,23 @@
+# Learn.co Educational Content License
+
+Copyright (c) 2018 Flatiron School, Inc
+
+The Flatiron School, Inc. owns this Educational Content. However, the Flatiron
+School supports the development and availability of educational materials in
+the public domain. Therefore, the Flatiron School grants Users of the Flatiron
+Educational Content set forth in this repository certain rights to reuse, build
+upon and share such Educational Content subject to the terms of the Educational
+Content License set forth [here](http://learn.co/content-license)
+(http://learn.co/content-license). You must read carefully the terms and
+conditions contained in the Educational Content License as such terms govern
+access to and use of the Educational Content.
+
+Flatiron School is willing to allow you access to and use of the Educational
+Content only on the condition that you accept all of the terms and conditions
+contained in the Educational Content License set forth
+[here](http://learn.co/content-license) (http://learn.co/content-license).  By
+accessing and/or using the Educational Content, you are agreeing to all of the
+terms and conditions contained in the Educational Content License.  If you do
+not agree to any or all of the terms of the Educational Content License, you
+are prohibited from accessing, reviewing or using in any way the Educational
+Content.

README.md

@@ -1,22 +1,36 @@
 # Set List Lab
 
 ## Objectives
+
 1. Use forms to create new elements and update the store.
 2. Display a list of the new elements in a separate component.
 
 ## Overview
 
-Guess what - the bands are back! What we want is an application that allows us to add band names, and then have those band names instantly rendered below. We need to be incorporating Redux by dispatching actions and updating the store each time someone submits a new band.
+Guess what - the bands are back! What we want is an application that allows us
+to add band names, and then have those band names instantly rendered below. We
+need to be incorporating Redux by dispatching actions and updating the store
+each time someone submits a new band.
 
-So we will be creating two different React components, and each of them need to connect to our Redux store. One of the components will be a form where we input our band name, and the other component will display the list of bands.
+So we will be creating two different React components, and each of them need to
+connect to our Redux store. One of the components will be a form where we input
+our band name, and the other component will display the list of bands.
 
 The createStore method and some basic setup has already been implemented for you.
 
 ## Instructions
 
-1. You will need to write the `BandInput` component. The component should have a form with a text input and submit button. We would like to update the *component's* state each time the user types a new character in the input. However, we only update the store's state when the user hits the submit button. 
-  * Note: To have access to the store's dispatch method, we pass through the entire store as a prop.
+1. You will need to write the `BandInput` component. The component should have a
+form with a text input and submit button. We would like to update the
+*component's* state each time the user types a new character in the input.
+However, we only update the __Redux__ store's state when the user hits the
+submit button.
 
-2. You will need to write the `Bands` component. This component should display a ul with a list element for each of the bands in the store's state. Each list element should have text with the corresponding name of the band.
+2. You will need to write the `Bands` component. This component should display a ul
+with a list element for each of the bands in the store's state. Each list
+element should have text with the corresponding name of the band.
 
-3. You will also need to fill in the `manageBand` reducer located under `./src/reducers/manageBand.js`. It will need to respond to an action of `type 'ADD_BAND'` and correspondingly concatenate a new band each time the action is dispatched.
+3. You will also need to fill in the `manageBand` reducer located under
+`./src/reducers/manageBand.js`. It will need to respond to an action of `type
+'ADD_BAND'` and correspondingly concatenate a new band each time the action is
+dispatched.