cocoon 1.1.2 → 1.2.0

data/.travis.yml

@@ -1,5 +1,9 @@
+language: ruby
+script: "bundle exec rake"
 rvm:
-  - 1.8.7
-  - 1.9.2
-  - rbx
-  - ree
+  - 1.9.3
+  - 2.0.0
+  - rbx-19mode
+gemfile:
+  - gemfiles/Gemfile.rails-3.2.13
+  - Gemfile

data/Gemfile

@@ -2,15 +2,17 @@ source "http://rubygems.org"
 
 
 group :development, :test do
-  gem "rails", ">=3.0.0"
-  gem "sqlite3-ruby", :require => "sqlite3"
+  gem "rails", ">=4.0.0"
+  gem "sqlite3"
   gem "json_pure"
   gem "jeweler"
-  gem "rspec-rails", ">= 2.6.0"
-  gem "rspec",       ">= 2.6.0"
-  gem "actionpack",  ">=3.0.0"
+  gem "rspec-rails", ">= 2.8.0"
+  gem "rspec",       ">= 2.8.0"
+  gem "actionpack",  ">=4.0.0"
   gem "simplecov", :require => false
 
+  gem 'nokogiri'
+
   gem "generator_spec"
 end
 

data/Gemfile.lock

@@ -0,0 +1,152 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    actionmailer (4.0.0)
+      actionpack (= 4.0.0)
+      mail (~> 2.5.3)
+    actionpack (4.0.0)
+      activesupport (= 4.0.0)
+      builder (~> 3.1.0)
+      erubis (~> 2.7.0)
+      rack (~> 1.5.2)
+      rack-test (~> 0.6.2)
+    activemodel (4.0.0)
+      activesupport (= 4.0.0)
+      builder (~> 3.1.0)
+    activerecord (4.0.0)
+      activemodel (= 4.0.0)
+      activerecord-deprecated_finders (~> 1.0.2)
+      activesupport (= 4.0.0)
+      arel (~> 4.0.0)
+    activerecord-deprecated_finders (1.0.3)
+    activesupport (4.0.0)
+      i18n (~> 0.6, >= 0.6.4)
+      minitest (~> 4.2)
+      multi_json (~> 1.3)
+      thread_safe (~> 0.1)
+      tzinfo (~> 0.3.37)
+    addressable (2.3.5)
+    arel (4.0.0)
+    atomic (1.1.10)
+    builder (3.1.4)
+    diff-lcs (1.2.4)
+    erubis (2.7.0)
+    faraday (0.8.7)
+      multipart-post (~> 1.1)
+    generator_spec (0.9.0)
+      activerecord (>= 3.0, <= 4.0)
+      railties (>= 3.0, <= 4.0)
+    git (1.2.5)
+    github_api (0.10.1)
+      addressable
+      faraday (~> 0.8.1)
+      hashie (>= 1.2)
+      multi_json (~> 1.4)
+      nokogiri (~> 1.5.2)
+      oauth2
+    hashie (2.0.5)
+    highline (1.6.19)
+    hike (1.2.3)
+    httpauth (0.2.0)
+    i18n (0.6.4)
+    jeweler (1.8.6)
+      builder
+      bundler (~> 1.0)
+      git (>= 1.2.5)
+      github_api (= 0.10.1)
+      highline (>= 1.6.15)
+      nokogiri (= 1.5.10)
+      rake
+      rdoc
+    json (1.8.0)
+    json_pure (1.8.0)
+    jwt (0.1.8)
+      multi_json (>= 1.5)
+    mail (2.5.4)
+      mime-types (~> 1.16)
+      treetop (~> 1.4.8)
+    mime-types (1.23)
+    minitest (4.7.5)
+    multi_json (1.7.7)
+    multi_xml (0.5.4)
+    multipart-post (1.2.0)
+    nokogiri (1.5.10)
+    oauth2 (0.9.2)
+      faraday (~> 0.8)
+      httpauth (~> 0.2)
+      jwt (~> 0.1.4)
+      multi_json (~> 1.0)
+      multi_xml (~> 0.5)
+      rack (~> 1.2)
+    polyglot (0.3.3)
+    rack (1.5.2)
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    rails (4.0.0)
+      actionmailer (= 4.0.0)
+      actionpack (= 4.0.0)
+      activerecord (= 4.0.0)
+      activesupport (= 4.0.0)
+      bundler (>= 1.3.0, < 2.0)
+      railties (= 4.0.0)
+      sprockets-rails (~> 2.0.0)
+    railties (4.0.0)
+      actionpack (= 4.0.0)
+      activesupport (= 4.0.0)
+      rake (>= 0.8.7)
+      thor (>= 0.18.1, < 2.0)
+    rake (10.1.0)
+    rdoc (4.0.1)
+      json (~> 1.4)
+    rspec (2.13.0)
+      rspec-core (~> 2.13.0)
+      rspec-expectations (~> 2.13.0)
+      rspec-mocks (~> 2.13.0)
+    rspec-core (2.13.1)
+    rspec-expectations (2.13.0)
+      diff-lcs (>= 1.1.3, < 2.0)
+    rspec-mocks (2.13.1)
+    rspec-rails (2.13.2)
+      actionpack (>= 3.0)
+      activesupport (>= 3.0)
+      railties (>= 3.0)
+      rspec-core (~> 2.13.0)
+      rspec-expectations (~> 2.13.0)
+      rspec-mocks (~> 2.13.0)
+    simplecov (0.7.1)
+      multi_json (~> 1.0)
+      simplecov-html (~> 0.7.1)
+    simplecov-html (0.7.1)
+    sprockets (2.10.0)
+      hike (~> 1.2)
+      multi_json (~> 1.0)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    sprockets-rails (2.0.0)
+      actionpack (>= 3.0)
+      activesupport (>= 3.0)
+      sprockets (~> 2.8)
+    sqlite3 (1.3.7)
+    thor (0.18.1)
+    thread_safe (0.1.0)
+      atomic
+    tilt (1.4.1)
+    treetop (1.4.14)
+      polyglot
+      polyglot (>= 0.3.1)
+    tzinfo (0.3.37)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  actionpack (>= 4.0.0)
+  generator_spec
+  jeweler
+  json_pure
+  nokogiri
+  rails (>= 4.0.0)
+  rspec (>= 2.8.0)
+  rspec-rails (>= 2.8.0)
+  simplecov
+  sqlite3

