Update NEWS and remove user-defined routing item from docs.

NEWS.md

 ## Changes for 0.9.4 (2013-05-05):
 
+* **SITE-BREAKING CHANGE**: Coleslaw now supports user-defined routing.
+  Instead of hard-coding the paths various content types are stored at,
+  they must be specified in the configuration file (.coleslawrc). Just
+  copy the `:routing` key from the [example][single_site.rc] to get
+  the old behavior.
 * Coleslaw no longer expects a particular repo layout. Use whatever
   directory hierarchy you like.
 
 
 * Initial release.
 
-[hacking_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/hacking.md
-[theming_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/themes.md
+[hacking_guide]:  https://github.com/redline6561/coleslaw/blob/master/docs/hacking.md
+[theming_guide]:  https://github.com/redline6561/coleslaw/blob/master/docs/themes.md
+[single_site.rc]: https://github.com/redline6561/coleslaw/blob/master/examples/single-site.coleslawrc

docs/hacking.md

 function. There may be other areas where it was assumed tags/dates
 will always be present.
 
-### User-Defined Routing
-
-There is no reason *coleslaw* should be in charge of the site layout or
-should care. If all objects only used the *slug* slot in their `page-url`
-methods, there could be a :routing argument in the config containing
-a plist of `(:class "~{format string~}")` pairs. A default method could
-check the :class key under `(routing *config*)` if no specialized
-`page-url` was defined. This would have the additional benefit of
-localizing all the site routing in one place. New Content Types would
-probably `pushnew` a plist onto the config key in their `enable` function.
-This has been implemented on the branch `user-defined-routing`.
-
 ### New Content Type: Pages!
 
 Many users have requested a content type PAGE, for static pages. It