+
+
+`request.method` would return `"DELETE"`.
+
+## Browser based submission of non-form content
+
+Browser-based submission of content types other than form are supported by using form fields named `_content` and `_content_type`:
+
+For example, given the following form:
+
+
+
+`request.content_type` would return `"application/json"`, and `request.content` would return `"{'count': 1}"`
+
+## URL based accept headers
+
+## URL based format suffixes
+
+## Doesn't HTML5 support PUT and DELETE forms?
+
+Nope. It was at one point intended to support `PUT` and `DELETE` forms, but was later [dropped from the spec](3). There remains [ongoing discussion](4) about adding support for `PUT` and `DELETE`, as well as how to support content types other than form-encoded data.
+
+[1]: http://www.amazon.com/Restful-Web-Services-Leonard-Richardson/dp/0596529260
+[2]: http://guides.rubyonrails.org/form_helpers.html#how-do-forms-with-put-or-delete-methods-work
+[3]: http://www.w3.org/TR/html5-diff/#changes-2010-06-24
+[4]: http://amundsen.com/examples/put-delete-forms/
diff --git a/docs/topics/changelog.md b/docs/topics/changelog.md
index a4fd39e2..15fb6301 100644
--- a/docs/topics/changelog.md
+++ b/docs/topics/changelog.md
@@ -1,8 +1,11 @@
-# Release Notes
+# Change Log
## 2.0.0
-**TODO:** Explain REST framework 2.0
+* **Fix all of the things.**
+* For more information please see the [2.0 migration guide][migration].
+
+---
## 0.4.0
@@ -105,3 +108,4 @@
* Initial release.
+[migration]: migration.md
\ No newline at end of file
diff --git a/docs/topics/formoverloading.md b/docs/topics/formoverloading.md
deleted file mode 100644
index 96cb1388..00000000
--- a/docs/topics/formoverloading.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# Browser hacks
-
-> "There are two noncontroversial uses for overloaded POST. The first is to *simulate* HTTP's uniform interface for clients like web browsers that don't support PUT or DELETE"
->
-> — [RESTful Web Services](1), Leonard Richardson & Sam Ruby.
-
-## Browser based PUT, DELETE, etc...
-
-**TODO: Preamble.** Note that this is the same strategy as is used in [Ruby on Rails](2).
-
-For example, given the following form:
-
-
-
-`request.method` would return `"DELETE"`.
-
-## Browser based submission of non-form content
-
-Browser-based submission of content types other than form are supported by using form fields named `_content` and `_content_type`:
-
-For example, given the following form:
-
-
-
-`request.content_type` would return `"application/json"`, and `request.content` would return `"{'count': 1}"`
-
-## URL based accept headers
-
-## URL based format suffixes
-
-## Doesn't HTML5 support PUT and DELETE forms?
-
-Nope. It was at one point intended to support `PUT` and `DELETE` forms, but was later [dropped from the spec](3). There remains [ongoing discussion](4) about adding support for `PUT` and `DELETE`, as well as how to support content types other than form-encoded data.
-
-[1]: http://www.amazon.com/Restful-Web-Services-Leonard-Richardson/dp/0596529260
-[2]: http://guides.rubyonrails.org/form_helpers.html#how-do-forms-with-put-or-delete-methods-work
-[3]: http://www.w3.org/TR/html5-diff/#changes-2010-06-24
-[4]: http://amundsen.com/examples/put-delete-forms/
diff --git a/docs/topics/migration.md b/docs/topics/migration.md
new file mode 100644
index 00000000..f6a301b8
--- /dev/null
+++ b/docs/topics/migration.md
@@ -0,0 +1,85 @@
+# 2.0 Migration Guide
+
+REST framework 2.0 introduces a radical redesign of the core components, and a large number of backwards breaking changes.
+
+### Serialization redesign.
+
+REST framework's serialization and deserialization previously used a slightly odd combination of serializers for output, and Django Forms and Model Forms for input. The serialization core has been completely redesigned based on work that was originally intended for Django core.
+
+2.0's form-like serializers comprehensively address those issues, and are a much more flexible and clean solution to the problems around accepting both form-based and non-form based inputs.
+
+### Generic views improved.
+
+When REST framework 0.1 was released the current Django version was 1.2. REST framework included a backport of the Django 1.3's upcoming `View` class, but it didn't take full advantage of the generic view implementations.
+
+As of 2.0 the generic views in REST framework tie in much more cleanly and obviously with Django's existing codebase, and the mixin architecture is radically simplified.
+
+### Cleaner request-response cycle.
+
+REST framework 2.0's request-response cycle is now much less complex.
+
+* Responses inherit from `SimpleTemplateResponse`, allowing rendering to be delegated to the response, not handled by the view.
+* Requests extend the regular `HttpRequest`, allowing authentication and parsing to be delegated to the request, not handled by the view.
+
+### Renamed attribnutes & classes.
+
+Various attributes and classes have been renamed in order to fit in better with Django's conventions.
+
+## Example: Blog Posts API
+
+Let's take a look at an example from the REST framework 0.4 documentation...
+
+ from djangorestframework.resources import ModelResource
+ from djangorestframework.reverse import reverse
+ from blogpost.models import BlogPost, Comment
+
+
+ class BlogPostResource(ModelResource):
+ """
+ A Blog Post has a *title* and *content*, and can be associated
+ with zero or more comments.
+ """
+ model = BlogPost
+ fields = ('created', 'title', 'slug', 'content', 'url', 'comments')
+ ordering = ('-created',)
+
+ def url(self, instance):
+ return reverse('blog-post',
+ kwargs={'key': instance.key},
+ request=self.request)
+
+ def comments(self, instance):
+ return reverse('comments',
+ kwargs={'blogpost': instance.key},
+ request=self.request)
+
+
+ class CommentResource(ModelResource):
+ """
+ A Comment is associated with a given Blog Post and has a
+ *username* and *comment*, and optionally a *rating*.
+ """
+ model = Comment
+ fields = ('username', 'comment', 'created', 'rating', 'url', 'blogpost')
+ ordering = ('-created',)
+
+ def blogpost(self, instance):
+ return reverse('blog-post',
+ kwargs={'key': instance.blogpost.key},
+ request=self.request)
+
+There's a bit of a mix of concerns going on there. We've got some information about how the data should be serialized, such as the `fields` attribute, and some information about how it should be retrieved from the database - the `ordering` attribute.
+
+Let's start to re-write this for REST framework 2.0.
+
+ from rest_framework import serializers
+
+ class BlogPostSerializer(serializers.HyperlinkedModelSerializer):
+ model = BlogPost
+ fields = ('created', 'title', 'slug', 'content', 'url', 'comments')
+
+ class CommentSerializer(serializers.HyperlinkedModelSerializer):
+ model = Comment
+ fields = ('username', 'comment', 'created', 'rating', 'url', 'blogpost')
+
+
diff --git a/docs/topics/rest-hypermedia-hateoas.md b/docs/topics/rest-hypermedia-hateoas.md
index 46a4c9d7..3aa1ff5f 100644
--- a/docs/topics/rest-hypermedia-hateoas.md
+++ b/docs/topics/rest-hypermedia-hateoas.md
@@ -20,7 +20,7 @@ the Design of Network-based Software Architectures][dissertation].
For a more thorough background, check out Klabnik's [Hypermedia API reading list][readinglist].
-# Building Hypermedia APIs with REST framework
+## Building Hypermedia APIs with REST framework
REST framework is an agnositic Web API toolkit. It does help guide you towards building well-connected APIs, and makes it easy to design appropriate media types, but it does not strictly enforce any particular design style.
--
cgit v1.2.3