data/History.md

@@ -1,5 +1,10 @@
 # Change History / Release Notes
 
+## Version 1.1.2
+
+* pull #118 (thanks @ahmozkya): remove the deprecated `.live` function, and use `.on` instead.
+  Note: at least jquery 1.7 is required now!
+
 ## Version 1.1.1
 
 * added the to be added/deleted element to the event, this allows to add animations/actions onto them

data/README.markdown

@@ -2,81 +2,69 @@
 
 [![Build Status](https://travis-ci.org/nathanvda/cocoon.png)](https://travis-ci.org/nathanvda/cocoon)
 
-cocoon is a Rails3 gem to allow easier handling of nested forms.
+Cocoon makes it easier to handle nested forms.
 
-Nested forms are forms that handle nested models and attributes in one form.
-For example a project with its tasks, an invoice with its ordered items.
+Nested forms are forms that handle nested models and attributes in one form;
+e.g. a project with its tasks or an invoice with its line items.
 
-It is formbuilder-agnostic, so it works with standard Rails, or Formtastic or simple_form.
+Cocoon is form builder-agnostic, so it works with standard Rails, [Formtastic](https://github.com/justinfrench/formtastic), or [SimpleForm](https://github.com/plataformatec/simple_form).
+It is compatible with rails 3 and rails 4.
 
-This project is not related to [Apache Cocoon](http://cocoon.apache.org/)
+This project is not related to [Apache Cocoon](http://cocoon.apache.org/).
 
 ## Prerequisites
 
-This gem uses jQuery, it is most useful to use this gem in a rails3
-project where you are already using jQuery.
-
-Furthermore i would advice you to use either formtastic or simple_form.
-
-I have a sample project where I demonstrate the use of cocoon with formtastic.
+This gem depends on jQuery, so it's most useful in a Rails 3 project where you are already using jQuery.
+Furthermore, I would advise you to use either [Formtastic](https://github.com/justinfrench/formtastic) or [SimpleForm](https://github.com/plataformatec/simple_form).
 
 ## Installation
 
 Inside your `Gemfile` add the following:
 
-````ruby
+```ruby
 gem "cocoon"
-````
+```
+
 
 ### Rails 3.1+
 
-Add the following to `application.js` so it compiles to the
-asset_pipeline
+Add the following to `application.js` so it compiles to the asset pipeline:
 
-````ruby
+```ruby
 //= require cocoon
-````
+```
 
 ### Rails 3.0.x
 
 If you are using Rails 3.0.x, you need to run the installation task (since rails 3.1 this is no longer needed):
 
-````ruby
+```bash
 rails g cocoon:install
-````
+```
 
-This will install the needed javascript file.
-Inside your `application.html.haml` you will need to add below the default javascripts:
+This will install the Cocoon JavaScript file. In your application layout, add the following below the default javascripts:
 
-````haml
+```haml
 = javascript_include_tag :cocoon
-````
-
-or using erb, you write
-
-````ruby
-<%= javascript_include_tag :cocoon %>
-````
-
-That is all you need to do to start using it!
+```
 
-## Usage
+## Basic Usage
 
-Suppose you have a model `Project`:
+Suppose you have a `Project` model:
 
-````ruby
+```bash
 rails g scaffold Project name:string description:string
-````
+```
 
-and a project has many `tasks`:
+And a project has many `tasks`:
 
-````ruby
-rails g model Task description:string done:boolean project_id:integer
-````
+```bash
+rails g model Task description:string done:boolean project:belongs_to
+```
 
-Edit the models to code the relation:
+Your models are associated like this:
 
-````ruby
+```ruby
 class Project < ActiveRecord::Base
   has_many :tasks
   accepts_nested_attributes_for :tasks, :reject_if => :all_blank, :allow_destroy => true
@@ -85,19 +73,19 @@ end
 class Task < ActiveRecord::Base
   belongs_to :project
 end
-````
+```
 
-What we want to achieve is to get a form where we can add and remove the tasks dynamically.
-What we need for this, is that the fields for a new/existing `task` are defined in a partial
-view called `_task_fields.html`.
+Now we want a project form where we can add and remove tasks dynamically.
+To do this, we need the fields for a new or existing `task` to be defined in a partial
+named `_task_fields.html`.
 
-We will show the sample usage with the different possible form-builders.
+## Examples
 
-### Using formtastic
+### Formtastic
 
-Inside our `projects/_form` partial we then write:
+In our `projects/_form` partial we'd write:
 
-````haml
+```haml
 = f.inputs do
   = f.input :name
   = f.input :description
@@ -109,27 +97,25 @@ Inside our `projects/_form` partial we then write:
       = link_to_add_association 'add task', f, :tasks
   = f.actions do
     = f.action :submit
-````
+```
 
-and inside the `_task_fields` partial we write:
+And in our `_task_fields` partial we'd write:
 
-````haml
+```haml
 .nested-fields
   = f.inputs do
     = f.input :description
     = f.input :done, :as => :boolean
     = link_to_remove_association "remove task", f
-````
-
-That is all there is to it!
+```
 
-There is an example project on github implementing it called [cocoon_formtastic_demo](https://github.com/nathanvda/cocoon_formtastic_demo).
+The example project [cocoon_formtastic_demo](https://github.com/nathanvda/cocoon_formtastic_demo) demonstrates this.
 
-### Using simple_form
+### SimpleForm
 
-Inside our `projects/_form` partial we then write:
+In our `projects/_form` partial we'd write:
 
-````haml
+```haml
 = simple_form_for @project do |f|
   = f.input :name
   = f.input :description
@@ -140,25 +126,25 @@ Inside our `projects/_form` partial we then write:
     .links
       = link_to_add_association 'add task', f, :tasks
   = f.submit
-````
+```
 
-and inside the `_task_fields` partial we write:
+In our `_task_fields` partial we write:
 
-````haml
+```haml
 .nested-fields
   = f.input :description
   = f.input :done, :as => :boolean
   = link_to_remove_association "remove task", f
-````
+```
 
-There is an example project on github implementing it called [cocoon_simple_form_demo](https://github.com/nathanvda/cocoon_simple_form_demo).
+The example project [cocoon_simple_form_demo](https://github.com/nathanvda/cocoon_simple_form_demo) demonstrates this.
 
-### Using standard rails forms
+### Standard Rails forms
 
-Inside our `projects/_form` partial we then write:
+In our `projects/_form` partial we'd write:
 
-````haml
-- form_for @project do |f|
+```haml
+= form_for @project do |f|
   .field
     = f.label :name
     %br
@@ -174,11 +160,11 @@ Inside our `projects/_form` partial we then write:
     .links
       = link_to_add_association 'add task', f, :tasks
   = f.submit
-````
+```
 
-and inside the `_task_fields` partial we write:
+In our `_task_fields` partial we'd write:
 
-````haml
+```haml
 .nested-fields
   .field
     = f.label :description
@@ -188,25 +174,23 @@ and inside the `_task_fields` partial we write:
     = f.check_box :done
     = f.label :done
   = link_to_remove_association "remove task", f
-````
-
-I will provide a sample project later.
+```
 
 ## How it works
 
-I define two helper functions:
+Cocoon defines two helper functions:
 
 ### link_to_add_association
 
-This function will add a link to your markup that will, when clicked, dynamically add a new partial form for the given association.
-This should be placed below the `semantic_fields_for`.
+This function adds a link to your markup that, when clicked, dynamically adds a new partial form for the given association.
+This should be called within the form builder.
 
-It takes four parameters:
+`link_to_add_association` takes four parameters:
 
 - name: the text to show in the link
-- f: referring to the containing form-object
+- f: the form builder
 - association: the name of the association (plural) of which a new instance needs to be added (symbol or string).
-- html_options: extra html-options (see `link_to`)
+- html_options: extra html-options (see [`link_to`](http://api.rubyonrails.org/classes/ActionView/Helpers/UrlHelper.html#method-i-link_to)
   There are some special options, the first three allow to control the placement of the new link-data:
   - `data-association-insertion-traversal` : the jquery traversal method to allow node selection relative to the link. `closest`, `next`, `children`, etc. Default: absolute selection
   - `data-association-insertion-node` : the jquery selector of the node
@@ -219,41 +203,45 @@ It takes four parameters:
   - `wrap_object` : a proc that will allow to wrap your object, especially useful if you are using decorators (e.g. draper). See example lower.
   - `force_non_association_create`: if true, it will _not_ create the new object using the association (see lower)
 
-Optionally you could also leave out the name and supply a block that is captured to give the name (if you want to do something more complicated).
+Optionally, you can omit the name and supply a block that is captured to render the link body (if you want to do something more complicated).
 
 #### :render_options
-Inside the `html_options` you can add an option `:render_options`, and the containing hash will be handed down to the form-builder for the inserted
-form. E.g. especially when using `twitter-bootstrap` and `simple_form` together, the `simple_fields_for` needs the option `:wrapper => 'inline'` which can
-be handed down as follows:
+Inside the `html_options` you can add an option `:render_options`, and the containing hash will be handed down to the form builder for the inserted
+form.
 
-(Note: In certain newer versions of simple_form, the option to use is ':wrapper => 'bootstrap')
+When using Twitter Bootstrap and SimpleForm together, `simple_fields_for` needs the option `:wrapper => 'inline'` which can
+be handed down as follows:
 
-````haml
-= link_to_add_association 'add something', f, :something, :render_options => {:wrapper => 'inline' }
-````
+(Note: In certain newer versions of simple_form, the option to use is `:wrapper => 'bootstrap'`.)
 
-If you want to specify locals that needed to handed down to the partial, write
+```haml
+= link_to_add_association 'add something', f, :something,
+    :render_options => {:wrapper => 'inline' }
+```
 
-````haml
-= link_to_add_association 'add something', f, :something, :render_options => {:locals => {:sherlock => 'Holmes' }}
-````
+To specify locals that needed to handed down to the partial:
 
+```haml
+= link_to_add_association 'add something', f, :something,
+    :render_options => {:locals => {:sherlock => 'Holmes' }}
+```
 
 #### :partial
 
-To overrule the default partial name, e.g. because it shared between multiple views, write
+To override the default partial name, e.g. because it shared between multiple views:
 
-````haml
-= link_to_add_association 'add something', f, :something, :partial => 'shared/something_fields'
-````
+```haml
+= link_to_add_association 'add something', f, :something,
+    :partial => 'shared/something_fields'
+```
 
 #### :wrap_object
 
-If you are using decorators, the normal instantiation of the associated will not be enough, actually you want to generate the decorated object.
+If you are using decorators, the normal instantiation of the associated object will not be enough. You actually want to generate the decorated object.
 
 A simple decorator would look like:
 
-```
+```ruby
 class CommentDecorator
   def initialize(comment)
     @comment = comment
@@ -273,10 +261,11 @@ class CommentDecorator
 end
 ```
 
-To use this, write
+To use this:
 
-```
-link_to_add_association('add something', @form_obj, :comments, :wrap_object => Proc.new {|comment| CommentDecorator.new(comment) })
+```haml
+= link_to_add_association('add something', @form_obj, :comments,
+    :wrap_object => Proc.new {|comment| CommentDecorator.new(comment) })
 ```
 
 Note that the `:wrap_object` expects an object that is _callable_, so any `Proc` will do. So you could as well use it to do some fancy extra initialisation (if needed).
@@ -284,9 +273,9 @@ But note you will have to return the (nested) object you want used.
 E.g.
 
 
-```
-link_to_add_association('add something', @form_obj, :comments, 
-                        :wrap_object => Proc.new { |comment| comment.name = current_user.name; comment })
+```haml
+= link_to_add_association('add something', @form_obj, :comments, 
+    :wrap_object => Proc.new { |comment| comment.name = current_user.name; comment })
 ```
 
 #### :force_non_association_create
@@ -297,10 +286,11 @@ a new nested object. But this has a side-effect: for each call of `link_to_add_a
 In most cases this is not a problem, but if you want to render a `link_to_add_association` for each nested element this will result
 in an infinite loop.
 
-To resolve this, specify that `:force_non_association_create` should be `true`, as follows:
+To resolve this, specify that `:force_non_association_create` should be `true`:
 
-```
-link_to_add_association('add something', @form_obj, :comments, :force_non_association_create => true)
+```haml
+= link_to_add_association('add something', @form_obj, :comments,
+    :force_non_association_create => true)
 ```
 
 By default `:force_non_association_create` is `false`.
@@ -309,7 +299,7 @@ By default `:force_non_association_create` is `false`.
 
 ### link_to_remove_association
 
-This function will add a link to your markup that will, when clicked, dynamically remove the surrounding partial form.
+This function will add a link to your markup that, when clicked, dynamically removes the surrounding partial form.
 This should be placed inside the partial `_<association-object-singular>_fields`.
 
 It takes three parameters:
@@ -330,96 +320,91 @@ On insertion or removal the following events are triggered:
 * `cocoon:before-remove`: called before removing the nested child
 * `cocoon:after-remove`: called after removal
 
-To listen to the events, you to have the following code in your javascript:
+To listen to the events in your JavaScript:
 
-    $('#container').bind('cocoon:before-insert', function(e, inserted_item) {
-        // ... do something
-    });
+```javascript
+  $('#container').bind('cocoon:before-insert', function(e, insertedItem) {
+    // ... do something
+  });
+```
 
-where `e` is the event and the second parameter is the inserted or removed item. This allows you to change markup, or
+...where `e` is the event and the second parameter is the inserted or removed item. This allows you to change markup, or
 add effects/animations (see example below).
 
 
-If in your view you have the following snippet to select an `owner`
-(we use slim for demonstration purposes)
+If in your view you have the following snippet to select an `owner`:
 
-````haml
+```haml
 #owner
   #owner_from_list
     = f.association :owner, :collection => Person.all(:order => 'name'), :prompt => 'Choose an existing owner'
   = link_to_add_association 'add a new person as owner', f, :owner
-````
-
-This view part will either let you select an owner from the list of persons, or show the fields to add a new person as owner.
+```
 
+This will either let you select an owner from the list of persons, or show the fields to add a new person as owner.
 
 The callbacks can be added as follows:
 
-````javascript
+```javascript
 $(document).ready(function() {
-    $('#owner').bind('cocoon:before-insert',
-         function() {
-           $("#owner_from_list").hide();
-           $("#owner a.add_fields").hide();
-         });
-    $('#owner').bind('cocoon:after-insert',
-         function() {
-           /* ... do something ... */
-         });
-    $('#owner').bind("cocoon:before-remove",
-         function() {
-           $("#owner_from_list").show();
-           $("#owner a.add_fields").show();
-         });
-    $('#owner').bind("cocoon:after-remove",
-         function() {
-           /* e.g. recalculate order of child items */
-         });
+    $('#owner')
+      .bind('cocoon:before-insert', function() {
+        $("#owner_from_list").hide();
+        $("#owner a.add_fields").hide();
+      })
+      .bind('cocoon:after-insert', function() {
+        /* ... do something ... */
+      })
+      .bind("cocoon:before-remove", function() {
+        $("#owner_from_list").show();
+        $("#owner a.add_fields").show();
+      })
+      .bind("cocoon:after-remove", function() {
+        /* e.g. recalculate order of child items */
+      });
 
     // example showing manipulating the inserted/removed item
 
-    $('#tasks').bind('cocoon:before-insert', function(e,task_to_be_added) {
+    $('#tasks')
+      .bind('cocoon:before-insert', function(e,task_to_be_added) {
         task_to_be_added.fadeIn('slow');
-    });
-
-    $('#tasks').bind('cocoon:after-insert', function(e, added_task) {
+      })
+      .bind('cocoon:after-insert', function(e, added_task) {
         // e.g. set the background of inserted task
         added_task.css("background","red");
-    });
-
-    $('#tasks').bind('cocoon:before-remove', function(e, task) {
+      })
+      .bind('cocoon:before-remove', function(e, task) {
         // allow some time for the animation to complete
         $(this).data('remove-timeout', 1000);
         task.fadeOut('slow');
-    })
-
-
+      });
 });
-````
-
-Do note that for the callbacks to work there has to be a surrounding container (div), where you can bind the callbacks to.
+```
 
+Note that for the callbacks to work there has to be a surrounding container to which you can bind the callbacks.
 
 When adding animations and effects to make the removal of items more interesting, you will also have to provide a timeout.
 This is accomplished by the following line:
 
-    $(this).data('remove-timeout', 1000);
+```javascript
+$(this).data('remove-timeout', 1000);
+```
 
-Note that you could also immediately add this to your view (on the `.nested-fields` container).
+You could also immediately add this to your view (on the `.nested-fields` container).
 
-### Control the Insertion behaviour
+### Control the Insertion Behaviour
 
-The default insertion location is at the back of the current container. But we have added two `data`-attributes that are read to determine the insertion-node and -method.
+The default insertion location is at the back of the current container. But we have added two `data-` attributes that are read to determine the insertion-node and -method.
 
 For example:
 
-````javascript
+```javascript
 $(document).ready(function() {
     $("#owner a.add_fields").
       data("association-insertion-method", 'before').
       data("association-insertion-node", 'this');
 });
-````
+```
 
 The `association-insertion-node` will determine where to add it. You can choose any selector here, or specify this (default it is the parent-container).
 
@@ -429,27 +414,24 @@ The `association-insertion-traversal` will allow node selection to be relative t
 
 For example:
 
-````javascript
+```javascript
 $(document).ready(function() {
     $("#owner a.add_fields").
       data("association-insertion-method", 'append').
       data("association-insertion-traversal", 'closest').
       data("association-insertion-node", '#parent_table');
 });
-````
+```
 
 ### Partial
 
-If no explicit partial-name is given, `cocoon` looks for a file named `_<association-object_singular>_fields`.
-To override the default partial-name use the option `:partial`.
-
-For the javascript to behave correctly, the partial should start with a container (e.g. `div`) of class `.nested-fields`.
-
+If no explicit partial name is given, `cocoon` looks for a file named `_<association-object_singular>_fields`.
+To override the default partial use the `:partial` option.
 
+For the JavaScript to behave correctly, the partial should start with a container (e.g. `div`) of class `.nested-fields`.
 
 There is no limit to the amount of nesting, though.
 
-
 ## Note on Patches/Pull Requests
  
 * Fork the project.
@@ -463,9 +445,8 @@ There is no limit to the amount of nesting, though.
 
 ## Contributors
 
-The list of contributors just keeps on growing. [Check it out](https://github.com/nathanvda/cocoon/graphs/contributors) !!
-I would really really like to thank all of them,
-they make cocoon more awesome every day. Thanks.
+The list of contributors just keeps on growing. [Check it out!](https://github.com/nathanvda/cocoon/graphs/contributors)
+I would really really like to thank all of them. They make cocoon more awesome every day. Thanks.
 
 ## Todo