Do a little bit of re-organization.

The read-write split is too complex with the id vs url style as well, so
it's in one doc now.  It's sorta good that it's one page because
everything is right there, but it is a little long. It might be better
to change this at some point, but let's keep it to one page per thing
for now.

I also changed the front page to explain what's up in a little bit more
detail.

_includes/header.html

@@ -4,8 +4,7 @@
     <nav>
       <ul>
         <li><a href="/">Overview</a></li>
-        <li><a href="/reading">Reading</a></li>
-        <li><a href="/updating">Updating</a></li>
+        <li><a href="/format">Format</a></li>
         <li><a href="/extending">Extending</a></li>
         <li><a href="/examples">Examples</a></li>
         <li><a href="/faq">FAQ</a></li>

examples/index.md

@@ -7,10 +7,12 @@ Examples are excellent learning aids. The following projects implementing JSON
 API are divided into server- and client-side. The server-side is further
 divided by implementation language. If you'd like your project listed, [send a
 Pull Request](https://github.com/json-api/json-api).
+implementations, but they both are slightly out of date at the moment.
 
 ## Client
 
-* [Ember](http://emberjs.com/) Data
+[ember-data](https://github.com/emberjs/data) is one of the original examplar
+implementations, but is slightly out of date at the moment.
 
 ## Server
 
@@ -20,4 +22,10 @@ Pull Request](https://github.com/json-api/json-api).
 
 ### Ruby
 
-* [ActiveModel::Serializer](https://github.com/rails-api/active_model_serializers)
+[ActiveModel::Serializers](https://github.com/rails-api/active_model_serializers)
+is one of the original examplar implementations, but is slightly out of date at
+the moment.
+
+[The rabl wiki](https://github.com/nesquena/rabl/wiki/Conforming-to-jsonapi.org-format)
+has page describing how to emit conformant JSON.
+