README.md in shreddies-0.1.0 vs README.md in shreddies-0.2.0

@@ -18,11 +18,11 @@
 
     $ gem install shreddies
 
 ## Usage
 
-Serializers should be named after your models and located in "`app/serializers`". Any public methods you define will be serialized, and you can quickly expose methods from the serialized subject using the `delegate` class method.
+Serializers should be named after your models and located in "`app/serializers`". Any public methods you define will be serialized, and you can quickly expose methods from the serialized subject using the `delegate` class method, which simply delegates to the subject.
 
 ```ruby
 # app/serializers/user_serializer.rb
 class UserSerializer < Shreddies::Json
   delegate :id, :first_name, :last_name, :email
@@ -63,16 +63,68 @@
 
 ```ruby
 User.all.as_json
 ```
 
+You may find that you don't want or need to return as much data in collections of objects, or may want to include differtent data. So if a serializer defines a `Collection` module, and a collection or array is being rendered, then that Collection module will automatically be included:
+
+```ruby
+ArticleSerializer < Shreddies::Json
+  module Collection
+    def url
+      "https://blah.com/#{subject.slug}"
+    end
+  end
+end
+```
+
+Conversely, you can define a `Single` module, and that will be included when rendering a single object.
+
+```ruby
+ArticleSerializer < Shreddies::Json
+  module Single
+    def body
+      'this body is really, really long, and I do not want it returned in lists.'
+    end
+  end
+end
+```
+
 ### Options
 
 Both `#as_json` and `.render` accepts an `options` hash, which will be forwarded to the serializer class, and available as `options`. This allows you to pass arbitrary options and use them in your serializer.
 
 The following standard options are supported, and provide additional built-in functionality:
 
+#### `serializer`
+
+By default `#as_json` will look for a serializer named after your model. So a `User` model will automatically use the `UserSerializer`. Sometimes you want to use a different serializer class, in which case you can use the `serializer` option:
+
+```ruby
+User.all.as_json serializer: User::AdminSerializer
+```
+
+#### `module`
+
+You can pass one or module names in the `module` option, and these modules will be included into the serializer. This is great for selectively including attributes and methods.
+
+```ruby
+Article.all.as_json module: :WithBody
+```
+
+```ruby
+ArticleSerializer < Shreddies::Json
+  module WithBody
+    def body
+      'This article body is really, really long'
+    end
+  end
+end
+```
+
+The `Collection` and `Single` modules can be defined and they will be automatically included. The Collection module will be included when rendering an array or ActiveRecord collection (`ActiveRecord::Relation`), and the Single module will be included when rendering a single obejct.
+
 #### `index_by`
 
 Give this option a property of your serialized subject as a Symbol, and the returned collection will be a Hash keyed by that property.
 
 ```ruby
@@ -95,9 +147,36 @@
     "lastName": "Other"
   }
 
   ...
 }
+```
+
+### Serializer Inheritance
+
+A serializer can inherit from any other serializer, which is a great way to create custom views:
+
+```ruby
+# app/serializers/user_serializer.rb
+class UserSerializer < Shreddies::Json
+  delegate :id, :first_name, :last_name, :email
+
+  def name
+    "#{first_name} #{last_name}"
+  end
+end
+
+class User::AdministratorSerializer < UserSerializer
+  def type
+    'administrator'
+  end
+end
+```
+
+Then call it like any other serializer:
+
+```ruby
+User::AdministratorSerializer.render(user)
 ```
 
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.