Add seeds
STEP 0: Clean up scaffold-generated junk

Why we say don't use it :)
STEP 1: Add a DOM element to do JS replacement on

We're adding an "anchor" for our Javascript.
STEP 2: Update ERB to use remote: true

Per

http://guides.rubyonrails.org/working_with_javascript_in_rails.html#server-side-concerns

there are a number of helpers that take `remote:
true` as an option. `link_to` is one of them.
Thanks to rails-ujs, this will be fired
asynchronously where javascript is supported.
Where not, it will simply do a get to that
resource.
STEP 3: Respond to an async request on the server

Our modified `link_to` (see previous commit) has
will ask `authors#show` for data.  Without a
`respond_to` block, those data will always be
HTML, we want executable javascript.

We modify this route to say "yes, I will accept a
javascript query."  Through the magic of naming
conventions, a javascript request to this resource
will default to the name `show.js.erb`.
STEP 4: Respond to authors#show with js

Here you have it.  We respond to a javascript
request by looking for the `#zoom-in` element.  We
then change its HTML to be the JavaScript
rendering of an ERB tag that renders HTML.
We have to use `escape_javascript` to make sure
that the ERB-interpolated HTML is transformed to
JS.

This is where this method to Ajax rendering in
Rails feels really _wrong_ to me.  I'll try to
clean it up subsequently, but it feels like we
could just render the parial's content locally.
I'll explore this idea after we get it working.
STEP 5: Final Step

Return an author's name (as HTML).

The advantage, theoretically, of using this
partial is that it could be

1.  shared among other views (DRY)
2.  **AND** not only is it DRY among HTML
templates, it's also going to work with any JS
clients (so the resource's data stay dry between
HTML representations and JS representations)

I see the idea here, but it just feels wrong and
really overcomplicated (to me).
OPTION: Don't use an ERB partial

If you don't think you're going to want data
sharing (hard to say at this point), consider
in-lining the knowledge held in the partial.